Mnyb;669698 Wrote: > Ok, this could have been a scanning/database error too " scan for > changes" is not always what it should be, especially in older versions > off the server it can leave corpses behind, sometimes after a tag fix > session in 7.5 or earlier you could end up with all kind of " ghost" > entries in the dB with scan for changes. 7.6 and 7.7 has improved > greatly but I would not bet the farm on it. Sometimes the clear and > rescan is the thing you have to do . > > It could also be bug that is fixed in the new version a likely > explanation.
I did a clear and rescan after each attempt at fixing something---probably ran it 6 or 7 times as I tried different things, so I don't think that was the issue. I almost never use "scan for new and changed"---I've not had good luck with that! My guess is that the initial data restore from the backup introduced a few errors in those tags/files and deleting and re-tagging eliminated those errors. -- rgro Rg System information ------------------------ Main: PS Audio Quintet > Vortexbox > Touch (wired) via optical > Rega DAC > LFD LE IV amp > VA Mozart Grands > REL Acoustics R305. Home Theatre: Duet/SBR (Wired) > Pioneer VSX 919 > Energy Take 5 Classic 5.1. SBS 7.7.0 r33626 running on a Vortexbox Appliance, V 1.9. Touch w/Hardware V.5. Touch: FW 7.7.0 r9550. Duet: FW 7.7.0 r9546. ------------------------------------------------------------------------ rgro's Profile: http://forums.slimdevices.com/member.php?userid=34348 View this thread: http://forums.slimdevices.com/showthread.php?t=91571 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/ripping
