Cue marker jumps to first set hot cue position
Bug #663216 reported by
Sean M. Pappalardo
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mixxx |
Fix Released
|
High
|
RJ Skerry-Ryan | ||
1.8 |
Fix Released
|
High
|
RJ Skerry-Ryan | ||
1.9 |
Fix Released
|
High
|
RJ Skerry-Ryan |
Bug Description
Steps to reproduce:
1) Start Mixxx
2) Load a song
3) Set the cue point
4) Set a hot cue point (after the cue point is all I tested)
5) Close Mixxx
6) Open Mixxx
7) Load the same song
8) Observe that the cue point has moved to the first hot cue position
Related branches
lp:mixxx/1.8
(Merged)
Changed in mixxx: | |
importance: | Low → High |
Changed in mixxx: | |
status: | Confirmed → Fix Committed |
assignee: | nobody → RJ Ryan (rryan) |
Changed in mixxx: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
You dont even have to manually set a cuepoint.
Example:
1 - Load fresh track with no cuepoint set until (check that Track properties->Track Cuepoints is empty)
2 - Set HOTcue #1 at 1:00.00
3 - Load different track
4 - Load 1st track again
5 - Observe that the cue point has moved to the first hot cue position , there is now one entry in Track properties->Track Cuepoints (Hotcue 1 at 1:00.00)
6 - If you delete the Hotcue and reload the original track , the Cuepoint is still at 1:00.00 and there are now two entries in Track properties->Track Cuepoints ( 2 x Hotcue 0(Zero) at 1:00.00)
If you manually delete the entries, the cuepoint is correctly at the tracks beginning again.
IMHO This bug should have an elevated priority as it affects every single track you load.