MetroSonus

that's awesome. the screen as noted would be for trouble shooting, but not part of the actual usage. Add a wireless midi connection and im rockin! My goal is to snag one of these off ebay .. embed the whole thing into that and use it as a live synth controller as well as a controller for Ableton Live. I want to embed a matrix of microswitches so that i can trigger things as well as switch patches on my synths within live.

does the x4 mean anything different ? I could use rotary encoders to the same effect as pots on the DINx4 (happy? ;D) ? "Not sure why you have the LTC (LED/Thru/COM) module?" Midi in / out.. or is that on the core? from the diagram I thought it was a seperate module. The code *looks* simple, but I allways manage to screw stuff like that up. I took a java class in college and I think we moved way to fast. When I get to that point I'll probabaly need help. "You might want an LCD for troubleshooting, and a DOUT if you want any LED's for flashy lights." Good point! and hmm...... Maybbbe. It's for use live, so everything is going to have to be based off of touch. If I had LEDs they'd be for the benifit of the audience. Do you know of a situation in which they would be handy for troubleshooting? Also what's the power on the midibox? can it run off batteries?

Ok more testing my understanding... For my keytar project.. I'll need: 1 core module 1 LTC 1 AIN 1 DIN I'll only need 12 of the 32 availible controllers on the DIN for my 1 octave, and then 2 for the octave shift keys, leaving 18 to either use or not for various other functions. Then I would simply write a code that will say for buttons # 1-12, which note value to output? The AIN will give me enough pots for cut off / resonance and maybe some effects sends. Question, I dont know if i'll do this or not, but would it be possible to use an analog joystick in place of two pots? then to just run the outputs of each pot from the stick into the AIN? It all seems clear except for the code! that'll take some work. I have a bit of experience, but not much. I'm up for a challenge though!

So let me see if i have this right .. I create a DIN module that gets connected to the 12 switches I want to use as keys. It connects to the other modules as usual, yet the program is custom written to encode activity from the switches into midi note on and off data? So in theory it should be ok to create a bit of code that would also allow me to change octaves based upon the input of say two particular pins? for up and down? So i dump the custom code via sysex.. hmm so it's the core that recieves the sysex dump? and there I specify that pin on DIN module are for note on and off date? I think I'm getting it...

ok, thanks! I gotta lota reading to do :o Trust me, I'll be back with questions.. lol

Hmm ... I guess my problem is a lack of understanding... What in the DIN module transmits the note values, is it built into the firmware? How would I know which button went to which key? Also is it possible to build a set of octave up / down buttons? Mainly what I want to do is to create a guitar hero like keyboard controller using momentary switches as keys. Mainly it's so I can play synth basslines live and stuff. Most of the midibox stuff seems straightforward when it comes to knobs and sliders.. but the keyboard stuff has me baffled.. thanks!

are there any good resources for making keyboard modules? I cant seem to find any.. I want to make a simple one octave controller with simple note on / off and combine with a couple other modules. Thanks!

Hmm roughly a 5x5 grid. The problem is, each vertical column can only play one clip at a time. the MIDIBox would have to know that the column is a group, and that only one "active" light can be on at a time. The way it works is when a clip (sequence) is triggered in that column, the current one stops playing at the end of its sequence and the new one starts. So the light would have to jump to the button that was just pressed.

Say I got bi colored LED buttons for Live 6, one color to specify a row, lets say horizontal rows will be blue, and when i trigger a sequence with the button, is it possible to have the LED for that button turn the other color? That way I will know what sequences are running.. Is this within the capabilities of the Dout board? or would it require custom programming.. ? thanxs..:)

Ok, MIDIBox is really starting to make snese to me, after two years of sort of reading it on and off. I'm using Live 6 quite seriously, and obviously need a custom controller. What I'm wanting to do is create a midibox 64 or so small enought to sit ontop of my lapoptop's keyboard. What im wanting to do is have a matrix of roughly 5x5 buttons for triggering clips, 4 knobs for EQs ect and two sliders for volume and X fade. So If i'm getting this right, the DIN module would accept the buttons.. and since I'm dealing with such a small footprint, I wanted to use momentary micro push button switches, normally open. Would these work? If not what would? The AIN module would run the 4 knobs, which are your typical linear taper pots? And the sliders as well.. which are just sliding pots right ? When this is built and working, I would then connect the midi out to my microkorgs midi in, and just activate the midi map function of live and then start pressing buttons and knobs to assign them? In general that is.. ok sorry about all this, just wanting to know all what i'm going to have to source out before working on it! thanx!