On Thu, 1 May 2008, 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.)
Ahh... I was about to say, the problem described occurred before the new CUE behavior; it seems related to waveform draw and not any particular cue behavior. I haven't tweaked my latency to minimum, sheer laziness. So it's like 40mS. I've complained of this problem a lot (umm, sorry :-) so nex chance I get (oh, by 2051) I will assault latency then see how it acts. I've got enough CPU, there's no reason I can't get it low(er). ------------------------------------------------------------------------- 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
