Cue point inches forward when repeatedly hammering the cue button in CDJ mode.

This is tricky, there is a race condition in the cue manager that I don't quite understand fully.

A workaround that does work is adding a 'window' in which two differing cues are considered the same. Two cues that are 60ms apart will be treated as the same. How precise are DJs about their cue point timings? This window might annoy someone because they won't be able to adjust finer than within 60ms of a given position.

A 60ms window works fine at 20ms latency, but at 40ms latency it doesn't.

Very precise with cues. First beat of first bar just like vinyl or cdj

________________________________
From: RJ Ryan <email address hidden>
To: <email address hidden>
Sent: Tue, September 14, 2010 12:49:20 AM
Subject: [Bug 605266] Re: Cue button for x-session pro doesn't work. Cuepoints
do not stay at designated cue when used with mouse. Each cue rehersal results in
cuepoint moving down waveform

This is tricky, there is a race condition in the cue manager that I
don't quite understand fully.

A workaround that does work is adding a 'window' in which two differing
cues are considered the same. Two cues that are 60ms apart will be
treated as the same. How precise are DJs about their cue point timings?
This window might annoy someone because they won't be able to adjust
finer than within 60ms of a given position.

--
Cue button for x-session pro doesn't work. Cuepoints do not stay at designated
cue when used with mouse. Each cue rehersal results in cuepoint moving down
waveform
https://bugs.launchpad.net/bugs/605266
You received this bug notification because you are a direct subscriber
of the bug.

Status in Mixxx: Confirmed
Status in Mixxx 1.8 series: Confirmed

Bug description:
Windows vista sp2. Hp Pavillion 1.9gig ram amd turion processor. Cue points
still move down waveform when repeatedly rehearsed for beatmatching.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/mixxx/+bug/605266/+subscribe

I'm going to continue to work on this in the hopes of fixing it for 1.9.0. Marking appropriately.

Barring some serious epiphany, I don't think this is fixable until the engine is in better shape.

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/5456