levon

Heres my initial layout design. not sure if ill go for a 2x40 or 4x40 LCD the red circles are encoders, the green ones are LED's and buttons. a nd blue squares are bigger buttons. 2x40 or 4x40 LCD 48 encoders 51 LED buttons 3 Switches. then all the normal midi ports etc..

So ive been reading the MIOS code examples and tried hacking together a few bits a pieces, and had a thought about what im trying to do. i want to have 1 digital encoder that effects the limits of 3 others. so when you change 2, 3, or 4 it will check the state of 1. and if the values of 2, 3, or 4 try to go above the set range, it will bring them back down to the maximum. so ill make a look up table, and then when the value is over that, it will scale it back down to the maximum. const unsigned char Enc_event_map[4][3] = { // k2 k3 k4 ... max depending on what k1 is. {0x10, 0x00, 0x0f}, // k1 =00 {0x11, 0x00, 0x1f}, // k1 =01 {0x12, 0x00, 0x2f}, // k1 =02 {0x13, 0x00, 0x3f}, // k1 =03 etc... }; in void 'ENC_NotifyChange(' something like: // overrun check: if new value is higher then the maximum allowed, scale down. if( new_value >= enc_event_map[k1][pin] +1 ) new_value = pot_event_map[k1][pin]; the code is quite rough.. but is that the general direction i should be going in?

since my original post wasnt getting any replys ive changed the title and tried to clarify my questions. was originaly few q's about controlling different messages with one knob and scalling Read second post. Few more questions from me, while im planning my interface for my G9.2tt midi controller HERE So what i plan to do is have 4 knobs lets call them K1 K2 K3 and K4 i want to scale knob one to send 0-14 (00h-0Eh) and deppending on what k1 is, the other 3 Knobs will have different ranges. so when K1 = 0..... k2, k3, k4 will have a minimum of 00h, but maxium will be 14h, 3Fh, 3Fh respectively when K1= 1.... K2, K3, K4 will have min= 00h, max= 01h 16h, 2Fh respectively. and so forth . and i want to do this for about 11 groups of knobs which means that ill be running 11 if loops for different knobs, will this slow my midibox down too much ill post psedocode for what i want to do, is this right? Knobx(address,min,max) if 0x00 = 0 #if knob 1 of the first group of knobs equals 1 K2(0x01,00,14) K3(0x02,00,3F) K3(0x03,00,3F) elseif 0x00 = 1 K2(0x01,00,01) K3(0x02,00,16) K3(0x03,00,2F) etc etc Now if i have a list of 14 elseif for for k1, and then i have say 11 different groups (A1-K1) is that going to impact on the performance of my midibox. all of this will be sending midi sysex.... of 7 bits, so with 11 groups of an average of 15 elseif situations per group, each with 3 variables its controlling.. now to state it a bit clearer... at any time, there will be 11 'if' loops running at a time, scaling 3 variables each, that are sent out as midi SysEx the input ill most likely be digital encoders. hmm, my eyes have gone cross eyed, if anyone cant understand that ill try and explain it better. thanks :)

i tried monitoring the output of TD drum studio, through midi-ox the same way, and it didnt work, so im thinking it is a problem with the way im routing in midi-ox, so i will have to have another play round with it. or plug the midi out of my computer into another computer. grrr

oh sorry, forgot to say.. it ONLY works via midi, USB is for asio audio only. so i dont have the USB plugged in. Maple midi is the same as midiyoke, provides 4 virtual midi ports.

Hi, i have a Zoom G9.2tt Guitar effects pedal and i have run into a problem. the G9.2tt comes with a piece of software for PC and mac that lets you program the pedal easier and then send them across, you can also go 'online' and edit with changes being made to the pedal in real time. my problem is, my G9.2tt will not send and receive midi SysEx data in its default on state. for it to send and receive SysEx data i have to pulg it into my computer via midi, open the software, and click 'online' then i close the software editor, and untill i turn the pedal off it will send and receive mid sysex data, (monitored by midiox) so i can send a message from midiox, and the pedal will change the settings to what i want.. but once i turn the pedal off, i have to repeat the conecting to PC before it will work again. so the pedal requires a 'handhake message before it Sysex works, and im unable to monitor this message in midiox. when i route the softwares midi out through midiox, nothing is received in midi-ox, and also the pedal does not receive anthing. so maybe i am routing it incorectly. ive contacted zoom about what is required to get the pedal to work with Sysex, but after 5 emails they are of no help, as they do not understand what i am asking for (they are japanise) in the ZOOM software i have the input port maple midi 2, and output maple midi 1 in midi ox: maple midi port 1---> SBlive Midi out SBlive midi IN--> Maple midi port 2 midi from the pedal is shown in the input winidow twice (so its being looped) but the output window once, and the software does not react to anything, and nothing sent from it will show in midi-ox can anyone pick a fault in what im doing? anyone got some ideas? thanks ,Levon

thanks stryd one for the hints. ive been looking throught examples of code and realised how easy it is to send midi SysEx data, with MIOS so there we go. ive decided ill build the two parts seperate.. and can just use the midi thru on one of them. means i can have them a few meters apart, and also only use one if thats all i want. so ill start with the midibox of knobs and buttons, then once that is done, attempt the floor controller. so, for now i got two tasks ill be working on designing the UI, and thinking what ill need to control everything from my pedal, and sorting out the midi sysEx data from my pedal, as zoom do not provide a midi data sheet. im thinking of going for mainly rotary encoders, as some variables (like the delay time) goes from 10ms to 5000ms, but then also a few pots, that ill assign to certian variables to be able to use them easier. so im thinking: 1 CORE 1 LTC (for midi thru) 1 LCD 1 AINx4 1 DINx4 1 DOUTx4 for leds though i will cut down the chips needed for the AIN,DIN and DOUT deppending how many i need of each. one question.. my pedal does not have the BPM tap accessable via midi, so the BPM needs changing by SysEx. is there a MIOS application already writen that will take a series of button presses and calculate the BPM? cheers everyone.

Hi everyone, ive been a long time lurker and posted a bit. but now i have decided to plan on building a midibox :D I hope this post is in the right place. and of course i have alot of questions but i will limit them to a few in this first post. first a bit about me. I'm a guitarist/drummer, etc... and a video editor by trade. i have a small bit of experience in programing C for Blender 3d, and also in python and flash actionscript. i have also be doing DIY electronics for a few years, build a distortion pedal, and 2 theremins, one a midi theremin. I'm also quite resorceful at hacking code together. and know midi quite well. now my questions i will give more detail on what the application is afterwards What i want my midibox to do, is send rotary encoders, or just standard pots as a midi SysEx message to a hardware controller. eg, i want it to send something like F0 41 12 3A XX F7 where XX is the pot or encoder. is this possible with midi box?, i have searched, and not found anything describing it. second, i would also like a button that can send a longer line of about 20-40 bits in length. and on the matter of software, im assuming the answer will be the later... but should i use midibox 64 or MIOS. or will both be capable of what i want to do? which is easier for a noob to midibox.. but not to a bit of programing Application: i own a G9.2tt and i want to make a midbox to control it better, as the on board controls are a bit limiting and the midi implementation is limited to patch changing, turning each effect block on and off, and CC for the assignable expression pedals. i want this to be a bank of pots or encoders, to be used by hand. so it seems midi Sysex is the only way to change some of the parameters on it. on top of that (actually on the floor), i would like to have a bank of pedals to be used by foot, that will change a single effect blocks settings, which would be a midi sysex line of about 20-40 bits. i would like to have say 5 pedals, and an up and down bank button. so i can store it as such: bank1 , clean, soft distortion, fuzz, deathmetal distortion, clean 2. bank2, Big muff, OD-2, etc, etc, etc bank3 , delay 300ms, 450ms, 1000ms, 2000ms, 2500ms. etc etc. i havent dont the calculations yet.. how much memory is available on the chips to store this sorta data, or could i use the bank stick for this? also what is the best way to have the 2 devices in different boxes; would it be better to make one midibox main cpu, and have a separate slave midibox for the pedal. or have the two midi boxes independent of each other and build a midi merger to combine them before going into the G9.2tt i have alot more questions, but ill leave it at these to start. thanks to everyone who helps, its about time i finally get off my arse and build a midi box :)

