Emby Theater only black screen

[sualfred 677]

I'm trying to get Emby Theater to work, but as soon as I'll start the playback, I only get a black screen with no sound.

Tried it on two different Xbox One outside of my network and locally on my Windows 10 machine.

 

The playback via the Web GUI, Kodi, Ember for Emby etc. is working great. Any idea?

 

Edit: Also tried the Emby and Emby for Android TV apps. No problem. It only facing the issue with Emby Theater.

 

2016-11-27 13:47:57.5852 Info Trakt: Playback Started2016-11-27 13:47:57.5852 Debug Trakt: a8d44158a0fa4632a2ebfbdd72642171 appears to be monitoring /media/b011e2b2-46f9-42c8-b132-dc7ee8a79ec7/omv4/filme/Saw 3D - Vollendung (2010)/Saw 3D - Vollendung (2010) h264-1080p DTSHD-MA-6ch 3D.mkv
2016-11-27 13:47:57.5852 Debug Trakt: Send movie status update
2016-11-27 13:47:57.6896 Info HttpClient: HttpClientManager POST: https://api-v2launch.trakt.tv/scrobble/start
2016-11-27 13:47:58.5366 Info HttpServer: HTTP GET http://192.168.2.250:8096/emby/Users/a8d44158a0fa4632a2ebfbdd72642171/Items?format=json&Fields=Path,Genres,SortName,Studios,Writer,ProductionYear,Taglines,CommunityRating,OfficialRating,CumulativeRunTimeTicks,Metascore,AirTime,DateCreated,MediaStreams,People,Overview,CriticRating,CriticRatingSummary,Etag,ShortOverview,ProductionLocations,Tags,ProviderIds,ParentId,RemoteTrailers,SpecialEpisodeNumbers,MediaSources,VoteCount&Ids=19229f256cca7b9e944f03bdaa1a8f1b. UserAgent: 
2016-11-27 13:47:58.5739 Info HttpServer: HTTP Response 200 to 192.168.2.44. Time: 38ms. http://192.168.2.250:8096/emby/Users/a8d44158a0fa4632a2ebfbdd72642171/Items?format=json&Fields=Path,Genres,SortName,Studios,Writer,ProductionYear,Taglines,CommunityRating,OfficialRating,CumulativeRunTimeTicks,Metascore,AirTime,DateCreated,MediaStreams,People,Overview,CriticRating,CriticRatingSummary,Etag,ShortOverview,ProductionLocations,Tags,ProviderIds,ParentId,RemoteTrailers,SpecialEpisodeNumbers,MediaSources,VoteCount&Ids=19229f256cca7b9e944f03bdaa1a8f1b
2016-11-27 13:47:58.8345 Error ServiceStackHost: Error occured while Processing Request: Unable to write data to the transport connection: The socket has been shut down.
*** 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 4.7.0.0
Processor count: 4
64-Bit OS: True
64-Bit Process: True
Program data path: /var/lib/emby-server
Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 14 12:30:00 UTC 2016)
Application Path: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe
Unable to write data to the transport connection: The socket has been shut down.
System.IO.IOException
 at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x00107] in <bd46d4d4f7964dfa9beea098499ab597>:0 
 at SocketHttpListener.Net.ResponseStream.InternalWrite (System.Byte[] buffer, System.Int32 offset, System.Int32 count) [0x0001b] in <33c4fa8b218e4df9a8fbe6eca87be836>:0 
 at SocketHttpListener.Net.ResponseStream.Write (System.Byte[] buffer, System.Int32 offset, System.Int32 count) [0x000bc] in <33c4fa8b218e4df9a8fbe6eca87be836>:0 
 at ServiceStack.Formats.HtmlFormat.SerializeToStream (ServiceStack.Web.IRequest req, System.Object response, ServiceStack.Web.IResponse res) [0x002e9] in <d43033603ec44e2fb3eac944675e834e>:0 
 at ServiceStack.HttpResponseExtensionsInternal.WriteErrorToResponse (ServiceStack.Web.IResponse httpRes, ServiceStack.Web.IRequest httpReq, System.String contentType, System.String operationName, System.String errorMessage, System.Exception ex, System.Int32 statusCode) [0x000ba] in <d43033603ec44e2fb3eac944675e834e>:0 
 at ServiceStack.ServiceStackHost.HandleUncaughtException (ServiceStack.Web.IRequest httpReq, ServiceStack.Web.IResponse httpRes, System.String operationName, System.Exception ex) [0x00025] in <d43033603ec44e2fb3eac944675e834e>:0 
 at ServiceStack.HostContext.RaiseAndHandleUncaughtException (ServiceStack.Web.IRequest httpReq, ServiceStack.Web.IResponse httpRes, System.String operationName, System.Exception ex) [0x0001c] in <d43033603ec44e2fb3eac944675e834e>:0 
 at ServiceStack.HttpResponseExtensionsInternal.HandleResponseWriteException (System.Exception originalEx, ServiceStack.Web.IRequest request, ServiceStack.Web.IResponse response, System.String defaultContentType) [0x00008] in <d43033603ec44e2fb3eac944675e834e>:0 
 at ServiceStack.HttpResponseExtensionsInternal+<WriteToResponse>d__6.MoveNext () [0x006ba] in <d43033603ec44e2fb3eac944675e834e>:0 
