Topic: UPnP Server Plug-in for Media Center 11 (Read 32634 times)

John Gateley · « **on:** April 13, 2005, 03:51:36 pm »

MC's UPnP Server version is available here:
[It's in Media Center 11.0.236 or later -- available shortly].
This is for Media Center 11 only.

Changes and fixes
1) Better autodetection (added a couple of new devices, removed Netgear MP101 because it was too generic and matched non MP101 devicees).
2) Support for Buffalo LinkTheater device
3) A new option that restricts to root level to audio fields only (for devices that do not have video output, and can't display pictures or TV).
4) Fixed the Use Flat URLs option. It was broken a few versions back when I changed the option handling code.

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

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 five 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.

5. "Allow Visual Content" should be turned on for devices that can display pictures or movies. Otherwise the top level of the library will be restricted to audio and playlists.

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=26774.0

John Gateley · « **Reply #1 on:** April 13, 2005, 04:11:14 pm »

Hi Noxon Users - I found the problem, and managed to sneak it in this build.

Thanks for your patience...

j

eso · « **Reply #2 on:** April 14, 2005, 01:58:46 am »

Yes, it works again. But I have the problem that I cannot browse my playlists. If I try the Noxon jumps back to it's first menu screen. Browsing the audio view scheme works.

And to answer your last question yesterday: the Noxon is a very simple device that can only be updated manually. But so far Terratec hasn't released any updates.

helpme · « **Reply #3 on:** April 14, 2005, 03:54:23 am »

Each release looks better and better

Any idea on Internet radio ? still getting the item unavailable message.

raistlin2k · « **Reply #4 on:** April 15, 2005, 01:45:05 am »

OK, I received my Netgear MP101 yesterday, and I'm impressed. It's really much better than the Noxon I had before.

BUT:
- I have frequent loss of connection during playback (wired) with MC as server, with Twonkyvision no problem at all.
- Using a viewing sheme with an umlaut in the name ("Hörspiel") the Netgear cannot browse past "Audio" from the main menu, it simply hangs, renaming the sheme to "Hoerspiel" everythink OK.
- Netgear browsing is MUCH slower using MC as server compared to Twonkyvision.

So my resumée: MC is the way to go, because Twonkyvision offers no custom views, but it is still quite buggy (speed, loss of connection) and need more improvement, PLEASE!! At the moment, I have to use Twonkyvision server because with MC it's too uncomfortable due to bugs.

please have a look at this, John!
thanks a lot
Raist

Afrosheen · « **Reply #5 on:** April 15, 2005, 02:34:10 am »

Problem with SMC ezStream

I'm using MC 11 240 Beta with UPnP Server 1.0.18
I've set it up with "specify ip address" and using the same address i use for my comp
it starts up and says this:

04/15/05 00:28:23 - JRiver UPnP Server Version 1.0.18 starting...
04/15/05 00:28:24 - Server running on address 192.168.2.110, port 4996
04/15/05 00:28:24 - Running
04/15/05 00:28:26 - Received request for device description

and when I have the NOTIFY option checked it says all of this:

04/15/05 00:28:27 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0001-0000-0004e2a7885e::upnp:rootdevice
04/15/05 00:28:27 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0000-0004e2a7885e, USN: uuid:00000000-0000-0001-0000-0004e2a7885e

Am I missing a step or is there something I'm not aware of that's not allowing me to use MC as my media server?

helpme · « **Reply #6 on:** April 15, 2005, 03:35:55 am »

