> I like this approach, and it never occurred to me. What's the > advantage of going this route instead of constantly applying a drift > adjustment to the pitch? >
If the drift gets too large, and for some reason the drift adjustment isn't working, the track may resync unnecessarily. I want a 100% guarantee that we only resync when the user lifts the needle. > > What should happen if the record gets stuck and jumps 5-10 seconds at a > > time? Should that be detected, or should the track just skip? (I don't > > know how serato handles that). The only way I can think of telling the > > difference between a needle drop and a stuck record is if there's a > > regular period of stuck-ness. Mixxx could automatically tell the record > > to keep playing at the previous rate, and the dj could clean off the > > needle and the record while the track is going. Then when they do a > > needle drop, mixxx would be set to relative mode because the needle drop > > isn't going to be anywhere near the skip position. (And still, you're > > going to get at least one skip before it figures it out, and you'd need > > all sorts of UI elements to announce that your record is skipping.) > > > > These are all good, open questions that I don't have an answer to, but > I'm excited to see that you're thinking about all these cool > possibilities. If you try to code something like that, I'd use the > "needle skip prevention" flag that we already have and change it to > something more general like "needle skip and broken record > protection". You definitely have a really cool idea. :) Ok, I just had an even cooler idea :). I'll keep track of how long the TC signal was lost, so if the needle jumps very quickly (<0.1 seconds) and moves a lot (>.5 seconds) it's almost certainly a record scratch or other error. Then mixxx would move to relative mode and ignore the absolute positioning. The awesome thing is, we can catch this as it's happening, alert the user that the needle skipped, and keep the track playing without any interruption whatsoever. If the user wants to go back to absolute mode they can (midi toggleswitch, say). I don't think there's a dj out there who can reposition a needle in the time it takes dust to skip a record, so it shouldn't mistake a fast but intentional reposition as a skip. And even if it does (like the dj drops the needle and it bounces), the user can lift the needle, set it back to absolute mode, and try again. 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
