Skip to content
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

Existing tracks discovered again, added as new (duplicate) #13540

Open
ronso0 opened this issue Aug 6, 2024 · 5 comments
Open

Existing tracks discovered again, added as new (duplicate) #13540

ronso0 opened this issue Aug 6, 2024 · 5 comments

Comments

@ronso0
Copy link
Member

ronso0 commented Aug 6, 2024

Bug Description

I did a rescan to add a new track, and (Tracks sorted by 'date added') suddenly some very old tracks showed up at the top of the list.

First I suspected these are false-positive missing tracks¹ discovered as new, but when I checked mixxxdb.sqlite in order to set date_added to 2022-something, I noticed these were duplicates².
This affected tracks in different directories, and only a few per directory, so I'm puzzled what's going on.

  • Maybe worth mentioning that all my music is on a separate drive mounted in /mnt/../audio and symlinked to ~/Music/audio, but it's been like this for ages without this issue 🤷
    No further symbolic links in that directory or any of its children³
  • I have Sync metadata from/to file tags enabled:
    could be I edited tags of some of the tracks lately (during last 3 months), but definitly not all.
    IIUC this would cause the directory hash to change, which in turn queues all contained files for import, but previously existing files should be ignored (marked 'verified') (ScannerGlobal is constructed with all file locations).
  • ³no symbolic links, so IIUC neither this nor this should be executed
  • ² none of the original tracks had fs_deleted or mixxx_deleted set, both originals and duplicates showed up in Tracks

Note that this happened with my custom branch, but the library and especially the scanner code is like in main.

¹I thought I filed a report for that issue, but I didn't, #9422 is releated though

Version

main, but noticed the missing issue also with 2.4 and 2.5 earlier

OS

Linux

@ronso0 ronso0 added the bug label Aug 6, 2024
@ronso0
Copy link
Member Author

ronso0 commented Aug 6, 2024

I'll add some logging so I can at least trace it, in case it happens again in my live builds.

@ronso0
Copy link
Member Author

ronso0 commented Sep 29, 2024

(dupe of #13140 somehow)

@macrophone
Copy link

I've got the same issue here :
Some tracks are "rediscovered" and duplicate in the library.

Also using a symlink for my music collection.

I can open the "Properties" dialog to look at the path, but trying to open "Properties" on the duplicate track makes Mixxx crashing. Same behaviour whatever track I try to read first : original or duplicate.

@macrophone
Copy link

#8009 seems related

@ronso0
Copy link
Member Author

ronso0 commented Dec 7, 2024

I took a closer look:
my music is in a directory in /mnt/[partition]/audio

  • the new duplicate track locations start with /../../../mnt/
  • old track locations start with /mnt/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants