Jump to content

Xbox One no matching profile


BorgSquared

Recommended Posts

BorgSquared

I have been having problems with DLNA with the Xbox One since the media player app was in preview.

 

It does not set the right device profile for my Xbox One.

 

2014-12-07 17:02:09.3511 Debug - Dlna: NOTIFY message received from 192.168.1.3:59163 on 0.0.0.0:1900. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xml,SERVER=WIN32/6.2 UPnP/1.0 DLNADOC/1.5 MediaBrowser/3.0.5445.6,NTS=ssdp:alive,NT=urn:schemas-upnp-org:service:ContentDirectory:1,USN=uuid:24c02322338687f2b0a7d10f7acd83ab::urn:schemas-upnp-org:service:ContentDirectory:12014-12-07 17:02:09.3511 Debug - CoverArt: CoverArt Registration Status - Registered: True In trial: False Expiration Date: 1/1/0001 12:00:00 AM Is Valid: True2014-12-07 17:02:09.3511 Debug - Genre Cleaner: GenreCleaner Registration Status - Registered: True In trial: False Expiration Date: 1/1/0001 12:00:00 AM Is Valid: True2014-12-07 17:02:09.3511 Debug - HttpServer: HTTP GET http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xml	Ip: 192.168.1.90:55761. Headers: FriendlyName.DLNA.ORG=XBOX-ONE,Cache-Control=no-cache,Connection=Close,Pragma=no-cache,Accept=text/xml, application/xml,Host=192.168.1.3:8096,User-Agent=Microsoft-Windows/6.2 UPnP/1.0 Microsoft-DLNA DLNADOC/1.502014-12-07 17:02:09.3511 Debug - Dlna: NOTIFY Device message received from 192.168.1.3:59163. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xml,SERVER=WIN32/6.2 UPnP/1.0 DLNADOC/1.5 MediaBrowser/3.0.5445.6,NTS=ssdp:alive,NT=urn:schemas-upnp-org:service:ContentDirectory:1,USN=uuid:24c02322338687f2b0a7d10f7acd83ab::urn:schemas-upnp-org:service:ContentDirectory:12014-12-07 17:02:09.3511 Debug - Dlna: NOTIFY * HTTP/1.1HOST: 239.255.255.250:1900CACHE-CONTROL: max-age = 600LOCATION: http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xmlSERVER: WIN32/6.2 UPnP/1.0 DLNADOC/1.5 MediaBrowser/3.0.5445.6NTS: ssdp:aliveNT: uuid:24c02322338687f2b0a7d10f7acd83abUSN: uuid:24c02322338687f2b0a7d10f7acd83ab���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������2014-12-07 17:02:09.3511 Debug - Dlna: NOTIFY message received from 192.168.1.3:59164 on 0.0.0.0:1900. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xml,SERVER=WIN32/6.2 UPnP/1.0 DLNADOC/1.5 MediaBrowser/3.0.5445.6,NTS=ssdp:alive,NT=uuid:24c02322338687f2b0a7d10f7acd83ab,USN=uuid:24c02322338687f2b0a7d10f7acd83ab2014-12-07 17:02:09.3668 Debug - Dlna: NOTIFY Device message received from 192.168.1.3:59164. Headers: HOST=239.255.255.250:1900,CACHE-CONTROL=max-age = 600,LOCATION=http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xml,SERVER=WIN32/6.2 UPnP/1.0 DLNADOC/1.5 MediaBrowser/3.0.5445.6,NTS=ssdp:alive,NT=uuid:24c02322338687f2b0a7d10f7acd83ab,USN=uuid:24c02322338687f2b0a7d10f7acd83ab2014-12-07 17:02:09.4449 Debug - Dlna: No matching device profile found. The default will be used. User-agent: Microsoft-Windows/6.2 UPnP/1.0 Microsoft-DLNA DLNADOC/1.50. 2014-12-07 17:02:09.4605 Debug - HttpServer: HTTP Response 200 to 192.168.1.90. Response time: 109.3788 ms.	Url: http://192.168.1.3:8096/mediabrowser/dlna/24c02322338687f2b0a7d10f7acd83ab/description.xml2014-12-07 17:02:09.4761 Debug - HttpServer: HTTP GET http://192.168.1.3:8096/mediabrowser/dlna/contentdirectory/contentdirectory.xml	Ip: 192.168.1.90:55762. Headers: FriendlyName.DLNA.ORG=XBOX-ONE,Cache-Control=no-cache,Connection=Close,Pragma=no-cache,Accept=text/xml, application/xml,Host=192.168.1.3:8096,User-Agent=Microsoft-Windows/6.2 UPnP/1.0 Microsoft-DLNA DLNADOC/1.50

 

 

