TK.

Hi, at which resolution are you using the analog inputs? (just copy&paste the configuration part of your .NGC file into this thread) Best Regards, Thorsten.

Great! :smile: So - the final V4.088 is now available for download. Changes: MIDIboxSEQ V4.088 ~~~~~~~~~~~~~~~~~ o improved glide function for polyphonic steps o BLM16x16+X support for Mute and Solo The new functions are available at Extra Row Button #3 and #4 (if a BLM16x8+X is connected, they replace Start/Stop at Extra Row Button #1 and #2) If Mute active: the extra column buttons mute/unmute tracks If Solo active: the extra column buttons solo/unsolo tracks LED Colour coding: - LED off: Track neither muted nor soloed - LED green: Track muted - LED yellow: Track soloed - LED red: Track muted and soloed - solo has higher priority, therefore track will be played Special Key combinations: - ALT+Mute clears all mutes - ALT+Solo clears all solos o added Robotizer Fx from Borfo o added LCD Screensaver. It will be active after 30 minutes by default. The time can be changed in the UTIL->OPT menu page. o added DETENTED4/DETENTED5 option for rotary encoders in MBSEQ_HW.V4 file o added new parameter layers "Nth1" and "Nth2" which trigger a special action on each nth bar (Nth1) starting at the 1st bar, or after nth bars (Nth2). Following trigger conditions are available: - Pl (Play each nth bar) - Mu (Mute each nth bar) - Ac (Accent each nth bar) - Ro (Roll each nth bar) - Fx (enable Fx each nth bar) - Nx (don't enable Fx each nth bar) o combined Record and Live page to a new single "Jam" page with sub pages to improve the overview and simplify the configuration. o added Live Pattern Recording to Jam page which can be used to play and record customizable arpeggiator sequences. Available in the Jam page (Utility->Jam->Ptn) See updated user manual for further information. The new features are described (in a bit more detail) in the user manual: http://www.ucapps.de/midibox_seq_manual_m.html Best Regards, Thorsten.

Yes. The example shows: EVENT_BUTTON id=2000 type=Meta meta=SetBank button_mode=OnOnly range=1:1 With: EVENT_BUTTON id=2000 type=Meta meta=SetBank button_mode=OnOff range=0:1 the button would set the second bank when press, and the first bank when depressed Or with: EVENT_BUTTON id=2000 type=Meta meta=SetBank button_mode=Toggle range=0:1 the button would toggle between the first and second bank Best Regards, Thorsten.

The question was related to MIDIbox NG. Here a configuration example for 4 banks: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fencbanks.ngc It shows how to send different CCs, but you could change the configuration to select different channels instead. E.g. instead of: # Bank 2 EVENT_ENC id= 17 hw_id = 1 bank=2 fwd_id=LED_MATRIX:1 fwd_to_lcd=1 type=CC chn= 1 cc= 32 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:1:2)%B" EVENT_ENC id= 18 hw_id = 2 bank=2 fwd_id=LED_MATRIX:2 fwd_to_lcd=1 type=CC chn= 1 cc= 33 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:2:2)%B" EVENT_ENC id= 19 hw_id = 3 bank=2 fwd_id=LED_MATRIX:3 fwd_to_lcd=1 type=CC chn= 1 cc= 34 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:3:2)%B" write: # Bank 2 EVENT_ENC id= 17 hw_id = 1 bank=2 fwd_id=LED_MATRIX:1 fwd_to_lcd=1 type=CC chn= 2 cc= 16 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:1:2)%B" EVENT_ENC id= 18 hw_id = 2 bank=2 fwd_id=LED_MATRIX:2 fwd_to_lcd=1 type=CC chn= 2 cc= 17 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:2:2)%B" EVENT_ENC id= 19 hw_id = 3 bank=2 fwd_id=LED_MATRIX:3 fwd_to_lcd=1 type=CC chn= 2 cc= 18 range= 0:127 offset= 0 ports=1000100000001000 lcd_pos=1:1:1 label="ENC #%3i %3d@(1:3:2)%B" ... Best Regards, Thorsten.

