basix

cool stuff, haven't really been actively following the developments until recently but this looks very nice. One thing that could make it more user friendly on the ipad is to have the screen and the rotary buttons in the middle section instead of on top, and also to make drag up and down alternate the values of the buttons instead of having to rotate them.

anyone?

Good morning Pascal, I know that it's not really needed, but I was thinking for which purposes I could use it and how it interacted with the SEQv3. Not really a question on how to build it or so.

Hi, I've been searching for explanation on how the button/led matrix works but couldn't find anything explaining in depth. Can someone please tell me how this exactly works? Or point me to the right paragraph in the manual? Does it work like some kind of monome trigger board? Thanks

Thanks Twin-x, but I already got enough webspace. Money however.. just kidding ;) First let's see if we can build a team. I don't think I'll be able to finish this on my own while doing 2 jobs, working 60kms away from home, my wife and our cat ;) And not to forget with all my other hobbies like music, satellite, linux routers/storage devices and all kinds of geeky/nerdy stuff I tend to get out of time very quickly. Nevertheless I'd like to start by calling out to people experienced with programming for midi based applications. I read that MIOS currently supports a dump from the banksticks/memory, but I understood it resets itself after giving the dump through sysex. (Is this still functioning like that?) My preference would actually go out to a real time midi based visual editor. I didn't have time yet to look into the MIOS/mbseq code or the sysex implementation but what I can tell is we can certainly make use of and/or extend the CC/NRPN functions in a way to be able to control it in real time through the software. Mix this with sysex and we got our software (actually it's a bit more difficult than it looks like :p) I also noticed there is an LCD message command through sysex, so extending that command to also return data that's currently on screen would make us capable of displaying the data on screen as well. This would be the first (and easiest?) phase, just to mimic the hardware functions through the software. In the meanwhile I could start designing the screens for: - drum mode (x0x style, but more like the doepfer schaltwerk layout so you don't have to switch between instruments to see what's going on) - pattern mode (reason's matrix sequencer style: http://www.soundonsound.com/sos/jul07/articles/reasontech_0707.htm) - only disadvantage is that it's a monophonic seq in this way - pattern chain mode/song mode - event viewer/tracker mode - i probably forgot some other things After that, we could start experimenting with all the stuff in the mbseqv3_sysex_implementation. It's cool that we can read out and write patterns etc. directly from/to the machine. Perhaps the sysex debug commands will even provide us everything we need already. I'd prefer this application to be compatible with as many OSes as are available, so I don't know if we should use java or c. Is it correct of me to think that java might have latency issues since it is being used in a non native instruction set? I think it also would be way too bloated if we used java, but what other options do we have to be able to maintain access to MIDI ports in an OS? The code would be GPL'ed of course. We could try in ABAP, since that's the only language I've been using for a while to program :p But first of all, I should start building my mbseq v3 and get to play around a bit with it :] I'm very sure this will drop like a bomb on synth/seq/workstation manufacturers. Imagine all the possibilities.. *drool*

if multi color leds were used, one could see it as follows: 1-16 green 17-32 red 33-48 orange = 2 colors lit (if available) ...

I think we should find some people first who want to contribute to this project since I probably won't be able to manage all this by myself. If we split up tasks, it'd be easier to realise things in a faster way.

I haven't built a midibox seq myself yet, but I've been preparing myself by reading the forums and the ucapps.de website since a few months. I'm planning on building one in August/september when I'm back home. I think this project (and all others btw) is awesome and thanks to TK, everyone can make additions to it. I thought perhaps an editor would be a great addition. I had following options in mind: - Basically everything you can change through the hardware buttons should be changeable with the software version. - Drum map mode where you can click buttons to enable that step (like a TR808, but with all instruments on one page, no need to switch instruments) - Event viewer/editor on a bigger screen - ARP/Pattern editor - Can read directly from midibox and/or can handle sysex dumps from the banksticks - ... Some kind of KARMA editor for the midibox seq ;) I have programming knowledge, but not in the MIDI or hardware controlling area. A good point to start at would probably be by choosing the language in which this application would be written. And who's volunteering to help? I hope there are some experienced programmers around who want to help. There are some open source midi programs which could be extended. Perhaps we should even think about creating a (VST) dll that converts data from seq to the native program which lets the user make the changes and put them back? There are a lot of options.. Let's consider the easiest and cheapest (time/money) one :) Keep up the good work TK!

Looks great! I'm planning on doing a panel mount myself as well after the holidays ;)