levon

so my original idea of a midibox was a bit ambitious. so ive decided to make it a bit simpler. i want to just make a few buttons that send midi messages. make it as simple as possible. is it possible to just attach a few switches to the the DIN plug on the CORE and not use a DIN Module? and will the same work for AIN and DOUT? thanks, Levon

I think when ever you read a post buy Stryd, you have to remember hes Australian.... we have a weird sense of humor here in australia

hhahah... whoops yes i ment to post this link http://ucapps.de/mios_c_set_dout.html

have a look at this code.. it will drive 128 LEDs deppending on the midi note played.

live can be used as a live sampler, im not heaps familiar with it, but kid beyond uses it that way check out this video http://www.ableton.com/_common/downloads/pages2/artist_kid_beyond/kid-beyond.mov

for the switching effects on and off, have a look at http://www.geocities.com/thetonegod/switches/switches.html

i saw a documentary on Moogs being made.. heres the info page of it here i remember something about the xypad just being a plate of metal that contacted with your finger... i cant figure out how it would work. maybe have a look round some torrent sites and you might find it.

Maybe im missing something, but with most delays, you can set the feedback to 0 and ballance too 100, and you will only get the delayed signal.

Thanks Cimo, i found ones that will work fine, and the cost isnt much more then if i was to buy the DPDT footswitches here. thanks

Do you think those switches would be suitable for stepping on? they do look good, as they would have a soft touch. ive been reading the wiki on your pedal board box but it wont work for what i need. im making a pedal board to control my Zoom G9.2tt, unfortunately everything besides program changes, and 3 expression pedals, need to be changed via SysEx messages.

Im planning on making a foot controller with Mios, Locally i think the only foot switches i can get are DPDT 'stompbox' style like these jaycar link as far as i can tell these will work with with Mios, but will that take up to DIN inputs? one for each pole? i want to use them as no latching, so what is the best way of hooking them up? im looking at getting about 20 switches, so they will be $4.95 each, but if anyone knows any other cheaper suppliers, Australian or otherwise illd appreciate it. thanks, Levon

Was alot quicker then the website said, got my screens yesterday :D

well i have ordered 2 of the blue ones, should take 3-4 weeks to get to australia... :(

sorry, Newb question.. but will these work with any MIOS midibox? or only Wilbas SID? thanks, Levon

Ild be up for buying 4. thanks, Levon

sorry, long time since i posted, but i finally cracked it, had to get another midi interface and go out of my computer, and back in. so it sends a message that turns on midi sysex sending and receiving. :) ill document it if anyone wants it who has a Zoom G9.2tt

apart from the Java editor, what else could you use help with? and what is the follow up project your working on? any details?

hey Stryd, did you make sense of the file i sent you? it is a bit of a mess. any better idea of how it can be done now? thanks.

hey stryd_one, check your Private messages

maybe a custom LCD driver would work, but you would probably need a seperate core just for the display. check out http://www.midibox.org/forum/index.php?topic=7724.0 he uses 2 240x64 GLCDs and in the documentation he has the driver he wrote for them.

Hey Stryd_one, yes the midi implimentation is preaty bad, and zoom wont do anything to fix it. they wouldnt give me a midi sysex implimentation chart as they dont want the end user to be able to use it...so ive had to work it out by monitoring in midi-ox. ive been a bit overwhelmed by all this midi box stuff, so i probably havent been explaining it so well. ive had a quick look at midibox UC, it looks great, i like the idea of the screens displaying the values in a list like that. though for my midibox i dont want to have any menus, i want every controll available from the knobs, ill have a better look through it over the weekend, but it looks like it will save me coding alot of stuff that is already done, ill clean up the xls and finish filling in all the values on the weekend... and send it to you PM thanks, Levon

hahah, yesterday was just one of those days where your brain decided F*** you, im not working today. yes i ment to say DOUT.

i believe you can only have 64 leds with 1 DINx4... so that is only 8 Led rings per DINx4 so with 4 DINx4 you could have 32 led rings.

ok i see what your saying. read below... ok cool im just concered that having that many variables would take up more space, or slow the processor down.. but what ever you think is the smarter way of doing it i will do. my G9.2tt uses midi system exclusive data to change any setting on the pedal. so lets say i want to change the efx1 block i would send the message F0 51 42 31 01 01 01 00 F7 to change it to the auto wah effect or F0 51 42 31 01 01 02 00 F7 to change it to the booster effect. so i have come to F0 51 42 31 AA BB CC DD F7 where AA is the Effects block (ranging from 01 to 09) then other functions use up to 19 BB is the parameter being changed and CC and DD is the value, DD only used when CC gets higher then 7F (only on the delay times) sending F0 51 42 31 a01 b01 c01 d00 F7 a01 is the effects block (efx1 in this case) b01 the parameter (01 is which effect) c01 is which effect (auto wah) d00 each effect block has a different number of effects in it.. so a different range.. and then each effect has 4 parameters, each with different ranges. so the auto wah has 4 parameters.. position, sens, resonance, volume that have a max of 01h, 14h ,1Ah and 64h respectivley the booster has different max for each parameter. ive got a list in open office calc(excel) of the max of each effects parameters, and they wont need to change ever. so is it better to remove it from the main application and put that on the bankstick? and in regards to limiting and scalling.. if i was using a Pot, i would want the full range to go from left at 0 to right at the max of that parameter. for encoders i would want it to max out at the max of the parameter turning clockwise, and bottom out at 0 turning counter clock wise.

sorry... im still considering weather to use encoders or pots.. so with encoders its limiting, pots its scalling, both methods would use the same variables, but process them differently. so for now i guess i will go for Encoders, and later down the track if i need to re write the code for pots i will. i know that the min of every parameter is 0, so i dont need a minimum value. but deppending on what K1 is equal to, i want K2,K3,K4's max to change ie when K1=0 ,the max of K2, K3, K4 are 01,1A,64 respectivley K1=1 ,the max of K2, K3, K4 are 6A,14,32 respectivley and so on and so on till K1=14 So it would be better having 1 list(array) of all the variables in a look up table, right? like this // k2 k3 k4 ... max depending on what k1 is. {0x01, 0x1A, 0x64}, // max when k1 =0 {0x6A, 0x14, 0x32}, // max when k1 =1 etc... {0x13, 0x00, 0x3f}, // max when k1 =14 and i also want about 11 sets for the different effects that i will be controlling. which would mean i would need 3 x 11 x 14 variables for the maximum values. A2,A3,A4 when A1=0-14 B2,B3,B4 when B1=0-14 ... K2,K3,K4 when K1=0-14 which is a stupid amount of variables. Instead i could have 1 table per effect, and then if i want to find the value of effect bank A, knob 2, when A1 =5 i just have to look up enc_table_A[4][0]. or am i missing something?