If I run media server then attempt to run media Centre (either by right clicking media server or from it's own shortcut) media centre shows as running in the task manager but does not display on screen.

Also any news on the extended character set problem that raistlin2k is having as well ? Like him I don't get this problem with twonky or the netgear server, only with MC

John Gateley · « **Reply #7 on:** April 15, 2005, 10:53:24 am »

Hi Y'all,

I'll check on these...

j

evanr76 · « **Reply #8 on:** April 16, 2005, 01:32:10 am »

John can you verify that the DSM-320 on your test bench is running the 1.05 firmware?

JimH · « **Reply #9 on:** April 16, 2005, 07:47:05 am »

Quote from: helpme on April 15, 2005, 03:35:55 am

If I run media server then attempt to run media Centre (either by right clicking media server or from it's own shortcut) media centre shows as running in the task manager but does not display on screen.

What build of MC are you using?

Marc · « **Reply #10 on:** April 16, 2005, 02:25:13 pm »

Why does the UPnP select some seemingly random IP address when left to its' own devices?

Currently, my system is running with a DHCP-assigned address (192.168.1.104), but the UPnP server selects 169.254.241.150 as its' address. Of course, my Netgear MP101 can't find this address, so I have to "hardcode" the -.104 address to get it to work. When the DHCP address changes (like when there was a power failure last time I was away on a business trip), the system breaks. My wife then calls me and says the MP101 can't find the server...

Can't the UPnP plugin detect the IP address of the system it's running on, and use this as the default? What am I missing here?

Thanks in Advance for whatever light you can shine on this. My system info. is as follows:

Media Center Registered 11.0.241 -- C:\Program Files\J River\Media Center 11\

Microsoft Windows XP Workstation 5.1 Service Pack 2 (Build 2600)
Intel Pentium 4 3071 MHz MMX / Memory: Total - 1048 MB, Free - 544 MB

Internet Explorer: 6.0.2900.2180 / ComCtl32.dll: 5.82 (xpsp_sp2_rtm.040803-2158) / Shlwapi.dll: 6.00.2900.2627 (xpsp_sp2_gdr.050309-1648) / Shell32.dll: 6.00.2900.2620 (xpsp_sp2_gdr.050225-1820) / wnaspi32.dll: N/A
Ripping / Drive P: Mode:Normal Type:Auto Speed:Max
Drive Q: PIONEER DVD-RW DVR-105 Mode:Normal Type:Auto Speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: No / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No

Burning / Drive P: LITE-ON LTR-52246S Addr: 1:0:0 Speed:52 MaxSpeed:52 BurnProof:Yes
Drive Q: PIONEER DVD-RW DVR-105 Addr: 1:1:0 Speed:16 MaxSpeed:16 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: Yes
Use playback settings: No / Normalization: None

JimH · « **Reply #11 on:** April 16, 2005, 02:27:55 pm »

Try Start/Run/CMD and then, at a command prompt, type ipconfig.

You may have more than one IP interfaces running. I had a similar problem and it turned out to be bluetooth, I believe. I had to disable the interface by going to Network Properties and right clicking on the bluetooth icon.

I'm not certain, but this may be a Windows problem.

helpme · « **Reply #12 on:** April 16, 2005, 05:38:27 pm »

Quote from: JimH on April 16, 2005, 07:47:05 am

What build of MC are you using?

I was using 240 241 seems to have fixed the problem. Thanks,

dun4cheap · « **Reply #13 on:** April 17, 2005, 03:10:35 am »

Update on the SMC EZStream this is the video and audio ezstream with FW 1.2.8b, 2004-11-10

AutoDetect On

04/17/05 00:57:33 - JRiver UPnP Server Version 1.0.18 starting...
04/17/05 00:57:34 - Server running on address 192.168.1.100, port 3374
04/17/05 00:57:34 - Running
04/17/05 00:57:35 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows NT/5.1)
04/17/05 00:57:35 - Received request for device description
04/17/05 00:57:35 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows NT/5.1)
04/17/05 00:57:35 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows NT/5.1)
04/17/05 00:58:03 - Server Stopped
04/17/05 00:58:06 - JRiver UPnP Server Version 1.0.18 starting...
04/17/05 00:58:07 - Server running on address 192.168.1.100, port 3415
04/17/05 00:58:07 - Running
04/17/05 00:58:09 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows NT/5.1)
04/17/05 00:58:09 - Received request for device description
04/17/05 00:58:09 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows NT/5.1)
04/17/05 00:58:09 - Cannot autodetect device, User-Agent: Mozilla/4.0 (compatible; UPnP/1.0; Windows NT/5.1)

Set to SMC EZstream

