mherger wrote: > > If I change the 2000 to 5000 then my playlist with 4000+ tracks in it > > won't disappear during a full rescan. That isn't likely to be the > > solution but at least indicates it has an effect. > > I wonder whether the use of tmp:// instead of file:// is indeed causing > > issues: the remote scanner would be triggered to prevent storing file > information about volatile tracks in the database. But as you figured > out it's only keeping around information for a limited number of > volatile tracks. > > But then I do wonder too, why you'd even have those tmp:// urls in the > playlist. I'd suggest you open the playlist file in a text editor and > replace all the tmp:// with file://, run a playlist scan, and you should > > be good.
Changing the tmp:// urls to file:// urls does indeed solve the problem which begs the question: Since LMS changes the clientplaylist to use tmp:// urls instead of the original track designations, why doesn't LMS change the tmp:// urls to file:// urls at the completion of the scan after validation? I don't understand why the clientplaylist tracks are rewritten to use tmp:// urls in the first place. ------------------------------------------------------------------------ zeke1831's Profile: http://forums.slimdevices.com/member.php?userid=71469 View this thread: http://forums.slimdevices.com/showthread.php?t=114177 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