hey any idea how i would find information about that bit crusher? ive cant find a way to download all the achives of the synth-diy mailing list... thanks

ive buit a friend a Pro Co rat, sounded good, fairly similar to the originals, though the original that i reverse enginered sounded a bit muddy compared to the one i build. my fav effects( i play guitar) are digital delay, analoge delay , reverb and a parametric EQ, i just have a crapy zoom 2020 multi effects, as well as an ibanez mu-405 (i think, dont recall) and i also use a volume pedal a fair bit, and of course i use distortion.

though you would have to tell it to only use the highest note.... cause when you fret a note you are tentioning the string between 2 frets. for say a A note on the low E string, the string hits fret 4 and fret 5. another thing is that when you are playing arpegeios you keep your fingers in position, and pick the notes in time, so you might have to come up with soem sort of 'picking' digitizer.

i use resolume as well, and im planning to make a midi controller at the end of the year. resolume just uses any midi device, so its more of what layout you want.... make it... and it should work rather easily. there is a resolume specific controller being made atm, for sale... not using MIOS. but there are pictures of the design of it http://www.resolume.com/react/index.php

ive built the jarcar theremin, it works, but it doesnt sound good :(

when i read that i cracked up laughing, so does that make me a geek? :D

i guess nuendo, cuebase or pro tools will do this well, though im sure there would be a cheaper program that could do it also