04/17/05 01:02:17 - Server Stopped
04/17/05 01:02:19 - JRiver UPnP Server Version 1.0.18 starting...
04/17/05 01:02:20 - Server running on address 192.168.1.100, port 3486
04/17/05 01:02:20 - Running
04/17/05 01:02:22 - Received request for device description
04/17/05 01:03:00 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::upnp:rootdevice
04/17/05 01:03:00 - Unknown SSDP Server method: NOTIFY, NT: uuid:01c84f81-015b717f-01e5bb87-febaf8b5, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5
04/17/05 01:03:00 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::urn:schemas-upnp-org:device:MediaRenderer:1
04/17/05 01:03:00 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::urn:schemas-upnp-org:service:AVTransport:1
04/17/05 01:03:34 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::upnp:rootdevice
04/17/05 01:03:34 - Unknown SSDP Server method: NOTIFY, NT: uuid:01c84f81-015b717f-01e5bb87-febaf8b5, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5
04/17/05 01:03:34 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::urn:schemas-upnp-org:device:MediaRenderer:1
04/17/05 01:03:34 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::urn:schemas-upnp-org:service:AVTransport:1
04/17/05 01:03:34 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::urn:schemas-upnp-org:service:ConnectionManager:1
04/17/05 01:03:34 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:01c84f81-015b717f-01e5bb87-febaf8b5::urn:schemas-upnp-org:service:RenderingControl:1
04/17/05 01:03:40 - Received request for device description

Hint for those of you with multiple NIC cards

If you go in to the network connections in the control panel and then select the Advance menu on top and then Advanced Settings it will list all your network connections. Select the device that you want MC to use to detect network settings and move it to the top of the list. It appears MC11 takes the topmost by default. Probably because it does not enumerate the controllers it just takes the default.

Lastly, when I try to set the IP address manually it trys to start on port 0 and errors out. Is this a bug or am I doing this wrong.

Thanks,

MartinD · « **Reply #14 on:** April 17, 2005, 02:54:30 pm »

Hi,

Automatic Detection does not work for Terratec Noxon. This is the log:

Code: [Select]

04/16/05 14:36:09 - Autodetected: Terratec Noxon
04/16/05 14:36:09 - Received request for device description
04/16/05 14:36:11 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/16/05 14:36:11 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/16/05 14:36:11 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/16/05 14:36:11 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/16/05 14:36:11 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:12 - 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/16/05 14:36:13 - 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/16/05 14:36:13 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/16/05 14:36:15 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0000-0000-08000E200000::upnp:rootdevice
04/16/05 14:36:15 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/16/05 14:36:15 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0000-0000-08000E200000, USN: uuid:00000000-0000-0000-0000-08000E200000
04/16/05 14:36:22 - 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/16/05 14:36:23 - 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/16/05 14:36:25 - 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/16/05 14:36:26 - 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/16/05 14:36:27 - 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/16/05 14:36:29 - 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/16/05 14:36:30 - 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/16/05 14:36:30 - 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/16/05 14:36:38 - Cannot autodetect device, User-Agent: 
04/16/05 14:36:38 - Cannot autodetect device, User-Agent: 
04/16/05 14:36:38 - Cannot autodetect device, User-Agent: 
04/16/05 14:36:38 - Cannot autodetect device, User-Agent: 
04/16/05 14:36:38 - Cannot autodetect device, User-Agent: 
04/16/05 14:36:38 - Unable to handle SOAP Action: "urn:schemas-upnp-org:service:ContentDirectory:1#Browse", URL Path: /ContentDirectory_control, Request:
04/16/05 14:36:38 - <?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>

It works when I explicitly select the Noxon.

I have the same problem as eso and can't browse my playlists (at least most of them, very simple smartlist are ok).

Thanks
-Martin

Marc · « **Reply #15 on:** April 17, 2005, 08:43:25 pm »

Quote from: JimH on April 16, 2005, 02:27:55 pm

Try Start/Run/CMD and then, at a command prompt, type ipconfig.

You may have more than one IP interfaces running. I had a similar problem and it turned out to be bluetooth, I believe. I had to disable the interface by going to Network Properties and right clicking on the bluetooth icon.

I'm not certain, but this may be a Windows problem.

You were right. It was picking up the other interface first. When I shut down the other interface, MC picks up the default IP. Too bad it doesn't have the smarts to select a preferred device type. But you could spend a lifetime chasing down machine-specific stuff, right?

Thanks for the help.

Marc

raistlin2k · « **Reply #16 on:** April 19, 2005, 02:13:55 am »

@Marc

