robin303

Cool! I'm thinking about "matrix" circuit board, the size of my whole frontpanel. You know, the boards with premade holes. Then I can nicely fit all pots and buttons on it, instead of a whole mass of wiring :)

A quick question: Has anyone of you ever used these buttons: I think they are really cool! They are the Reichelt DIT and DTL types: "Digi-taster". Euro 1,75 each. What I was wondering, how can these be fitted to a front panel? Or should a circuit board be used to mount them? ???

I did actually consider the MIDIbox16 but I think it really lacks knobs, so to say. The point is that my way of music making is quite physical. I want to turn knobs, press buttons and then record that live action in the sequencer instead of doing it the other way round :) Here is a pic of one of my favourite 'real' instruments that I use a lot: the Yamaha SK30! Music making with this beast is really a physical thing as you are turning knowbs and sliding faders all the time. Unfortunately it doesn't have midi yet.. Anyway, that's what I'm looking for: controlling the super-powerfull Reason software with a box of knobs! ;D I think however that 64 pots and 64 buttons must be quite enough to program Reason devices for live recording. It's not that I want to control the whole program with one box. Just one or two devices at a time. I have been trying to get the transport buttons to work with Serge's vMidiBox but so far I have not been able to do so. I think the point is that I really don't understand this whole "Event Type" business: Captain Hastings, what should be the correct setting for a vMidiBox button to trigger, for instance, the Reason play button? And did anyone figure out how to control the pattern selection (1 to 8) in the Matrix and Redrum modules with midi remote? Before building a box, it;'s really good to first know what you can actually do with one. Thanks to Serge for the great Virtual MidiBox software!!

Wow, a rock-solid reply ;D This clears up some of the questionmarks hanging around my head! ??? This definately answers my question. I went into reason right away and discovered the fact that there's no midi out :( So it will be "absolute pots" then... The nasty thing will be that if I change banks while performing, all knobs will change position right away. Ok, but what if I, for instance, turn a mute channel off with my mouse? The MIDIbox will not get a signal to turn the led off because Reason doesn't send out MIDI data right? Will, from that moment on, the led be inconsistent with the actual on/off value in Reason? I understand what you mean. But why wouldn't this little trick work? What is also weird is the fact that, when I select "Edit MIDI remote mapping" in Reason, the transport buttons DO have green arrows on them. This indicates that they can in fact be mapped to a midi key? Cheers, Robin

Hello everyone in this fine community! Here's my first post on the board.. My name's Robin and I'm planning on building a MIDIbox64; I have just ordered my PCB's at Mike's site and I have a big orderlist ready to send out to reichelt monday. My primary target for using the MIDIbox is controlling the various aspects of Reason 2.0 in a live setup. I have a cool design in my head but also still some questions .. ;D Can I use 360 degrees pots (unlimited turning) if I set the midibox in relative mode? Or should i stick to the 300 degree ones like the P6M-LIN 10K at reichelt.de? Can you give me some examples of how the DOUT module works and what can be done with it? I did see some posts on this subject in the forum about ledrings, vumeters and leds as feedback to the DIN module, but I just don't understand the concept of the DOUTX4 (I did order two of them though) Is there a way to build the powersupply into the box or should I stick with an external adapter? Would anyone have an idea if it's possible to control the REWIND and FOWARD buttons of reason with a single jog wheel? Well that's my first list of questions :) Cheers, Robin