technobreath

Nils, this aint a single midi i/o - I need 4 i/o - transpose 4 instruments at once (or seperate transpose settings for each port if I feel like it) - this is mostly input from keyboards to VSTi. - I usually play with 2 or 3 keys, and one of my weaknesses as a musician is that I use transposing a lot, have too little practice playing in for example B, and all those funky ones hehe. So what I'm after is a box where I can simply transpose in between songs or in the middle of songs. Some times that happens without it being planned. So This is primarily to make it as slick and flexible as possible for me in live situations. I can always set the transpose settings in the host (I use BloXpander - extremely happy with that - in live situations), but that aint that flexible. I need to configure each setting and save em as subscenes or scenes. On the stagepiano (one that I borrow every time I gig since I don't own my own that portable piano yet), all midi outputs are filtered through the transpose settings, so I can easily do what I want with midibox in that piano, but the same doesn't apply for the other controllers - there it involves more clicks here and there to get to the transpose settings. So I figured, I want something that does the same as the yamaha stage - for all controllers. And maybe I one time need to put it between midi out and midi in on the synth, turn off local control too. All in all, tho the function of the box is gonna be simple and "cheap" - I think this will do exactly what I need no more no less. I was under the impression that 4 midi i/o like this would be simpler and more realistic, more stable etc on the lpc core? kpete. That's not gonna be an issue I believe - since the transposing happens (I can't think of any exceptions) between songs, or parts of songs whe I don't play anything. The few songs that this is a problem for, fast transitions in transpose settings, I play with two different controllers, so when the time is close, I transpose the controller I aint using at that moment, and it will be ready for me to just throw my hands at when time comes. :).

Thanks guys. I'm not used to digging in the code for midibox (yet). But this seems easy enough. Am I correct that I can do what I want the app to do with a lpc core? Nils:

Yo. Good to see you got my back :). I often overlook stuff like this. In this case I didn't see there was two places you could order the DK38. I'll change it. The customs fees... the first list is above the limit already. If the total (the goods including the shipping) amount was just short of 27 euros with todays numbers, it would be free. 200 norske kroner is the magic limit. Often it will go straight through though. But customs fees is something I always something I take in account when importing. If it goes through, bonus :). Most important thing is that the package is marked with cn22 sticker (or whatever it's called) and that it is clear what is in the package and what it's worth - if customs stop the package because they are not sure what it's worth, or what's really inside it, it could easily be a couple of weeks of mailing paperwork back and forth to get it. :)

Haha! Code is ok, but there's just so much code :( You happen to know where to look too? :)

Thanks hawk! I'll dig the seq4 code and have a look! :) Many greets from Hoth :)

Yo, it's been a while since I was wondering what subforum to put a thread in, but this might be the best place for it. I'm planning a "simple" box, 4 midi i/o - a prosessor - that simply transposes the incomming midinotes on a midi input. Either globally over all 4 midi ports or one by one. I'm no coder, but as far as I understand I can use the LPC stuff I have laying around on my workbench (for ages now) for this. My question is really nothing more than: Where do I go looking to find code examples relevant to what the box is supposed to do? If the box is small in size, I'll have some select buttons, a LCD and an encoder on it. If it turns out it has to be bigger, I'll include buttons for selecting a tuning directly (that will be -12 to +12 semitones) instead of having to turn the encoder for each step, tho this is also a fast solution. Some LEDs will go with the buttons too for status indication besides the info from the LCD. Anyway, this is a rather simple and boring project for being a midibox, but feel free to give me ideas :P hehe.

Yeah, this looks very promising - and interesting indeed! I have been thinking on and off about building a cnc myself, but it's still a very intimidating thought! :P Very nice work!

Agree with all of the above. and: I also think we should consider the scenario, that many sellers of the same products in a "small" community, would probably cause all of the sellers bleed money. I am pretty sure that putting together kits, get PCBs produced, managing the shop, costumer support - and all the rest which I don't even have the knowledge to list here :smile:, takes a lot of time. A seller / shop also needs to be solid, steady and not on / off when it comes to all of these points. Running a shop like this is basically a full time job, and I for sure wouldn't like to do all that as a sparetime activity. I simply wouldn't have time for anything else. And most of us have families, many have kids, including me, and finding time to even build the kits can be challenging. So hands in the air for you SmashTV for making this available for us! :smile:

I was thinking, was it the link I wrote he means? Hehe, The main outs are inverted, it looks like. Not being the circuit designer, I would still claim that it is a compromise to make the circuit simpler. The IC is quad opamp? And the guy designed it this way to get away with only one chip. Maybe it would be smarter inverting the headphones instead then? Maybe free Eagle was used to route the board, and there was simply not space for more opamps :)... When I design this stuff using eagle, I use a seperate PCB for the main outputs (4 opamps) and a seperate board for headphones amp. Then if I need more outputs I have them on seperate PCBs too (usually two outputs each board). Not a optimal solution, but when designing stuff for home-etching like I usually do, there's simply just no room for a lot of top layer routings and tiny traces :P. If mixer design is low channel count, like this, the inputs also goes on the main output pcb. ;).

What NorthernLightX said. However, a question I have... :) It would be cool to know what u are using it for, more spesific, what you are connecting it to... Sometimes people confuses a potmeter with everything that looks like one, and it is really not a potmeter - it can be either a potmeter, a rotary switch or maybe rotary encoder, these three can look very similar on the surface, but in reality they are very different from each other. Just making sure you know that it really is a potmeter you want, and not a simple switch. But if you need to switch between 6 different resistances (measured in Ohm) the approach suggested by NorthernLightX is very good, This might, if you already know about the basics of electronics , seem like stupid questions from my end. In that case - I didn't mean it that way ;) - just making sure we can help you the right way by determing what you know and what you are building :). Have a nice day! Tbreath