Simply assign ýour server a static IP.
Normally the DHCP in a router uses IP range from 1-128 for dynamic assignment, so just use an IP above for the server.

For example:
I assigned my server 192.168.2.200 (easy to remember), now it's working without any problems.

Hope this helps you without having to disable the other network device...

Raist

edb · « **Reply #17 on:** April 23, 2005, 08:58:35 am »

Have just tried MC11 with upnp plug in for the first time with my Go Video D2730. Music works a treat.... now all I need is pictures and video and this setup would be beautiful! I have been looking for a media center that supports a large library of music, pictures and video for... well too long. And MC is close... v close. As well as a D2730 we have iPods. So you can see getting it all together is a headache.

The D5 (and its many variants) stream video and pictures well but do an awful job of the indexing. One flat level for all folders makes seaching a nightmare, and unless you want to get into hacking its code and the access db thats out. Nero Mediahome is buggy, slow, crashes, and seems a mish mash of third party pieces, so thats out. On2Share - oh dear. Allegro - its OK, but thats all I can say - not really a media center at all. Windows Media connect and iPod, dont think that marriage is ever going to work. TwonkyVision - also close. Does a great job of reading the iTunes XML library, but support for pictures and video is still not there, at least for the D2730., and of course there is no UI piece...

Which leaves you guys.... Nice product. Very nice. Any chance of getting the picture and video serving going? I can browse the directories, genre etc to get to the files, but they wont play no matter what options I select on the server side. ...

04/23/05 09:56:10 - JRiver UPnP Server Version 1.0.20 starting...
04/23/05 09:56:11 - Server running on address 192.168.1.102, port 3544
04/23/05 09:56:11 - Running
04/23/05 09:56:16 - Received request for device description
04/23/05 09:56:16 - Browse BrowseDirectChildren 0
04/23/05 09:56:18 - Browse BrowseDirectChildren 3
04/23/05 09:56:22 - Browse BrowseDirectChildren 196
04/23/05 09:56:22 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777, USN: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777
04/23/05 09:56:22 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1, USN: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777::urn:schemas-upnp-org:device:InternetGatewayDevice:1
04/23/05 09:56:22 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777::upnp:rootdevice
04/23/05 09:56:22 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANDevice-1_0-0090a2777777, USN: uuid:upnp-WANDevice-1_0-0090a2777777
04/23/05 09:56:23 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANDevice:1, USN: uuid:upnp-WANDevice-1_0-0090a2777777::urn:schemas-upnp-org:device:WANDevice:1
04/23/05 09:56:23 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANConnectionDevice-1_0-0090a2777777, USN: uuid:upnp-WANConnectionDevice-1_0-0090a2777777
04/23/05 09:56:23 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANConnectionDevice:1, USN: uuid:upnp-WANConnectionDevice-1_0-0090a2777777::urn:schemas-upnp-org:device:WANConnectionDevice:1
04/23/05 09:56:23 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:Layer3Forwarding:1, USN: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777::urn:schemas-upnp-org:service:Layer3Forwarding:1
04/23/05 09:56:23 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1, USN: uuid:upnp-WANDevice-1_0-0090a2777777::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
04/23/05 09:56:23 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANIPConnection:1, USN: uuid:upnp-WANConnectionDevice-1_0-0090a2777777::urn:schemas-upnp-org:service:WANIPConnection:1
04/23/05 09:56:24 - Browse BrowseDirectChildren 217
04/23/05 09:56:25 - Browse BrowseDirectChildren 218
04/23/05 09:56:26 - Browse BrowseDirectChildren 218

Cheers

SimonT · « **Reply #18 on:** April 24, 2005, 04:04:18 pm »

I'm new to Media Centre but very impressed so far. Having read many threads, I understand that the Philips Streamium i250 (audio only) is not standard UPnP, but there seems to be something out there to get things running? Any help would be greatly appreciated - any chance that this will be appearing in a later update?

If you're looking for new ideas, check out the AlienStream plugin for slimserver - something like that for Media Centre would be teriffic...

Thanks for any help,
Simon T.

dun4cheap · « **Reply #19 on:** April 25, 2005, 11:20:30 am »

