Print

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

[Mike Joy]

MC 23 fails to continue play playlist when using DLNA.

Setup vortexbox as server

WDTVLIVEHUB for dnla

No problem with MC22

 any solutions???

[JimH]

In MC, try changing the setting for SetNextAVTransport in the settings for the DLNA server.

[AndrewFG]

In MC, try changing the setting for SetNextAVTransport in the settings for the DLNA server.

Jim, I know that I keep saying this, but MC could easily test the renderer if it supports SetNext, and if it does not, it could easily turn off this setting. Just call th SetNext SOAP Action once, and if the renderer returns anything than HTTP 200 OK, or suffers a socket disconnect, then turn off the feature automatically.

[JimH]

Bob thinks that the renderers aren't reliable in what they report.

I agree with you that we could probably make some changes automatically.

I appreciate that you keep saying it, by the way.

[AndrewFG]

Don’t ask the renderers what they report. Try to issue the command. And if it fails, the feature is clearly not supported.

[bob]

It does test and that normally works.
It's only the broken renderers that say they support it and don't work properly that is the issue.

[AndrewFG]

Hi bob, it’s good to hear you do that. I just find it stunning that at least once a week I am posting a message here about Disable SetNext. There must apparently be so many bad renderers out there, it is hard to believe. All I am getting at really is that if I am clever enough to read these symptoms in an often garbled post, and conclude “Disable SetNext” then it surely must be possible to devise some kind of automaton inside MC that can do the same with less pain all round..

[bob]

Hi bob, it’s good to hear you do that. I just find it stunning that at least once a week I am posting a message here about Disable SetNext. There must apparently be so many bad renderers out there, it is hard to believe. All I am getting at really is that if I am clever enough to read these symptoms in an often garbled post, and conclude “Disable SetNext” then it surely must be possible to devise some kind of automaton inside MC that can do the same with less pain all round..

I've been working on controller code a lot lately, trying to make it more flexible over funky renderer behavior. It might be possible to add more checking, it's not clear to me how it's failing since I don't have a device which reproduces that behavior.
Another possibility would be to just turn it off by default.