-
-
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
Do not save missing tracks to prevent inconsistent metadata #3811
Conversation
The metadata of tracks in the database should not be modified as long as they are missing to prevent inconsistencies with the file metadata. This will become an issue soon. Other changes: - Return more meaningful results when saving tracks - Perform checks behind the internal API in TrackCollectionManager and use debug assertions in TrackDAO
Makes sense. Should this go into 2.3? |
No. It is not an issue yet and would cause merge conflicts. Main has already advanced in track management. |
One edge case is that you edit track properties and then unmount the drive with the track file before the track has been saved. Unfortunately, synchronizing the genre/mood tag with custom tags causes tracks to become dirty without manual editing. This could happen with any data migration that is performed lazily at runtime. Better be restrictive and discard pending changes in this rare edge case instead of risking inconsistencies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two minor comments, than LGTM
Thank you.
Thank you. |
Co-authored-by: Jan Holthuis <holthuis.jan@googlemail.com>
The metadata of tracks in the database should not be modified as long as they are missing to prevent inconsistencies with the file metadata. This will become an issue soon (when synchronizing custom genre/mood tags with metadata).
Other changes: