TK.

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.

I'm not sure if the higher voltage is good for all components; if you want to be at the save side, don't use it! Best Regards, Thorsten.

This is exactly the behavior if there is no (or no matching) MBSEQ_HW.V4 file on your SD Card. Because in this case the "standard frontpanel" layout will be selected, which has no multiplexers (like Wilba's one) - hence, one button can trigger multiple functions, and some LEDs are assigned to 8 functions as well. Note that the file is named "MBSEQ_HW.V4" and not "MBSEQ_HW.V4.txt" - could this be the error? Are you aware of this page which describes the installation procedure? http://www.ucapps.de/midibox_seq_manual_in.html The MBSEQ_HW.V4 file is located in the hwcfg/wilba directory of the release package. The latest firmware version can be found under: http://www.ucapps.de/mios32_download.html We've V4.094 meanwhile... and the MBSEQ_HW.V4 has changed... Best Regards, Thorsten.

Does it still happen with the new version? I'm asking because I'm still not able to reproduce this. However, I noticed that sometimes the sequencer is not running smoothly during the save operation - but it doesn't lead to a crash. After the operation it continues as usual. Best Regards, Thorsten.

cool! :) Whenever you select a track, a corresponding CC will be sent (Port, MIDI channel and CC number can be configured). This feature was requested by somebody who wanted to synchronize the track selection with his DAW (as far as I remember it was Ableton Live) - but I don't know, what exactly he configured in his DAW, and I'm also not sure about the advantages. It was just a quick hack for him ;-) Best Regards, Thorsten.

Great! :) I can only speculate about the contrast pot - as you can see in the schematic: http://www.ucapps.de/mbhp/mbhp_core_stm32f4.pdf it sets the V0 voltage between Vs and Vd (0..5V) - do you measure this voltage change? Best Regards, Thorsten.

Hi Chris, adding a resistor (e.g. 470 Ohm) to between the core output pin and WS2812 is probably a good idea, see this posting for the arguments: https://electronics.stackexchange.com/questions/177019/why-does-a-resistor-in-my-neopixel-data-line-work-at-all The LED should turn off once the Core starts to drive data into the chain. Enable the "fastboot" option so that this happens as fast as possible Best Regards, Thorsten.

The square is at the same side like the notch, and it shows to pin number 2 (because the connector is mounted at the bottom of the LCD, and not at the top) This can be very confusing, therefore I prefer pictures ;) Best Regards, Thorsten.

Where are the notches - please compare with: Best Regards, Thorsten.

I updated the documentation at the bottom of this page http://www.ucapps.de/mbhp_core_stm32f4.html It shows how the LCD should be connected And I've some good news: I tried the wrong connection with one of my old LCDs - and this didn't fry the LCD. Instead, the Lumi pot changed the contrast - exactly the same effect noticed by @Nirokesan Changing the connection again - LCD working again! :) So, I think that my statement, that a wrong connection destroys the LCD is wrong, I just never tried this. ;) Actually this was based on experiences with the PIC based MBHP_CORE module, which had a different pinning. For 32bit cores a new pinning has been introduced, which seems to be fool-proven. And also based on the circuit this makes sense (although it wasn't my intention): Vs/Vd will be connected to B-/B+ if the connector is rotated, so that the Lumination pot controls the LCD supply current instead of the backlight supply. Best Regards, Thorsten.

For me it's very interesting, that we now have a second case with similar symptoms. Maybe this gives me the missing hint for the root cause. Questions to you: did you ever connect the LCD cable the wrong way by accident? Please don't try to change the cable orientation - this could destroy the LCD. If you are able to change the contrast of the black bars with the contrast pot, you know that it's currently connected the right way which LCD are you using exactly? does the same happen if only a single LCD is connected? could you please check the connections with the "testlcdpin" command and report the measurements? I built different STM32F4 core modules in the past, some of them are frequently used - and I never noticed such a problem. But there might be a general difference in my configuration: in the bootloader, I enabled "fastboot" mode. Could you please try the same at your side? The setup procedure is documented here: http://www.ucapps.de/mios32_bootstrap_newbies.html Best Regards, Thorsten.