JJZolx;530925 Wrote: > It just struck me... The inotify triggered scan failed to properly > remove the old content. But did you try running a new & changed scan > before running the full clear & rescan? The necessary database cleanup > may well be done by a new & changed scan, which has undergone a lot of > improvements in 7.5e/7.6. A full scan was usually required in the past > to do this, but may not be been necessary now.
well it rescan'd it via inotify, so I ended up with two albums of identical names. That's why I did a clear. As to it not working in prior versions? It certainly did a year ago with MySQL. It took a few minutes before the library started repopulating, but then i could play anything that it had scanned. (I actually have the same problem right now: an album that I tagged with Musicbrainz is not the exact copy on Musicbrainz, so it only tagged the album name on the first 12 tracks or something, leaving 3 with a different name from the ripping. I changed the name on all tracks to match, yet the two halves have not been merged into a single album id... a 'scan for new/changed' takes 30 seconds and is effectively a no-op, since nothing has changed since the inotify-rescan hours ago. So, no that is not a fix for the root... and certainly not a fix for "clear/rescan will die if any track is played") As it stands now, yes, i can see the library, but if I actually try to play anything, the scan is terminated. Restarting the server will find the terminated scan, decide it is not newer than the last completed scan, and discard it. The tracks with the same album name (that have different album ids) will remain with different album id's. -- snarlydwarf ------------------------------------------------------------------------ snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179 View this thread: http://forums.slimdevices.com/showthread.php?t=76850 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
