Hi - yes I confirm that Chromecast isn't running on my network at all. Many thanks - John

Hi,
thanks for the log.

It seems to be caused by the new mDNS discovery method added because of Chromecast audio devices detection:
https://www.ventismedia.com/mantis/view.php?id=14645#c49633

It is detecting a device 'DAW' that doesn't seem to be Chromecast at all and crashes on it. Will be fixed in the build 2108 (item 2 here https://www.ventismedia.com/mantis/view.php?id=14645#c49633 )

Logged with debug as ticket: #IAN-428-42013

Hi - Unfortunately 2106 exhibits the same behaviour (big white screen), so I'll generate you a log this evening when I'm at home.

Hi, unfortunately Rusty has posted 17 days old build (2104) instead of the new 2106,
please download the 2106 debug from here: https://www.dropbox.com/s/t27i396fruejv0i/MediaMonkey_5.0.0.2106_Debug.exe?dl=0
and give a try.

If 2106 also fails for you then please generate debug log.
Thanks!

Unfortunately this has got worse. On build 2104 when I try to "play to" another device, the whole mm5 app goes white with no error message and I have to kill it in task manager.

Great - thanks Ludek.

[quote=jmcc post_id=445349 time=1527115269 user_id=55657]
If I then press "Stop" on PC2 so that the seekbar goes back to zero, when I play something using PC1 as controller all works as it should. It's like once the song is launched on PC2, it will continue playing it until stopped on PC2 itself,
[/quote]

I cannot replicate, in my case double clicking track on PC2 (MM5) always clears the now playing queue on PC1 (MM4) and adds the double clicked song and plays it.
But maybe the issue is that I am testing 2106 while you are testing 2089 (3 months old build), I will ask the MM5 team to release another alfa/beta.

That's how I do it now, but it's not a very elegant solution. There's also potential issues with audio redirection using RDP.

Just RDP into the second PC

Hi - I've now seen it exhibiting both behaviours. If I play something directly on PC2, it plays fine, but if I then select something on PC1, when I double click on it, it plays what was previously playing on PC2. If I then delete the now playing list on PC2, then try to play something via PC1, it still plays the song that was previously playing on PC2. If I then press "Stop" on PC2 so that the seekbar goes back to zero, when I play something using PC1 as controller all works as it should. It's like once the song is launched on PC2, it will continue playing it until stopped on PC2 itself, after which it hands back song selection control to the DLNA controller, though the Play, Pause, etc. transport controls have been working fine all along.

Hi Ludek, here's my scenario:

PC1 - controller running MM5 with "Play To" set to PC2.
PC2 - DLNA server and renderer on MM4

When you start playback - is the song playing on MM4 instance?

When I right-click and "Play Now" on the controller (PC1) for a DLNA based song on PC2, a song starts playing on the renderer (PC2), but it's not the song that I selected on PC1, but the song from the "Playing" queue on PC2. If I delete everything from the "Playing" queue on PC2, then nothing plays when I right-click and "Play Now" on the controller (PC1).

Hi, doing a quick test on the same PC with MM4 (renderer + server) and MM5 (control point) and it works here.
In MM4 NP queue is only a single track (added by MM5 when I double clicked it in MM5) and once the playback ends then MM5 adds next track from MM5 NP to MM4 NP and plays:
https://www.dropbox.com/s/ng8qlb66n4uc2yc/Screenshot%202018-05-23%2011.53.24.png?dl=0

EDIT:
What exactly isn't working for you?
a) When you start playback - is the song playing on MM4 instance?
b) Is the seekbar moving and in sync on both instances?
c) Once the first track ends, does it start playback of the next track in MM5 queue?

Playing with it a bit and found that b) wasn't true once (i.e. seekbar wasn't moving in MM5) and sometimes c) happens, i.e. it plays only one track. Looking into it...

If the playback doesn't start at all for you then please generate debug log from the MM5 (control point) instance for me to analyze.

EDIT2: The issues with postponing to the next track and seekbar moving (b,c) are fixed in build 2106

Not sure if it was a MM5 controlling MM4 issue, but when I tried this last night with PC1 (running MM5) as controller, PC2 (running MM4) as DLNA server and renderer it played the playlist loaded on PC2 rather than the songs I had selected from PC1 acting as remote. When I removed the playlist from PC2 it didn't play anything.

In a sense this validates the fact that it doesn't pass via PC1, but something still seems to be awry.

Excellent - I'll give it a go this evening when I get home!