Guest asrequested Posted September 11, 2017 Share Posted September 11, 2017 (edited) I've noticed (after the fact) this has happened several times. With the same show, on one occasion. I am recording a show, right now, that I happened to notice that the tuner light was off, when it was on previously and I knew my show being recorded. I looked in the dashboard, it reported that it was still recording, but actually wasn't. Then I saw the tuner light come back on and recording continued. There are now two pieces of the same show. There are two transcode logs, because there are two recordings. It did the same thing, last week, with the same show. There was one other, at that time. Here's the error 2017-09-10 21:42:19.429 Info App: FFMpeg recording exited with code -1073741819 for E:\Recorded Shows\The Last Ship\Season 4\The Last Ship S04E05 Allegiance.mkv 2017-09-10 21:42:19.429 Error App: Error recording to E:\Recorded Shows\The Last Ship\Season 4\The Last Ship S04E05 Allegiance.mkv *** Error Report *** Version: 3.2.30.0 Command line: C:\Users\Peter\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True Processor count: 8 Program data path: C:\Users\Peter\AppData\Roaming\Emby-Server Application directory: C:\Users\Peter\AppData\Roaming\Emby-Server\System System.Exception: Recording for E:\Recorded Shows\The Last Ship\Season 4\The Last Ship S04E05 Allegiance.mkv failed. Exit code -1073741819 at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Emby.Server.Implementations.LiveTv.EmbyTV.EncodedRecorder.<Record>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Emby.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__97.MoveNext() System.Exception at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Emby.Server.Implementations.LiveTv.EmbyTV.EncodedRecorder.<Record>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Emby.Server.Implementations.LiveTv.EmbyTV.EmbyTV.<RecordStream>d__97.MoveNext() 2017-09-10 21:42:19.429 Info App: Live stream 6c35c92a2db1497dbe04c1eedd3d2c79_native_c4ca24fc60a3a4bb95e321700f019f00_2b27a64b0031863a310174592fdbbc42 consumer count is now 0 2017-09-10 21:42:19.429 Info App: Closing live stream 6c35c92a2db1497dbe04c1eedd3d2c79_native_c4ca24fc60a3a4bb95e321700f019f00_2b27a64b0031863a310174592fdbbc42 2017-09-10 21:42:19.429 Info App: Closing HDHR live stream 2017-09-10 21:42:19.429 Error HttpServer: Error in HttpListenerResponseWrapper: An existing connection was forcibly closed by the remote host *** Error Report *** Version: 3.2.30.0 Command line: C:\Users\Peter\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True Processor count: 8 Program data path: C:\Users\Peter\AppData\Roaming\Emby-Server Application directory: C:\Users\Peter\AppData\Roaming\Emby-Server\System System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at Emby.Server.Implementations.Net.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Emby.Server.Implementations.HttpServer.SocketSharp.WebSocketSharpResponse.CloseOutputStream(HttpListenerResponse response) System.Net.Sockets.SocketException at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at Emby.Server.Implementations.Net.SocketStream.Write(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.InternalWrite(Byte[] buffer, Int32 offset, Int32 count) at SocketHttpListener.Net.HttpResponseStream.DisposeCore() at SocketHttpListener.Net.HttpResponseStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at Emby.Server.Implementations.HttpServer.SocketSharp.WebSocketSharpResponse.CloseOutputStream(HttpListenerResponse response) 2017-09-10 21:42:19.429 Info HttpServer: HTTP Response 500 to 127.0.0.1. Time: 2409533ms. http://127.0.0.1:8096/LiveTv/LiveStreamFiles/4d9c8c780303412caa658bcafb82e568/stream.ts 2017-09-10 21:42:19.429 Info App: Live stream 6c35c92a2db1497dbe04c1eedd3d2c79_native_c4ca24fc60a3a4bb95e321700f019f00_2b27a64b0031863a310174592fdbbc42 closed successfully 2017-09-10 21:42:19.445 Info App: Retrying recording in 60 seconds. Edited September 11, 2017 by Doofus Link to comment Share on other sites More sharing options...
Luke 37129 Posted September 11, 2017 Share Posted September 11, 2017 Try turning off quicksync and see if that has an impact. Link to comment Share on other sites More sharing options...
Guest asrequested Posted September 11, 2017 Share Posted September 11, 2017 Try turning off quicksync and see if that has an impact. Ah yes, it may be the decoding, again. The show was h264 and I had h264 decoding, enabled. I've just disabled all HW decoding and left HW encoding, on. I'll recording something, and see what happens. Link to comment Share on other sites More sharing options...
Guest asrequested Posted September 11, 2017 Share Posted September 11, 2017 With the HW decoding turned off, I recorded three different shows. All recorded, correctly. I'll leave it with those settings, still with Quick Sync encoding enabled, and see if the issue repeats in the future. Link to comment Share on other sites More sharing options...
Luke 37129 Posted September 11, 2017 Share Posted September 11, 2017 Thanks for the feedback. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now