On Fri, Dec 24, 2004 at 09:43:09PM -0000, sidstationownsyou wrote: > 1. Sorry man, but I'm going to keep this behaviour. It took a lot of work to make CC and > sysex messages be sent automatically at appropriate times. Here's why I decided very early > on to incorporate this functionality: > The values in the table, popup buttons, etc. represent the CURRENT state of the machine. > If, at any time, those values did not represent the sound your hearing from Machinedrum, > this paradigm would be broken well, this is misleading. it's not displaying the current state of the active machine as much as it's presenting the user with a set of values and changing the current machine on the MD to match that set. i realize that, barring a sysex request to dump the current kit, there's no way to represent what's truly in the MD in your application. then again, a request for a current kit dump when you select a machine might be ideal; there's not *that* much data, assuming you can remotely request a "current kit" dump from the MD. that moment's lag seems preferable to an automatic update that you have to undo (in the program, or, in some cases, on the MD). i appreciate your desire for immediate feedback, and a "send" button would probably be overkill when your program could send CCs when any machine parameter is accessed. however, the following really shouldn't send CCs to the machinedrum: 1. selecting a machine to edit. it essentially copies the previous machine to the new one. 2. change application focus. your multiple windows approach for auditioning is compelling, but if i change my focus to the finder, or terminal, then i'm not auditioning patches, i'm multitasking. if, while taking a quick break from MML to write you an email, i made changes to the machine via the MD's panel (it can happen), i have to save them, or i'll lose them when i command-tab back to machine lab. 3. launching the app. this provides no undo, and you have to reload or undo the kit on the machinedrum. > BTW, you can always unplug your MIDI cables if you don't want data to be sent. MD > Machine Lab functions fine offline. er, i presume you're just being cheeky, here? =) > 2. I plan on implementing sysex file importing very soon ;) that's awesome, andrew. i hope i'm not coming on too strong, here. i think MML has the makings of a truly great tool, and i'm emphatic only because i care. lastly, there's the matter of making a donation. dude! paypal! =) -- yours, niall. .. . . . . . . . . . aleph null. a simple insinuation around silence. http://syncretism.net .. .. gpg public key - http://www.aleph-null.net/niall.gpg .. ..
Message
Re: [elektron] MD Machine Lab released!
2004-12-25 by niall munnelly
Attachments
- No local attachments were found for this message.