TK.

Hi Zeno, the MIDIbox16E firmware doesn't support analog pots, therefore the analog pins don't have to be tied to ground. For the display only output pins are used - just let them open. Just only the 10k pull-up resistors at the digital inputs (Port J6 and J9) are a must. Best Regards, Thorsten.

Problem is, that all development and/or premade boards for this SMD (=hard to solder) chip are more expensive than a ready-made USB MIDI interface, so that you cannot really save money. Best Regards, Thorsten.

Hi Frank, it's easier for me to implement an option which allows to connect two 2x40 displays to the core - I will check it after the graphic LCD driver has been finished. However, I see no difficulties. Best Regards, Thorsten.

Hi Frank, it's easier for me to implement an option which allows to connect two 2x40 displays to the core - I will check it after the graphic LCD driver has been finished. However, I see no difficulties. Best Regards, Thorsten.

This time from Andreas (Germany) - he made this control surface for the most recent release of NI Traktor. The box consist of 2 cores, running with MB64 and MB16E firmware, and a lot of DIN and AIN modules for the pots, faders, buttons, encoders.

This time from Andreas (Germany) - he made this control surface for the most recent release of NI Traktor. The box consist of 2 cores, running with MB64 and MB16E firmware, and a lot of DIN and AIN modules for the pots, faders, buttons, encoders.

Well done! :) Best Regards, Thorsten.

Well done! :) Best Regards, Thorsten.

Hi Basta, every core features a lot of redundant functions, which are not required in a multicore-system. An extreme example: with 3 cores, one running with MIDIbox NG, the other two with MIDIbox MF v100pre2, you will be able to connect 128 LEDs & 128 Buttons & 128 Pots to to the NG core, and 2 * 64 LEDs, 2 * 64 Buttons, 2 * 8 motorfaders to the MF cores. An extreme example into the other direction: a MIDIbox MF can also be used without any LCD, LED or button. Bankswitching can be realized with Program Change events, or the host software can manage the bank handling by itself (-> Cubase/Logic/etc...). Configuration is possible via SysEx. Best Regards, Thorsten.

Hi Basta, every core features a lot of redundant functions, which are not required in a multicore-system. An extreme example: with 3 cores, one running with MIDIbox NG, the other two with MIDIbox MF v100pre2, you will be able to connect 128 LEDs & 128 Buttons & 128 Pots to to the NG core, and 2 * 64 LEDs, 2 * 64 Buttons, 2 * 8 motorfaders to the MF cores. An extreme example into the other direction: a MIDIbox MF can also be used without any LCD, LED or button. Bankswitching can be realized with Program Change events, or the host software can manage the bank handling by itself (-> Cubase/Logic/etc...). Configuration is possible via SysEx. Best Regards, Thorsten.

I've prepared the MBSID driver for the next official release of JSynthLib, that's the reason why it isn't selected by default anymore. To enable the driver you've to go into the Config->Synths menu, press the "Add Device" button, select the MIDIbox SID driver, thereafter the "show details" button if you want to change the MIDI channel & Device ID Best Regards, Thorsten.

yes, I've already enough time for all the other things which are necessary for a pleasurable life - that's perfectionized scheduling ;-) Jack: the PIC18F452-I/P is required, this is the DIP version (the big one which is easy for soldering) Best Regards, Thorsten.

yes, I've already enough time for all the other things which are necessary for a pleasurable life - that's perfectionized scheduling ;-) Jack: the PIC18F452-I/P is required, this is the DIP version (the big one which is easy for soldering) Best Regards, Thorsten.

Hi Dan, yes, correct. Just mix them. As I already wrote, the hardware itself is compatible (unfortunetaly the software isn't). Also the price is compatible ;-) (the PIC16F877-20/P costs about US$8.80 at Digikey, the PIC18F452-I/P US$9.40) Best Regards, Thorsten.

Hi Dan, yes, correct. Just mix them. As I already wrote, the hardware itself is compatible (unfortunetaly the software isn't). Also the price is compatible ;-) (the PIC16F877-20/P costs about US$8.80 at Digikey, the PIC18F452-I/P US$9.40) Best Regards, Thorsten.

I created the layouts with the Linux version of Eagle. Don't know if they are incompatible, but normaly - with the most up-to-date release - it should work. Best Regards, Thorsten.

I created the layouts with the Linux version of Eagle. Don't know if they are incompatible, but normaly - with the most up-to-date release - it should work. Best Regards, Thorsten.

No, but there are special hex-switch-dials available which are working fine. They have 16 positions, 1 input, 4 outputs. Best Regards, Thorsten.

No, but there are special hex-switch-dials available which are working fine. They have 16 positions, 1 input, 4 outputs. Best Regards, Thorsten.

Heico just built an option into his box which enables him to connect the MIDIbox directly with the gameport without a MIDI interface. But he isn't able to use both, the MIDI-In and the Gameport plug, at the same time. Best Regards, Thorsten.

Heico just built an option into his box which enables him to connect the MIDIbox directly with the gameport without a MIDI interface. But he isn't able to use both, the MIDI-In and the Gameport plug, at the same time. Best Regards, Thorsten.

Axel made such buttons by himself: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1034795420 http://ucapps.digitaljunk.org/cgi-bin/yabb/YaBB.cgi?board=parts_q;action=display;num=1034830289 Best Regards, Thorsten.

Axel made such buttons by himself: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1034795420 http://ucapps.digitaljunk.org/cgi-bin/yabb/YaBB.cgi?board=parts_q;action=display;num=1034830289 Best Regards, Thorsten.

Hi Djaychela, thanks for the informations. I don't have further questions so far, as I'm still waiting for the ordered components which enable me to build all the required modules for working with the emulated MC more efficiently. However, good to know that the MC isn't able to update the fader positions faster than the MIDIbox MF (which requires about 0.2 ms in worst case :)) Best Regards, Thorsten.

Hi Djaychela, thanks for the informations. I don't have further questions so far, as I'm still waiting for the ordered components which enable me to build all the required modules for working with the emulated MC more efficiently. However, good to know that the MC isn't able to update the fader positions faster than the MIDIbox MF (which requires about 0.2 ms in worst case :)) Best Regards, Thorsten.