Print

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

[John Gateley]

MC's UPnP Server version 1.0.17 is available here:
http://www.jriver.com/~gateley/server_upnp1017.mjp
This is for Media Center 11 only.

Changes and fixes
1) Improved handling of options.

--------------------------------------------------------

Instructions for using the UPnP Server
Click on Plug-ins in MC's tree, then on UPnP Server.  On the right side of the UPnP Server page, set "Options" and then click on "Start" to start the server.

If a media receiver is already on the network, and the server is started, the receiver should pick up the server right away. When a media receiver is first turned on, if the server is already started, the receiver should pick up the server. Some receivers may not do both correctly, so try both.

If you cannot see your view scheme, make sure that:
1) The View Scheme is selected to Show in Theater View (under Edit View Scheme).
2) The View Scheme is a child of "Audio", "Images" or "Video".

Options
You can convert files to other formats (such as MP3 or WMA) as they are streamed.  See Options on the UPnP page.

If you have multiple network interfaces on your computer, such as an ethernet and a bluetooth interface, you may need to specify the IP address the UPnP server uses (it will only listen on a single interface, and may choose the one the device is not on).

Unless you are reporting log information here, you can turn off many warings by unchecking "Warn on unrecognized NOTIFY".

There are a set of options handling the different devices. Normally, you should select Receiver: Automatic Detection. If this does not correctly identify your UPnP device (it reports the device detected on the message page), then choose the device name. If your device name is not present, choose
Advanced and use the four special cases:

1.  "Replace Empty Genre" is required for the NETGEAR MP101, and possibly others. It replaces blank genres with "Unknown". The MP101 will otherwise refuse to play tracks with blank genres.

2.  "Use Flat URLs" is required for the SMC EZ Stream and the Terratec Noxon. These receivers cannot handle complex URLs (internal to the protocol) and this hack changes the URLs to simpler ones.

3. "Include SessionID" must be turned off for Roku. It may be required for others. If you know of a device that requires it, please let me know.

4. "No server header" must be turned on for the D-Link DSM 320. It stops the emission of an HTTP Server header.

A log is generated on the UPnP Server page in MC.  If you have a UPnP device that doesn't work, you can copy the log from MC's UPnP Server (under the tree/plug-ins) and paste it into a thread here. Make sure the "Warn on unrecognized NOTIFY" option is selected before creating the log.

A thread that explains more about UPnP and how MC supports it:
http://yabb.jriver.com/interact/index.php?topic=25689.0

Supported UPnP Devices are here:
http://yabb.jriver.com/interact/index.php?topic=25839.0

The previous thread on the UPnP Server:
http://yabb.jriver.com/interact/index.php?topic=26730.0

[John Gateley]

Hi Y'all, I've improved the option handling, but I need help with a couple of devices we don't have in house. If you have a terratec Noxon, or an SMC EZStream, could you set the "Auto Detect" feature, connect, and then copy and paste the log here? It will tell me what I need to know to auto detect these.

Thanks, and enjoy,

j

[Myron]

John,

Any luck on the internet radio streaming issue with the SL400i yet?

[John Gateley]

Hi Myron,

Bad news: Philips is getting files in a way incompatible for streams. I've got a post up in the streamium forum, maybe I'll get some leads from that. But it means it's not a simple problem.

Gory details: The Streamium does an HTTP GET with a URL that tells UPnP Server which file or stream to get. This GET has a "Range: bytes=0-" header (which means  give it all bytes). The response must include a "Content-Range: bytes=0-x/y" header where x and y should be the length of the stream minus 1, and the length of the stream, respectively. Now you see the problem: the stream doesn't have a length, so I can't put anything meaningful in there.

j

[Myron]

John,

Thanks for the update.  This is indeed bad news, but it does spur a couple of questions:

Can you identify what's changed between the .14 and .15 release of the server that would impact radio streams?  The .14 server at least worked for 41 seconds before quitting, so I'm wondering if some arbitrarily large number could be used for the stream length.  If radio streams could be made to work for some hours, that could be an acceptable compromise, at least for now.

Are Streamiums unique in this implementation?

The other thing you may or may not be aware of is that Streamiums do support internet radio streams but they must be entered on a Philips web server.  Each user has an account and can store custom radio URLs.  So somehow, Philips' server is acting as an interface between all the Streamiums out there and all the internet streams.  I seem to remember that you at least had access to a Streamium unit, so could something be learned by "watching" how streams work the "official" way?

