Bugzilla – Bug 3456
Scan for new and changes misses ID3 tag changes
Last modified: 2008-09-15 14:38:25 UTC
If I change an ID3 tag, or add one to a previously untagged file, the data base does not see the change unless I do a complete clear and rescan. This shows up in practice because I rip long (hour or more) radio programs into my library. It seems that sometimes the track being ripped is added to the database before the rip is complete. My rip program tags the file after its been ripped, and the tagging doesn't show up. I guess I don't know what the changed in scan for new and changed means, but I hoped the scanner used file modification times to select which files to rescan.
This seems to be true in my testing, too. 1) I initially scanned my music when I installed. 2) I edited the ID3 tag of one MP3 file. 3) I hit rescan. 4) I hit refresh until the message about the rescan still being under way was not shown. 5) I skipped ahead to the track I had edited, and noted its ID3 information had not changed. 6) I restarted the server, and again, noted the ID3 information was not changed. I searched for this bug elsewhere in the database, but didn't notice it already in there.
Fixed in change 7800
Verified fixed in SlimServer Version: 6.3.0 - 7895 - Windows XP - EN - cp1252
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.