Vuze Forums

So I have an older Samsung LED TV with DLNA. I'm trying to get vuze to play a video to the TV over LAN.
This fails with error "Download failed too recently, ignoring".
I looked closely at what's causing the error. It appears that vuze fails to download connectionmanager schema:

Code:
Renderer: getSupportedSourceProtocols failed: Download failed too recently, ignoring

Code:
org.gudy.azureus2.plugins.utils.resourcedownloader.ResourceDownloaderException: http://mytvip:52235/ConnectionManager1.xml: Error on connect for 'http://mytvip:52235/ConnectionManager1.xml': 404 Not Found

Indeed, there is no schema at "http://mytvip:52235/ConnectionManager1.xml"

Now, the connection manager schema url comes from the device descriptor schema, which vuze downloads successfully:

Code:
Downloading: http://mytvip:52235/dmr/SamsungMRDesc.xml

The content of the device descriptor is as follows:

Code:
<root xmlns="urn:schemas-upnp-org:device-1-0">

<specVersion>

<major>1</major>

<minor>0</minor>

</specVersion>

<device>

<deviceType>urn:schemas-upnp-org:device:MediaRenderer:1</deviceType>

<dlna:X_DLNADOC xmlns:dlna="urn:schemas-dlna-org:device-1-0">DMR-1.50</dlna:X_DLNADOC>

<friendlyName>TV in a living room</friendlyName>

<manufacturer>Samsung Electronics</manufacturer>

<manufacturerURL>http://www.samsung.com</manufacturerURL>

<modelDescription>Samsung DTV DMR</modelDescription>

<modelName>Samsung DTV DMR</modelName>

<modelNumber>1.0</modelNumber>

<modelURL>http://www.samsung.com</modelURL>

<serialNumber>20081224DMR</serialNumber>

<UDN>uuid:72712b85-8e29-fd3d-2f42-a5e67efd1cc8</UDN>

<serviceList>

<service>

<serviceType>urn:schemas-upnp-org:service:RenderingControl:1</serviceType>

<serviceId>urn:upnp-org:serviceId:RenderingControl</serviceId>

<controlURL>/upnp/control/RenderingControl1</controlURL>

<eventSubURL>/upnp/event/RenderingControl1</eventSubURL>

<SCPDURL>RenderingControl1.xml</SCPDURL>

</service>

<service>

<serviceType>urn:schemas-upnp-org:service:ConnectionManager:1</serviceType>

<serviceId>urn:upnp-org:serviceId:ConnectionManager</serviceId>

<controlURL>/upnp/control/ConnectionManager1</controlURL>

<eventSubURL>/upnp/event/ConnectionManager1</eventSubURL>

<SCPDURL>ConnectionManager1.xml</SCPDURL>

</service>

<service>

<serviceType>urn:schemas-upnp-org:service:AVTransport:1</serviceType>

<serviceId>urn:upnp-org:serviceId:AVTransport</serviceId>

<controlURL>/upnp/control/AVTransport1</controlURL>

<eventSubURL>/upnp/event/AVTransport1</eventSubURL>

<SCPDURL>AVTransport1.xml</SCPDURL>

</service>

</serviceList>

</device>

</root>

So it turns out that ConnectionManager1.xml schema url on my TV is relative to the location of the device descriptor schema. Namely:

Code:
http://mytvip:52235/dmr/ConnectionManager1.xml

and not

Code:
http://mytvip:52235/ConnectionManager1.xml

where vuze is trying to find it.
Same goes for AVTransport1.xml and RenderingControl1.xml schemas.

According the UPNP specs, SCPDURL is "relative to the URL at which the device description is located". Vuze appears to be looking for it in the root of the server.

I tried doing a playback on my windows medial player 11 DLNA and it works just fine with my TV.
So I'm wondering if there is a bug in the vuze plugin or and obscure issue with my TV DLNA configuration. I'm running the latest Vuze 5.7 with the latest upnp plugin 0.5.6 on Windows 7.

upnp_user