|
Playlist Trouble
|
|
14-11-2017, 16:39
Post: #4
|
|||
|
|||
|
RE: Playlist Trouble
It shouldn't be necessary to do a full rescan to solve the problem you were having.
If Kodi is saving UPnP object IDs for playlist entries and using them later (for example, after MinimServer has been restarted), this would explain the problem you are seeing. MinimServer increments the UPnP SystemUpdateID variable every time there is a change to object IDs and informs the control point of this change. It is an error for the control point to use cached information after there has been a change to SystemUpdateID. For example, the Naim control point implements the SystemUpdateID protocol to clear its cache when necessary. It is likely that Asset UPnP uses a different scheme for object IDs that makes a change to these less likely and/or less frequent than with MinimServer. This would mask incorrect caching behaviour by the control point. Many control points that don't support the SystemUpdateID protocol clear their cache of object IDs when the server restarts. For MinimServer, this would include any Restart or Rescan event. I think this would be sufficient to ensure that MinimServer playlist object IDs remain valid. The situation gets tricky if the control point is storing playlists in an internal form across a server restart (and a change to SystemUpdateID). The Naim control point attempts to handle this by remembering the browsing sequence to locate each item in the playlist but this doesn't work if the browsing menu selection labels change, which can happen with MinimServer. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



