features_sqlite branch saves Cue point by channel rather than song
Bug #502447 reported by
pi r squared
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Medium
|
RJ Skerry-Ryan | ||
Bug Description
Using Mixxx features_sqlite r2349.
Steps to reproduce:
Load track in Channel 1 and set Cue point as normal at a position other than 0:00. Any future tracks loaded into Channel 1 will have exactly the same Cue point. If a new Cue point is set, when the original song is loaded into Channel 1 it will adopt the new Cue point.
Similar behaviour happens for Channel 2.
Related branches
| Changed in mixxx: | |
| milestone: | none → 1.8.0 |
| tags: | added: library |
Revision history for this message
| RJ Skerry-Ryan (rryan) wrote | #1 |
| Changed in mixxx: | |
| assignee: | nobody → RJ Ryan (rryan) |
| importance: | Undecided → Medium |
| status: | New → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #2 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
Thanks pi r squared,
I just fixed this in trunk (we merged features_sqlite into trunk today).