--- End of stack trace from previous location where exception was thrown ---
 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <8f2c484307284b51944a1a13a14c0266>:0 
 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <8f2c484307284b51944a1a13a14c0266>:0 
 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <8f2c484307284b51944a1a13a14c0266>:0 
 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0 
 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <8f2c484307284b51944a1a13a14c0266>:0 
 at ServiceStack.Host.RestHandler+<ProcessRequestAsync>d__13.MoveNext () [0x0044d] in <d43033603ec44e2fb3eac944675e834e>:0 
InnerException: System.Net.Sockets.SocketException
The socket has been shut down
 at System.Net.Sockets.Socket.Send (System.Byte[] buffer, System.Int32 offset, System.Int32 size, System.Net.Sockets.SocketFlags socketFlags) [0x00030] in <bd46d4d4f7964dfa9beea098499ab597>:0 
 at System.Net.Sockets.NetworkStream.Write (System.Byte[] buffer, System.Int32 offset, System.Int32 size) [0x000b4] in <bd46d4d4f7964dfa9beea098499ab597>:0 


2016-11-27 13:47:58.8345 Info HttpServer: HTTP Response 500 to 192.168.2.1. Time: 1343ms (slow). http://XXXX.XXXXX.XXXX:8096/emby/videos/19229f256cca7b9e944f03bdaa1a8f1b/stream.mkv?DeviceId=470b6c2ad741d0b36c8406957f10e0932939fd73&MediaSourceId=19229f256cca7b9e944f03bdaa1a8f1b&VideoCodec=h264&AudioCodec=ac3,mp3,aac&AudioStreamIndex=1&VideoBitrate=3808000&AudioBitrate=192000&Level=41&Profile=high&PlaySessionId=6089ac70b6084f458961f1aa9e6440dd&CopyTimestamps=false&TranscodingMaxAudioChannels=2&EnableSubtitlesInManifest=false&Tag=53067d9544a80c0324d9e050bc0bcf69&EnableSplittingOnNonKeyFrames=false
2016-11-27 13:47:59.0048 Info HttpServer: HTTP GET http://192.168.2.250:8096/emby/Users/a8d44158a0fa4632a2ebfbdd72642171/Items?format=json&Fields=Path,Genres,SortName,Studios,Writer,ProductionYear,Taglines,CommunityRating,OfficialRating,CumulativeRunTimeTicks,Metascore,AirTime,DateCreated,MediaStreams,People,Overview,CriticRating,CriticRatingSummary,Etag,ShortOverview,ProductionLocations,Tags,ProviderIds,ParentId,RemoteTrailers,SpecialEpisodeNumbers,MediaSources,VoteCount&Ids=19229f256cca7b9e944f03bdaa1a8f1b. UserAgent: 
2016-11-27 13:47:59.0804 Info HttpServer: HTTP Response 200 to 192.168.2.83. Time: 76ms. http://192.168.2.250:8096/emby/Users/a8d44158a0fa4632a2ebfbdd72642171/Items?format=json&Fields=Path,Genres,SortName,Studios,Writer,ProductionYear,Taglines,CommunityRating,OfficialRating,CumulativeRunTimeTicks,Metascore,AirTime,DateCreated,MediaStreams,People,Overview,CriticRating,CriticRatingSummary,Etag,ShortOverview,ProductionLocations,Tags,ProviderIds,ParentId,RemoteTrailers,SpecialEpisodeNumbers,MediaSources,VoteCount&Ids=19229f256cca7b9e944f03bdaa1a8f1b
2016-11-27 13:48:02.7003 Info HttpServer: HTTP GET http://XXXX.XXXXX.XXXX:8096/emby/Users/a8d44158a0fa4632a2ebfbdd72642171. UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
2016-11-27 13:48:02.7123 Info HttpServer: HTTP Response 200 to 192.168.2.1. Time: 12ms. http://XXXX.XXXXX.XXXX:8096/emby/Users/a8d44158a0fa4632a2ebfbdd72642171
2016-11-27 13:48:02.7408 Info HttpServer: HTTP GET http://XXXX.XXXXX.XXXX:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
2016-11-27 13:48:02.7440 Info HttpServer: HTTP GET http://XXXX.XXXXX.XXXX:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
2016-11-27 13:48:02.7507 Info HttpServer: HTTP Response 200 to 192.168.2.1. Time: 7ms. http://XXXX.XXXXX.XXXX:8096/emby/System/Configuration
2016-11-27 13:48:02.7507 Info HttpServer: HTTP Response 200 to 192.168.2.1. Time: 10ms. http://XXXX.XXXXX.XXXX:8096/emby/System/Logs
2016-11-27 13:48:04.3252 Info HttpServer: HTTP GET http://XXXX.XXXXX.XXXX:8096/emby/System/Logs/Log?name=server-63615833701.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Edited November 27, 2016 by sualfred

