TK.

A new version is available: MIDIbox NG V1.031 ~~~~~~~~~~~~~~~~~ o the STM32F4 variant of the firmware supports USB Host mode! See also o MIDI clock input ports now disabled by default to avoid feedback loops in various setups o improved "ain_filter_delay_ms" implementation to support sensors (experimental stage) o Covered new use case which allows to transform velocity values of incoming notes. See cfg/test/conev_6.ngc EVENT_RECEIVER and EVENT_SENDER have to be specified with "key=any", so that any key will be received and sent. o support for DIN/DOUT emulation on digital IO ports J10A/J10B (LPC17: J10/J28) See examples in cfg/test/diocfg_1.ngc and cfg/test/diocfg_2.ngc Best Regards, Thorsten.

Hi Przemek, hm... at least I can say that this isn't related to the software, especially because all inputs are debounced. Maybe buttons and encoders are damaged, e.g. because the guy who soldered the components overheated them. E.g. I had a similar problem with a button which is also used in the sammich devices and had to replace it. Best Regards, Thorsten.

Hallo Julian, vermutlich hast Du die Device ID (ueber dem Query Button) verstellt. Sie sollte auf "0" stehen. Gruss, Thorsten.

Fine! :) The J10 ports overlay DIN shift register positions. So, with this default example DIN 1 and 2 wouldn't have a function anymore. If somebody would add a MBHP_DINX4 module, and still would like to use the J10A/B based inputs, he would change the emu_din_sr parameter to higher numbers (of unused DIN SR positions) No, this isn't possible. Just build the Low-Cost adapter as documented here: http://www.ucapps.de/mbhp_sdcard.html Best Regards, Thorsten.

Great! Thanks also for the detailed report. I guess that sooner or later somebody else with similar interests will come back to us. :) > Is that easy to "just" remove the PID controller in the MF soft and assign output not to the PIC PWM but AOUT ? yes, this would be easy. Do you have a schematic of the PID controller? Best Regards, Thorsten.

@stuartm: V4.084 got a new function which helps to overcome this issue. In the UTIL->Options page you can define the order at which particular CC layers are sent (before or after program change). @Luke: I haven't changed the format in the last years... this seems to be an unintended change. Could you please send me one of your preset tracks so that I can compare? And do you remember with which version you created the problematic tracks? Best Regards, Thorsten.

Cool! :) I've released a new version of the usb_midi_2x2 and usb_midi_4x4 application which supports the USB MIDI host mode. It's the most simple application for this purpose. Best Regards, Thorsten.

Maybe the number is too high so that an overrun happens? Which note is played when you are using din_key_offset=1 which note when you are using din_key_offset=2 and 3... and 4... are you able to increase it until the expected note will be played? At which value an unexpected note will be played? Best Regards, Thorsten.

Hi Marc, from the HW side it should be possible with MIDIbox NG. But do you already know, if these parameters are accessible via MIDI? Best Regards, Thorsten.

Hi, the encoder behaviour has been improved in an unreleased MIOS8 and MBSID version. Please join the beta test! :-) An update is very easy: install MIOS Studio (if not done yet): http://www.ucapps.de/mios_studio.html Connect MIDI IN/OUT of your MB6582 to your computer, open MIOS Studio, select the MIDI interface, try the bidirectional communication with the "Query" button. If working, first upload the new MIOS V1.9h version, thereafter the new MIDIBox SID application. Both are linked in this posting: Best Regards, Thorsten.

Hi Chris, did you enable the FANTOM_XR_VARIANT switch in keyboard.c? In fully customized variant the din_key_offset parameter isn't considered. Best Regards, Thorsten.

Of course, providing something to such an audience is a nice motivation :smile: (as long as the requests don't get too illusory or clash too much with given concepts ;-) Please try this version: http://www.ucapps.de/mios32/midibox_ng_v1_031_pre3.zip Configuration examples can be found in cfg/test/diocfg_1.ngc: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_1.ngc and cfg/test/diocfg_2.ngc http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Fdiocfg_2.ngc I haven't tried this, but with this new feature is should also be possible to scan a 8x8 DIN *or* a 8x8 DOUT matrix (unfortunately 3 8bit ports would be required to scan a 8x8 DIN and DOUT matrix at the same time). Best Regards, Thorsten.

The wishlist is located at the bottom of this file: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2FCHANGELOG.txt But I only take over requests where I think that they are useful for myself, and/or the implementation & testing isn't so difficult. When you don't find certain functions in the documentation, then it's very likely not available. Either because nobody requested such a function yet, or there is a conflict with another function which you've overlooked. When you are writing "Cant find any documentation about it" it sounds to me like a complaint, and not like a request! :no: J10B (on MBHP_CORE_LPC17: J28) is typically used as extension port for CLCDs/GLCDs. Normally I prefer to use the ports only for a single purpose to avoid conflicting configurations which could lead to the next request from somebody else to make it somehow possible without considering what it means at my end. I spend some thoughts about possible solutions anyhow, and came to the conclusion that the most simple way would be to provide a new function which maps J10A/J10B to DIN or DOUT shift registers (some kind of "shift register emulation") E.g. with: DIO port=J10A emu_din_sr=1 DIO port=J10B emu_din_sr=2 I could provide the possibility to handle J10A and J10B pins the same way like pins of the first and second DIN shift register (id=1..16) Advantage: this would work completely transparent for the firmware, so that encoders could be connected as well, and configured like if they are connected to shift registers. With: DIO port=J10A emu_din_sr=1 DIO port=J10B emu_dout_sr=1 it would be possible to use J10A for buttons (id=1..8), and J10B for LEDs (id=1..8) Is this the right direction, or do you have something else in mind which conflicts with this approach? Best Regards, Thorsten.

Yes, this works: But as you can see in the schematic, the emulated soft1 button is at J10A:D3 = PE11 and not PE8 PE8 (=J10A:D0) is the first encoder pin. Best Regards, Thorsten.

Fine! :) Yes, 10k pull-ups are too weak for the LCD signals, therefore I recommend 1k Best Regards, Thorsten.

