On 1/9/06, Cory <[EMAIL PROTECTED]> wrote: > btw, I've found that if a sound is playing, and you .play it again, > the first will stop playing and re-trigger.
I would say that's the expected behavior for a drum machine. If you have a 100 millisecond file playing every 50 milliseconds, and it plays all the way through to the end, you're going to end up with unwanted reverb/echo/delay. > I'm still not getting great timing even with the modifications > suggested here. If a 30th of a second is it, maybe RealBasic is > meant for this. I'm using microseconds, but would a timer be better? 125 millieseconds is the speed of a 1/16 note hi-hat at 120BPM (think techno), and IMHO that's a lot of resolution for most drum machines and their application. I wrote a MIDI-based metronome that can do that without even thinking. If I halve the note value, the quality and usefulness of the rhythm degrades pretty quickly. If I go into another app, it hiccups, but that's definitely expected. In my goofing off with Reason and Logic Audio, there does come a point when even a mouse movement or click will cause a hiccup in the rhythm just like in an RB app, but they need to be playing at 300+ in order to get that to happen. I'd be curious to know how Apple and Propellerhead are able to better handle the higher speeds. But, just because one can play at 150+ BPM, doesn't necessarilly mean one should. Reason goes up to 999, but it's not terribly useful at that speed. I'm curious as to the the quality of the soudns you're using bit rate, frequency, type, etc. Too high of quality becomes too hard to play on most machines. cheers -- Philip Regan [EMAIL PROTECTED] http://homepage.mac.com/pregan REALBasic 2005r4, Mac OS 10.3.9, Mac-centric development Xcode 1.5 _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
