Print

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

[mimizone]

One of my DLNA renderer is not the most stable (a Sony STR-DN1050 receiver).
The problem is that it throws off Media Center and makes the user experience not smooth.

Here's the problem:
Sometimes, the renderer seems to not be able to play anymore (crashed probably, that requires a power cycle of the receiver...thanks Sony...)

JRiver MC would then show a blocking popup with the message "There was a problem controlling the selected DLNA device." etc...
With only the option to press "OK"
But if a bunch of tracks are still in the list to be played, JRiver is going to try to play every tracks.

It has 2 consequences.
JRiver is not responsive when trying to talk to the DLNA device, showing the rainbow wheel as a cursor, like everytime JRiver waits for a DLNA response in my experience, since it seems to not be async/non-blocking calls.

then the same over and over again top-level error pop-up window is shown.

all that until the player went over all the remaining tracks in the list for the device.


Is there a quick fix to that behavior by just toggling a setting?

Would be great if the player was not stuck because of an external device time-outing.
Maybe the pop-up could offer the option to stop trying?

[JimH]

What version of MC are you using?

[bob]

I've seen that before as well.
I think it should flush the playlist when the device goes down or as you say allow the popup to offer dismissing the playback queue.

[mimizone]

Now I use the latest version 28.0.98

But that problem has been around for a while.
I experienced the same since version 24.

One thing to note is that if I just wait a few minutes (I would have to measure) and don't press OK on the popup right away, MC doesn't try to play the next tracks anymore I believe, and shows another popup about having issues connecting or something along those lines.
I'll try to capture that message next time it happens.

There must be 2 different timeouts or something like that in the source code I assume.