Print

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

[mattkhan]

I noticed this in https://yabb.jriver.com/interact/index.php/topic,114694.msg793974.html#msg793974

I have some DLNA devices and an MC client configured with the "DLNA Controller" checkbox checked. If I select something to play and send it to the DLNA device then I get errors and the target device logs that MC is trying to tell it to play a uri like

Code: [Select]

setAVTransportURI: uri=m01p://xxx.xxx.xxx.xxx:yyyyy/MCWS/v1/File/GetFile?File=780388, metadata=<DIDL-Lite xmlns="urn:schemas-upnp-org:metadata-1-0/DIDL-Lite/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:upnp="urn:schemas-upnp-org:metadata-1-0/upnp/" xmlns:dlna="urn:schemas-dlna-org:device-1-0" xmlns:av="urn:schemas-sony-com:av" xmlns:pv="http://www.pv.com/pvns/" xmlns:jriver="urn:schemas-jriver-com:jriver">

if I repeat the same operation on the MC server, with an DLNA server configured with the same options, then the setAVTransportURI log statement above is the same except it uses http instead of m01p

This looks like a bug to me, i.e. the client appears to be using its internal protocol when passing that onto the DLNA device.