Emby not workin on DLNA device

[tmataraza 0]

• I have a samsung smart tv and a denon avr-e300 home theater receiver that both are DLNA ready. I have emby server installed on a FREENAS server with a static IP. The Server, TV and receiver are all networked and have Static IPs. Emby works beautifully on all my devices using the webserver IP except on the DLNA devices. It says the video files are music files, then error out when I try to play them. I have tried .mkv and .mp4. What other file

•  
  type should I use?

[cyrille_v 0]

I have same problem. Latest version of emby server installed on FreeBSD 10.2, Can browse media folders from iPhone and pc browser. Can switch and play on both, but my

DLNA compatible Pioneer player does not see emby server, Also embry server does not see Pioneer DLNA player. All od devices are with static IPs.

Any suggestion and ideas?  

[Luke 39391]

I have same problem. Latest version of emby server installed on FreeBSD 10.2, Can browse media folders from iPhone and pc browser. Can switch and play on both, but my

DLNA compatible Pioneer player does not see emby server, Also embry server does not see Pioneer DLNA player. All od devices are with static IPs.

Any suggestion and ideas?  

 

For the upcoming server release there is a fix for the Play To feature that will allow Emby to see the device.

[wkl_lau 0]

Same here, I have been looking for a good media server for home. Right now I am using Universal media server because it can stream to all DLNA device but the web interface looks unrefined. I really want switch to Emby and so far it satisify all my requirement, But it cannot stream to my Pioneer XV-BD717W player. I have the same experience with Plex (Emby is developed from plex I think?)

 

I am using EMBY version 3.0.8300.0 (latest as of Oct 22) and due to this limitation I am keeping it in a test machine and won't switch until the DLNA issue is resolved.

[Luke 39391]

Emby is developed from Emby

 

Thanks for the report. We are looking into it.

[wkl_lau 0]

Hello it has been 2 years since my last reply. Emby still not working with my Pioneer XV-BD717W. Right now I am using Emby 3.5.2. When trying to browse Emby's media library from the device, It give me network errors,

 

I attach Emby's Log.

 

if you need anything else please let me know. 

 

Thx

Log 2018-09-11.txt

Edited September 12, 2018 by wkl_lau

[Luke 39391]

Hi, what this means is that we're probably sending back a response that the Pioneer doesn't like. Unfortunately I don't have a Pioneer receiver for testing so it's difficult to say what that might be. Hopefully there is a knowledgeable community member who can help track this down. Thanks !

[wkl_lau 0]

is there anything I can do to help? Any other test or log I can provide? Wireshark?  Emby is close to perfection except DLNA. 

[Luke 39391]

In this situation what i'll generally do is compare the responses we're sending back to that from another application that is working.

[wkl_lau 0]

Hi I plug my server and client (win10 using WMP as DLNA client) in a private VMnet and connection is successful. Here is the log.

 

BTW, do I HAVE TO assign a profile? Will generic profile work?

Emby WMP 13-09-2018.txt

Edited September 14, 2018 by wkl_lau

[Luke 39391]

Unfortunately that's different. That won't tell us what the Pioneer doesn't like about our communications.

[wkl_lau 0]

OK, so what else you need to debug? I mean the pioneer almost accept all DLNA source, Universal media server, native Windows media player DLNA, etc The only 2 server it has problem with is Plex and Emby.

 

Please tell me what else can I do

[Luke 39391]

I will need to try and find a developer with a Pioneer receiver who can help us. Thanks.

[wkl_lau 0]

Thanks, today I notice something else. today I promote my test server to be a domain controller (install Server essential experience - which makes it a DC) and Emby no longer seen by my pioneer. Not sure if this is related.

 

Thx

[Luke 39391]

What are the differences in the network?

[wkl_lau 0]

No change in the network, IP is the same, 

 

I used UPnP tools from http://www.meshcommander.com/upnptools and run device spy. it doesn't see it