Just wondering since it appears that MC11 has reached RC stage will the upnp pluigin be updated. It lists support for the SMC ez stream, but I have had no luck in getting mine to work. I have tried just about everything. That latest release shows a different log but in the end it still fails. Has anyone had any luck with this device? Also is the support only audio or video as well?

Any help would be appreciated.

John Gateley · « **Reply #20 on:** April 25, 2005, 01:03:49 pm »

Quote from: edb on April 23, 2005, 08:58:35 am

Have just tried MC11 with upnp plug in for the first time with my Go Video D2730. Music works a treat.... now all I need is pictures and video and this setup would be beautiful!

The log tells me that the Go Video player doesn't like the picture and movie format. It's hard for me to guess why without having one. Do you have a network sniffer available?

j

John Gateley · « **Reply #21 on:** April 25, 2005, 01:06:08 pm »

Quote from: smnthorn on April 24, 2005, 04:04:18 pm

I'm new to Media Centre but very impressed so far. Having read many threads, I understand that the Philips Streamium i250 (audio only) is not standard UPnP, but there seems to be something out there to get things running? Any help would be greatly appreciated - any chance that this will be appearing in a later update?

Hi Simon,

Unless there are other devices using the same protocol, or there's a lot of i250's, unfortunately probably not.

j

John Gateley · « **Reply #22 on:** April 25, 2005, 01:09:07 pm »

Quote from: dun4cheap on April 25, 2005, 11:20:30 am

It lists support for the SMC ez stream, but I have had no luck in getting mine to work. I have tried just about everything.

Unfortunately, it appears the EZ Stream has chosen to revert to a proprietary mode, recognizing only it's own server, and not 3rd party servers. This happened with a recent ROM upgrade. Sorry...

j

helpme · « **Reply #23 on:** April 25, 2005, 09:29:48 pm »

MP101 keeps freezing Up.

I'm having trouble with my MP101's intermittantly locking up. This occurs after they have been running anywhere from 15 minutes onwards.

I can select an album, start playing tracks and then after a few tracks the MP101 locks up, refusing to find and play the next track. Navigation also fails to work and if I get any sort of message it is "lost connection to the server"

The server log only shows serving the last track played and then requests for children.

I realise that the wireless network is a big unknown in this set up but I can run other Upnp media servers all day without this happening. (I would much prefer to run MC for all its other features)

Is there anything you can suggest in terms of network sniffers that could help identify the problem ?

Thanks,
Stephen Brown

raistlin2k · « **Reply #24 on:** April 26, 2005, 01:39:22 am »

Same here,
MP101 still loses connection to MC after a while (wireless and wired), other servers work OK, so the error must be on the side of MC

Hope you can locate and solve the problem, John.
I'm not very experienced in network sniffing, but I really would like to help you on that. Tell me what logs of which program I should create to help you with that...

Thanks
Raist

John Gateley · « **Reply #25 on:** April 26, 2005, 01:00:47 pm »

Hi Y'all,

I haven't seen this with my MP101.

Try ethereal for network sniffing (www.ethereal.com)

When it happens on the wired network, is it a complete hang of the MP101 or can you still control the box with the remote control?

j

SuperRabbit0 · « **Reply #26 on:** April 26, 2005, 02:35:26 pm »

I also use an MP101 and experience the same problem where it loses connection to the server. It doesn't happen in 15 minutes like the other user had said but rather after a couple of hours.

The server log just shows the request for the last song played and then no more activity, as if the MP101 had been turned off or disconnected (it hadn't) or the a playlist had played through (it also hadn't).

When this happens, I do not lose control of my MP101 and it acts as if connected to the server. ie. I do not have to reboot and can immediately browse music.

I would say the longest it has stayed connected is 3 hours.

I also have another, even worse problem on my MP101. When navigating the menus, I have to go very slow. If i move the menus around quickly, the MP101 always freezes with a little hourglass in the top right corner that never goes away. Only way to recover seems to be to power it off by pulling the plug out of the back. I am not sure if it is overloading memory or something but was wondering if (a) anyone else experiences this problem and (b) MC could force the slowdown somehow to prevent this from happening?

John Gateley · « **Reply #27 on:** April 26, 2005, 02:47:51 pm »

Hi SuperRabbit0

I think your problem is a little different. Check the file that it is trying to play when it stops. See if you can play this file by itself.

