On Fri, 2010-02-26 at 21:18 +0000, Mark Hills wrote: > The timecoder no longer makes the distinction between 'alive' or not, > preferring to smoothly make the transition from pitch 0.0 to movement, > rather than a jump from off to on. Crucially the pitch filtering has moved > into the timecoder itself which allows this, and means the filtering is on > a per-sample basis (and not a per-pitch-reading basis, which was > incorrect).
> As for pitch, there is always a speed measured from the audio input, even > if it's zero. So if you really want to make the distinction between > 'going' or 'not' then you'd need to threshold it. I'd recommend this only > for an icon or visual display, but not for audio playback itself. xwax > doesn't make this distinction at all (but early versions did). I'll take another look at my algorithm to see if I really need the "alive" measurement. You're probably right, there's no functional difference between lifting the needle and stopping the record. For now I've written in code to listen to the audio signal and trigger based on how loud the sound was, but I may not need that at all. I think, though, that there were a lot of near-zero pitch readings that were messing things up. owen ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