however, if I run UpnpScanner (http://alax.info/blog/257) it will see it.

[Luke 39391]

Can you try rebooting the Pioneer with Emby Server running?

[gruni 2]

My problem is similar:

After restarting Emby Server my pioneer N-50a see Emby DLNA. Switching pioneer off for a while, it will not find Emby DLNA again. Server alive every 10 sec. Makes no change, I have to restart Emby. My iPhone-APP 8playerPRO shows the same issue. QNAP DLNA, music station and so on is switched off. Emby Server is 3.6.0.80.

 

A simple option to adjust DLNA folder structure similar to Twonky will be very fine as well. 10 entries in 4 Lines of my network player are not useful, for example I need only songs and playlists after entering Dlna menue.

[Luke 39391]

What version of Emby Server?

[gruni 2]

emby-server-qnap_3.6.0.80_x86_64

[Luke 39391]

Can you please attach the emby server log? thanks.

 

@@softworkz

[gruni 2]

Hi Luke,

I had to restart my QNAP in other reasons, so Emby server restarts as well. Now Emby server alive signal is working. Pioneer takes some seconds until Emby DLNA appears. 

It seems that alive signal needs a server restart and pioneer N-50a needs the DLNA alive signal.

I think you can close my pioneer/DLNA topic.

[Luke 39391]

Thanks for the info.

[JAAlperin 3]

Been running Emby as a Warden plugin in FreeNAS for years.  Version 3.3.1.0 on FN 11.2 runs flawlessly on my OPPO BD-93 at home, but recently I tried to access my server from a remote ROKU.  Sorry, server version is too old.  So, installed 3.6.0.80 in an iocage jail.  Used Backup & Restore Plugin to configure as before.  OPPO no longer sees Emby without Blast Alive of 10 seconds, and then displays "Loading" forever.

 

2018-12-25 15:08:40.770 Info HttpServer: HTTP GET http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/description.xml. UserAgent: OPPO PLAYER

2018-12-25 15:08:40.772 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 2ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/description.xml

2018-12-25 15:08:40.820 Info HttpServer: HTTP SUBSCRIBE http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/events. UserAgent: 

2018-12-25 15:08:40.820 Info HttpServer: HTTP SUBSCRIBE http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/connectionmanager/events. UserAgent: 

2018-12-25 15:08:40.821 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 1ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/events

2018-12-25 15:08:40.821 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 1ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/connectionmanager/events

2018-12-25 15:09:01.724 Info HttpServer: HTTP GET http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/icons/logo240.png. UserAgent: 

2018-12-25 15:09:01.725 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 1ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/icons/logo240.png

2018-12-25 15:09:03.020 Info HttpServer: HTTP POST http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/control. UserAgent: OPPO PLAYER

2018-12-25 15:09:03.076 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 56ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/control

2018-12-25 15:09:03.226 Info HttpServer: HTTP POST http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/control. UserAgent: OPPO PLAYER

2018-12-25 15:09:03.237 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 11ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/control

2018-12-25 15:09:03.357 Info HttpServer: HTTP POST http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/control. UserAgent: OPPO PLAYER

2018-12-25 15:09:03.379 Info HttpServer: HTTP Response 200 to 192.168.0.124. Time: 22ms. http://192.168.0.234:8096/dlna/12420aa7b8d54d0890f8cfc58a79a0d7/contentdirectory/control

 

The Post and response sequence repeats until cancelled.

 

I've checked that the OPPO profile is the same on both systems.

 

Any suggestions would greatly appreciated.

[softworkz 4464]

The problem is most likely due to another DLNA service running on your NAS device.

 

Normally co-existence wouldn't be a problem, a you've seen with Emby 3.3.

 

But there's been a regression in the .net core framework since .net core version 2.1 and it persists in version 2.2. 

Emby 3.3 used .net core 2.0 (or maybe MONO) where this problem didn't exist.

Unfortunately there's nothing we can do about it. MS has already fixed this for .net core 3.0, but it's not yet released.

 

Your only option at this time is to disable the other DLNA service on your device.

Edited December 26, 2018 by softworkz