It doesn't even use the default Xbox One profile. I would like to create a custom profile but the base profile isn't even being used. I even tried changing the friendly name to match my Xbox's system name ("Xbox-One" not "Xbox-SystemOS"). Nothing works.

Link to comment
Share on other sites

dantheman

Mediabrowser is blind to what the Media Player app is doing.  It's equivalent to browsing the server's directories on a PC and double clicking on a video file.  Mediabrowser won't know it's happening.

 

"DLNA play to" works, and opens the Xbox Video app, which handles incoming DLNA streaming.  In this case, Mediabrowser is aware of the destination device, and selects the proper profile.  Select the Xbox One in the web client inside the Chromecast-looking panel.

 

I made a response here:

http://mediabrowser.tv/community/index.php?/topic/11998-xboxone-playing-the-same-file-even-though-i-try-to-play-a-different-file/?p=156060

 

If my understanding is flawed please correct me!

Edited by dantheman
Link to comment
Share on other sites

  • 3 months later...

I've just made a post over in another thread, but I've worked out how to get the DLNA server detecting the Xbox One correctly.

 

In the Identification section for the Xbox One profile, remove everything (including what's set under Http Headers). Then, add a new Http Headers entry

FriendlyName.DLNA.ORG EQUALS XBOXONE

Does that fix any other issues you're having Borg?

 

Edit: it looks like the Http Headers aren't checked when trying to match profiles, so this isn't quite the workaround I expected. As a short-term, probably, but it may affect other devices being correctly identified.

 

Edit 2: And this time it looks like setting just the Friendly Name identifier to XBOXONE is working (after restarting the server just to be sure) without giving false-positives for other devices. *shrugs*
I believe the Friendly Name that is used by the Xbox is whatever the system is named under the console settings, so this might be why so many people are having DLNA issues with MB and the Media Player app?
 

Edited by Sebbs
Link to comment
Share on other sites

The identification values are used by the Play TO function, whereas the http headers are used when browsing server content from the device.

 

Now that you know that, let me know if you'd like to revise this. If this is an improvement we can include it into the supplied profile. thanks.

Link to comment
Share on other sites

jasonwilliams

server_log.txtI've been using the Play-To function for several months with the name of the console (in System settings on the Xbox) set in the "Friendly Name" of the profile and it has worked perfectly up till recently.  I'm not sure what changed, but now I get an error "Unable to start your item".  I have attached the logs.

 

The media player app does indeed always attempt to play the first item in the folder, but I haven't tried add the http header above.  I will try that as well.

 

Is anybody else receiving errors on Play-To?

 

 

Link to comment
Share on other sites

Thanks for clearing that up Luke.

 

With that information and what I did last night to get it all working correctly...

  • For Play To
    • the Friendly Name in Identification needs to be the name given to the console in it's System settings
      • Media Browser's OTB value for this is the same as the Xbox's OTB name, but a few people will change it when setting up their console
    • I wasn't able to confirm if the Model Name value is correct or not (or should even be used)
  • For Browsing
    • The Http Headers should only contain an equals condition for FriendlyName.DLNA.ORG, with the value set to the console's name (as above)

I suspect the User-Agent string used by the Xbox is the same that Windows 8/8.1 will use when Explorer does network discovery for any DLNA sources, but I've yet to confirm that.

Link to comment
Share on other sites

jasonwilliams

I can confirm that with the http header, media player works fine.

 

Still having trouble with Play-To though.

Link to comment
Share on other sites

jasonwilliams

post-2605-0-30997800-1427840708_thumb.jpgHi Luke,

 

I've attached my working settings for the http header.  This works for media player on Xbox, but not for Play-To.  As mentioned earlier in the post, matching the name of your console (which is user configurable) to the "Friendly Name" on the profile will work.  In my case, the "Play To" functionality broke recently but I think my problem might be system specific (looks like an executable problem).

Link to comment
Share on other sites

  • 2 weeks later...

I am now doing my own Xbox One testing and will personally get DLNA perfected. In my initial testing with the Media Player app, to be honest just about everything is going quite well.

 

I have not tested Play To yet but will soon.

 

A couple notes/assumptions:

 

- Both the xbox and media player app are fully updated

- Media player app is at default settings

- Emby server is at default settings with no modifications to any Dlna profiles

Link to comment
Share on other sites

Please try this out on today's server release. I put in a number of Xbox One fixes and it's working very well for me.

Link to comment
Share on other sites

  • 2 weeks later...
BorgSquared

That fixed it, thanks Luke.

 

Oh, and I had to change the friendly name and it's matching header to my console name.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...