Finally, I'd just like to add that internet streams are important, but personally, I'd rather see more basic functions added to your UPnP server before internet streaming is ironed out.  I'm thinking about things like alphabetic search, shuffle and eventually cover art.

[Rob L]

I haven't tried .17 yet, but by the looks of it, it hasn't fundamentally changed since .16, and with .16 I still can't get streams to work on my MP101 - I still get the "Item is currently unavailable" whichever stream I try and access.

The UPnP log screen doesn't even show it trying to access the stream - I was surprised to see someone else quoting a log entry that did actually have http:// entries in it, because mine never does!

[John Gateley]

Hi Myron,

Thanks for the comments, I'll look into it when I get a chance...

Rob - what stream are you trying?

j

[Rob L]

several, all of which play fine locally in MC11.

This is probably the simplest example in terms of the actual URL though:

http://s2.soundicradio.com:8100

[helpme]

I haven't tried .17 yet, but by the looks of it, it hasn't fundamentally changed since .16, and with .16 I still can't get streams to work on my MP101 - I still get the "Item is currently unavailable" whichever stream I try and access.

The UPnP log screen doesn't even show it trying to access the stream - I was surprised to see someone else quoting a log entry that did actually have http:// entries in it, because mine never does!

Same problem here in all the builds so far.

MP3 and WMA streams play fine in MC11  , placed into a radio playlist but only get the "Item is Currently unavailable" message on the MP101 and nothing in the log.

Streams like

http://64.236.34.97:80/stream/1024 for MP3

or

mms://media4.abc.net.au/network1  for wma

Stephen

[helpme]

Problem with extended character set ?

With Build 230 I was not able to browse or search for Bublé, Michael on mP101

Whenever a browse even got the place where the next screen would show Bublé the MP101 would search for five minutes then loose connection with the server ?

The server log shows nothing.

Changing the name to Buble fixed the problem.

I'm also still finding the MP101 does have a tendency to loose the server. Either when standin idle for a while after playing an album or even when playing an album and I try to back out and search for something else.

[MartinD]

Hi John,

1.0.17 does not work with the Noxon.

I have chosen "Terratec Noxon" in the options dialog.
This is the log:

Code: [Select]

04/09/05 13:46:23 - Received request for device description
04/09/05 13:46:27 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/09/05 13:46:27 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/09/05 13:46:27 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/09/05 13:46:27 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/09/05 13:46:27 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
04/09/05 13:46:27 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:AVTransport:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:AVTransport:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1
04/09/05 13:46:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:HtmlPageHandler:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:HtmlPageHandler:1
04/09/05 13:46:29 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/09/05 13:46:31 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/09/05 13:46:33 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/09/05 13:46:34 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/09/05 13:46:35 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
04/09/05 13:46:35 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:device:MediaRenderer:1
04/09/05 13:46:38 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:RenderingControl:1
04/09/05 13:46:44 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:00000000-0000-0000-0000-08000E200000::urn:schemas-upnp-org:service:ConnectionManager:1
04/09/05 13:46:44 - Unable to handle SOAP Action: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse", Request:
04/09/05 13:46:44 - <?xml version="1.0" encoding="utf-8"?>
<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ObjectID>0</ObjectID>
<BrowseFlag>BrowseDirectChildren</BrowseFlag>
<Filter>*</Filter>
<StartingIndex>0</StartingIndex>
<RequestedCount>10</RequestedCount>
<SortCriteria />
</u:Browse>
</s:Body>
</s:Envelope>

With "Automatic Detection" I get

Code: [Select]

04/09/05 13:50:41 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible)
04/09/05 13:50:41 - Received request for device description
04/09/05 13:50:45 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/09/05 13:50:45 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
...
(rest is same as above)
The Noxon "sees" MC. The request is sent when I try to browse the server.

-Martin

[evanr76]

As of .234,

I still can't choose options for WMA conversion (Media Core crashes in wm_enc.dll).

The first few seconds of songs still repeat with the DSM-320 v1.05.

Just me?

[JimH]

As of .234,

I still can't choose options for WMA conversion (Media Core crashes in wm_enc.dll).

The first few seconds of songs still repeat with the DSM-320 v1.05.

Just me?

I can't duplicate this.  What OS?  Did you let MC update Windows Media when you installed?

[SuperRabbit0]

Not sure where to put this but it seems worth a shot.  I spent much of the weekend playing with Twonkyvision and Media Center UPnP services.