Hi Julian, button ids are normally mapped to digital inputs of MBHP_DIN modules connected to the SRIO chain via J8/9 If you want to trigger button events with J10A:D0..D7, you could use the button emulation function of the SCS (because the SCS is normally connected to J10A) So, please try: RESET_HW # the SCS should emulate button/enc functions in main page SCS soft1_button_emu_id=2000 \ soft2_button_emu_id=2001 \ soft3_button_emu_id=2002 \ soft4_button_emu_id=2003 \ shift_button_emu_id=2004 \ enc_emu_id=2000 EVENT_BUTTON id=2000 type=CC chn=1 cc=16 range=0:127 ports=1111000000000000 EVENT_BUTTON id=2001 type=CC chn=1 cc=17 range=0:127 ports=1111000000000000 EVENT_BUTTON id=2002 type=CC chn=1 cc=18 range=0:127 ports=1111000000000000 EVENT_BUTTON id=2003 type=CC chn=1 cc=19 range=0:127 ports=1111000000000000 EVENT_BUTTON id=2004 type=CC chn=1 cc=20 range=0:127 ports=1111000000000000 Best Regards, Thorsten.

Yes, now your MBSEQ V4L turned into a MIDI FX machine. Cheers! Best Regards, Thorsten.

Alright. Note that the new bootloader won't change the LCD behaviour at your side. I'm sure that this is a HW issue, because I've checked the SW drivers with various CLCDs and GLCDs some time ago, and you are the first guy who reported such an effect. Best Regards, Thorsten.

Ok, please try this version: http://www.ucapps.de/mios32/midibox_seq_v4l_085_pre1.zip The clock divider should be taken over for all tracks now (not only the note tracks) I wasn't able to reproduce the PitchBend issue, but this might be related to a handling error. E.g. the CLEAR function will only clear the note tracks if you push GP button #1 resp. #9 In order to clear the PitchBend track, push CLEAR+GP button #4 resp. #12 The LED above these buttons should flicker if PitchBend events are sent Does this help? Best Regards, Thorsten.

Ok, understood. I spend some time in order to make this possible - the configuration isn't straightforward, but I hope that this will meet your expectations: upload this firmware to the core: http://www.ucapps.de/mios32/midibox_seq_v4l_085_pre1.zip enter the "store" command after upload. This will ensure that the latest parameters are visible in the file (that's the reason why LiveForceToScale wasn't visible previously - last time you stored this file was with a version which didn't provide this parameter) edit the MBSEQ_C.V4 file: Change MIDI_BUS_Channel 0 ... to MIDI_BUS_Channel 0 17 (bus will listen to all channels) Change the MIDI channel of MIDI_BUS_Channel 1 ... and MIDI_BUS_Channel 2 and MIDI_BUS_Channel 3 ... to 0 (bus won't listen to channels) Change LiveKeepChannel to 1 Parameters should be taken over automatically once you save the file (terminal will show "AUTOLOAD 'MBSEQ_C.V4'") Best Regards, Thorsten.

Yes, there is a hidden feature in MBSEQ V4L which allows you to enable force-to-scale for the In->Out option! :) Connect to MIOS Studio, open the MIOS32 File browser, edit the SESSIONS/DEF_V4L/MBSEQ_C.V4 file. Search for "LiveForceToScale" and set it to 1 Thereafter save the change, and then enter "reset" in MIOS Terminal in order to reboot the device. Best Regards, Thorsten.

Hi Benoit, there is a workaround for this in following (unreleased) version: http://www.ucapps.de/mios32/mios32_bootloader_v1_016.zip (store command will be retried if flash operation failed - I guess that this is related to flash protection, but haven't debugged this further. With the retry the store command will work reliable) LCD: it's very likely a hardware issue. LCD isn't correctly initialized after power-on, and in your pictures it looks like the second line will never be written. This indicates, that the D6 pin is always 0 Check it with the scope. If it doesn't toggle than my assumption is correct and you know where to continue with debugging. Best Regards, Thorsten.

Hi, you could switch between the modes with the Ctrlr based editor: It makes sense to explore the capabilities of MBSID with this editor anyhow before you start editing with the CS :) Best Regards, Thorsten.

Ok, you already found out the required calculation by yourself! :) For the case that it helps: in mf.inc you will find following lines MF_Tick_TraceFader movff ADRESL, MF_TRACE_VALUE_L ; take original value from ADC so that AIN deadband doesn't matter! movff ADRESH, MF_TRACE_VALUE_H You could replace them by: MF_Tick_TraceFader movff MF_VALUE_L, MF_TRACE_VALUE_L ; take original value from ADC so that AIN deadband doesn't matter! movff MF_VALUE_H, MF_TRACE_VALUE_H in order to display the translated response in MIOS Studio There is no alternative way how I can help you to visualize the changes. I know that the task to find a satisfying calibration table w/o further analysis is a challenge - but providing more sophisticated debugging helps would result into much more effort at my side. Best Regards, Thorsten.

Please follow this guide: -> http://www.ucapps.de/midibox_seq_manual_tut5.html It should answer both questions. If not, please let me know what is unclear, I will improve the page! :smile: It's possible to route the transposers & arpeggiators to different busses in order to handle up to 4 independent note entries (regardless if from external keyboards or loopback tracks) Best Regards, Thorsten.