TK.

Version v1.4e is available now: MIDIboxFM V1.4e ~~~~~~~~~~~~~~~ o all drumsets are selectable again (previously only A1..A5) o presets/midibox_fm_drumsets.syx has been overworked, it now contains 16 *different* drumsets o changed encoder mode to MIOS_ENC_MODE_DETENTED3 since it's compatible with most encoders [/code] Here a quick demo of the new drumsets: http://www.ucapps.de/mp3/midibox_fm/mbfm_drumsets.mp3 (the superlow tuned toms are only audible with good speakers or with a headphone ;-) Best Regards, Thorsten.

It's now fixed in MBFM V1.4e MIDIboxFM V1.4e ~~~~~~~~~~~~~~~ o all drumsets are selectable again (previously only A1..A5) o presets/midibox_fm_drumsets.syx has been overworked, it now contains 16 *different* drumsets o changed encoder mode to MIOS_ENC_MODE_DETENTED3 since it's compatible with most encoders [/code] Here a demo of the new drumsets: http://www.ucapps.de/mp3/midibox_fm/mbfm_drumsets.mp3 Best Regards, Thorsten.

Hi, it would be cheaper to use a MBHP_CORE_LPC17 module with the MIDIO128 application. The MBHP_CORE_LPC17 supports up to 4 MIDI INs and OUTs + USB MIDI And MIDIO128 comes with an integrated MIDI router + support for the MBHP_AINSER64 module Best Regards, Thorsten.

I can't reproduce this issue. E.g. I tried it together with a Yamaha RM1x, but both sequencers are always 100% in sync. Could you please attach your session in a .zip file? Best Regards, Thorsten.

I'm using a switched PSU as well (cheap 10 EUR no-name from Pollin), it works without problems. No, I think that 15V is a high voltage to drive motorfaders, but I might be wrong in your case... Best Regards, Thorsten.

I just checked this for you under Logic Studio: They appear as two separate devices, and it's possible to assign different fader groups to the HUIs. Best Regards, Thorsten.

You have to check if the button has been pressed (pin_value == 0): if( pin_value == 0 ) { MM_VPOT_SendJogWheelEvent(-1); } [/code] this explains why it would be decremented twice before. It doesn't explain why it has been decremented 3 ticks... but maybe this was just a wrong observation? Best Regards, Thorsten.

This was a typo in the Wiki page, it's fixed now Best Regards, Thorsten.

Very strange... do you have access to another computer? Best Regards, Thorsten.

The GM5x5x5 LED circuit isn't an ideal design, the LEDs are flickering too fast. And putting a LED into the current loop means that there is no current for the optocoupler at the MIDI target anymore ;-) Have a look into the http://www.ucapps.de/mbhp_ltc.html schematic for a perfect HW based MIDI activity indicator. Best Regards, Thorsten.

I've experiences with the coreless motors which are used for Alps faders, but my impression is that they are faster, but also much louder, therefore I don't really like them. No, it isn't prepared for such high voltages. It wouldn't drop on an ideal power supply. ;-) I've no experiences with motors which are supplied at such high voltages - I never tried this out by myself. Personally I prefer low voltages (e.g. 5V) and a bit slower, but much more silent moves. Best Regards, Thorsten.

Of course, you are right, in this case the usage of a Mutex is required as well. I mixed this with the mutex which is mentioned in the MIOS32 documentation (MIOS32_SPI). The only reason for not using mutexes would be to keep the code as simple as possible - but once you learned how to setup them, there is no reason for not using this "protection" mechanism. Best Regards, Thorsten.

Did you already plug the LPCXPRESSO into the MBHP_CORE_LPC17 module? This isn't required and can cause such issues if you don't follow my guide 100% Most simple way: unplug the module, it will (resp. should) be powered via the LPC-Link USB port anyhow during programming. Best Regards, Thorsten.

The last block is written into the internal EEPROM, strange that this failed! What happens if you upload the application again? Is the EEPROM range still failing? Best Regards, Thorsten.

Hi, you have to consider that the LEDs are connected from the left to the right of the MBHP_DOUT module, which means: first LED connected to D7, next to D6, next to D5, etc... Buttons are connected in the opposite order (D0, D1, D2, ...) In most documentations this had been made very clear meanwhile, but not in the MBMM docs - therefore you won't find so many hints about this in the forum. Best Regards, Thorsten.

See the MBHP_MF_NG topic - the Mackie HUI protocol has been implemented meanwhile! :-) At least under Logic it requires a dedicated port for each HUI, somebody reported that under Protools chaining could be possible by sending MIDI events over different channels, but I can't test it. So, the most proper solution is the usage of dedicated MIDI ports. Either via the MIDI USB 4x4 application for MBHP_CORE_LPC17, or a commercial MIDI interface. Best Regards, Thorsten.

Yes, correct. The flag is set by FILE_CheckSDCard which should be frequently called and should be protected via Mutex Note that the Mutex is only required if the SPI port is shared with another device (e.g. MBHP_ETH interface) Best Regards, Thorsten.

For sure, I'm just still waiting for the Ctrlr update which helps to get my panels working again. Best Regards, Thorsten.

Leider ein bekanntes Problem. "help" hilft (im warsten Sinne des Wortes). Alternativ kannst Du auch den Korg MIDI Driver installieren: Gruss, Thorsten.

MIDI IN/OUT LEDs are no MIOS32 feature, they have to be supported by the firmware. MBSEQ doesn't support such LEDs - but an integrated MIDI monitor screen, which is very helpful for debugging MIDI connections: MENU+MIDI, select "Misc." -> GP16 Best Regards, Thorsten.

Hi, It is fixed with the MBHP_MF_NG module (the successor of the V1 module). I can't say this, because I haven't tested these motors. It should work, but with such a high current consumption you really need a stronger PSU circuit... ...yes, and it will be required. Yes, you can also connect each module to individual MIDI IN/OUTs It's probably better done via software, but currently not implemented. As always the problem: there is no spare pin for this. :-/ We could sacrifice the status LED pin for such a purpose; I would have to create a special firmware for you. Or if you've assembler skills: you could modify the firmware by yourself of course. Best Regards, Thorsten.

The 6th Byte ist the Device ID which matches with the MIOS32 ID that can be changed with the "mios32_bootloader" update package. It allows you to address up to 128 different devices over a single MIDI Interface. :) Best Regards, Thorsten.

Klasse! :) Gruss, Thorsten.

It's released now: @Hawkeye: great work - as always! :) Best Regards, Thorsten.

It's released now in v4.059 -> Last WE I added a random accent generator which leads to even more interesting results! :) Best Regards, Thorsten.