Cyril

Yes you can create .xml files from within cubase and save them but in this way you can't assign a function to a pots without choosing a device. For example you create a new project without any Audio or VST instrument track: in the generic remote configuration windows first you choose "VST Mixer" but then you have only the choice between "device" (périphérique in french) or "selected" (selectionné). If you choose device it appear like that in the .xml file: <entry ctrl="Track (01) Fader"> <value><device>VST Mixer</device><chan>-1</chan><tag>1025</tag><flags>0</flags></value> And if you choose selected, it appear like that: <entry ctrl="Track (01) Fader"> <value><device>VST Mixer</device><chan>-2</chan><tag>1025</tag><flags>0</flags></value> In this way you can't say to Cubase not to choose "device" or "selected" but to choose the first track you create. The only way is to modify the .xml file by replacing the number -1 or -2 by number 0, for the first track, by number 1 for the second track, and so on... Best Regards, Cyril

I'm using Cubase SX 1 (because SX 2 generic remote control seems to be really bad for the moment) and on my midibox64 I have 1 fader, 2 button and 4 pots for each tracks. I wanted to create a generic remote .xml file to assign some functions (volume, eq, pan) to each fader, pots and buttons before any vst instruments or audio tracks were loaded. First I have noticed that .xml files can be edited with windows wordpad. I can save the file and it is still working. The file is divided in two part (like in the generic remote configuration window). The first part describe the controller name, status, midi channel, adress, etc. It appear like this: <ctrl><name>Track (01) Fader</name><stat>176</stat><chan>0</chan><addr>40</addr><max>127</max><flags>1</flags></ctrl> In the second part, the controller assignement is described like this: <entry ctrl="Track (01) Fader"> <value><device>VST Mixer</device><chan>0</chan><tag>1025</tag><flags>0</flags></value> First you can choose the device (in this example it's the VST Mixer) : <value><device>VST Mixer and then the device channel : <value><device>VST Mixer</device><chan>0 If you choose the channel number 0, the controller is assigned to the first track in the VST Mixer. I think Cubase assign first the audio tracks, then the VST instruments tracks. Now you can choose the controller action (tag). It consist in a number (Cubase give a number to each controller action): <value><device>VST Mixer</device><chan>0</chan><tag>1025 In this example, the number 1025 consist in track volume. To understand which action correspond to the number I have selected them in the generic remote configuration window and then I have exported it and opened it with Windows wordpad. For example, number 1027 consist in track mute, number 1028 consist in track solo, number 1162954544 consist in Eq 1 Gain. Finally you can choose the pot behaviour (flags) : <value><device>VST Mixer</device><chan>0</chan><tag>1025</tag><flags>0 With number 0 no flags is defined. Number 256 consist in toggle mode. After importing the new .xml file everything is working fine and Cubase assign every function I want everytime I create a new VST instrument or Audio track ;D I hope this can be usefull for some other Cubase and Midiboxer users... There are other functions that I can't control (for example all "command" functions because of the flags). I'm still searching a way to reach it. I don't understand why Steinberg doesn't provide a good and complete explanation about how to configure the generic remote (I mean a more precise explanation than how to choose the midi in and out :P ) or to program your own driver... Best Regards Cyril

Thanks you Thorsten, you helped me solve my problems: First I have enabled the midi-to-com option and... Cubase receives normal midi messages again. Then I have disabled the midi merger option and sending sysex works great. if only I had read better the Midibox64 tutorial ("If you connect the MIDI In of the MIDIbox with MIDI Out of your computer, you should disable the MIDI merger in order to avoid endless feedback loops")! ::) I don't know why but with the midi-to-com port I have no more random data. Now everything works great except that I have some problems requesting sysex with VMidibox, but that's no a big problem because I don't really need it the way I use my box. So now it's time for music!!! 8) Best Regards

The box dimensions are 450 x 255 mm... I bought a prefabricated case and I drilled all holes by hand (certainly the hardest part of the project). I saw your new Midibox design in the Design Concepts forum... It will be very nice too ;) Is my english so bad? ;D If you think a french speaking midiboxer, yes! But I come from the french speaking part of Switzerland...

I have some midi transfer problems with my Midibox64 (based on the PIC16F). In the beginning I was using the midi in/out connectors but I had strange midi messages every second when using Cubase (like aftertouch or similar midi messages). Sending sysex to the box was possible but didn't work sometimes resulting in strange letters in the LCD display (I had to restart the box). So I decided to try the midi-to-com port (I removed the optocoupler and pluged the Max232). Now I have no more strange midi activities (except that Cubase receives only pitchbend and aftertouch messages from the box) but I can't send or request sysex any more. I tested all the drivers but none functions. Another strange things: the green LED remains always lit... How can I know if it's an hardware problem without reprogramming the PIC with the test firmware (I'm afraid to damage the PIC by removing it from the socket :-[).

After checking all my connections i still have some (little) problems : 1. led's 1,2,3 works fine but led 4 doesn't lit at all. 2. led 24 doesn't lit when i push the corresponding button, but both led 22 and 24 lit at the same time when I push button 22. 3. led's corresponding to button F1 to F4 works in toggle mode only when I disable navigation buttons in Serge's editor. I've tested my midibox with Cubase and every buttons works fine (btw, this box is amaziiiiing! Thanks Thorsten you're a Genius :D). Another problem: in Cubase I receive every 5 seconds some aftertouch and program change events. I think it's a problem with some pots that are not good isolated from the front panel, i'll investigate in this direction and check some connections... Best Regards, Cyril

I looked carrefully to the MBHP core schematic and I discover that both midi in and out plugs were reversed (because my midi plugs are mounted upside down) ;D Thanks Thorsten! Best Regards.

I looked carrefully to the MBHP core schematic and I discover that both midi in and out plugs were reversed (because my midi plugs are mounted upside down) ;D Thanks Thorsten! Best Regards.

My midibox 64 is build and everything is working good except that my box doesn't send or receive midi events... It's seems like I have hardware problem but I can't locate it (I'm a beginner in electronic :-/). Can anybody help me finding the problem? My midibox has the LTC module and only the output led is (strangely) always lit. I get aprox 5V from the output port and 0V from the input port. Thanks in advance for your help!

