I'm confused by the tmp:/// designation in the URL of the track location
as I also see file:/// used which would seem more appropriate. To avoid
a future problem under what conditions would the tmp:/// designation be
used by LMS?
I don't know why that designation is being used in your case. I see it
whenever I have items in the current playlist that were put there before
a full rescan. Pure speculation on my part, but I assume that since the
database has been rebuilt, the old track ID is no longer correct. So LMS
creates a temporary link to use and discards it as soon as the track as
been played or the playlist cleared.
In general the "volatile tracks" using the tmp:// protocol are handled
like regular file URLs, except that these items are not stored in the
database. It's what makes eg. the "browse filesystem" feature possible.
And continuing to play your current playlist while a wipe & rescan is
going on: in this situation we don't want to write to the database from
the server part, to let the scanner have full control over it. So your
guess comes pretty close.
So one question probably is why you'd have tmp:// URLs in a playlist.
Maybe they're pointing at files that no longer exist?
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
