TK.

Da kann ich Dir leider nicht weiterhelfen - ich habe mich mit VB noch nie beschaeftigt und habe es auch nicht vor, da diese Programmiersprache zu eng an das Betriebssystem gekoppelt ist. Du koenntest es ja mal mit Java versuchen. Auf der MIDIbox SID Seite findest Du die JSynthLib; in synthdrivers/MIDIboxSID/MIDIboxSIDDevice.java befindet sich die Funktion reconfigure_device_id(), in der ein SysEx-String versendet wird. Gruss, Thorsten.

Da kann ich Dir leider nicht weiterhelfen - ich habe mich mit VB noch nie beschaeftigt und habe es auch nicht vor, da diese Programmiersprache zu eng an das Betriebssystem gekoppelt ist. Du koenntest es ja mal mit Java versuchen. Auf der MIDIbox SID Seite findest Du die JSynthLib; in synthdrivers/MIDIboxSID/MIDIboxSIDDevice.java befindet sich die Funktion reconfigure_device_id(), in der ein SysEx-String versendet wird. Gruss, Thorsten.

Hi Dan, looks ok so far :) I will answer this question as soon as I get the display from Reichelt I will support the KS0107/KS0108 controller, it comes with the same bus interface like the HD44780 and seems to be available in a lot of LCDs no - this feature is possible in theory, but for me it's a low-priority job to integrate this into the MIDIbox-link protocol, since I don't need it by myself. Note that the MB64 can also send Pitch Bender events - you could plug 8 faders to the analog inputs as cheap replacement for the motorfader section :) To the unused inputs: all open analog inputs must be tied to ground all open digital inputs must be tied to +5V via a 10k Pull Up resistor. You will notice that such resistors are already available at every input of the DIN module, so you don't have to take special care - it's just plug & play :) Best Regards, Thorsten.

Hi Dan, looks ok so far :) I will answer this question as soon as I get the display from Reichelt I will support the KS0107/KS0108 controller, it comes with the same bus interface like the HD44780 and seems to be available in a lot of LCDs no - this feature is possible in theory, but for me it's a low-priority job to integrate this into the MIDIbox-link protocol, since I don't need it by myself. Note that the MB64 can also send Pitch Bender events - you could plug 8 faders to the analog inputs as cheap replacement for the motorfader section :) To the unused inputs: all open analog inputs must be tied to ground all open digital inputs must be tied to +5V via a 10k Pull Up resistor. You will notice that such resistors are already available at every input of the DIN module, so you don't have to take special care - it's just plug & play :) Best Regards, Thorsten.

Hi Ynot, yes, could work! :) With the new LED_MAP feature such functions can be added very easily Best Regards, Thorsten.

Hi Roman, I plan to support such individual adaptions in the MIDIbox NG design in form of PlugIns. This are code extensions which can be hooked into the BIOS and interact with all control elements. In the meantime there is no other way than to take and to modify one of the existing firmwares (they are available on request). Currently it isn't trivial to add such extensions, since every firmware has been optimized for special applications. The MIDIO128 firmware is optimized for digital IO, but additional analog controllers would make the performance poor. And with the MB64 firmware it's contrary. You could try to change the MIDIO128 firmware in order to add a pot handler as low priority task, but this requires some assembler knowledge... With the MB NG design this will be solved, but you have to wait till next year, ok? :) Best Regards, Thorsten.

Hi Roman, I plan to support such individual adaptions in the MIDIbox NG design in form of PlugIns. This are code extensions which can be hooked into the BIOS and interact with all control elements. In the meantime there is no other way than to take and to modify one of the existing firmwares (they are available on request). Currently it isn't trivial to add such extensions, since every firmware has been optimized for special applications. The MIDIO128 firmware is optimized for digital IO, but additional analog controllers would make the performance poor. And with the MB64 firmware it's contrary. You could try to change the MIDIO128 firmware in order to add a pot handler as low priority task, but this requires some assembler knowledge... With the MB NG design this will be solved, but you have to wait till next year, ok? :) Best Regards, Thorsten.

Hi, ok, in your first posting you wrote about 8 joysticks, and AINX2 means that the half of a AINX4 module is enough for this setup - just a hint for people who make the PCBs by themself. However, having more than necessary inputs doesn't hurt and could be usefull for the experimental phase. :) Yes, just write me a mail later. It's just a quick change in the firmware. Best Regards, Thorsten.