My midibox 64 is build and everything is working good except that my box doesn't send or receive midi events... It's seems like I have hardware problem but I can't locate it (I'm a beginner in electronic :-/). Can anybody help me finding the problem? My midibox has the LTC module and only the output led is (strangely) always lit. I get aprox 5V from the output port and 0V from the input port. Thanks in advance for your help!

Thanks Thorsten! I have tried Serge's editor (which is wonderfull) but now I can't send sysex to my box :-/ I think it's a connection problem because the LCD shows no reaction when I send or request sysex. I'm using the midi output of my soundblaster card. I had no problem with it and my synth, so I think the problem isn't there. Another thing is strange: the midi out led stays always lit... I'll verify all connections and hope to find the problem. Best Regards, Cyril.

Thanks Thorsten! I have tried Serge's editor (which is wonderfull) but now I can't send sysex to my box :-/ I think it's a connection problem because the LCD shows no reaction when I send or request sysex. I'm using the midi output of my soundblaster card. I had no problem with it and my synth, so I think the problem isn't there. Another thing is strange: the midi out led stays always lit... I'll verify all connections and hope to find the problem. Best Regards, Cyril.

My midibox is build and everything is ok except that the wrong leds are lighting when I push buttons... In an old topic Thorsten wrote that the new midibox 64 firmware enable led mapping but I can't understand how to achieve it. Can I access led maps with the midibox menus or do I need to send sysex or to use Serge's editor? Btw how can I configure leds to stay lit when I push a button (because now they stay lit only when I hold the button pushed...) Thanks in advance!

My midibox is build and everything is ok except that the wrong leds are lighting when I push buttons... In an old topic Thorsten wrote that the new midibox 64 firmware enable led mapping but I can't understand how to achieve it. Can I access led maps with the midibox menus or do I need to send sysex or to use Serge's editor? Btw how can I configure leds to stay lit when I push a button (because now they stay lit only when I hold the button pushed...) Thanks in advance!

I read this topic one more time(http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1044220843;start=4#4) and Thorsten wrote: I'm still wondering if the Midibox 64 firmware enables to control LED's with the host application to display track volume... :-/ I have one DOUT module which means that I can connect 32 LED's. But I'm only using 20 LED's to display buttons status. Can I use the last 12 LED's to display a master bargraph for instance? If not, can I build a Midibox 16E (which means 1 Core Module with Midibox 16E firmware and one DOUT module) without encoders, functions buttons and LCD, to display 16 tracks volume, how do I link it (via MIDI) to the Midibox 64 and can I control it with the Midibox 64? Excuse me, that's a lot of questions and I don't know if they're clear enough...

Hi RAF! Some people here have already succeeded to use led bargraph (VU-meter) to show sound signal level with Cubase SX. See this topic : http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1039632633 But I think it's only possible with Midibox 16E (and you have to take care of midi bandwidth). The idea is really cool... ;) I Think I'll try to build it on my next Midibox!

A new era has begun... ;D

Hi all! What do you think about a future Midibox "all in one" like that: screenshot comes from http://www.kvr-vst.com Coooool.... ;D This is a "new concept" (I've already seen a open system concept not so far ;) ) by Open Labs (http://www.openlabs.com). We have already pots, sliders, encoders and buttons... The display, pc keyboard, pointing device, hardrive, motherboard, etc. seems not to be a problem to find... But what about a midibox with an integrated midi keyboard and pitch/modulation wheel?

Look at this link to know how to connect buttons to DIN module : http://www.ucapps.de/mbhp/mbhp_dinx4_32buttons.pdf You can choose how many buttons you would like to connect. But note that four buttons are requiered to control the Midibox internal program (snapshot, exec, right, left). So you can choose to connect from 4 to 32 buttons... Just let unused digital inputs open...

Salut Gilles! Trop cool d'avoir un forum en français (même si j'habite en Suisse en fait... heureusement qu'on entend pas l'accent sur un forum... ;D )

Je crois (en lisant les FAQ) que le code source n'est disponible qu'en faisant la demande par e-mail à Thorsten...

ouais c'est vrai ... j'avoue... ;) Exactement! C'est ça qui est cool... :D

DOUT Module lets you connect LED's on your midibox. They reacts when you push buttons (DIN module). DOUT Module isn't necessary but it's usefull to see the status of a button (on/off) or of a track (mute/solo). For more information on how DOUT module works see this topic: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1044220843;start=4#4 Hope it helps... :) Best Regards

Thanks! My midibox has a display and Serge's Midibox editor is a must...so I'll take care of the order ;) Best regards

Hi all! My pots are mounted on a stripboard. Now I want to connect them to the AIN module but I am wondering if I need to connect them in a specific order. has to be the first pot (A0) connected first to J7 (Vs;Vd) and so on? A0 = first connected to J7 A1 = second connected to J7 ... Or can I connect them to J7 like I want?