|
Metadata Issue
|
|
21-06-2013, 14:38
(This post was last modified: 21-06-2013 14:40 by simoncn.)
Post: #2
|
|||
|
|||
RE: Metadata Issue
(21-06-2013 13:50)wazza69 Wrote: Hi, This can happen if the control point has cached the contents of the browse tree and this is out of sync with the server's current browse tree after new music has been added and MinimServer has been restarted. For example, the container ID artist$23 might be Bob Dylan originally (the 23rd artist in alphabetical sequence). After some new artists have been added and MinimServer has been restarted, the 23rd artist might be Cream instead. If the control point is using out-of-date cached data (which it shouldn't be doing), it may send MinimServer a request for artist$23 (expecting Bob Dylan) and receive response data for Cream instead. The control point should automatically detect a server restart and refresh its cache. It sounds like n-stream isn't doing this. Is it possible to force n-stream to reload its cache from the server? |
|||
|
« Next Oldest | Next Newest »
|
| Messages In This Thread |
|
Metadata Issue - wazza69 - 21-06-2013, 13:50
RE: Metadata Issue - simoncn - 21-06-2013 14:38
RE: Metadata Issue - wazza69 - 25-06-2013, 13:23
|
User(s) browsing this thread: 1 Guest(s)

Search
Member List
Calendar
Help



