Adrian wrote:
I thought DB was step input only. How do you record 'live', so to speak, other than by programming a KC as a rest?)
I don't actually RECORD it live. I just play the beat out, normally for someone else, and if they make a suggestion for changing it, I just play it that way. Then I step-enter it in.
I guess if you wanted to have a second program like SoundHack running to capture your DoggieBox "performance," you could do that... but it hasn't been my intention (so far) to try to do it that way.
Live recording of the keys you press would enter into a completely different realm of user interface and program code... right Ben?
DC
On 24-Feb-2005 18:46, Dan Costello wrote:
I don't actually RECORD it live. I just play the beat out, normally for someone else, and if they make a suggestion for changing it, I just play it that way. Then I step-enter it in. I guess if you wanted to have a second program like SoundHack running to capture your DoggieBox "performance," you could do that... but it hasn't been my intention (so far) to try to do it that way. Live recording of the keys you press would enter into a completely different realm of user interface and program code... right Ben?
Though I suppose if DB eventually gained the ability to import MIDI files (or at least strip the drum parts from MIDI files and import them), and also had the kind of ability to use the velocity/volume adjustment to automatically change volume or sample, depending on the situation, then you could actually do something like tap out a live pattern on a MIDI input device (complete with velocity readings) and import the resulting MIDI file into DB (where you could then edit it, clean it up, and step enter further parts and changes ...).
Then DB wouldn't need to have any "live UI", but you could still tap out parts to import for use it in pretty easily (if you had the MIDI gear).
Cheers, Carl