Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[sjhilton]

Hi,
I have a setup with a server and two clients used primarily for audio. The server is on my NAS and one client plays to my DAC/amplifier (hifi client) and the other client displays the currently playing track on the TV (TV client). My ideal setup would be to have both clients using the 'show playback zones from the server on the client' option as this would allow complete playlists to be displayed on the TV client rather than just the track playing on the hifi client.
The issue I am noticing is that if I play DLNA content to the hifi client the tv client displays a random album (not a track from the album) from my local MC library as playing. I've done a little bit of digging with MCWS and it appears that the DLNA track and the album have the same 'key'. The key appears to be generated by MC itself rather than coming from the source DLNA content. Has anyone observed a similar issue? I've replicated this on a couple of clients, but it could be something peculiar to my library/setup.
Happy to provide further details.
Thanks in advance for any thoughts.

[sjhilton]

Hi,
Further updates on this - the server itself (which is headless) indicates the correct playing media for DLNA content. It is just the TV client that exhibits this behaviour. Looking at a number of the posts on this forum indicates that a 'key' is allocated to each media file in the library database. I haven't been able to identify why a 'key' would be allocated to an album. I also don't understand why DLNA content would be allocated a 'key' if it is not imported into the database. I disabled all of the import functions on each of the clients and also the 'import on play' on the server, but this didn't have any effect on the behaviour.
Any thoughts welcome.

[sjhilton]

A final thought on this is that I've been looking at previous discussions of MC acting as a DLNA proxy eg https://yabb.jriver.com/interact/index.php?topic=95524.0 and https://yabb.jriver.com/interact/index.php?topic=119987.0. That could mean that the server presents the various zones on the clients as different dlna renderers (as well as other dlna renderers). If that was able to be implemented I suspect that may solve my current issue.

[thecrow]

Has anyone observed a similar issue? I've replicated this on a couple of clients, but it could be something peculiar to my library/setup.

I see the same problem on my setup too.
As you say, I only see it when using a client connected to a server and then sending to a DLNA zone.
It's been like this for years and I've been unable to fix it.