TK.

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.

Hi Bartosz, the entire history is in github, which means that in your downloaded repository you could switch back to the sources which were used for v1.036 The appr. commit was 6edfcd51ad6cb78f83d6094c5c9d1b7c5b85ddb3 So, just enter "git checkout 6edfcd51ad6cb78f83d6094c5c9d1b7c5b85ddb3" to switch back. There are also ways to compare the "good version" with the latest one, e.g.: https://github.com/midibox/mios32/compare/6edfcd51ad6cb78f83d6094c5c9d1b7c5b85ddb3..master Or you could clone the repository two times, switch one to the good version, and then use a diff tool such as "beyond compare" to analyze the changes: Best Regards, Thorsten.

Hi, you could send values from the Tick() hook - by using a static variable you can ensure that the values will only be sent once after startup. Something like this (untested code) ///////////////////////////////////////////////////////////////////////////// // This function is called by MIOS in the mainloop when nothing else is to do ///////////////////////////////////////////////////////////////////////////// void Tick(void) __wparam { static unsigned char ain_sent = 0; if( ain_sent == 0 ) { unsigned char pin; unsigned char num_ain = MIOS_AIN_NumberGet(); ain_sent = 1; // only sent once after startup for(pin=0; pin < num_ain; ++pin) { MIOS_MIDI_TxBufferPut(0xb0); // CC at channel 1 MIOS_MIDI_TxBufferPut(pin); // pin number corresponds to CC number MIOS_MIDI_TxBufferPut(MIOS_AIN_Pin7bitGet(pin)); } } } Best Regards, Thorsten.

Hi Stahl, thanks for the confirmation, the comment is corrected now in the source code Best Regards, Thorsten.

Discussions about Wavetables now here:

Great! New v2.046 version now officially released :) Best Regards, Thorsten.