More > JRiver Media Center 27 for Linux
Duplicate entries each time autoimport runs
zybex:
Are you using NextCloud to sync your files to some other PC/Server/NAS? If so, try disabling it and then import the folder 2 or 3 times to see if the issue is still there.
File sync services can cause issues because they modify and virtualize the files they handle. If you are syncing 2 or more PCs and importing the same files in both of them, the tags added to the file during import on one side cause the file to be modified and re-synchronized to the other side. If you're using it to sync 2 local folders and then importing both folders, the same will occur.
wer:
If the filespec that MC accesses is truly identical, MC should consider them the same file.
Please post a screenshot in MC with the file list of the view visible, and with the entire contents of the [Filename] field visible as a column, for the affected files. Make sure the column is wide enough that the entire contents is visible.
Cmely:
Here is the screenshot.
The filenames are exactly the same...and when I use the command "Locate on explorer" on both files, I get the same result...
zybex:
--- Quote from: wer on January 14, 2021, 02:54:49 pm ---If the filespec that MC accesses is truly identical, MC should consider them the same file.
--- End quote ---
I was thinking of 2 special cases:
1. PC A imports the file from NAS1, which adds tags to it; this causes the file to be re-synced to NAS2. If there's another MC on the other side, it will see that as a modified file and re-import it, possibly modifying it again and triggering a loop between the 2 PCs (though in this case I don't think there would be duplicate entries in MC)
2. Even with 1 PC only, if sync virtualization is enabled the file's inode number changes after the file is uploaded (a new empty sparse file is written in its place). This may cause MC to see it as a distinct file and reimport it; the reimport causes the file to be materialized, and the loop repeats.
wer:
It was my understanding that MC checked the filename to see if the file was already in the DB or not. If that was the case, it shouldn't be able to import the file twice, changed inode or not, NAS or not, cloud or not, if the [Filename] is identical.
The screenshot appears to show identical filenames. I wish that screenshot were of the whole window, so we could see if there are stacks, or broken links, or particles, or anything else. Stacks or particles can produce the screenshot shown, for as much as it shows.
There have been instances in the past where people had unusual characters like   in their filename, which were visually indistinguishable from regular characters, but MC considered them different and imported both files. Something like that could be involved here.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version