TK.

Auch die LED-Pattern kann man im midibox16e.ini File anpassen (siehe http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=german;action=display;num=1039009816 ) [LED_PATTERNS] 0.00 = 0000000000000001 0.01 = 0000000000000001 0.02 = 0000000000000011 0.03 = 0000000000000011 0.04 = 0000000000000011 0.05 = 0000000000000111 0.06 = 0000000000000111 0.07 = 0000000000000111 0.08 = 0000000000001111 0.09 = 0000000000001111 0.0A = 0000000000001111 0.0B = 0000000000011111 0.0C = 0000000000011111 0.0D = 0000000000011111 0.0E = 0000000000111111 0.0F = 0000000000111111 0.10 = 0000000000111111 0.11 = 0000000000111111 0.12 = 0000000001111111 0.13 = 0000000001111111 0.14 = 0000000001111111 0.15 = 0000000011111111 0.16 = 0000000011111111 0.17 = 0000000011111111 0.18 = 0000000111111111 0.19 = 0000000111111111 0.1A = 0000000111111111 0.1B = 0000001111111111 0.1C = 0000001111111111 0.1D = 0000001111111111 0.1E = 0000011111111111 0.1F = 0000011111111111 umaendern in: [LED_PATTERNS] 0.00 = 0000000000000001 0.01 = 0000000000000001 0.02 = 0000000000000011 0.03 = 0000000000000011 0.04 = 0000000000000111 0.05 = 0000000000000111 0.06 = 0000000000001111 0.07 = 0000000000001111 0.08 = 0000000000011111 0.09 = 0000000000011111 0.0A = 0000000000111111 0.0B = 0000000000111111 0.0C = 0000000001111111 0.0D = 0000000001111111 0.0E = 0000000011111111 0.0F = 0000000011111111 0.10 = 0000000111111111 0.11 = 0000000111111111 0.12 = 0000001111111111 0.13 = 0000001111111111 0.14 = 0000011111111111 0.15 = 0000011111111111 0.16 = 0000111111111111 0.17 = 0000111111111111 0.18 = 0001111111111111 0.19 = 0001111111111111 0.1A = 0011111111111111 0.1B = 0011111111111111 0.1C = 0111111111111111 0.1D = 0111111111111111 0.1E = 1111111111111111 0.1F = 1111111111111111 Insgesamt kannst Du vier verschiedene Patterns definieren und den Encodern zuweisen... viel Spass beim "Malen nach/mit Zahlen" ;-) Gruss, Thorsten.

Die MIDIbox hat einen eingebauten MIDI Merger, der alle Daten, die in den MIDI-In reingehen am MIDI-Out wieder ausgibt. Wenn In- und Out-Port der MB16E direkt an einen Computer angeschlossen sind, sollte der MIDI-Merger deaktiviert werden, damit es keine Feedback-Loop gibt. Normalerweise stellt man den MIDI-Merger direkt an der MIDIbox ein, aber da Du kein Display angeschlossen hast, musst Du die Konfiguration ueber MIDI vornehmen. Dazu benoetigst Du folgende Programme: das http://www.ucapps.de/midibox/mk_syx.zip Skript Perl: http://aspn.activestate.com/ASPN/Downloads/ActivePerl/index/ die vsysexbox von Serge http://serge.ucapps.de (die vmidibox16e ist momentan leider nicht mit der aktuellsten Firmware kompatibel und hat auch sonst so seine Macken!!!) Nachdem Du Perl installiert hast, gehst Du einfach in das mk_syx/samples Verzeichnis, aenderst mit Deinem Lieblingseditor die midibox16e.ini Datei nach Deinen Wuenschen ab, rufst in einer DOS-Shell das Skript auf (perl ..\mk_syx.pl midibox16e.ini midibox16e.syx), laedst das .syx-File in die vsysexbox und sendest sie zur MIDIbox - das wars auch schon :) Zu Deiner eigentlichen Frage: in der .ini-Datei kann man den Merger in folgender Zeile deaktivieren: [MIDI_MERGER] enabled umaendern in: [MIDI_MERGER] disabled Und ganz wichtig: das neue mk_syx-Script funktioniert auch nur mit der neusten Firmware zusammen: http://www.ucapps.de/midibox16e/midibox16e_v1004pre1.hex.zip Gruss, Thorsten.

