Cue changes in pref dialog are lost if the track is loaded

Bug #890423 reported by Daniel Schürmann
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Committed
Low
Unassigned

Bug Description

If you edit the cue points in properties (right click in library) all changes are lost if you unload the track from deck.

Tags: cue
RJ Skerry-Ryan (rryan)
Changed in mixxx:
importance: Undecided → Low
Revision history for this message
jus (jus) wrote :

This influences the "Auto Recall Cue" option in the Mixxx preferences too.

* Set a Cue point on this track
* Deleted via Property editor afterwards
* Eject the track and reload it in the deck

The track is loaded from the very beginning although the Cue point is still there (according to Property editor) and should have been loaded from the Cue point ("Auto Recall Cue" option= on).

Changed in mixxx:
status: New → Confirmed
tags: added: cue
Revision history for this message
Kartik Gupta (kartikgupta0909) wrote :

In this bug, if you close mixxx with the track on the deck and after setting the cue point then the cue point is lost whereas if you eject the cue point then the cue point is saved. Possibly the cue is being saved when the track is being ejected whereas it should be set as soon as the cue button is pressed. This fact can be verified by looking at the properties after setting up the cue but not ejecting the track, the new cuepoint is not shown, but if you eject the track once and then have a look at the properties then you can see that cuepoint. I d like to take this up if nobody else is working.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

I have not looked at the code, but it sounds like we have two concurrent track info objects.
These info objects are stored back the database once the fall out of scope and out of a strong track cache.
So once we have two of them, the last on wins.

An other reason could be that a changed cue is not stored into the track info object at the right time.

Uwe has recently done some work that the track management that will finally prevent such duplicates.
With some luck this bug is already fixed in master.

Revision history for this message
Be (be.ing) wrote :

I cannot reproduce this.

Changed in mixxx:
status: Confirmed → Fix Committed
Revision history for this message
Swiftb0y (swiftb0y) wrote :

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

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.