Jump to content

[BUG] DLNA Play To Broken


SHOCKWAVE

Recommended Posts

SupaMonkey

I can confirm its not working on my LG TV as well since the last update! If I plug in my laptop and use it through kodi its all good, but sometimes just easier to watch straight from the tv!

Link to comment
Share on other sites

eddiepropane

Hi all,

 

I have the issue where emby does not recognise my tv (Panasonic 58DX902B) again.

 

This has been on and off over the last few beta releases, from the last couple of releases 3.1.215 was working fine again and 3.1.218 has re-introduced the error.

 

The TV just does not show in the logs at all.

 

I can see through looking at the last few versions logs that it has changed from originally identifying the TV as it's local IP address which was working then it did not show at all. Then it showed up as it's uuid and not the IP which was working also and then in between the last releases it has changed between showing as uuid and working and not showing at all.

 

I am guessing there are changes being made to the DLNA identifictaion code from Luke's earlier post around the DLNA code being leaner and lighter now which could be impacting us, I know it can work so sure it will get figured out by the awesome team :)

 

Thanks, Bob..

Link to comment
Share on other sites

eddiepropane

Hi,

 

Thanks and no problem.

 

Thought I should give an update as it randomly working now..

 

I was busy for a few hours and did use the TV in between at some points but when I came back to it later the DLNA server was showing on the TV.

 

Server was started at 14:05 and first time the TV shows up is 18:51:

 

2016-11-12 18:51:55.0634 Info HttpServer: HTTP GET http://192.168.0.110:8096/dlna/5f1dea7ea13e4970863c3757f6033d48/description.xml. UserAgent: Panasonic MIL DLNA CP UPnP/1.0 DLNADOC/1.50
2016-11-12 18:51:55.0634 Debug Dlna: Found matching device profile: TX-58DX902B
2016-11-12 18:51:55.0634 Info HttpServer: HTTP Response 200 to 192.168.0.15. Time: 0ms. http://192.168.0.110:8096/dlna/5f1dea7ea13e4970863c3757f6033d48/description.xml

 

Thought I should let you know, as per your above post you are on it anyway so thanks again, Bob.

Link to comment
Share on other sites

Shizuyori

yep 8500 seems to work perfectly with the ps4 now :S

^ initially, it seems to time out dropping playback a lot, i've reverted back to 7300 again, good luck finding the problem.

Link to comment
Share on other sites

Bancko007

The next Problem:

2016-11-20 22:50:10.3826 Info HttpServer: HTTP Response 200 to 192.168.23.92. Time: 13ms. http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control2016-11-20 22:50:10.6655 Info HttpServer: HTTP POST http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control. UserAgent: UPnP/1.0 DLNADOC/1.50 Kodi2016-11-20 22:50:10.7820 Info HttpServer: HTTP Response 200 to 192.168.23.92. Time: 117ms. http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control2016-11-20 22:50:11.3798 Info HttpServer: HTTP POST http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control. UserAgent: UPnP/1.0 DLNADOC/1.50 Kodi2016-11-20 22:50:11.3999 Error UpnpContentDirectory: Error processing control request	*** Error Report ***	Version: 3.0.8500.0	Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby-server -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe -restartpath /usr/lib/emby-server/restart.sh	Operating system: Unix 3.16.0.4	Processor count: 1	64-Bit OS: True	64-Bit Process: True	Program data path: /var/lib/emby-server	Mono: 4.6.1 (Stable 4.6.1.5/ef43c15 Fri Oct 28 20:53:32 UTC 2016)	Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe	One or more errors occurred.	System.AggregateException	  at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at System.Threading.Tasks.Task`1[TResult].GetResultCore (System.Boolean waitCompletionNotification) [0x00034] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at System.Threading.Tasks.Task`1[TResult].get_Result () [0x0000b] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at MediaBrowser.Dlna.ContentDirectory.ControlHandler.GetResult (System.String methodName, MediaBrowser.Dlna.Server.Headers methodParams) [0x00087] in <35101133b7a640dcbd52ab6fffba6952>:0 	  at MediaBrowser.Dlna.Service.BaseControlHandler.ProcessControlRequestInternal (MediaBrowser.Controller.Dlna.ControlRequest request) [0x000cd] in <35101133b7a640dcbd52ab6fffba6952>:0 	  at MediaBrowser.Dlna.Service.BaseControlHandler.ProcessControlRequest (MediaBrowser.Controller.Dlna.ControlRequest request) [0x0001e] in <35101133b7a640dcbd52ab6fffba6952>:0 	InnerException: System.InvalidCastException	Specified cast is not valid.	  at MediaBrowser.Dlna.ContentDirectory.ControlHandler+<GetUserItems>c__async2.MoveNext () [0x0012f] in <35101133b7a640dcbd52ab6fffba6952>:0 	--- End of stack trace from previous location where exception was thrown ---	  at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 	  at MediaBrowser.Dlna.ContentDirectory.ControlHandler+<HandleBrowse>c__async0.MoveNext () [0x00404] in <35101133b7a640dcbd52ab6fffba6952>:0 	2016-11-20 22:50:11.4064 Info HttpServer: HTTP Response 200 to 192.168.23.92. Time: 27ms. http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control2016-11-20 22:50:11.7666 Info HttpServer: HTTP POST http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control. UserAgent: UPnP/1.0 DLNADOC/1.50 Kodi2016-11-20 22:50:11.8781 Info HttpServer: HTTP Response 200 to 192.168.23.92. Time: 112ms. http://192.168.23.5:8096/dlna/13bab4ce8b541afdf6960699924a27bb/contentdirectory/control