When the NetGear sees an unplayable file in the middle of a playlist, it stops playing the playlist instead of going on to the next.

j

davisford · « **Reply #28 on:** April 27, 2005, 01:48:02 pm »

Hi John,

Any update on the Roku issues identified in this thread?

http://yabb.jriver.com/interact/index.php?topic=26757.0

Regards,
Davis

Rob L · « **Reply #29 on:** April 27, 2005, 06:05:30 pm »

Or getting radio working on an MP101 for that matter ;-)

John Gateley · « **Reply #30 on:** April 27, 2005, 08:29:11 pm »

You're in for a pleasant surprise tomorrow Rob

It's not perfect, but it's a lot better.

j

Myron · « **Reply #31 on:** April 27, 2005, 09:39:17 pm »

Quote from: John Gateley on April 27, 2005, 08:29:11 pm

You're in for a pleasant surprise tomorrow Rob
It's not perfect, but it's a lot better.

j

OOOOOH.....

Does this apply to internet radio on the Streamiums as well?

SuperRabbit0 · « **Reply #32 on:** April 29, 2005, 04:53:02 pm »

Quote from: John Gateley on April 26, 2005, 02:47:51 pm

Hi SuperRabbit0

I think your problem is a little different. Check the file that it is trying to play when it stops. See if you can play this file by itself.

When the NetGear sees an unplayable file in the middle of a playlist, it stops playing the playlist instead of going on to the next.

j

I really don't think this is the problem. In order to test this, I set the MP101 to keep repeating one track before I went to bed last night.

Here is the resulting log...

04/29/05 00:37:59 - JRiver UPnP Server Version 1.0.22 starting...
04/29/05 00:38:00 - Server running on address 192.168.1.101, port 2004
04/29/05 00:38:00 - Running
04/29/05 00:40:39 - Received request for device description
04/29/05 00:40:39 - Browse BrowseDirectChildren 0
04/29/05 00:41:02 - Browse BrowseDirectChildren 0
04/29/05 00:41:03 - Browse BrowseDirectChildren 1
04/29/05 00:41:39 - Browse BrowseDirectChildren 6
04/29/05 00:41:44 - Browse BrowseDirectChildren 18
04/29/05 00:41:45 - Browse BrowseDirectChildren 23
04/29/05 00:41:51 - Browse BrowseDirectChildren 23
04/29/05 00:41:55 - Browse BrowseDirectChildren 23
04/29/05 00:41:55 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - Volcano.mp3
04/29/05 00:41:55 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - Volcano.mp3
04/29/05 00:46:39 - Browse BrowseDirectChildren 23
04/29/05 00:46:39 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:46:39 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:49:25 - Browse BrowseDirectChildren 23
04/29/05 00:49:25 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:49:25 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:52:11 - Browse BrowseDirectChildren 23
04/29/05 00:52:11 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:52:11 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:54:57 - Browse BrowseDirectChildren 23
04/29/05 00:54:57 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:54:57 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:57:43 - Browse BrowseDirectChildren 23
04/29/05 00:57:43 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 00:57:43 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:00:29 - Browse BrowseDirectChildren 23
04/29/05 01:00:29 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:00:29 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:03:15 - Browse BrowseDirectChildren 23
04/29/05 01:03:15 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:03:15 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:06:01 - Browse BrowseDirectChildren 23
04/29/05 01:06:01 - Sharing (without conversion): M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:06:01 - Received request for file: M:\Edie Brickell\Volcano\Edie Brickell - I'd be Surprised.mp3
04/29/05 01:09:53 - Received request for device description
04/29/05 01:09:53 - Browse BrowseDirectChildren 0
04/29/05 01:09:53 - Browse BrowseDirectChildren 23
04/29/05 01:09:53 - Browse BrowseDirectChildren 23

and that's the end of it. It justs stops playing.

Everyone in the house was sound asleep at 1:09 when it stopped working.

In the morning, the MP101 was connected to the server (though at the root menu) and browsing worked fine.

I have a wired connection to my MP101.

helpme · « **Reply #33 on:** April 29, 2005, 09:08:17 pm »

No change for me on the internet radio with build 251.

I can play the radio station from the playlist in MC11

From the MP101 I still get "Item Currently Unavailable"

I've tried turning off norton firewall but no change.