Die MIDIbox hat einen eingebauten MIDI Merger, der alle Daten, die in den MIDI-In reingehen am MIDI-Out wieder ausgibt. Wenn In- und Out-Port der MB16E direkt an einen Computer angeschlossen sind, sollte der MIDI-Merger deaktiviert werden, damit es keine Feedback-Loop gibt. Normalerweise stellt man den MIDI-Merger direkt an der MIDIbox ein, aber da Du kein Display angeschlossen hast, musst Du die Konfiguration ueber MIDI vornehmen. Dazu benoetigst Du folgende Programme: das http://www.ucapps.de/midibox/mk_syx.zip Skript Perl: http://aspn.activestate.com/ASPN/Downloads/ActivePerl/index/ die vsysexbox von Serge http://serge.ucapps.de (die vmidibox16e ist momentan leider nicht mit der aktuellsten Firmware kompatibel und hat auch sonst so seine Macken!!!) Nachdem Du Perl installiert hast, gehst Du einfach in das mk_syx/samples Verzeichnis, aenderst mit Deinem Lieblingseditor die midibox16e.ini Datei nach Deinen Wuenschen ab, rufst in einer DOS-Shell das Skript auf (perl ..\mk_syx.pl midibox16e.ini midibox16e.syx), laedst das .syx-File in die vsysexbox und sendest sie zur MIDIbox - das wars auch schon :) Zu Deiner eigentlichen Frage: in der .ini-Datei kann man den Merger in folgender Zeile deaktivieren: [MIDI_MERGER] enabled umaendern in: [MIDI_MERGER] disabled Und ganz wichtig: das neue mk_syx-Script funktioniert auch nur mit der neusten Firmware zusammen: http://www.ucapps.de/midibox16e/midibox16e_v1004pre1.hex.zip Gruss, Thorsten.

Hi Josh, for the update cycle I took special care and implemented a nice feature called "dynamic priorities" which samples the last two turned pots more often then the others. Therefore, the latency (or update-cycle) for these two pots is less than 1ms (note that the transmission of a MIDI events gets about 960 µS). All the other 64 pots of MB64 are sampled in between 10-15 mS. Summary: the general update frequency is 50-70 samples/second (MB64), the dynamic update frequency of the last two turned pots about 100 samples/second Best Regards, Thorsten.

Hi Josh, for the update cycle I took special care and implemented a nice feature called "dynamic priorities" which samples the last two turned pots more often then the others. Therefore, the latency (or update-cycle) for these two pots is less than 1ms (note that the transmission of a MIDI events gets about 960 µS). All the other 64 pots of MB64 are sampled in between 10-15 mS. Summary: the general update frequency is 50-70 samples/second (MB64), the dynamic update frequency of the last two turned pots about 100 samples/second Best Regards, Thorsten.

Should be a 2200uF - it's time again to check the consistency of all schematics and docs ;-) Best Regards, Thorsten.

Should be a 2200uF - it's time again to check the consistency of all schematics and docs ;-) Best Regards, Thorsten.

Great Frank! :) It seems that Cubase sends the message strings with two different device identifiers - or did you change the ID during the run? The first string goes to device 2F and includes Preparing Connection Cubase SX - Version 1.0.5.58 The second string goes to device 14 and includes Pan Pan Left-Right Page:01/02 How does Cubase react with LCEMU_ID 14 or 2F? If the message handling under Cubase is the only imperfection, I will add an option which allows to display string which are going to any Mackie device What's about the button function, do they work? Best Regards, Thorsten.

Great Frank! :) It seems that Cubase sends the message strings with two different device identifiers - or did you change the ID during the run? The first string goes to device 2F and includes Preparing Connection Cubase SX - Version 1.0.5.58 The second string goes to device 14 and includes Pan Pan Left-Right Page:01/02 How does Cubase react with LCEMU_ID 14 or 2F? If the message handling under Cubase is the only imperfection, I will add an option which allows to display string which are going to any Mackie device What's about the button function, do they work? Best Regards, Thorsten.

Ok, I see - the example file isn't perfect ;-) I didn't assign all button functions to my physical MB16E, since my own version has only 8 buttons (the 4 navigation buttons, and four MIDI triggers; in the configuration file Button number 17-24). However, all other button inputs are functional when I temporary connect two DINX4 modules, but since my desk is currently full of instruments, I had to replace everything which needs too much place ;-) In the next days I will start to build a more compact prototype which allows me to use the LC emulation more on a more ergonomic way - and with much more buttons! :) The navigation buttons are normaly used for the MB menu navigation, but you can disable it in LC emulation mode and use the buttons as normal MIDI triggers. Best Regards, Thorsten.

Hi, I will check the db resolution with Logic this weekend. Which sequencer software are you using? And which possibilities are given by the program to control higher resolutions from external? Best Regards, Thorsten.

Hi, I will check the db resolution with Logic this weekend. Which sequencer software are you using? And which possibilities are given by the program to control higher resolutions from external? Best Regards, Thorsten.