As I have been a long time fan of Media Center I am hoping I can get it working just how I want and it seems to be coming along great so far.

There are a few things that would greatly improve the experience with my new Netgear MP101 (with a wired connection).

1)  Make the Genre, Artist, etc. buttons on the remote usable.  These are a very good idea.  Looking at the Twonky development logs, it looks like they had to add some special functionality to make them work.

2)  Allow me to get rid of the Audio and Video entries when I go through "Browse Music" on the MP101.  I have tried delting them, making them not viewable in Theater Mode but they still are there.

3)  Allow it to go right through the Audio entry.  Even if I move all of my views to be a child of Media Library in MC, they still appear under Audio on the MP101.  I would like to select Browse Music and have my list of views appear.

4)  I am not sure why but my MP101 loses connection with the MC service after a while (usually several hours).  I ran Twonky all night and it never lost connection.  Most MC could make was 3 hours at a time.  I had the MP101 set to Shuffle Repeat All....

Anyways, thanks for the great work on this plugin.  Once I read about it here, I bought an MP101 right away and I am glad I did!

[John Gateley]

Thanks for the suggestions.

About the losing connection - I've seen a similar thing, but it is content that is not playable on the MP101 (like a video file).
Could this be the problem?

j

[eso]

Just for info, I have the same problem with the Terratec Noxon not allowing to browse the MC UPnP server anymore.

04/13/05 09:25:26 - Unable to handle SOAP Action: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse", Request:
04/13/05 09:25:26 - <?xml version="1.0" encoding="utf-8"?>
<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ObjectID>0</ObjectID>
<BrowseFlag>BrowseDirectChildren</BrowseFlag>
<Filter>*</Filter>
<StartingIndex>0</StartingIndex>
<RequestedCount>10</RequestedCount>
<SortCriteria />
</u:Browse>
</s:Body>
</s:Envelope>

[John Gateley]

For those with the Noxon problems, I'm missing a small but critical piece of info.

There's a newer version with a better error message now at:

http://www.jriver.com/~gateley/server_upnp1017.mjp

Please download it and report the new and improved error here.

j

[eso]

Please download it and report the new and improved error here.

Here it is:

04/13/05 18:33:49 - Unable to handle SOAP Action: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse", URL Path: /control, Request:
04/13/05 18:33:49 - <?xml version="1.0" encoding="utf-8"?>
<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<u:Browse xmlns:u="urn:schemas-upnp-org:service:ContentDirectory:1">
<ObjectID>0</ObjectID>
<BrowseFlag>BrowseDirectChildren</BrowseFlag>
<Filter>*</Filter>
<StartingIndex>0</StartingIndex>
<RequestedCount>10</RequestedCount>
<SortCriteria />
</u:Browse>
</s:Body>
</s:Envelope>

[John Gateley]

Under the UPnP Options, choose "Advanced" as the receiver, then select "Use Flat URLs" and "Include Session ID".
Let me know if it works...

j

[eso]

Under the UPnP Options, choose "Advanced" as the receiver, then select "Use Flat URLs" and "Include Session ID".
Let me know if it works...

These options are both enabled already. I have tried it with the Noxon preset and by setting the advanced options manually.

[John Gateley]

I was afraid of that. Do you know if the Noxon has upgraded it's software recently?

It looks like the problem is on the Noxon side - we give it a URL to use, and it is mangling that URL.

A network sniff of the entire communication sequence would be helpful, if any of y'all Noxon owners can sniff the network...

j

[eso]

Do you know if the Noxon has upgraded it's software recently?

No, it's the same Noxon that had already worked quite well with MC. I haven't used it for some weeks so I cannot tell with which version the MC UPnP support stopped working.

I currently don't have a tool like ethereal installed so I would need to do so first. But I'm quite busy at the moment so I cannot tell when I'll find the time...

[John Gateley]

a lot of the UPnP devices automatically upgrade their software. The Noxon may have done the same.

I'm kind of stuck without a Noxon and without a network sniff, so if you could do that sometime it would help.

j

[eso]

No, the Noxon doesn't update automatically. And Terratec hasn't released any updates for it yet. I'll see if I can install Ethereal within the next days and perform a scan.

[John Gateley]

How do you know the noxon doesn't update automatically? I'm curious because the evidence is pointing towards a change on Noxon's end. I'm not sure, of course, but that's what it looks like. If you're positive that the noxon doesn't update itself, I will look in other directions...

j