Is there anything else I could try to help identify the problem ?

Rob L · « **Reply #34 on:** April 30, 2005, 10:13:49 am »

Yep, sorry, still not working for me either.

Are we just not doing it right somehow??

eso · « **Reply #35 on:** May 01, 2005, 03:31:56 am »

The latest version 1.0.22 from build 252 doesn't work with my Noxon anymore. It always jumps back to the Noxon's home screen when trying to browse beyond the two top level menu entries "Audio" or "Playlists". MC even crashed once but I couldn't reproduce that.

The log doesn't show anything special, only the "Browse..." messages.

ugilt · « **Reply #36 on:** May 01, 2005, 09:43:51 am »

Which firewall ports needs to be opnened ?

John Gateley · « **Reply #37 on:** May 02, 2005, 01:53:39 pm »

Internet radio doesn't work on the Streamium yet - they have a strange way of getting content that doesn't mix well with the way that we serve.

mms streams don't work, but http streams should be working on the MP101.

j

JimH · « **Reply #38 on:** May 02, 2005, 03:29:51 pm »

Quote from: smnthorn on April 24, 2005, 04:04:18 pm

I'm new to Media Centre but very impressed so far. Having read many threads, I understand that the Philips Streamium i250 (audio only) is not standard UPnP, but there seems to be something out there to get things running? Any help would be greatly appreciated - any chance that this will be appearing in a later update?

User RobL apparently got it to work by writing some code. Take a look at this thread at streamiumcafe.com:
http://www.streamiumcafe.com/ubbthreads/showflat.php?Cat=0&Board=pclink&Number=4363&Main=1180&Post4363

Rob L · « **Reply #39 on:** May 02, 2005, 05:46:37 pm »

Yup, I already mailed him directly :-)

John: Can you try this stream on the MP101:

http://stream5.mystic.be:2730/~~~stream~~~.mp3

It's just an example of the several radio stations I listen to through other systems, but the MP101 just says "Item is currently unavailable" when I try to access any of them - including the one above.

John Gateley · « **Reply #40 on:** May 03, 2005, 01:14:17 pm »

Hi Rob,

That one currently isn't working at all for me, so I can't even try it with the MP101...

j

Rob L · « **Reply #41 on:** May 03, 2005, 01:17:58 pm »

You can't even get that working in MC?

I'll have another look when I get home this evening then...

John Gateley · « **Reply #42 on:** May 03, 2005, 01:32:23 pm »

That's correct. Next time post 3 or 4 that don't work, so I can try different ones.

j

Rob L · « **Reply #43 on:** May 03, 2005, 05:40:13 pm »

Odd, that stream's working fine for me in MC! Just checked again.

