Formerly not existing track cannot be loaded
Bug #1800395 reported by
Daniel Schürmann
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mixxx |
Fix Released
|
Medium
|
Daniel Schürmann | ||
Bug Description
If a track was missing, but the user has restored it, it can happen the the "not existing" state is still cached in Mixxx an the track is rejected during load to a deck even though it actually exists.
| Changed in mixxx: | |
| status: | New → In Progress |
| Changed in mixxx: | |
| assignee: | nobody → Daniel Schürmann (daschuer) |
Revision history for this message
| Uwe Klotz (uklotzde-deactivatedaccount) wrote | #1 |
| Changed in mixxx: | |
| milestone: | none → 2.2.0 |
Revision history for this message
| Uwe Klotz (uklotzde-deactivatedaccount) wrote | #2 |
| Changed in mixxx: | |
| importance: | Undecided → Medium |
| Changed in mixxx: | |
| milestone: | 2.2.0 → 2.1.6 |
| summary: |
- Formaly not existing track cannot be loaded + Formerly not existing track cannot be loaded |
| Changed in mixxx: | |
| status: | In Progress → Fix Committed |
| Changed in mixxx: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Swiftb0y (swiftb0y) wrote | #3 |
| lock status: | Metadata changes locked and limited to project staff |
To post a comment you must log in.
I've also experienced this situation after starting Mixxx, with all my audio files located on a separate disk that needs to be mounted manually. Thanks for adopting this bug, I will test the fix!