INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: 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
-
Hi Noxon Users - I found the problem, and managed to sneak it in this build.
Thanks for your patience...
j
-
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.
-
Each release looks better and better :)
Any idea on Internet radio ? still getting the item unavailable message.
-
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
-
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?
-
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
-
Hi Y'all,
I'll check on these...
j
-
John can you verify that the DSM-320 on your test bench is running the 1.05 firmware?
-
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?
-
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
-
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.
-
What build of MC are you using?
I was using 240 241 seems to have fixed the problem. Thanks,
-
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,
-
Hi,
Automatic Detection does not work for Terratec Noxon. This is the log:
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
-
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
-
@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
-
8) 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
-
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.
-
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.
-
8) 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
-
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
-
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
-
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
-
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
-
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
-
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?
-
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
-
Hi John,
Any update on the Roku issues identified in this thread?
http://yabb.jriver.com/interact/index.php?topic=26757.0
Regards,
Davis
-
Or getting radio working on an MP101 for that matter ;-)
-
You're in for a pleasant surprise tomorrow Rob :)
It's not perfect, but it's a lot better.
j
-
You're in for a pleasant surprise tomorrow Rob :)
It's not perfect, but it's a lot better.
j
OOOOOH..... 8)
Does this apply to internet radio on the Streamiums as well?
-
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.
-
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 ?
-
Yep, sorry, still not working for me either.
Are we just not doing it right somehow??
-
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.
-
Which firewall ports needs to be opnened ?
-
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
-
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
-
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.
-
Hi Rob,
That one currently isn't working at all for me, so I can't even try it with the MP101...
j
-
You can't even get that working in MC?
I'll have another look when I get home this evening then...
-
That's correct. Next time post 3 or 4 that don't work, so I can try different ones.
j
-
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
-
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
-
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.
-
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
-
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
-
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.
-
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.
-
I just tried the last build with the Noxon but it didn't improve much. At least I managed two times to browse into my audio files and to play a file, but mostly it jumps back to the start screen. Accessing "Playlists" isn't possible at all. And when I tried to stop the UPnP server plugin afterwards MC hang. I had to kill it from the task manager.
I still have the impression that this is a timing problem. It seems that the Noxon is expecting a response from the server but doesn't get it in time and therefore jumps back to it's main menu screen. Wouldn't it be possible to cache the menu levels for the UPnP server so that they could be sent immediately?
-
Great, your're caching it now - and it works! Browsing on the Noxon is possible again, and it is fast too.
There's still a little drawback: it seems that a menu level gets first cached when it is visited for the first time. That means that the Noxon will still timeout (that's obvious now) and jump back to the main menu when a large menu level is accessed for the first time. When navigating there a second time it works.
A solution could be to cache all the child levels of a menu as soon as it is displayed.
-
Update of my testing:
This time I got a crossed network cable and connected the Netgear MP101 directly to my server (which is only suitable for testing, my server is in the garage!!).
Although browsing of files on the MP101 is faster, it's still not the same speed as with TwonkyVision Mediaserver. Moreover I get frequent search failure messages with MC, whereas searching for the same CD in Twonky works with no problems at all.
At the current state,MC cannot be recommended as a reliable UPNP Server, although it has to possibilities to become the best one in the world (I only mention custom view shemes, which is ONLY offered by MC yet). Please look into your UPNP plugin and try to fasten it somehow. I don't know why Twonky is faster, but perhaps you can find out how Twonky transmits the data and why it is so much faster and more reliable this way.
I also wanted to exclude my old P3-500 being the reason for being MC so slow in transmitting upnp browsing data, so I took the serial-ATA raid (with my music) and plugged it into my workstation Athlon64-3500+, but the speed didn't increase anyway, so it's not a problem of hardware limitations, but of MC Upnp Code.
Thanks for the hint about ethereal, I will do some extensive testing to find out why Twonky is so much faster here at my place.
Thanks
Raist
-
Is anyone running stable with a D-Link DSM-320?
I'm seeing many drop-outs and disconnects....
-
Ugilt, more details: what exactly is happening.
Raistlin - the slowdown is probably not in the communication, but in the database back end. I'm looking into this, but you cannot compare MC's UPnP server to Twonkyvision's server - we do very different things.
j
-
Roku Soundbridge is working with build 11.0.266:
http://yabb.jriver.com/interact/index.php?topic=27680.0
-
With 11.0.266, I'm still getting the "Failed to Browse" errors with my Roku. I'm getting a lot further than I used to, but I still can play by genre or pick an album. It only works if I have a short list.
-
Ugilt, more details: what exactly is happening.
Raistlin - the slowdown is probably not in the communication, but in the database back end. I'm looking into this, but you cannot compare MC's UPnP server to Twonkyvision's server - we do very different things.
j
Although I'm not very experienced in network traffic (I already said this before, no? :P ), I believe as well that it is not a problem of communication but of the way how MC offers the data (I think you mean this by database back end). Anyway, I would be very happy with some optimizations of the code towards more browsing speed. (I think I'm not alone with this wish)!!
Thousand Thanks for looking into this!!
Raist
P.S. What's the difference between Twonky and yours, both serve Media Files, no? I know Twonky can only do this, and MC can do much more (like custom viewes), but in the end the Upnp plugin of MC itself is just the same like twonky standalone to me.
-
Here's the details of my DSM-320 experience..
I can browse my media files but from time to time I get an "unable to access folder" and then need to reboot my DSM
While playing music the DSM very often stops playing - allways within the first 3 tunes - very often just a couple of seconds into nr 2 tunes played, sometimes within the first one.... reboot needed
I can not verify this (not much debugging possible on the DSM!) but I do heavily suspect that the DSM looses the connection with the server and then stop responding.
Anyone using this with same symptons or is it just me?
I'm aware this is new stuff so perhaps an option to enable some debugging could be usefull?
-
P.S. What's the difference between Twonky and yours, both serve Media Files, no? I know Twonky can only do this, and MC can do much more (like custom viewes), but in the end the Upnp plugin of MC itself is just the same like twonky standalone to me.
I'd have to agree.
I've been using MC as a jukebox for some time and would love to use it as a server for all its great features.
But I still can't play more than four songs without my MP101 locking up and I still get the internet radio to do any more than display "Item Currently unavailable"
With exactly the same setup I can run the Netgear server and Twonky to serve music all day without failure. (I admit they each have other problems)
I want to use MC and am sure that one day it will be great...but for the moment I can't rely on it as a music server.
I can post details of logs etc. if that will help. I tried using the network capture but ended up with some huge files. Is there anything specific that might help ?
-
Are you using the most recent build? 269 is current.
Is the connection wireless?
-
Are you using the most recent build? 269 is current.
Is the connection wireless?
I will try 269 later today. My last test was after the last time the UPNP server was listed as updated.
The connection to two MP101's is wireless.
-
I can certainly play more than four songs on my MP101, though it's unreliable at the best of times - though this isn't specific to serving off of MC.
However, the radio station support definitely is totally broken in the current incarnation of the server plugin.
And it would be nice if the international character support could work properly too :-)
(It's definitely possible to use International characters - it works with other servers - I guess John just needs to work out how to do it...)
-
I will try 269 later today. My last test was after the last time the UPNP server was listed as updated.
The connection to two MP101's is wireless.
Partial Sucess.
I managed to play a whole album for the first time with MC, so things may be looking up. I'll certainly test some more and post if the problem reoccurs.
Internet radio ... same as before, I just get "Item not currently available"
Plus the international character set issue mentioned by RobL
Other than that if the server is reliable I'm certainly looking forward to learning to use more of the features of MC than the small subset I've played with so far.
-
As I just found out I cannot browse one of my view schemes with the Noxon, even on the second try. It seems as if this view scheme isn't cached by the UPnP server. The scheme contains three view items: the first is of type "Playlist", the second "Album Artist (auto)", and the third "Album".
While browsing with the Noxon I also experienced a crash of MC once again, like with previous versions. I'm not sure if this is related to the above mention view scheme. So far I couldn't reproduce it.
-
The next build has a much faster server. Give it a try with the Rokus and see...
j
-
I just got an I-O-Data Linkplayer.
Their server software works but is limited.
I'm trying to use Media Center as the server even though it not not one of the supported devices. I'm a newbie with the Media center and need help.
The Linkplayer will connect to the MC server by manually putting in the IP address and artist/album/song info/playlist will come up on the screen in lists on a gray screen, but I cannot get any audio. (Audio works fine when using the Linkplayer server software)
The files are WMA files (not lossless).
I'm running both MC server and UPNP plugins (which I assume I need to.)
Below is from UPNP server log. Any suggestions ??
05/17/05 19:17:45 - JRiver UPnP Server Version 1.0.20 starting...
05/17/05 19:17:46 - Server running on address 192.168.1.100, port 1268
05/17/05 19:17:46 - Running
05/17/05 19:17:47 - Received request for device description
05/17/05 19:17:47 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:17:47 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:17:47 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:17:52 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:17:52 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:17:52 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:17:57 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:17:57 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:17:57 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:18:02 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:18:02 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:18:02 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:18:08 - Server Stopped
05/17/05 19:18:18 - JRiver UPnP Server Version 1.0.20 starting...
05/17/05 19:18:19 - Server running on address 192.168.1.100, port 1299
05/17/05 19:18:19 - Running
05/17/05 19:18:21 - Received request for device description
05/17/05 19:18:22 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:18:22 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:18:22 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:18:27 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:18:27 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:18:27 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:18:32 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:18:32 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:18:32 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:18:37 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:myiBoxUPnP::upnp:rootdevice
05/17/05 19:18:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:myiBoxUPnP, USN: uuid:myiBoxUPnP
05/17/05 19:18:37 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:SyabasSTB:1, USN: uuid:myiBoxUPnP::urn:schemas-upnp-org:device:SyabasSTB:1
05/17/05 19:18:37 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777, USN: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777
05/17/05 19:18:38 - 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
05/17/05 19:18:38 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:upnp-InternetGatewayDevice-1_0-0090a2777777::upnp:rootdevice
05/17/05 19:18:38 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANDevice-1_0-0090a2777777, USN: uuid:upnp-WANDevice-1_0-0090a2777777
05/17/05 19:18:38 - 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
05/17/05 19:18:38 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANConnectionDevice-1_0-0090a2777777, USN: uuid:upnp-WANConnectionDevice-1_0-0090a2777777
05/17/05 19:18:38 - 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
05/17/05 19:18:38 - 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
-
Tried build 270 with my Roku this evening -- much better! I got one or two "failed to browse" messages, but I was able to get past it if I tried again. So far, none of the crashes I saw in earlier builds either.
Thank you!
Now, if I could only press play at "Blues" rather than Select Blues, Select All artists, Select All Albums, Select All songs, and finally press Play. Ease of use is one of the main benefits of the Roku and MC, but all these extra clicks (not to mention time) drives my wife and I nuts. I know it sounds nit-picky, but this may make me go back to WMC for UPnP, even though there is a lot I don't like about WMC.
-
I just got an I-O-Data Linkplayer.
Their server software works but is limited.
Please try updating to the latest build of MC11. It's 11.0.270 right now and available in a thread near the top of this board.
-
Jim,
I updated to the newer version and same thing happens. I get the library on a gray screen. I can start songs on the Linkplayer with the Library and it shows they are playing but I get no sound (however, they do start playing on the computer with sound).
I know the Linkplayer is working because I can use their server and get sound. Any settings I'm missing in Media Center?
-
Willieneal - this is a device I haven't tried yet. The best thing to do is to get a network sniff and send it to me (google Ethereal sniffer).
j
-
JOHN GATELEY, YOU ARE A GENIUS!
I bow low in front of you, the new UPNP plugin is super fast for browsing, and till now no music interruption occured (knocking on wood) on my MP101, regardless if connected wired or wireless.
I'm really pleased by the speed-up and the playback stability, what exactly did you change?
Last thing to fix is the support of international characters, then MC can go gold with regard to UPNP support :) (at least for music, don't know for other media)
Thanks a thousand times.
Raist
-
It was an unexpected interaction between the encoder plugin and the UPnP server. Glad it helped,...
j
-
It was an unexpected interaction between the encoder plugin and the UPnP server. Glad it helped,...
j
The encoder plugin? Although I wasn't using transcode at all?
Thanks
Raist
-
Thus the "unexpected" :)
j
-
Is it my imagination or has the WAV option been removed from the list of encoder options for file conversion in 1.0.25? I seem to remember playing WMA files on my Streamium so the WAV option must have been there ot some point...
I think it needs to be an option. For example, if a device does not support WMA but supports WAV and MP3 (like the Streamiums) this forced a double compression when playing WMA files. Having the WAV option would eliminate this problem.
I also noticed that if the conversion selection is set to "Convet if necessary" and I play a WAV file on my Streamium, it gets converted (to MP3 if this encoder is chosen). This isn't right since the Streamium supports WAV. (I'm using the "Advanced" setting for Receiver type to disable international character filtering.)
How does the server decide if it needs to convert ot not? Should there be a way to specify to the server which formats the receiver supports or can the server query the receiver for this list?
-
Great Job on the latest build !
The speed of browsing has improved and I can play whole albums without my MP101 locking up.
Looks like I can now use MC as my media server.
Just waiting for Internet Radio and then MC will blow all the other servers out of the water.
-
I posted this in the release thread, but then I realized that it would be better to post it here.
I installed build 271 this eveneing, but now I notice that the UPnP conversion options are limited to MP3 and Ogg. What happened to the WMA that I had setup in previous versions? Was it intentional to remove that? Unfortunately, I didn't notice what the value was set to in the last build or two, so I can't say when the other options were removed.
I have all my files in WMA Lossless, so I figure it would be better to keep the formats in the same family.
-
Some more info regarding the Roku and the latest version.
1. Build 271 removed WMA from the list of formats available for UPnP conversion. Only MP3 and Ogg is available. I know it was this build because the first time I tried to play a file from the Roku, MC asked to install the LAME encoder. Obviously, given that I had the setting for WMA and Lame wasn't even installed on my box, the change must be recent.
2. Just for grins, I tried changing my Artist/Album view back to normal. In an attempt to get around the timeouts, I grouped my artist view. It turns out that I can now easily get the timeout to occur with my artist list (1100+). Also, if I retry quickly and often, MC hung twice. I had to use the task manager to kill it. Further playing around showed that any list over about 140 items would time-out with the first attempt to load it. Usually, the list would load on the second attempt. However, I was never able to load the full artist list.
Back to WMC I go.
-
I posted this in the release thread, but then I realized that it would be better to post it here.
I installed build 271 this eveneing, but now I notice that the UPnP conversion options are limited to MP3 and Ogg. What happened to the WMA that I had setup in previous versions? Was it intentional to remove that? Unfortunately, I didn't notice what the value was set to in the last build or two, so I can't say when the other options were removed.
I have all my files in WMA Lossless, so I figure it would be better to keep the formats in the same family.
(My answer from the release thread:)
I reported a few times about the WMA VBR and WMA lossless bugs. Library Server was sending them at constant 128 kbps. UPnP server uses the same conversion options. I suppose there was no easy solution and they decided to disable WMA from the conversion options for now.
Keeping the formats in the same "family" does not give any advantage. WMA lossless is lossless and there is no difference between it and APE or uncompressed wave.
If you are using a high quality setting you could as well use MP3. Some listening test results are showing that high bitrate LAME encoded MP3 files can actually be better than WMA. In any case the difference will be marginal if you are using for example CBR 320 kbps.
However, I was hoping to get the WMA lossless conversion working. I would have used it for my APL files. The disc image APE & APL link files format does not work without conversion with Library Server. Now I have to convert them to a lossy format or use a network share without the server's playcount function.
-
Nice answer Alex - I'll get the WMA sorted out eventually, but not in the next few days...
j
-
I can live with MP3 to the Roku. I was only converting WMA Lossless to something smaller so my wireless network would respond a little better. With the Roku, most all of the higher bitrate formats sound alike to me anyway (certainly not the case on my main system!). As I said, I thought keeping things in the same family would be helpful if the WMA tools could do conversions directly. I guess if the conversion process is SrcFormat -> WAV -> DestFormat then it doesn't matter what you convert to.
Regarding the timeouts, I did a little more digging. After reading through several more posts, I uninstalled everything, deleted the registry keys, and re-installed 271. Things got better, but I still got a couple of timeouts. The difference this time is that I could proceed all the way to playback. Before, I could get all the way through at all.
Is there any word on the update from Roku? From what I can tell, there are two forces at work here. First, the MC UPnP server is not as fast as say WMC. Second, the folks from Roku admit that they don't handle slow servers well, and it will be fixed in the next release of their software. Of course, they say nothing about when that will come out.
-
The caching of menu levels has helped browsing on the Noxon, but because it mostly works on the second try (or sometimes only on the third ?) it is not really as good as it could be. Browsing the view scheme that I described in my post earlier in this thread isn't possible at all.
But what is worse: MC (i.e. probably the UPnP server) crashes regularly when I browse it with the Noxon. I cannot reproduce it with a particular sequence but on browsing it will occasionally crash without any message.
And maybe related: when the UPnP server is running and I have browsed it with the Noxon, MC will not terminate sometimes. The UI and task icon have vanished but in the task manager I can see that it's still running and I have to kill it from there.
-
eso,
Make sure you have the latest build. A similar problem was just fixed.
-
Make sure you have the latest build. A similar problem was just fixed.
I have - I encountered this (once again) when I tried to install build 274 today. The installer stopped because the previous version was still in memory. After killing it and then re-running the install I also tried browsing with the Noxon which led to the crash I mentioned.
-
UPNP 1.0.28
Nice to see some more optimizations for speed! Just one hint, you didn't edit the installer script to update build number so its 1.0.28 in the upnp log windows, but 1.0.27 in the plugin-manager. Could be confusing when reporting bugs. (I think there was also an update in the past where the build nr stayed the same, but it should increase everytime you change sometime, for better bug reporting)
Anyway, I'm really impressed by your efforts to boost up the server.
Now I have a question: When searching for "S" with my Netgear MP101, it fails in my soundtrack viewing sheme (sorted by "album" tag) although there are only 185 soundtracks inside. Doing the same in another viewing sheme with more than 1000 children, no problems at all.
The crazy thing is, I never get search failures except this view sheme and only when searching for "S" (what I do frequently these days: Star Wars 8) )
I would be very very happy for any hints with regard to search failures.
Thanks
Raist
-
you didn't edit the installer script to update build number so its 1.0.28 in the upnp log windows, but 1.0.27 in the plugin-manager. Could be confusing when reporting bugs.
Oops ! Thanks.
I don't know about the S search, I'll give it a try, see if I can find anything out...
j
-
1.0.28 (b277): still many browsing timeouts with the Noxon, UPnP-Server/MC still crashing after some browsing.
-
With build 277, I'm still getting timeouts on some lists. With standard Artist/Album (grouped), I get a timeout every time I go to S-T. This group has 209 artists in it. What's new about this build is that I can't try again right away. Once I get the timeout, anything I try will show a "failed to browse data" message. After a few seconds, I am able to try again. With previous builds I could usually get just about anythihg to load if I tried again right away.
I'm using a Roku.
-
Help. I'm using build 278 and when I run the uPnP server my wireless connection time's out every 5 minutes. When I turn off the server, the wireless connection is fine. I'm using a Streamium device.
Here is a sample of the log from the server.
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001::upnp:rootdevice
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-InternetGatewayDevice-1_0-12345678900001, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001::urn:schemas-upnp-org:device:InternetGatewayDevice:1
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:Layer3Forwarding:1, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001::urn:schemas-upnp-org:service:Layer3Forwarding:1
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANDevice-1_0-12345678900001, USN: uuid:upnp-WANDevice-1_0-12345678900001
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANDevice:1, USN: uuid:upnp-WANDevice-1_0-12345678900001::urn:schemas-upnp-org:device:WANDevice:1
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1, USN: uuid:upnp-WANDevice-1_0-12345678900001::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANConnectionDevice-1_0-12345678900001, USN: uuid:upnp-WANConnectionDevice-1_0-12345678900001
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANConnectionDevice:1, USN: uuid:upnp-WANConnectionDevice-1_0-12345678900001::urn:schemas-upnp-org:device:WANConnectionDevice:1
05/26/05 23:26:28 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANIPConnection:1, USN: uuid:upnp-WANConnectionDevice-1_0-12345678900001::urn:schemas-upnp-org:service:WANIPConnection:1
05/26/05 23:26:32 - Received GENA message
05/26/05 23:26:32 - GENA Renew message
05/26/05 23:26:56 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::upnp:rootdevice
05/26/05 23:26:57 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3
05/26/05 23:26:57 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::upnp:rootdevice
05/26/05 23:26:57 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:device:MediaRenderer:1
05/26/05 23:26:57 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:RenderingControl:1
05/26/05 23:26:57 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:ConnectionManager:1
05/26/05 23:26:57 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:AVTransport:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001::upnp:rootdevice
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-InternetGatewayDevice-1_0-12345678900001, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:InternetGatewayDevice:1, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001::urn:schemas-upnp-org:device:InternetGatewayDevice:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:Layer3Forwarding:1, USN: uuid:upnp-InternetGatewayDevice-1_0-12345678900001::urn:schemas-upnp-org:service:Layer3Forwarding:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANDevice-1_0-12345678900001, USN: uuid:upnp-WANDevice-1_0-12345678900001
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANDevice:1, USN: uuid:upnp-WANDevice-1_0-12345678900001::urn:schemas-upnp-org:device:WANDevice:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1, USN: uuid:upnp-WANDevice-1_0-12345678900001::urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: uuid:upnp-WANConnectionDevice-1_0-12345678900001, USN: uuid:upnp-WANConnectionDevice-1_0-12345678900001
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:WANConnectionDevice:1, USN: uuid:upnp-WANConnectionDevice-1_0-12345678900001::urn:schemas-upnp-org:device:WANConnectionDevice:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:WANIPConnection:1, USN: uuid:upnp-WANConnectionDevice-1_0-12345678900001::urn:schemas-upnp-org:service:WANIPConnection:1
05/26/05 23:26:58 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::upnp:rootdevice
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:device:MediaRenderer:1
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:RenderingControl:1
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:ConnectionManager:1
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:AVTransport:1
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::upnp:rootdevice
05/26/05 23:26:59 - Received request for device description
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:device:MediaRenderer:1
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:RenderingControl:1
05/26/05 23:26:59 - Received request for service description
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:ConnectionManager:1
05/26/05 23:26:59 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3::urn:schemas-upnp-org:service:AVTransport:1
05/26/05 23:27:00 - Received request for service description
05/26/05 23:27:00 - Unknown SSDP Server method: NOTIFY, NT: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe009bc3
-
Using 278 build...
Is streaming of Internet radio supose to work to a DSM-320?
- or I'm a simply failing to press the rigth buttons on my remote... :-\
-
John,
Right now, whenever I hit Playlists on the MP101, MC spins it's little heart out evaluating all of my Smartlists which in a library of about ~50,000 takes a while. So long in fact, the MP101 usually gives up. I've had to delete all the auto-smartlists and pare down my own smartlists to the bare minimum to get the MP101 to not time out.
There's no network traffic going on, it's strictly an internal MC thing. Clicking on "Playlists" in the MC tree takes the same amount of time (which is why I never do that) but you can't get around it on the MP101.
Would it be possible to not evaluate the smartlists until they're selected, or maybe give us a filter to select which playlists are available on the device?
Otherwise, the MP101 is running with no problems at all.
-------------------------
Media Center Registered 11.0.279 -- C:\Program Files\J River\Media Center 11\
Server 5.2 Service Pack 1 (Build 3790)
Intel Pentium 4 2387 MHz MMX / Memory: Total - 523 MB, Free - 120 MB
Internet Explorer: 6.0.3790.1830 / ComCtl32.dll: 5.82 (srv03_sp1_rtm.050324-1447) / Shlwapi.dll: 6.00.3790.1830 (srv03_sp1_rtm.050324-1447) / Shell32.dll: 6.00.3790.1830 (srv03_sp1_rtm.050324-1447) / wnaspi32.dll: 4.57 (1008) , ASPI for Win32 (95/NT) DLL, Copyright © 1989-1997 Adaptec, Inc. / Aspi32.sys: 4.57 (1008)
Ripping / Drive D: SONY DVD RW DRU-530A Mode:ModeSecure Type:Auto Speed:Max
Digital playback: Yes / Use YADB: Yes / Get cover art: Yes / Calc replay gain: Yes / Copy volume: 32767
Eject after ripping: Yes / Play sound after ripping: No
Burning / Drive D: SONY DVD RW DRU-530A Addr: 1:0:0 Speed:40 MaxSpeed:40 BurnProof:Yes
Test mode: No / Eject after writing: Yes / Direct decoding: Yes / Write CD-Text: Yes
Use playback settings: No / Normalization: None
-
Just an update. I am running version 276. With that release, the Roku M1000 still had a problem with UPnP support. However, I am now running another device HomePod (http://shop.store.yahoo.com/gloolabs/homepod1.html), that so far is running reliably. It's the same database of over 14,000 tracks. I no longer have the Roku M1000 to play with, but I am happy this works with my HomePod. Needless to say, I believe the problems are not with MC11, but on the client-side.
Chris
-
Hi John, I upgraded to MC11 .279 from .269 and now Roku is broken again. What I mean by broken is the Roku cannot browse any of the nodes anymore, and MC11 crashes on the server side.
I tried to delete the reg key again, and re-import part of my library, reboot Roku, but it did not fix the problem.
-
John,
Right now, whenever I hit Playlists on the MP101, MC spins it's little heart out evaluating all of my Smartlists which in a library of about ~50,000 takes a while. So long in fact, the MP101 usually gives up. I've had to delete all the auto-smartlists and pare down my own smartlists to the bare minimum to get the MP101 to not time out.
I cannot do much - the MP101 is asking for the details, and I have to give it to them.
But there is a fix - create playlist groups and move your smartlists to the playlist groups. Then they will not be immediately under the playlists node in the tree, and you won't evaluate all of them when you click on it.
j
-
Hi John !
Thanks to you for improvements on UPnP plug-in (specially on video format recognition MPEG, DiVx ... ) :D
But I have a problem with Philips Streamium SL300i :
This device have a alphanumerical search function with numeric pad used like for SMS.
I.e. in any list, you can hit 3 times in a row the digit 3 (first hit D, second E, third F...) to search items beginning with letter F ... The search begins only with OK
This behaviour works with PMM (Philips Media Manager) and TwonkyVision but not with MediaCenter. In MediaCenter, hitting 3 times digit 3 gives 333 ... then OK starts the search.
And the search gives the 333th item on the list (in my case the 58th Yougoslavie is the last)
The log is :
06/01/05 17:58:56 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe007dc8::upnp:rootdevice
06/01/05 17:58:56 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe007dc8::urn:schemas-upnp-org:device:MediaRenderer:1
06/01/05 17:58:56 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe007dc8::urn:schemas-upnp-org:service:RenderingControl:1
06/01/05 17:58:56 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe007dc8::urn:schemas-upnp-org:service:ConnectionManager:1
06/01/05 17:58:56 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:FEEDBABE-5AFE-F00D-0090-3efffe007dc8::urn:schemas-upnp-org:service:AVTransport:1
06/01/05 17:58:58 - Browse BrowseDirectChildren 3(Video)
06/01/05 17:58:59 - Browse BrowseDirectChildren 173(Video\Genre)
06/01/05 17:59:00 - Browse BrowseDirectChildren 3(Video)
06/01/05 17:59:01 - Browse BrowseDirectChildren 174(Video\All (4))
06/01/05 17:59:04 - Browse BrowseDirectChildren 178(Video\Unassigned)
06/01/05 17:59:18 - Browse BrowseDirectChildren 177(Video\Voyage)
06/01/05 17:59:18 - Browse BrowseDirectChildren 176(Video\Video)
06/01/05 17:59:19 - Browse BrowseDirectChildren 175(Video\Famille)
06/01/05 17:59:20 - Browse BrowseDirectChildren 0()
06/01/05 17:59:21 - Browse BrowseDirectChildren 3(Video)
06/01/05 17:59:23 - Browse BrowseDirectChildren 1(Audio)
06/01/05 17:59:27 - Browse BrowseDirectChildren 5(Audio\Artist/Album)
06/01/05 17:59:27 - Browse BrowseDirectChildren 1(Audio)
06/01/05 17:59:35 - Browse BrowseDirectChildren 1(Audio)
06/01/05 17:59:35 - Browse BrowseDirectChildren 1(Audio)
06/01/05 17:59:36 - Browse BrowseDirectChildren 58(Audio\Yougoslavie)
06/01/05 18:00:01 - Browse BrowseDirectChildren 0()
06/01/05 18:00:02 - Browse BrowseDirectChildren 0()
06/01/05 18:00:07 - Browse BrowseDirectChildren 1(Audio)
06/01/05 18:00:07 - Browse BrowseDirectChildren 0()
06/01/05 18:00:09 - Browse BrowseDirectChildren 1(Audio)
06/01/05 18:00:10 - Browse BrowseDirectChildren 5(Audio\Artist/Album)
06/01/05 18:00:10 - Browse BrowseDirectChildren 1(Audio)
06/01/05 18:00:14 - Browse BrowseDirectChildren 1(Audio)
06/01/05 18:00:14 - Browse BrowseDirectChildren 1(Audio)
06/01/05 18:00:14 - Browse BrowseDirectChildren 58(Audio\Yougoslavie)
06/01/05 18:02:10 - Received GENA message
06/01/05 18:02:10 - GENA Renew message
Any idea about it ?
Friendly
-
It's an undocumented extension to the UPnP protocol. Now that I know it exists, I'll add it, but it won't be in 11.0
j
-
It's an undocumented extension to the UPnP protocol. Now that I know it exists, I'll add it, but it won't be in 11.0
j
I'm really sorry to give you an extra load of work ;)
Thanks
Friendly
-
So, I was using the server PC today and had the Task Manager open while playing music from a Roku. It seems that the CPU usage goes up to 100% when a file is requested and transcoded (it's using the default MP3 VBR setting and converting from WMA lossless). Is it supposed to take so much CPU power? The PC has an Athlon XP 2800+ with 512 MB RAM.
-
I cannot do much - the MP101 is asking for the details, and I have to give it to them.
But there is a fix - create playlist groups and move your smartlists to the playlist groups. Then they will not be immediately under the playlists node in the tree, and you won't evaluate all of them when you click on it.
j
Hmmm. They weren't directly under Playlsits to begin with but moving them 2 levels down does the trick. Thanks.
-
Hey, any plans to support the Play@TV device? Intel was really pushing them as UPnP gods when they first launched, but the product hasn't evolved at all. When I try to connect to the MC Plug-in, the Play@TV device doesn't see it at all.
Any thoughts?
Thanks!
-
UPnP bump
-
What does the UPnP status screen show? If you can get a sniff of the network traffic, I'll take a look to see what's going on.
j
-
John, I have an opportunity to purchase an HP EW5000. Do you anticipate there will ever be support for this product in MC?
Thanks,
Jeff
-
Unable to stream radiostation to DSM320 - works in MC11
This is my log:
06/06/05 21:15:28 - JRiver UPnP Server Version 1.0.28 starting...
06/06/05 21:15:29 - Server running on address 192.168.0.95, port 3108
06/06/05 21:15:29 - Running
06/06/05 21:32:55 - Received request for device description
06/06/05 21:32:56 - Received request for service description
06/06/05 21:32:56 - Received request for service description
06/06/05 21:34:01 - Received request for device description
06/06/05 21:34:01 - Received request for service description
06/06/05 21:34:01 - Received request for service description
06/06/05 21:34:05 - Browse BrowseDirectChildren 0()
06/06/05 21:34:09 - Browse BrowseDirectChildren 4(Playlists)
06/06/05 21:34:13 - Browse BrowseDirectChildren 6(Playlists\NetRadio favoritter)
06/06/05 21:34:15 - Sharing (without conversion): http://80.160.69.50/100fm
06/06/05 21:34:15 - Received request for file: http://80.160.69.50/100fm
06/06/05 21:34:15 - Sharing (without conversion): http://80.160.69.50/100fm
06/06/05 21:34:15 - Received request for file: http://80.160.69.50/100fm
06/06/05 21:34:15 - Sharing (without conversion): http://80.160.69.50/100fm
06/06/05 21:34:15 - Received request for file: http://80.160.69.50/100fm
06/06/05 21:34:18 - Sharing (without conversion): http://80.160.69.50/100fm
06/06/05 21:34:18 - Received request for file: http://80.160.69.50/100fm
06/06/05 21:34:18 - Sharing (without conversion): http://80.160.69.50/100fm
06/06/05 21:34:18 - Received request for file: http://80.160.69.50/100fm
And then the last two lines just keep repeating... any clues?
-
John, I have an opportunity to purchase an HP EW5000. Do you anticipate there will ever be support for this product in MC?
Probably not - it's not UPnP based, as far as I can tell.
j
-
Unable to stream radiostation to DSM320 - works in MC11
This is my log:
06/06/05 21:34:15 - Sharing (without conversion): http://80.160.69.50/100fm
It's hard to tell - I cannot get this stream to work for me in MC11.
Some streams cannot play on a device if we don't have a decoder, even though they play in MC11.
j
-
It's hard to tell - I cannot get this stream to work for me in MC11.
Some streams cannot play on a device if we don't have a decoder, even though they play in MC11.
j
I'm confused.
Does this mean that MC can use an external decoder for native playback of the stream but this encoder is not available when serving via UPnP?
-
Hi John,
Thank you for your offer to help. Here is the capture from the boot-up of the Play@TV power up sequence:
06/06/05 19:17:17 - JRiver UPnP Server Version 1.0.20 starting...
06/06/05 19:17:18 - Server running on address 192.168.2.254, port 3136
06/06/05 19:17:18 - Running
06/06/05 19:18:02 - Received request for device description
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::upnp:rootdevice
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: uuid:01e35c77-b85b-45ec-80c8-000f6500062e, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:device:MediaRenderer:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:AVTransport:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:ConnectionManager:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:RenderingControl:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::upnp:rootdevice
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: uuid:01e35c77-b85b-45ec-80c8-000f6500062e, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:device:MediaRenderer:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:AVTransport:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:ConnectionManager:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:RenderingControl:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::upnp:rootdevice
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: uuid:01e35c77-b85b-45ec-80c8-000f6500062e, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:device:MediaRenderer:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:AVTransport:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:ConnectionManager:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:RenderingControl:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: upnp:rootdevice, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::upnp:rootdevice
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: uuid:01e35c77-b85b-45ec-80c8-000f6500062e, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:device:MediaRenderer:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:device:MediaRenderer:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:AVTransport:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:AVTransport:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:ConnectionManager:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:ConnectionManager:1
06/06/05 19:21:18 - Unknown SSDP Server method: NOTIFY, NT: urn:schemas-upnp-org:service:RenderingControl:1, USN: uuid:01e35c77-b85b-45ec-80c8-000f6500062e::urn:schemas-upnp-org:service:RenderingControl:1
Any ideas?
Thanks in advance,
--John
-
It asked for the device description, so it saw the server. However, it didn't like our device description for some reason. The device description has been validated by the Intel tools, so this is probably a bug in the device software.
Are these devices easily available? Anyone else have them?
j