Elektron Musical Instruments

niall,

"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."

- The later paradigm is what my old program (Machinedrum Machine Maker) used to use. I 
found this clunky, and prefer the first paradigm.


I was considering sysex kit dumps as a solution a few months ago, but then I realised that 
there is no way to determine the currently selected kit over MIDI.


"1. selecting a machine to edit.  it essentially copies the previous machine to the new one."

- I'm not sure what you mean... could you eleborate? By "machine", do you mean "track"?


"but if i change my focus to the finder, or terminal, then i'm not auditioning patches, i'm 
multitasking"

- true, but re-sending the data isn't problem IMO


"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."

- I didn't intend users to tweak MD's knobs while MD Machine Lab is running. I am, 
however, trying to add the ability to detect CC messages which originate from 
Machinedrum. I'm finding it tricky though, so no guarantees.


"3. launching the app.  this provides no undo, and you have to reload or undo the kit on 
the machinedrum."

- as I wrote in my previous reply, I could make it so that a each time MIDI data is about to 
be sent, an alert sheet pops up to ask the user if the want to send the data. Or maybe just 
have the alert pop up the first time the document is opened. I would add a checkbox in 
Preferences which allow the user to enable or disable this behaviour.


"lastly, there's the matter of making a donation.  dude!  paypal!"

- Paypal makes you pay for the service. I really don't expect to make much money at all. 
Plus paypal doesn't let people send you non-monetary donations (like CDs, gear, 
shoelaces, etc.)


Andrew