-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
relinking library directory should automatically rescan library #12858
Comments
How do I assign this issue to me? |
There's no need to assign the issue, you can just go ahead and open a pull request when you have a fix implemented. Please include |
Relinking = relocate dir? |
Yes, using the Relink button in the Library preferences. |
Why is a rescan required? IIUC, if the (inner) directory structure didn't change (dirs or tracks renamed / deleted) all tracks should be updated correctly. |
Note: relinking was actually broken before #12462 (dirs were update but not the tracks). |
I noticed this issue when testing migration into the Flatpak sandbox https://mixxx.org/news/2024-02-21-official-flatpak-now-available-on-flathub/ |
I saw that, but does that mean we need a full rescan in order to get access to each track? |
Okay, I tried this myself:
Conclusion:The rescan is not required in general. Relink is sufficient. |
That will change the result. That shouldn't be required. |
The only useful dir permissions Mixxx has after installation are for The Flatpak sandbox docs advice to use This is with |
Really? The file picker dialog goes through the XDG File Chooser portal, so it should let you choose any directory that your user has permission to, including outside the Flatpak sandbox. |
Right, relinking is only needed if the user already had directories outside of these paths in their Mixxx database. |
What shall I say, xdg-desktop-portal is 1.6.1-1ubuntu2 which is quite old I guess. |
Would rescanning after a Relink ever be a terrible thing? Wouldn't it be fast if it isn't necessary (that is, if the records for the relinked folder are already in the library)? Maybe after Relinking, rather than forcing a rescan, we should make rescanning optional and prompted, just as we do when the user Adds a new directory. It seems wrong not to warn the user that the directory they just relinked might not be available until rescan. |
The dir is available immediately, relinking just replaces the file paths in the database which is blazing fast.
Define 'terrible' ; )
Rescan blocks the GUI (to avoid database inconsistencies caused by concurrent access (scanner vs. user modifications like metadata edit, play count etc.) and it can take long. Refactoring the scanner to allow scanning specific directories is an option though, as well as offering a specific rescan after relinking. |
It is not, if rescanning is enabled at startup and you just started Mixxx. The rescan removes the entries, so it's just like a "Remove" in terms of library contents. Also, the user might (erroneously, maybe) Relink to a ("bogus") folder that doesn't match the entries in the library. In this case, the user might want to be informed of the error, rather than being forced to rescan and "cement" the error in the contents of the library. I don't like the idea of forced rescan, especially if it will rescan ALL the directories rather than only the ones Relinked or Added. I don't see a manual rescan button in 2.5.0. Maybe we should have a button for that, and some indication that Relink could require a rescan after you do it. I think the user should initiate rescans, since they are potentially so expensive. |
... and auto-rescan bites us again 😞 |
Bug Description
Relinking a library directory in the Library preferences requires manually rescanning the library for Mixxx to find the files. This should be done automatically when saving the changed preferences.
Version
2.4.0
OS
Fedora 39
The text was updated successfully, but these errors were encountered: