Naim App Change Playlist Server
Posted by: juanito on 28 October 2015
After updating my NAS streamer software (Twonky), the streamer name changed.
Whilst the Naim App can find the streamer, none of my playlists work - presumably because of the streamer name change.
I cannot remember what the streamer was called in order to change the name back to the original.
Is it possible to edit the streamer name in the Naim App playlists to avoid having to recreate them all from scratch?
Oh dear, Twonky's gone wonky again.
I don't believe there's a way in the UI. If you could do this, you'd have to find the app's data in the memory of the device, download it to a computer, edit it (byte by byte) and then upload it again. There's no guarantee that after all that work that the playlists will function or even remain readable; they may crash the app or just disappear.
Probably not even worth trying.
Thanks <sigh> that's what I was thinking as well...
It's a pity the Naim App playlists can't be exported/transferred somewhere to make it easy to edit them - it's a lengthy task to re-create them on the Naim App itself.
I know it doesn't help your current situation, but people do seem to have more trouble with Twonky than with most other DLNA servers. Installing another server such as Minim or Asset may be a better bet in the long term. Would you consider this option?
As far as I know, Twonky is the only streamer Thecus offer for their NAS.
I guess I could install something else using some Linux acrobatics, but that still wouldn't take away the Naim App playlist issue and Twonky has worked without problems for me.
It would seem to make more sense for the Naim App playlist to use the streamer IP address rather than it's network name, but anyway...
Using the IP address would be most unwise, as that can sometimes change on reissue of the DHCP lease (typically reissued by the DHCP server every 24 hours).
Using the DNS name is actually more reliable (usually!) and the correct thing to do; things shouldn't change their name unnecessarily.
I guess you're right, but if the App looked for the streamer network name and then put the associated IP address in the playlist then, as long as the streamer had a static IP address, the playlist would still be good if the network name changed.
Of course, you could equally well argue the opposite.
..both my streamer and ND5 XS have static IP addresses, which seems to work better on a LAN with Linux, Mac and Windows machines.
You could try the web configuration page for Twony by going to port 9000 at the IP address of your NAS:
poke around and you should see quite a few configuration settings, including the server name. It's unusual for this to have changed, unless the host name for your Thecus has changed, as it defaults to an environment variable (%hostname%)... But you can call it what you like...so if you can look in a playlist file and see what it used to be, this might help.
Also useful is to check the base path for your music files, as that defaults to a generic location, and you might have files elsewhere. If you can play songs but not playlists, this isn't likely broken.
Regards alan
Thanks - I tried that, but the NAS network name had not changed and the Twonky server network name in the Twonky playlists is the new name.
I can play both individual tracks and Twonky playlists from the Naim App, it's just the Naim App playlists that were the problem.
Anyway, I've just finished tediously recreating the playlists on the App.
I guess you're right, but if the App looked for the streamer network name and then put the associated IP address in the playlist then, as long as the streamer had a static IP address, the playlist would still be good if the network name changed.
Of course, you could equally well argue the opposite.
..both my streamer and ND5 XS have static IP addresses, which seems to work better on a LAN with Linux, Mac and Windows machines.
DHCP is the default for almost all network devices (including Naim devices).
More people use dynamic IPs than use static IPs and those who use static are more likely to understand and be able to fix problems themselves.
Therefore it makes most sense to default to the system that works best with DHCP.