ultra

at a local electronics shop i got headers design to be plugged into one another, in-line. they're handy for 2 or 3 pin connections. sorry i don't have a part number for you. so those, along with phil's solution for the bigger header could work. but personally i would remove all the cable and use proper headers and connectors, at least on one end.

grnsky: please attempt to better research this. three reasons: 1. you're asking very fundamental questions that have been answered on the forum, wiki, this thread, etc and don't need to be answered again. if the answers confuse you, then you take a step backward from there and research whatever the answer pertains to. 2. you'll improve your researching skills and overall understanding of how it works and be able to better answer your own questions in the future. 3. your accomplishments will feel more rewarding. please know that nobody is trying to be unhelpful. it's just that the help already exists and it's up to you to find and use it. if you looked over my history of posts, you'll find me doing some of the very same things, and getting the very same answers from people (read read read). but as i became better about doing my own research, i also became much more understanding of how midibox works. and a lot of my past research has already answered future questions. ultra

well the range is ok because the 7805 is a 5v regulator. if you're going > 1A, you'll want to use the 2A version of the 7805 (forget the part #). i'm not sure if a higher input voltage will give you more current. in a circuit that doesn't have a regulator, of course higher voltage = higher current. but i think that because of the regulator, current draw will be based on 5v (maybe someone else can confirm if i'm correct?) because it's all post-regulator. i can say for sure though that you should check your overall current draw once the midibox is completed and make sure your dc adapter's rating is higher. in previous incarnations of my seq, i had > 1A draw and had to switch to a 2A regulator and a dc adapter that allows for 1.5A. ultra

the buttons just make an electrical connection (a short) between vss and the data pins. when you press them, it loads the DIN shift register and mios scans it to see which buttons have been pressed.. encoders work sort of like two buttons. one button to turn one direction, and another for another direction. however you need to tell mios where the encoders are because they actually create a series of pulses that tell mios which direction they've been turned. for the buttons, single pole works, as do any other number of poles. all that matters is you connect a data pin and vss to poles that are not connected when the button is not pressed, and are connected when the button is pressed. video game buttons work for this, i believe. any normally open, momentary switch works. for illuminating switches, you have to drive them with a DOUT module. consider the LED to be a separate thing from the switch: switch is pressed (shift register loaded on DIN module) core scans for pressed switches core executes code on switch press - code could include telling an LED to illuminate with a DOUT module if you only wanted the LED to illuminate as the button is pressed, you could use a two-pole switch, as long as the poles are always isolated from each other. one pole could be connected to the DIN module, the other could complete a circuit that connects vss/vdd to the led and a resistor. ultra

congratulations on your seq. i'm almost done with mine and your post is getting me even more excited about it :).

yes i suppose it has been. i haven't yet looked into the midi router application because i don't have enough gear yet to need it. of course that's slowly changing. have you seen the midi delay in the toys of the week thread?

i'm not sure i'll yet have a use for this, but awesome! i used to write midi applications in VB and i think a lot of people underestimate what you can actually do with the language. here's some proof :). in fact i was in the middle of writing a sequencer in VB when i came across the midibox seq (never built anything electronic before then). i never finished it because i was too busy emptying buckets of drool. any chance you'd make this in c, on a midibox? ultra

is your sequencer sending sync on its output?

another update. i'm still waiting on replies and payments from a few people, but the boards are on order and should arrive in about 10 days. deep88 and petterniklas: according to my records i've sent you a pm asking for shipping info and haven't received it. please pm me with your shipping information so i can make an invoice. valant, please pm me and let me know what's going on as my records show the invoice has been sent. thanks, ultra

in ableton live they are called signature numerator and signature denominator.

well if they do, they can't keep up.

yeah i like it. it's basic but it was easy to wire up a proto board and the panel was pretty cheap. it fits into a pactec pt-8 case. :)

yeah here it is

thanks dcer10. unfortunately i went ahead and ordered a schaeffer panel so no slave button. however, once i learn about how it all works, i'd like to redo this one in c because i think some cool modifications could be done and i don't know assembler. stryd and i were talking about cc sequencing a bit and that might be a fun add-on. but at the very least, i want to re-write it anyway so i can learn a bit about timing, time delays, and that sort of thing. and i could also have it store last used settings to a bankstick. i'll post some pics soon. it should be done in a couple weeks. i'm just waiting on schaeffer. :D

sorry i meant the mackie control

i'm definitely bidding on this one. :)

well check the ucapps page. there's now an ethernet module on there, but the page is right now under construction.

well it's official. the ethernet module has shown up on ucapps, and i'll be using it for liveapi instead of the way i've been doing it. i never got over the feeling that this is "hacked" and would be using too much midi for it to work properly. with ethernet, i'm pretty sure i can use whatever data i want with no worries. liveapi has the option to connect via telnet and this seems to be the right way. i can transmit any data i want without worries about what protocol it fits into. so this unfortunately means that midibox live will be using core32 only. and i won't be going back to the pic based core to make something work on there. core32 just makes it too easy, and i personally don't have plans on using liveapi for anything i'd make with the pic based core. also, this will give the opportunity for OSC communication with max for live. i'm not sure where that will take me and it's not a high priority right now. using midibox to communicate directly and properly without the need for another control layer like mfl is my goal. this still doesn't get around the problem of ableton updates breaking my code. however, i think i'll start with the newest version of 7 and go from there. when 8 comes out, i'll see what changes need to be made and i can release updates from there.

hey at least you're using chips manufactured in 1992.

the paia stuff is pretty easy because of the guides/tutorials. it's pretty much step-by-step. my girlfriend is just completing her theremax and has never worked with electronics before. if you go with a 6582, the pt-10 case seems cheapest at allied electronics (http://www.alliedelec.com/Search/SearchResults.aspx?N=0&Ntk=Primary&Ntt=pt-10&sid=11FB9D74305C). it's about $7 more at mouser, which is surprising. might be a moot point if you're not in the states.

chronic this is the dog glcd. i think this is awesome phil. it reminds me of the hidden games on our scopes at school. some have tetris and others have centipede.

just an update: still waiting on payment from six people, so i should be able to order the pcbs very soon. thanks to all for being patient :). ultra

so did you buy these? i'm in for a couple, if so.

i tried this out and it works fine. you just need a two-pin jumper from the gm5's available vss/vdd to j2 of the core, like nils said. for current requirements, by default i think this will only allow 100mA (maybe it was 200?), so check your current. if you edit the code appropriately and burn the eeprom for the gm5, you can get up to 500mA (but i wouldn't go quite that high in case of spikes). i got this working on an ultracore (core + 4x IIC + banksticks) with two bright optrex lcds at about 400mA. i might have had some other hardware attached as well. i don't remember offhand how i did it, but i can look into it if you need > 100mA. let me know. ultra

so i've finally come back to this project and i think i can quickly get it done now. i've replaced the 30 buttons with 15 encoders. although i'm not sure if this is completely practical or not. do any of the buttons work as "modifiers" where you have to hold it for another function? or are all buttons just a quick press, and can be replaced with encoders? thanks, ultra