Hi, ok, in your first posting you wrote about 8 joysticks, and AINX2 means that the half of a AINX4 module is enough for this setup - just a hint for people who make the PCBs by themself. However, having more than necessary inputs doesn't hurt and could be usefull for the experimental phase. :) Yes, just write me a mail later. It's just a quick change in the firmware. Best Regards, Thorsten.

Ok - no pots, but encoders; it's ok :) Best Regards, Thorsten.

Ok - no pots, but encoders; it's ok :) Best Regards, Thorsten.

Es freut mich zu hoeren, dass nun alles funktioniert :) Gruss, Thorsten.

Es freut mich zu hoeren, dass nun alles funktioniert :) Gruss, Thorsten.

This time from Matti (Finland). The great surface (on the right side!) has been made by himself with 3mm aliminum and endcheecks of Gaia-mahogany. Check also his homepage: http://gamedude.klaanit.net/~mle/

This time from Matti (Finland). The great surface (on the right side!) has been made by himself with 3mm aliminum and endcheecks of Gaia-mahogany. Check also his homepage: http://gamedude.klaanit.net/~mle/

Dimitris: I will support a 40x2 LCD anyhow, but this solution isn't the best, since 15 characters have to be removed. :-/ The graphical LCD should contain a ks0107b / ks0108b controller. Thats a very common chip for cheap displays. It cannot handle with characters by itself; the command set supports "set address" and "write 8-pixel" and thats all. However, I will get my display end of week and will check the performance :) Best Regards, Thorsten.

Hi, there is a very trivial and fast solution which allows you to solve the problem with little effort from my side, and thats the lookup-table method. It works on this way: the controller gets the x and y position of the joysticks and fetches the corresponding radius and angle from two large tables with 128x128 values. 2*128*128 = 32kByte --- thats exactly the capacity of a BankStick. :) Which modules are required for this project: a core module a JDM module (but you could also ask your friends to burn the PIC) a AINX2 (-> 16 inputs, premade PCB not available) or AINX4 (-> 4 inputs, premade PCB available) a BankStick a modified MIDIbox64 firmware which converts the values automatically a special dump file for the BankStick, which can be transfered via MIDI and the joysticks of course Best Regards, Thorsten.

Hi, there is a very trivial and fast solution which allows you to solve the problem with little effort from my side, and thats the lookup-table method. It works on this way: the controller gets the x and y position of the joysticks and fetches the corresponding radius and angle from two large tables with 128x128 values. 2*128*128 = 32kByte --- thats exactly the capacity of a BankStick. :) Which modules are required for this project: a core module a JDM module (but you could also ask your friends to burn the PIC) a AINX2 (-> 16 inputs, premade PCB not available) or AINX4 (-> 4 inputs, premade PCB available) a BankStick a modified MIDIbox64 firmware which converts the values automatically a special dump file for the BankStick, which can be transfered via MIDI and the joysticks of course Best Regards, Thorsten.

Yes, definitely! :) On this way we can save a lot of unnecessary pots/buttons/LEDs and the poly mode configuration (where all three voices should have the same values) will be easier. And all pots will get an optional soft-overtake feature in order to prevent parameter jumps. :) Best Regards, Thorsten.

Yes, definitely! :) On this way we can save a lot of unnecessary pots/buttons/LEDs and the poly mode configuration (where all three voices should have the same values) will be easier. And all pots will get an optional soft-overtake feature in order to prevent parameter jumps. :) Best Regards, Thorsten.

Hi Frank, thanks again for testing! :) The LED-ring-pattern (0-3) is selected by logic itself, it's coded in the returned CC and therefore cannot be assigned to the encoder like in other ENC_MODE_*'s. However, you are able to change the LED pattern itself. Best Regards, Thorsten.

Hi Frank, thanks again for testing! :) The LED-ring-pattern (0-3) is selected by logic itself, it's coded in the returned CC and therefore cannot be assigned to the encoder like in other ENC_MODE_*'s. However, you are able to change the LED pattern itself. Best Regards, Thorsten.

...but please keep in mind that I'm planning a special firmware for a dedicated SID control surface which allows to control the SID parameters more ergonomically. I will publish the final layout for the panel w/ pots/encoders/display/buttons/LEDs in january, when I've time enough to think about a perfect solution. Not every parameter will become it's dedicated pot or button, some can be combined, and together with a LCD<->pot/encoder/button interaction tweaking the sounds will finally make more fun! :) In the meantime you could use the Java editor and maybe a MIDIbox with 16 pots or more to access the most important parameters w/o the mouse. Best Regards, Thorsten.

