Cue marker is not saved upon quit

Bug #1596237 reported by Vincent Malstaf
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Medium
Unassigned

Bug Description

When I set a new cue marker and then quit the program, the marker is not saved.
I'm using Mixxx 2.0.0 on Linux Mint 64bit.
All the best,
Vincent.

description: updated
summary: - Cue marker is lost upon quit
+ Cue markers is lost upon quit
summary: - Cue markers is lost upon quit
+ Cue markers are lost upon quit
summary: - Cue markers are lost upon quit
+ Cue marker is lost upon quit
summary: - Cue marker is lost upon quit
+ Cue marker is not saved upon quit
Revision history for this message
Dale (dj-kaza) wrote :

The normal Cue? Do you really expect it to? That is a fluid cue that is expected to change (multiple) times every time a track is played as you cue up different areas. Or do you mean the Hot Cues (eg 1-4 set by Z,X,C,V for Deck 1.) If you mean the later I definitely don't experience that here on Ubuntu. If you mean the former maybe you should learn to use the proper cues.

Revision history for this message
Vincent Malstaf (vincent-malstaf) wrote :

Thanks for the reply Dale,

With the cue-marker I mean the starting point "C" were you want the song to begin.
When the soundfile is not playing you can set this marker by clicking on the CUE(STOP) button.
When playing and you press CUE, it stops and goes back to this point.

Now, when you then load another file in that player, this position is saved in the database, but when you immediately close Mixxx, this information is not saved.
Loop-markers are also not saved.

But Hot-cues are different: they are saved upon exit also when you don't load another file.

To reproduce (I have Mixxx 2.0.0 x64 "Late Night" theme, on Linux Mint):
- load a file X in player 1
- click somewhere on the sample
- click on the cue(stop) button
- click somewhere else on the sample
- set the left and right loop-markers

> Situation A
- open another file Y in player 1
- quit en restart Mixxx
- load file X in player 1
=> markers are stored in database

> Situation B
- quit en restart Mixxx
- load file X in player 1
=> markers are NOT stored in database

I hope this helps.
Vincent.

Revision history for this message
Vincent Malstaf (vincent-malstaf) wrote :

Ok, it probably depends on how you expect Mixxx to work.

I often want to skip the beginning of a track or set a precise loop, and save this for the next time I open it. This works fine until I close Mixxx, then the changes in the LAST file(s) are lost.

Maybe you would expect the cue-marker always to be reset to the beginning when you reopen a file?

How is works now is at least confusing to me.
To be sure cues are saved, I eject all the players before quitting Mixxx.

Revision history for this message
ronso0 (ronso0) wrote :

Hi there. I reported this issue only for Cue point
lp:1640983

Ejecting players before quitting mixxx doesn't make a difference for me, though:
neither Cue nor Loop markers are stored.

@Vincent: I think you're right to expect the Cue point to be stored after quitting. Also, in Preferences > Interface there's a checkbox "Jump to main Cue point on track load".

Changed in mixxx:
assignee: nobody → Uwe Klotz (uklotzde)
status: New → In Progress
Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

If cues are not stored at all you should check you database. Version 27 adds the column 'color' to the table 'cues'.

I got database errors in the log that reported mismatching columns when inserting cues. The database version was already at 27, but the new column 'color' was still missing. I don't know how this happened. Just a hint if someone else is affected by this strange issue, too.

Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :
Changed in mixxx:
status: In Progress → Fix Committed
jus (jus)
Changed in mixxx:
importance: Undecided → Medium
milestone: none → 2.1.0
Changed in mixxx:
status: Fix Committed → Fix Released
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/8583

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.