TK.

Probably I found the problem, please try this version: -> http://www.ucapps.de/mios32/midibox_seq_v4_095_pre10.zip Whenever the "step edit" feature was used in EDIT page, the played notes remained in the queue and then overwrote notes during live recording. Now they should be properly erased. If the issue happens again, open MIOS Studio and enter "dbg_record" in the MIOS Terminal. This should give you a list of played notes - and maybe help to understand the problem (and to give me more information :) However, probably you won't need this debug option anymore if the bugfix is working as intended. Best Regards, Thorsten.

Great that this helped at your side! :) But for the records: currently I'm not able to reproduce this issue. The test procedure: turn on MIDIbox with unconfigured AOUT module in CV page selected AOUT_NG module exit CV page (so that this setting will be stored) power-cycle MBSEQ -> AOUT_NG properly configured and working can be repeated with multiple power-cycles: AOUT_NG properly configured and working Best Regards, Thorsten.

Yes, such a hack would be possible in core/seq_cv.c, function SEQ_CV_SendPackage If more people are interested, I could provide a general function. Best Regards, Thorsten.

Unfortunately c-2 (note value #0) is consequently used at many places to disable the note (no MIDI event will be sent) The only workaround I could imagine is a private firmware modification which transforms a particular note to c-2 Best Regards, Thorsten.

Ok, added to the wish list. I guess that this could be useful for common tracks as well. Should be fixed now: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre9.zip A frequently requested feature, meanwhile even mentioned in one of Oozitron's tutorial videos :) Best Regards, Thorsten.

Interesting, I wasn't aware of this! This issue is now fixed here: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre8.zip And I also added a reset function to this page :) Best Regards, Thorsten.

Thanks for the information! This was caused by an unintended stack overflow It should be fixed in following version: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre7.zip Best Regards, Thorsten.

Thanks for the inspiration - I will try this soon! :) Best Regards, Thorsten.

I'm still unsure, if for me as a right-handed person it would be better to have the wheel section at the left side. There are situations where I want to quickly switch between selection groups (such as between track and parameter layer selection) while changing steps with the right hand. In this case, it's actually better if I could switch with the left hand. Best Regards, Thorsten.

No spam! I always enjoy your music :) Best Regards, Thorsten.

Thanks! Best Regards, Thorsten.

You can find the API to access the LEDs directly under: http://midibox.org/mios32/manual/group___b_l_m___s_c_a_l_a_r.html Best Regards, Thorsten.

Hi Christiano, very nice first posting with so many detailed information! Welcome on board! :) Actually providing a proper solution for keyboard transpose (and velocity map) changes was still on my TODO list. It's implemented now, please try this version: http://www.ucapps.de/mios32/midibox_ng_v1_036_pre4.zip A configuration example (for a single keyboard) can be found under: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_6.ngc http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fkb_6.ngr As you can see, I preferred to use .NGR commands instead of meta events, because we want to change parameters of an event (KB:1) instead of a physical device (KB) I tested this with a Fatar keyboard (donated by FantomXR! :)) - works fine! I can even change the transpose value with the SCS encoder while playing some keys, the corresponding note-off events are matching so that we won't get hanging notes. We've many solutions for this case 1) the most simple: I could increase the number of supported keyboards from 2 to 4, because I think that especially for organs the slightly increased latency (a couple of uS, not more!) doesn't really matter. This would mean that you could control all keyboards from a single core 2) for reacting on a single CC number multiple times, just define EVENT_* with different IDs Best Regards, Thorsten.

Alright, parameter layer assignments are copied now: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre6.zip Can now be done with this update. press&hold EDIT button, and select the "Par View" (which is the 303 view for common tracks) - this will keep the parameter layer view. Btw.: Trg and Layer view are now supported for drum tracks as well The port assignment wasn't recovered correctly, should work now. Best Regards, Thorsten.

Ok, the CC values are now configurable in the options page (item 20/26) http://www.ucapps.de/mios32/midibox_seq_v4_095_pre4.zip Pitch/Program Change/Aftertouch are now sending as well, but note that these are channel events and not key specific events. Which means, that only the first drum instrument can change the values, the remaining instruments won't send such MIDI events. Best Regards, Thorsten.

Alright, so please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre3.zip This turns your MIDIbox into a MIDIbox SEQ V4+ :) For the V4+ variant CCs can be assigned to drum track layers. The CC number is statically assigned: the first assigned layer will send CC#16..C#32, the second assigned layer CC#33..C#48, etc. depending on the drum instrument. I tried this with the MIDI automation of StylusRMX, and it works there. Best Regards, Thorsten.

@k2z3k0 and @u-link: are you already using the STM32F4 core? In this case I might be able to provide configurable drum CCs as an option for MBSEQV4+ @k2z3k0: I'm surprised that the screen isn't updated immediately in your case, I've to check this! @u-link: drum track transpose: good idea! I will check this And thanks for starting a cheat sheet! :) @slo: there is a third pointer which is the "song position", currently not displayed in the menu page, but only in the song page. I've to check & document, how this works together with synchronized mutes/unmutes. Best Regards, Thorsten.