...but please keep in mind that I'm planning a special firmware for a dedicated SID control surface which allows to control the SID parameters more ergonomically. I will publish the final layout for the panel w/ pots/encoders/display/buttons/LEDs in january, when I've time enough to think about a perfect solution. Not every parameter will become it's dedicated pot or button, some can be combined, and together with a LCD<->pot/encoder/button interaction tweaking the sounds will finally make more fun! :) In the meantime you could use the Java editor and maybe a MIDIbox with 16 pots or more to access the most important parameters w/o the mouse. Best Regards, Thorsten.

Here are the new files with more dedicated features for the LC emulation: http://www.ucapps.de/midibox16e/midibox16e_v1004pre2.hex.zip http://www.ucapps.de/midibox_mf/midibox_mf_v1000pre2.hex.zip http://www.ucapps.de/midibox/mk_syx.zip New features: o support for LED-rings in LC emulation o support for MIDIbox Link (only tested in LC mode yet) o LED shift registers can be mapped to different functions Currently both firmwares can only be configured with the mk_syx script. From the .ini files: ################################################################################ # MIDI Merger: enable the merger in order to forward the incoming MIDI # events to the MIDI Out. A must if you would like to plug a keyboard # on the MIDI In, or if you want to cascade MIDIboxes # Allowed Keywords: # disabled don't use merger at all # enabled merges all external with internal events # mblink_fp MIDIbox Link Forwarding Point: like a common MIDI merger, # but internal events will be framed so that a MIDIbox Link # End Point can distinguish between a event which has been # sent by a common MIDI device and events which have been # generated by a MIDIbox # mblink_ep MIDIbox Link End Point: merges only external events # from a MBLink FP (Forwarding Point) ################################################################################ [MIDI_MERGER] enabled See also this posting: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1038961702 ################################################################################ # LED Map: assignes the LED shift registers to the Button Shift # registers or special values # Currently following values are supported: # 0 Default Setting (see Map below) # 1 Button Shift Register 1 (Button ID #1-#8) # 2 Button Shift Register 2 (Button ID #9-#16) # 3 Button Shift Register 3 (F1-F4 and Navigation Buttons: ID #17-#24) # 4 Button Shift Register 4 (Button ID #25-#32) # 5 Button Shift Register 5 (Button ID #33-#40) # 6 Button Shift Register 6 (Button ID #41-#48) # 7 Button Shift Register 7 (Button ID #49-#56) # 8 Button Shift Register 8 (Button ID #57-#64) # 9 Internal Bank (1 of 8) # 10 External Bank (1 of 8) # 11-15 reserved # 16 MIDI Status received for Button ID #1-#8 ([MIDI_LEDS] must be enabled!) # 17 MIDI Status received for Button ID #9-#16 ([MIDI_LEDS] must be enabled!) # 18 MIDI Status received for Button ID #17-#24 ([MIDI_LEDS] must be enabled!) # 19 MIDI Status received for Button ID #25-#32 ([MIDI_LEDS] must be enabled!) # 20 MIDI Status received for Button ID #33-#40 ([MIDI_LEDS] must be enabled!) # 21 MIDI Status received for Button ID #41-#48 ([MIDI_LEDS] must be enabled!) # 22 MIDI Status received for Button ID #49-#56 ([MIDI_LEDS] must be enabled!) # 23 MIDI Status received for Button ID #57-#64 ([MIDI_LEDS] must be enabled!) # 24-31 reserved ################################################################################ [LED_MAP] LED_SR1 = 1 # (Button ID #1-#8) LED_SR2 = 2 # (Button ID #9-#16) LED_SR3 = 3 # (F1-F4 and Navigation Buttons: ID #17-#24) LED_SR4 = 4 # (Button ID #57-#64) LED_SR5 = 5 # (Button ID #25-#32) LED_SR6 = 6 # (Button ID #33-#40) LED_SR7 = 7 # (Button ID #41-#48) LED_SR8 = 8 # (Button ID #49-#56) A more practical example can be found in the midibox16e_lc.ini and midibox_mf_lc.ini files Some words to the LC emulation with multiple core modules: the LC_EMULATION_ID should only be set for the last MIDIbox in the chain - the "MIDIbox Link End Point". All other MIDIboxes should work in common mode and configured as "MIDIbox Link Forwarding Point" Example: a chained MIDIbox16E and MIDIbox MF should be configured on this way: # MIDIbox16e .ini file # ... [MIDI_MERGER] mblink_fp # ... [LC_EMULATION_ID] 00 # ... # MIDIbox MF .ini file # ... [MIDI_MERGER] mblink_ep # ... [LC_EMULATION_ID] 10 # or 14 for Mackie Control emulation # ... Best Regards, Thorsten.