hey niall! Thanks for the feedback. Please let me know if you have any more ideas regarding MD Machine Lab in the future. 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 - which brings me to the window focus thing... Consider the situation where you have 2 or more drum documents open which use the same track. I didn't want to pop up an alert saying "sorry, but you can open that document", so I had to figure out a way choosing which one of the documents would active on Machinedrum. I chose that the window which is currently the main window (the document in the foreground) should be in sync with Machinedrum. Switching focus to one of the other documents causes that document to take over (if it has the same track as the previous window). This behaviour can be quite useful. If you have several different variations of a drum, and you're trying to decide which one is best to use on a track, you can quickly switch between different sounds simply by clicking on different document windows. User feedback should be instant: if you adjust the value slider, hit the randomize button, change machines, perform and undo or redo, etc., you should hear the result right away. 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. BTW, you can always unplug your MIDI cables if you don't want data to be sent. MD Machine Lab functions fine offline. 2. I plan on implementing sysex file importing very soon ;) Merry Christmas! Andrew --- In elektron-users@yahoogroups.com, niall munnelly <aleph@a...> wrote: > hi, andrew, > > machine lab will prove invaluable for making unimagined sounds reveal themselves. > you've really done a great job with this. i have one major and a few minor feature > requests: > > 1. the program shouldn't output CC messages automatically. please consider adding a > "send" button that will update the MD only when this button is clicked. if you hit the > randomize button, change window focus to another app and return to machine lab, or > change the instrument being edited, the program sends all of the buffered settings to > the machinedrum. even launching it sends the changes. > > 2. naming new kits is hella fun, so please make this open sysex files, so we can mess with our > existing kits. > > ....actually, that's all i want to write right now. i need to save my new kit, so i > don't lose it when i launch machine lab again (i gotta click that donation link, > now... =). > > -- > 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-24 by sidstationownsyou
Attachments
- No local attachments were found for this message.