Other examples (all of which I've just confirmed as working in MC):

http://s2.soundicradio.com:8100
(which I posted in a previous thread)

http://stream3.mystic.be:2680/~~~stream~~~.mp3

http://stream-hautdebit.frequence3.net:8000/~~~stream~~~.mp3

http://212.73.29.83:8500/~~~stream~~~.mp3

John Gateley · « **Reply #44 on:** May 04, 2005, 10:07:33 am »

Hi Rob, it was the danged firewall guy's fault the station wasn't working for me. Once I got that fixed, the station
worked fine. What does the UPnP Status page show for you? Are you converting or not?

j

dun4cheap · « **Reply #45 on:** May 04, 2005, 11:08:40 am »

John,

I assume the SMC EZ Stream is still not working? Would it be possible to simulate the smc software? Or is this unrealistic.

BTW,

Thanks for getting back to me earlier. I know you have been working hard on MC11 so appreciate your time and efforts.

John Gateley · « **Reply #46 on:** May 04, 2005, 12:22:43 pm »

Hi dun4cheap,

I don't know a lot more about it. You can check twonkyvision's page, they've stopped supporting it as well. Unless SMC changes their mind and opens it back up, there's not a lot I can do.

j

Rob L · « **Reply #47 on:** May 05, 2005, 10:21:40 am »

John,
I had it set to "convert as necessary", but I've just turned that off, as well as turning off the firewall.

Nothing actually appears in the UPnP server log - I turned on "Warn on unrecognised NOTIFY" for completeness, but I don't think that matters.

This is the entire log for the period I was trying to access the streams:

05/05/05 16:17:36 - Browse BrowseDirectChildren 7
05/05/05 16:17:36 - Browse BrowseDirectChildren 7
05/05/05 16:17:36 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::upnp:rootdevice
05/05/05 16:17:36 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0000-0030bdb0cdce, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce
05/05/05 16:17:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-upnp-org:device:InternetGatewayDevice:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-microsoft-com:service:OSInfo:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-microsoft-com:service:OSInfo:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:Layer3Forwarding:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-upnp-org:service:Layer3Forwarding:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0001-0030bdb0cdce, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANDevice:1, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce::urn:schemas-upnp-org:device:WANDevice:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0002-0030bdb0cdce, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANConnectionDevice:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:device:WANConnectionDevice:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANEthernetLinkConfig:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANEthernetLinkConfig:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANPPPConnection:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANPPPConnection:1
05/05/05 16:17:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANIPConnection:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANIPConnection:1
05/05/05 16:18:06 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::upnp:rootdevice
05/05/05 16:18:06 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0000-0030bdb0cdce, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce
05/05/05 16:18:06 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-upnp-org:device:InternetGatewayDevice:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-microsoft-com:service:OSInfo:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-microsoft-com:service:OSInfo:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:Layer3Forwarding:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-upnp-org:service:Layer3Forwarding:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0001-0030bdb0cdce, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANDevice:1, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce::urn:schemas-upnp-org:device:WANDevice:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0002-0030bdb0cdce, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANConnectionDevice:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:device:WANConnectionDevice:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANEthernetLinkConfig:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANEthernetLinkConfig:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANPPPConnection:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANPPPConnection:1
05/05/05 16:18:07 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANIPConnection:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANIPConnection:1
05/05/05 16:18:36 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::upnp:rootdevice
05/05/05 16:18:36 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0000-0030bdb0cdce, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce
05/05/05 16:18:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-upnp-org:device:InternetGatewayDevice:1
05/05/05 16:18:36 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-microsoft-com:service:OSInfo:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-microsoft-com:service:OSInfo:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:Layer3Forwarding:1, USN: uuid:00000000-0000-0001-0000-0030bdb0cdce::urn:schemas-upnp-org:service:Layer3Forwarding:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0001-0030bdb0cdce, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANDevice:1, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce::urn:schemas-upnp-org:device:WANDevice:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1, USN: uuid:00000000-0000-0001-0001-0030bdb0cdce::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:00000000-0000-0001-0002-0030bdb0cdce, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANConnectionDevice:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:device:WANConnectionDevice:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANEthernetLinkConfig:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANEthernetLinkConfig:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANPPPConnection:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANPPPConnection:1
05/05/05 16:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANIPConnection:1, USN: uuid:00000000-0000-0001-0002-0030bdb0cdce::urn:schemas-upnp-org:service:WANIPConnection:1

JimH · « **Reply #48 on:** May 10, 2005, 10:03:43 am »

These changes were introduced in last night's build (MC 11.0.262):

12. Fixed: Additional Roku autodetection.
13. Fixed: UPnP Settings for Allow Visual and Filter International Characters sometimes didn't work.
17. Fixed: WAV files didn't play on Roku because of incorrect MIME type.
18. FIxed: Several dropdown box sizes for encoding.

godavego · « **Reply #49 on:** May 10, 2005, 01:07:23 pm »

I tried MC 11.0.262 with my Roku M500 last night, but I still have the same issues.

1. Downloading large lists fails. It's much better than it was, but I still can't play things. For example, it used to be that if I selected the genre Blues, it would fail right away. Now, I can get the list of Blues artists, but I fail trying to get the list of songs to play.

2. Cause enough failures with 1, and MC will crash. Unfortunately, I wasnt able to get the crash info, but I was able to make it crash twice in about 10 minutes. All I was doing was getting the browse failure message, hitting exit on the remote, and trying to load again.

3. Can't press play until I get to the song, but due to 1, I can't get to the song.

As a result, I still can't replace my WMC server.

INTERACT FORUM

Author Topic: UPnP Server Plug-in for Media Center 11 (Read 32634 times)

helpme

helpme

helpme

helpme

helpme