[Guest asrequested]

Are you trying the desktop app or the UWP app in the Microsoft store? The XBox app is the UWP...

[Luke 42078]

Also, please try it again. Thanks.

[sualfred 677]

Also, please try it again. Thanks.

It's working with tv.ember.media but still not with the latest Emby Theater app from the Windows Store.

[sualfred 677]

Did a clean Emby installation and updated Mono to 4.6.2.7-0xamarin3.

 

Working:

- Default web GUi

- Android app

- Android TV app

- tv.emby.media

- Emby Theater (latest desktop client)

- Emby for Kodi

- Ember for Emby (Windows Store UWP)

 

Not working with the same socket shutdown error:

- Emby Theater (tested on 2 XBox One and 2 Windows 10 devices - local + remote connection)

 

The ffmpeg process is running, the video just doesn't arrive at the client.

Edited December 2, 2016 by sualfred

[Luke 42078]

What socket shutdown error do you mean? If you mean from the first post, can you please attach the complete server log as well as the ffmpeg log (if one was created). thanks.

[sualfred 677]

What socket shutdown error do you mean? If you mean from the first post, can you please attach the complete server log as well as the ffmpeg log (if one was created). thanks.

 

It's always the same as in the first post. Attached are both logs.

 

As I said, ffmpeg and the streaming is running. 

ffmpeglog.txt

serverlog.txt

[Luke 42078]

We'll take a look, thanks.