Another special condition that I haven't considered... ;-) Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre23.zip Best Regards, Thorsten.

Ok :phone: Best Regards, Thorsten.

This is related to the typical confusion about the pin order. The first DOUT pin (offset 0) is D7, the next (offset 1) is D6, etc.. Documentation is much better in newer projects (e.g. in MIOS32 based projects I used "D7..D0" instead of offset "0..7") Best Regards, Thorsten.

I won't have enough time to look into this and give you instructions how to proceed. What I'm normally doing: reading the datasheet first to understand the differences (!!!) Setting the environment variables, try compile, solve compile errors until an image can be built by taking an existing derivative as an example (the Posix "find" and "grep" commands are your friends ;-) Then start to upload & debug the image - this can take some time, especially if you never did this before. Even I would need several days to do the adaptions & troubleshooting - hope that you understand that therefore a "quick look" won't help. Just continue and come up with more specific questions once you encountered general issues for which you don't find a solution after 2..3 hours Best Regards, Thorsten.

The MIDI router works independent from the remote access and "Play Live forwarding" method, and no filtering takes place here. I'm not sure if this is really desired. If you use a keyboard for recording, you should configure a bus in Rec mode, and activate forwarding in the Jam page. Hanging notes can happen if you change the router configuration while notes are played - there is no protection measure against this. Best Regards, Thorsten.

yes, in any case all pull-ups should be added regardless if a feature is currently used by the firmware or not. Best Regards, Thorsten.

Good that you even tested this part now! ;-) C-6 is the remote key (configured in MBSEQ_HW.V4) which should neither be recorded, nor forwarded under all circumstances This wasn't considered under all conditions after the last changes anymore. So, please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre22.zip All bus configurations have to be checked again for recording, transposer/arpeggiator and forwarding. Best Regards, Thorsten.

31250 baud = 32 uS per bit. So, the observed jitter is matching with the baudrate quantisation; it doesn't surprise me that it happens. The same quantisation takes place at the receiver side again, which means that the worst case jitter is around 64 uS + system based latency & jitter of the receiving MIDI device (which might be several mS) Best Regards, Thorsten.

Alright, I will document this at the http://www.ucapps.de/midibox_seq_manual_ki.html page (which is currently empty ;-) Sooner or later I will revise the code based on the features which have been integrated in the last months. Currently there is a lot of cumbersome "experimental" code which I added quick&dirty for evaluation purposes. Once I'm sure that the feature set is settled, it makes sense to think about a proper solution. :) This wasn't intended - should work with pre21 This option hasn't been considered, it should be fixed as well Please try: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre21.zip Best Regards, Thorsten.

Hi, the code can be found here: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2Fcommon%2Fmios32_enc.c Best Regards, Thorsten.

Some devices have problems with the program change, I can't help here :-/ Best Regards, Thorsten.

-> Best Regards, Thorsten.

Thanks for the valuable feedback! :smile: Here a new version: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre20.zip I did following changes: 1) previously the record button switched between Edit/Jam page depending on recording enable Now it always switches to the Jam page independent from record enable 2) previously the position for step recording was independent from the position selected in the EDIT page Now this position is the same to avoid inconsistencies 3) EDIT page: previously special modes (like STEP RECORDING) where displayed at the place where normally the instrument is located Now the instrument/special mode display alternates (slowly) 4) fixed „hanging notes“ issue in EDIT RECORDING function To answer your questions & requests: should be fixed with 2) Please check if this causes new (unintended) side effects Would be inconsistent... But: once you controlled the step position with Knob 11, you can use the datawheel to change the value as well. With change 2) it should have direct influence on the edit position so that there is hopefully less confusion about the cursor... Actually EDIT recording is the same like STEP recording with the difference, that it would also be STEP recording if no recording, or live recording is enabled. changed now fixed with 1) changed with 3) hopefully fixed with 4) From Stuartm (confirmed by Jjonas): We've a general issue here with the way how MBSEQ handles the quantisation. If the quantisation threshold is reached, MBSEQ puts the note into the next step, and then mutes the entire step so that it won't be played twice. For drum tracks I would have to differentiate between the recorded layers, and existing layers - this requires an extension. The same mechanism also causes a problem if a long note is recorded as mentioned by Jjonas. Since the quantisation can't look into the future, it doesn't know if the note will be played for more than one step, and therefore just stops it to avoid hanging notes. I've to spend some thoughts about how to solve both problems, but it will take some time and since the changes are criticial (-> error prone) they won't be part of the upcoming release. Best Regards, Thorsten.

