TK.

Cool! :) Btw.: meanwhile "gputils" is part of Homebrew: https://brew.sh For those who know this package manager: just enter "brew install gputils" Best Regards, Thorsten.

Upgrade is in progress, could you please check if problems are solved? If not I can request support from Invision Best Regards, Thorsten.

Hi Michael, I think that you are asking for the "Follow" function - it's really well hidden (some years ago this was an obvious function for me, meanwhile even I have to search in the user manual having only the name in mind...) Press MENU+EXIT to enable/disable follow mode Best Regards, Thorsten.

main.asm indicates that these are the 1.9h sources: https://github.com/midibox/mios8/blob/master/mios/main.asm Best Regards, Thorsten.

Hi, I checked options, and come to the conclusion that the only way to get rid of this issue is to update the forum software. Unfortunately this won't come for free, a new license would cost US $105... :-/ Not sure if we could get the money via donations, there are not so many active forum members anymore like some years ago Best Regards, Thorsten.

Hi Smithy, I was able to edit your post with my account, see bottom of first posting: http://midibox.org/forums/topic/20619-build-guide-midibox-quad-genesis/ However, I noticed that the "Default" theme was selected in your account preferences, while others (like me) have an automatic selection. I changed this for your account, does it work now? Best Regards, Thorsten.

You're welcome! :) Access should work now. You got an email with login credentials - please change your password Best Regards, Thorsten.

Hi Kazik, 1) FAST button control with Bookmarks: this can only work if you disable the "ENC_AUTO_FAST" feature in your MBSEQ_HW.V4 file, which overrules interactive FAST button changes Background: with ENC_AUTO_FAST, FAST mode will be auto-selected depending on the selected parameter layer, and can be temporary (!) overruled by pressing the FAST button. Without this feature, FAST button has full control over the encoder behaviour 2) HUMANIZER changing CC values: works at my side, would need more input to give you guidance, please use the appr. thread to discuss at the right place Best Regards, Thorsten.

Best Regards, Thorsten.

Thanks for the feedback! It was a nice challenge to nail down this issue, because it only appears in conjunction with the TPD, which explains why many other MBSEQ users didn't notice this so far! :) Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_098_pre3.zip Best Regards, Thorsten. P.S.: background -> https://github.com/midibox/mios32/commit/66fa4df5960d51c93ee90c065062c5ba28fdde69

How could I reproduce this issue? Could you please give step-by-step instructions? Best Regards, Thorsten.

It might be possible to hack this into the firmware, do you have a compiler setup ready? Best Regards, Thorsten.

Does it work at your side? I noticed that the change wasn't working with the "selection row" of the MIDIphy front panel, now fixed here: -> http://www.ucapps.de/mios32/midibox_seq_v4_098_pre2.zip Best Regards, Thorsten.

Interesting timing of this posting: recently I noticed a very similar problem and hacked a quick change into the firmware to move forward. Let's make it official :-) -> http://www.ucapps.de/mios32/midibox_seq_v4_098_pre1.zip From the ChangeLog: MIDIboxSEQ V4.098 ~~~~~~~~~~~~~~~~~ o Phrase Mode: if Option 3/33 "Pattern Change Synchronization" is activated, patterns will start from step 1 after song position change. This is especially useful if phrases contain tracks with different lengths. Option 5/33 "Restart all Tracks on Pattern Change" should be disabled in this case because it won't lead to the intended results. Best Regards, Thorsten. P.S.: I removed your first posting because it seems to be a duplicate

Hi Christian, I agree that your keyboard doesn't handle Note-Off messages correctly. According to the MIDI Spec (-> https://web.archive.org/web/20071005165318fw_/http://www.borg.com/~jglatt/tech/midispec/noteoff.htm ) the default velocity should be 64 if not supported, but it sends 0 instead. Your other keyboard sends 127, which is actually also wrong if it doesn't support this feature - but somehow works better. Actually it's recommended that keyboards send Note On with velocity 0 to turn off the note, because this keeps the runtime status, ensures that no extra byte has to be sent out and therefore saves some time (ca. 320 uS) Behringer Neutron: either sets a very long release time (e.g. for VCA envelope) with Note Off Velocity 0, or it doesn't handle Note Off correctly -- 0 is a valid value and if there is no special processing for this velocity value, it should be handled like any other. This would add +1 mS latency, which is acceptable. Best Regards, Thorsten.