MinimServer & Naim NDX/n-Stream Playlists errors

[simoncn]

(07-12-2014 23:45)stampie Wrote:  So, after trying out a few things I have narrowed down the cause of the problem, just not sure where a fix needs to be implemented.

Firstly, naim app creates the same playlist regardless of where it is carried out in the app (so is not relevant to the problem).

I have managed to copy some of the playlist files to my pc for analysis in notepad, and discovered the following:

- I created a new playlist for an album, which worked for a day, but then suddenly the naim app stated the files could not be located on the server.

- I then created another new playlist for the same album, which is still working a couple of days later.

- By comparing the playlists, there is a difference in the contents in a value called UUID, which is shown against each track in the playlist.

During this period I have added new music to my collection and updated minimserver and naim app accordingly. (I provide this information in case relevant to the changing UUID values)

Please find attached the two playlists for Simon to take a look at.

Based on Simon's input I will then raise the issue with Naim.

thanks for reading
Nick

Thanks for this new information.

From a MinimServer perspective, the important difference seems to be the ObjID, not the UUID. The first track in the working playlist has an ObjID value of 0$=Artist$24061$albums$*a68$*i16448 and the first track in the not working playlist has an ObjID value of 0$=Date$908$albums$*a67$*i16401.

When MinimServer is restarted after adding new music, previous ObjIDs are likely to stop working. I'm not aware of anything in the UPnP specification that says this is incorrect behaviour.

I think the UUID field is something internal to the control point.

Some questions:

1) Are you using the new Naim app or the older n-Stream app?

2) How did you copy the playlists to your PC?

3) Do you see this problem if MinimServer hasn't been restarted?