Hallo Dmitry, hast Du das Problem mittlerweile geloest? Wahrscheinlich war der MIDI-Merger eingeschaltet, dadurch ist eine Rueckkopplung entstanden, die Cubase durcheinander gebracht hat. Gruss, Thorsten.

Hallo Dmitry, hast Du das Problem mittlerweile geloest? Wahrscheinlich war der MIDI-Merger eingeschaltet, dadurch ist eine Rueckkopplung entstanden, die Cubase durcheinander gebracht hat. Gruss, Thorsten.

Isn't the PIC delivered with the core module? This must be a fault! :-/ Best Regards, Thorsten.

http://www.ucapps.de/midibox16e.html (remove the buttons, the display, the LED-rings, the banksticks, some software features, and you have a pocket dial ;-)) Best Regards, Thorsten.

http://www.ucapps.de/midibox16e.html (remove the buttons, the display, the LED-rings, the banksticks, some software features, and you have a pocket dial ;-)) Best Regards, Thorsten.

Encoders with inbuilt buttons are coming with 5 pins: 3 for the encoders, 2 for the button function. I see no difficulties - the buttons have to be assigned on the following way: [BUTTONS] # Following Button events are documented in the logic control user # manual, chapter 13 "Control Surface Layout and IDs" # LC event: "select buttons" for the V-Pot section 1 = 90 20 7F @OnOff # select function of V-Pot 1 2 = 90 21 7F @OnOff # select function of V-Pot 2 3 = 90 22 7F @OnOff # select function of V-Pot 3 4 = 90 23 7F @OnOff # select function of V-Pot 4 5 = 90 24 7F @OnOff # select function of V-Pot 5 6 = 90 25 7F @OnOff # select function of V-Pot 6 7 = 90 26 7F @OnOff # select function of V-Pot 7 8 = 90 27 7F @OnOff # select function of V-Pot 8 Best Regards, Thorsten.

Currently the MBMF is working with a 8 bit resolution (=256 values). 10 bits (=1024 values) should also be possible, but only for sending (-> Pitch Bender events, NRPN). For receiving it makes no sense to work with such a high resolution, since the motors are moved so fast that differences of 10µm (10 cm / 1024 values) cannot be realised ;-) Best Regards, Thorsten.

Currently the MBMF is working with a 8 bit resolution (=256 values). 10 bits (=1024 values) should also be possible, but only for sending (-> Pitch Bender events, NRPN). For receiving it makes no sense to work with such a high resolution, since the motors are moved so fast that differences of 10µm (10 cm / 1024 values) cannot be realised ;-) Best Regards, Thorsten.

Hi Dave, for a confirmation you could contact Simeon, he modified the gerber files for "Advanced Circuits" (see his webpage: http://www.soundcreationsinc.com/midibox/) Best Regards, Thorsten.

Hi Dave, for a confirmation you could contact Simeon, he modified the gerber files for "Advanced Circuits" (see his webpage: http://www.soundcreationsinc.com/midibox/) Best Regards, Thorsten.

Hi Dan, yes, no hardware update is necessary for the MIDImon. :) Best Regards, Thorsten.

Hi Dan, yes, no hardware update is necessary for the MIDImon. :) Best Regards, Thorsten.

Hi, you don't have to wait for MIDIbox NG, since the preliminary releases of MB16E and MBMF can already handle with the complete Mackie HUI protocol :) In difference to the features which were already provided by the MIDIboxes, the LC emulation requires only a subset of them - the motorfaders just need to be moved on Pitchbender events, they must send Pitch Bender events, the V-pots must send the ticks based on a special formula, the LED-Rings react on different MIDI events, the buttons need to send Note events, the LEDs must react on Note events, the display must be accessible by the host software. Ok, and there is a special password sequence which was new to me. However, just another variant ;-) The intelligence is not in the MIDI controller, but in the host software... 16 Tracks are possible, but the protocol supports only 8 tracks per MIDI line. So, two MIDI In/Out pairs and 4 core modules are required. Cubase: is there somebody out there who wants to help me to determine if Cubase SX can already handle with the same protocol which is used by Logic Control? I don't own Cubase (and I don't want to see any cracked version in my Mailbox!!!) therefore I cannot test it. I need to know: is the Mackie Control driver already included in the official Cubase SX release? does this driver send any request over the MIDI lines during startup? Or is there a way to send a request manually? For LC, the request is "F0 00 00 66 10 F7" - do you see something similar? If you don't own an external MIDI monitor, you can track these requests by using MIDI-Ox in conjunction with MIDI-Yoke (a virtual MIDI device) Best Regards, Thorsten.