[sualfred 677]

Thanks, don't hesitate to ping me if you need further information or when you need me for testing.

[sualfred 677]

We'll take a look, thanks.

 

Do you  have any updates?

I've upgraded to Premium to use ET on the other devices and currently I wonder if this will ever work on my side

[swhitmore 781]

Black screen here too. What logs do you need?

[Luke 42078]

Hi @@sualfred, try this version of ffmpeg:

 

https://github.com/MediaBrowser/Emby.Resources/blob/master/ffmpeg/linux/ffmpeg-git-20160215-64bit-static.7z

 

You can set it up under Transcoding in the Emby server dashboard.

[sualfred 677]

Hi @@sualfred, try this version of ffmpeg:

 

https://github.com/MediaBrowser/Emby.Resources/blob/master/ffmpeg/linux/ffmpeg-git-20160215-64bit-static.7z

 

You can set it up under Transcoding in the Emby server dashboard.

 

Strange, this verison is working, but it has no VAAPI configuration included. 

 

I've compiled the latest ffmpeg snapshot of today -> no access

I'll give it a try with the older 3.1.6 and report back as soon as the testbuild is made.

 

 

Edited December 6, 2016 by sualfred

[Luke 42078]

Thanks for confirming. We have not yet tested 3.2 so best to stay on 3.1 for now.

[sualfred 677]

Thanks for confirming. We have not yet tested 3.2 so best to stay on 3.1 for now.

 

Just finished the 3.1.6 build. As you said, it's caused by ffmpeg 3.2. 

 

This 3.1.6 build is working and is VAAPI enabled:

https://1drv.ms/u/s!Aj8g8aA7CEOwgedkk8tXevryHXNWHw

(compiled on Debian Jessie)

 

So... the bottom line of 3.2:

Works everywhere except ET UWP version.

 

Thanks for your time. I'm looking forward to see the 3.2 compatiblity.

Edited December 6, 2016 by sualfred

[sualfred 677]

Args, it's only working if the playback is streamed directly or with software transcoding. VAAPI still leads into black screen. 

[sualfred 677]

Thanks for confirming. We have not yet tested 3.2 so best to stay on 3.1 for now.

 

Just want to report back that it's working with Emby 3.1 and the latest Windows Store version of today.

 

But I've noticed that the custom ffmpeg path setting is gone in 3.1. Is this a wanted behaviour?

[Luke 42078]

On some platforms yes.

[sualfred 677]

On some platforms yes.

 

Bad news. Problem is back with 1.1.47.....

Black screen (but audio) with VAAPI transcoding. All other clients are fine. 

 

Edit:

I manually installed the 1.1.42 from the Testing board section and there it's working fine, even with VAAPI.

Edited December 27, 2016 by sualfred

[Luke 42078]

Hi, we're sorry to hear about this. In order for us to best help you, please provide the information requested in how to report a media playback issue. thanks !

[sualfred 677]

Hi, we're sorry to hear about this. In order for us to best help you, please provide the information requested in how to report a media playback issue. thanks !

 

Attached are the logs again.

It's only affecting VAAPI transcoded playback. Screen is black but sound is playing.

ffmpeg.log.txt

server.log.txt

[Luke 42078]

And it's fine without vaapi?

[sualfred 677]

And it's fine without vaapi?

 

Yep. Software transcoding is fine. 

 

< 1.1.42 = Black screen with vaapi

1.1.42 = works with vaapi

1.1.47 = Black screen with vaapi

 

Only happens in the UWP ET app. Desktop works, web version works, Emby for Fire TV works, etc.

 

[Luke 42078]

Can you provide ffmpeg logs from the two app versions for comparison? thanks.

[sualfred 677]

Can you provide ffmpeg logs from the two app versions for comparison? thanks.

 

Sure. Logs are attached.

1-1-47.txt

1-1-42.txt

Edited December 27, 2016 by sualfred