TK.

Hi Rogic, MB64 doesn't support encoders, I think that you are either searching for MIDIbox16E, or for the upcoming MIDIbox NG... The encoder connections to the DINX4 module can be found at the DIN page: http://www.ucapps.de/mbhp_din.html (-> mbhp_dinx4_16enc.pdf). They don't need a power supply. Best Regards, Thorsten.

Hi Justin, did you follow the instructions under http://www.ucapps.de/howtodebug.html ? Best Regards, Thorsten.

Hi Justin, did you follow the instructions under http://www.ucapps.de/howtodebug.html ? Best Regards, Thorsten.

Hi Shawn, the slow voltage dropping at RB6 and the power pins is the normal behaviour of the JDM circuit. It will get stable during programming. But 13.25V at MCLR# seems to be too low. You can increase this voltage in the hardware configuration setup by lowering the I/O delay. Best results with "delay = 1" Best Regards, Thorsten.

Hi Shawn, the slow voltage dropping at RB6 and the power pins is the normal behaviour of the JDM circuit. It will get stable during programming. But 13.25V at MCLR# seems to be too low. You can increase this voltage in the hardware configuration setup by lowering the I/O delay. Best results with "delay = 1" Best Regards, Thorsten.

Sure, this is possible, but it also requires some modifications. The display messages have to be sent to a "MIDIbox Link Endpoint" via MIDI instead to the LCD port. I've already planned to provide a MIDIbox NG example PlugIn for this method when the new platform is ready for use, but don't expect it before February ;-) Best Regards, Thorsten.

Sure, this is possible, but it also requires some modifications. The display messages have to be sent to a "MIDIbox Link Endpoint" via MIDI instead to the LCD port. I've already planned to provide a MIDIbox NG example PlugIn for this method when the new platform is ready for use, but don't expect it before February ;-) Best Regards, Thorsten.

Hi Adam, based on this schematic: http://users.auth.gr/~mixos/projects/pcb/sensors/001/index_en.htm the pinout is the same, but the BC667 seems to be a PNP instead of a NPN - the polarity is exchanged, therefore the transistor has to be connected on a different way. Do you know, how to fix the circuit, or should I draw a schematic? Best Regards, Thorsten.

Hi Adam, based on this schematic: http://users.auth.gr/~mixos/projects/pcb/sensors/001/index_en.htm the pinout is the same, but the BC667 seems to be a PNP instead of a NPN - the polarity is exchanged, therefore the transistor has to be connected on a different way. Do you know, how to fix the circuit, or should I draw a schematic? Best Regards, Thorsten.

Hi Dan, the fairchild EEPROMs are not ok, 32k means: 32 kbit = 4kbyte. You could use the 511-M24256-BN6 from ST (available at Mouser) instead. The parts from TI should be ok 4x40 displays: with the MIDIbox NG design you will be able to write your own LCD driver (based on my examples) which displays what you want. On the other hand: I don't think that such 4x40 LCDs are ergonomic, because normaly you want to see the track names exactly above the channel strips in the right order. Best Regards, Thorsten.

Hi Dan, the fairchild EEPROMs are not ok, 32k means: 32 kbit = 4kbyte. You could use the 511-M24256-BN6 from ST (available at Mouser) instead. The parts from TI should be ok 4x40 displays: with the MIDIbox NG design you will be able to write your own LCD driver (based on my examples) which displays what you want. On the other hand: I don't think that such 4x40 LCDs are ergonomic, because normaly you want to see the track names exactly above the channel strips in the right order. Best Regards, Thorsten.

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.

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.