Albert Santoni wrote: > I've also noticed it is highly dependent on your latency. If you hit cue > twice very quickly with a low latency (say 16 ms), you won't get the > problem. (So it's also possible that trying to cue twice in less time > than the latency just won't work, which makes a bit of sense to me.) >
My latency is 3-4ms and it still happens pretty consistently. I'm using an M-Audio Conectiv for my audio interface. > By the way, this isn't a problem with the new cue code, it's been a > problem for a long time. Because it goes away with lower latencies, it > hasn't been at the top of my list. > Sorry, I should have phrased that better. It was more that I was playing with the new cue behavior when I noticed it. > It's definitely worth putting in the bug tracker though... > https://bugs.launchpad.net/mixxx/ > Will do. I'll add your comments as well to help whoever gets around to it. Thanks. -Dan G. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