This error occurs when I call a genre.

Link to comment
Share on other sites

SupaMonkey

Just an update - 8500 still no good. Latest beta (3.1.229.0 b) still no good - still cant see server from my LG TV that used to see it just fine pre 8400.

Link to comment
Share on other sites

thanks for the report. I have an LG TV for testing and it is working OK with that, but I will continue to test and pursue this. Thanks.

Link to comment
Share on other sites

Bartouille

Well, hello again.

 

I'm still experiencing DNLA issues.

On stable branch, no stable DLNA since 3.08x versions.

I've uninstalled stable and switched to beta branch wich was working great til 3.1.225 update (if I'm well remembering). No chance with beta by now.

 

The weird thing is that this DLNA behaviour is not easily reproductible. For instance, I got the DLNA stuff working on a fresh 3.0.84 install and lost it when updating to 3.0.85 (I'm always waiting a few hours for DLNA to be sure). When downgrading to 3.0.84, no DLNA. When reinstalling from scratch on 3.0.84, no DLNA either !

 

It sounds like sometimes the server is sometimes well firing DLNA and sometines not (no DLNA in logs). Each time I'm losing upnp cast to, I'm also losing emby server in DNLA servers list on devices. It's also all or no DLAN.

 

Anyway, nearly each time I want to move from version to version for testing and reverse, I have to install from fresh the whole server (usually, the library is broken) and I'm getting a bit tired of this :(

 

I'm not very happy with that but I've decided to disable updates and stick to 3.0.73 wich is working flawlessly (hoping i'll manage to get my library scans reaching the end).

 

Emby's great but these DLNA issues are getting very painful.

Link to comment
Share on other sites

Is everyone here who is still having an issue on Windows?

Client Device- Windows 10 x64

Client Device - latest android Emby app

 

Both Client devices are unable to play to anything on the network. 

 

Server Software is installed on Windows Server 2008 R2 x64 

Link to comment
Share on other sites

Happy2Play

Use "Play To" on old Samsung TV daily from web client on a tablet.  Server 3.0.8500.0 is on WHS 2011 (ie Server 2008 R2)

Link to comment
Share on other sites

Client Device- Windows 10 x64

Client Device - latest android Emby app

 

Both Client devices are unable to play to anything on the network. 

 

Server Software is installed on Windows Server 2008 R2 x64 

 

Hi there @@nope123. In order to best help you with that, please provide the information requested in how to report a media playback issue. Thanks !

Link to comment
Share on other sites

  • 2 weeks later...

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