Live Patterns are now stored/restored in the local (session specific) MBSEQ_C.V4 file with following format: LivePattern 1 o............... LivePattern 2 o.......o....... LivePattern 3 ....o.......o... LivePattern 4 o...o...o...o... LivePattern 5 *...o...*...o... LivePattern 6 ..o...o...o...o. LivePattern 7 ..*...o...*...o. LivePattern 8 o.o.o.o.o.o.o.o. LivePattern 9 *.o.o.o.*.o.o.o. LivePattern 10 .o.o.o.o.o.o.o.o LivePattern 11 .*.o.*.o.*.o.*.o LivePattern 12 oooooooooooooooo LivePattern 13 *ooooooooooooooo LivePattern 14 *ooooooo*ooooooo LivePattern 15 *ooo*ooo*ooo*ooo LivePattern 16 ooooo*ooooooo*oo And the "recording" page has been renamed to Jam. Please help to test this release candidate (no additional features planned for this version): http://www.ucapps.de/mios32/midibox_seq_v4_088_pre19.zip Best Regards, Thorsten.

Hi, no, this isn't supported yet. In general pulses are not supported - only setting/resetting an output pin, but not triggering it for a certain time Best Regards, Thorsten.

Danke fuer den Hinweis, der Fehler ist gefixt. Ich habe auch mal (auf die schnelle) das MacOS Build Script angepasst, so dass sich die Applikation kompilieren laesst. Leider crasht es schon sehr frueh - evtl. wegen eines Kompatibilitaetproblems mit PYMIDI - es wird aufwendig das zu debuggen, deshalb lass ich es erstmal wieder sein. Die Emulation ist mit der Maus sowieso sehr umstaendlich zu bedienen. Es gibt zwar noch eine iPad Variante, doch hier ist das Display zu klein und das MIDI Timing ist sehr unstabil - deshalb habe ich das nie veroeffentlicht. Die Juce-Anpassung ist nicht trivial - lassen wir das Thema ;-) Gruss, Thorsten.

It was counted from the start, and then repeated each Nth bar. I see the benefit, and the most simple way to satisfy both is just to separate between Nth1 and Nth2 behaviour. Try this version: http://www.ucapps.de/mios32/midibox_seq_v4_088_pre18.zip o added new parameter layers "Nth1" and "Nth2" which trigger a special action on each nth bar (Nth1) starting at the 1st bar, or after nth bars (Nth2). Best Regards, Thorsten.

One of those quick changes that you shouldn't release w/o testing ;-) It's fixed in pre17 (link changed in the posting above); thanks for the quick feedback! :) Best Regards, Thorsten.

Hi, there was never a "soldering guide", just only these pages: http://www.ucapps.de/midibox_seq_v3.html http://www.ucapps.de/midibox_seq_v3_options.html Best Regards, Thorsten.

It's technically possible, but will require some complicated software extensions. Actually I hope that ST will provide it together with the USB driver library, but it seems that it's even too complicated for those guys ;-) Best Regards, Thorsten.

Ja, auf dem Subversion Server liegt eine Version fuer MacOS, die ich jedoch schon lange nicht mehr gepflegt habe. Ich muesste das Projekt auf die neusten Xcode Version portieren, und ein paar .c files, die mittlerweile hinzugekommen sind, einbinden. Arbeitest Du unter MacOS? (es gibt weder eine Anpassung an Windows, noch an Linux...! Das muesste man grundsaetzlich anders angehen, bspw. basierend auf Juce) Gruss, Thorsten.