The required source code change isn't so difficult, but I can't provide this as a generic solution to everybody since it generates some overhead at my side (people ask for documentation, more comfortable configuration, special options, etc). So, for your particular case, the SEQ_MIDI_ROUTER_Receive function has to be enhanced: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_seq_v4%2Fcore%2Fseq_midi_router.c By something like: if( port == UART0 && midi_package.event == NoteOn && midi_package.velocity > 0 ) { int offset = 14; if( midi_package.velocity <= offset ) midi_package.velocity = offset+1; midi_package.velocity = (127*(midi_package.velocity-offset)) / (127-offset); } This would apply the linear curve to all notes received via MIDI1 (UART0) Best Regards, Thorsten.

Happy new year! :) I just tried the random generator, (still) works fine at my side - need more input. Concerning CC layer in drums: technical problem is, that there is no place to configure the CC number: - the memory area which is usually used to configure the CC number is allocated by the Note number of the drum instrument - but even if I would introduce dedicated memory locations for the CC number, I've no idea where to place the configuration item - the EVENT page is completely allocated. :-/ The only possibility that I see is to provide pre-configured CC numbers for drums (such as CC#1 - Modulation Wheel) - but I'm sure that people will ask for more flexibility sooner and later for good reasons, so that the actual problem won't be solved. Best Regards, Thorsten.

Congratulation, really good work! :) I would like to give some feedback on the MCU usage: I don't think that it's really required, the STM32F4 core has more than enough bandwidth to handle this as a "background task". According to your documentation you decided to use a separate MCU for this task due to limitations in MBNG. But this limitation only exists since I preferred less latency and universal usage (SRIO can be used for multiple purposes, not only for controlling RGB LEDs). If these design constraints wouldn't exist, we could simply control the SRIO on a similar way like you did in the MCU code. MIOS32 provides a MIOS32_DONT_SERVICE_SRIO_SCAN switch which can be defined in mios32_config.h to disable the common SRIO scan approach. With this switch you are able to initiate the scan in your app MBNG works this way meanwhile, but a more simple example can be found in the Keyboard tutorial: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F029_keyboard_velocity%2F The first transfer is initiated with MIOS32_Init(): // limit the number of DIN/DOUT SRs which will be scanned for faster scan rate MIOS32_SRIO_ScanNumSet(2); // speed up SPI transfer rate (was MIOS32_SPI_PRESCALER_128, initialized by MIOS32_SRIO_Init()) MIOS32_SPI_TransferModeInit(MIOS32_SRIO_SPI, MIOS32_SPI_MODE_CLK1_PHASE1, MIOS32_SPI_PRESCALER_64); // prescaler 64 results into a transfer rate of 0.64 uS per bit // when 2 SRs are transfered, we are able to scan the whole 16x8 matrix in 300 uS // standard SRIO scan has been disabled in programming_models/traditional/main.c via MIOS32_DONT_SERVICE_SRIO_SCAN in mios32_config.h // start the scan here - and retrigger it whenever it's finished APP_SRIO_ServicePrepare(); MIOS32_SRIO_ScanStart(APP_SRIO_ServiceFinish); See APP_SRIO_ServicePrepare() and APP_SRIO_ServiceFinish() how to prepare and process a scan. Since the STM32F4 is pretty fast, there is no need to use a timer in your case. Just start the next scan once the last has been finished and buttons have been checked like shown in the tutorial. This results into back-to-back scan, where the update speed is a result of the number of SRs and the SPI transfer rate - both values are set in the example above. This way you could also store new RGB values in the DOUT registers. BAM should be possible by updating the DOUT register only each 2nd, 4th, 8th, 16th time. Pseudo code: iteration_ctr = (iteraction_ctr + 1) % 16; if( iteration_ctr == 0 || iteration_ctr == 2 || iteration_ctr == 4 || iteration_ctr == 8 ) { bam_ctr = (bam_ctr + 1) % 4; DOUT = color_value[bam_ctr]; } Best Regards, Thorsten.

Very nice idea, and also very easy to implement :) Please try this version: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre2.zip Best Regards, Thorsten.

I don't think that a pattern synchronisation makes much sense for this operation. If it's only because you want to get an orientation about the pattern position, then we've to find other measures (see below) You are right! Nobody complained about this dependency so far, but I can easily change it. Resp.: did this now in v4_095_pre1, please try it out: http://www.ucapps.de/mios32/midibox_seq_v4_095_pre1.zip Unfortunately no place in the step view. In v4_095_pre1 I added it to the main screen (root menu), hope that it helps Best Regards, Thorsten.

A new minor-release is available: MIDIboxSEQ V4.094b ~~~~~~~~~~~~~~~~~~ o fixed LED handling for common frontpanels (e.g. MUTE LED stayed active regardless of selected view) Here the explanation for this effect: the high load is caused by LED updates. Whenever the sequencer is playing, LEDs will only be updated when a new step is played, or the user pressed a button. But in idle mode I simply update them each mS regardless of this. It has no real impact on the performance, but it could be improved in future. You are right, currently these settings can only be automatically changed by switching to another session. It would be difficult to integrate this into the song tables. Especially groove settings might contain a lot of additional data (e.g. if customized grooves are used) which doesn't fit into the table format. This behaviour was requested by k2z3k0: COPY+PASTE in the PATTERN view will only copy the groups and switch to the next slots. In order to permanently store into these slots you've to push the SAVE button (if not assigned to a Fx button, enter EXIT and press the SAVE button there). Best Regards, Thorsten.

should work again Best Regards, Thorsten.

Explained in detail in following tutorials: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F014b_enc_j5_relative%2F http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F015b_enc_j5_absolute%2F Best Regards, Thorsten.