revengineer 128 Posted November 21, 2017 Share Posted November 21, 2017 I regularly have iptv recordings fail on emby. The iptv provider is at time unreliable, so I am not whether this is an emby or a provider issue. The error message is given below. I did not submit the whole log because my iptv user/password is plastered all over the place. An annoying side effect of the failed recordings is that even in case of the error, 0-byte recording files are created and listed in the emby interface. Since recordings are retried multiple times, I end up with many junk file that require cleanup. If the issue at hand leads back to the provider, I suggest to change emby to delete the failed recording or open the record file only after the connection is established. 2017-11-20 05:13:01.000 Info App: Opening recording stream from tuner provider 2017-11-20 05:13:01.000 Info App: Streaming Channel m3u_bd1b850990973c512ce073419fd55fdd83651a695bf6ffd56464631c4b1dcebd 2017-11-20 05:13:01.000 Info App: Live stream opened after 0.0005ms 2017-11-20 05:13:01.001 Info App: Returning mediasource streamId 51877c3595e44f5c8a8c414f22233f326fc0761745ee08d5f7455927e631dd9a, mediaSource.Id 2bfe1850d263439396ea5c9ccb562235_6fc0761745ee08d5f7455927e631dd9a, mediaSource.LiveStreamId null 2017-11-20 05:13:01.001 Info App: Beginning recording. Will record for 48.9833116166667 minutes. 2017-11-20 05:13:01.001 Info App: Writing file to path: M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv 2017-11-20 05:13:01.001 Info App: C:\Users\admin\AppData\Roaming\Emby-Server\system\ffmpeg.exe -async 1 -vsync -1 -fflags +igndts -analyzeduration 5000000 -i "http://watch.necroiptv.com/live/xxx/yyy/2903.ts" -t 00:48:58.998 -codec:v:0 libx264 -force_key_frames "expr:gte(t,n_forced*5)" -vf "yadif=0:-1:0" -pix_fmt yuv420p -preset superfast -crf 23 -b:v 25000000 -maxrate 25000000 -bufsize (25000000*2) -vsync -1 -profile:v high -level 41 -fflags +genpts -map_metadata -1 -threads 0 -codec:a:0 aac -strict experimental -ab 320000 -sn -y "M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv" 2017-11-20 05:13:02.430 Info App: Triggering refresh on M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv 2017-11-20 05:13:02.432 Info App: Refreshing recording parent M:\Recorded TV\Series\SOKO Wismar 2017-11-20 05:13:02.434 Info App: ffmpeg recording process started for M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv 2017-11-20 05:13:02.825 Info HttpClient: HttpClientManager GET: https://www.thetvdb.com/api/B89CE93890E9419B/series/201841/all/en.zip 2017-11-20 05:13:04.352 Info App: FFMpeg recording exited with code 1 for M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv 2017-11-20 05:13:04.589 Error App: Error recording to M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv *** Error Report *** Version: 3.2.36.0 Command line: C:\Users\admin\AppData\Roaming\Emby-Server\system\EmbyServer.dll -service Operating system: Microsoft Windows NT 6.2.9200.0 64-Bit OS: True 64-Bit Process: True User Interactive: True Processor count: 4 Program data path: C:\Users\admin\AppData\Roaming\Emby-Server Application directory: C:\Users\admin\AppData\Roaming\Emby-Server\system System.Exception: Recording for M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv failed. Exit code 1 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__96.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__96.MoveNext() 2017-11-20 05:13:04.589 Info App: Live stream 2bfe1850d263439396ea5c9ccb562235_6fc0761745ee08d5f7455927e631dd9a consumer count is now 0 2017-11-20 05:13:04.589 Info App: Closing live stream 2bfe1850d263439396ea5c9ccb562235_6fc0761745ee08d5f7455927e631dd9a 2017-11-20 05:13:04.589 Info App: Live stream 2bfe1850d263439396ea5c9ccb562235_6fc0761745ee08d5f7455927e631dd9a closed successfully 2017-11-20 05:13:04.589 Info App: Triggering refresh on M:\Recorded TV\Series\SOKO Wismar\SOKO Wismar 2017-11-20.mkv 2017-11-20 05:13:04.590 Info App: Refreshing recording parent M:\Recorded TV\Series\SOKO Wismar 2017-11-20 05:13:04.590 Info App: Retrying recording in 60 seconds. Link to comment Share on other sites More sharing options...
ebr 14960 Posted November 21, 2017 Share Posted November 21, 2017 What does the ffmpeg log look like? Link to comment Share on other sites More sharing options...
revengineer 128 Posted November 21, 2017 Author Share Posted November 21, 2017 ffmpeg log attached. Log (1).txt Link to comment Share on other sites More sharing options...
ebr 14960 Posted November 21, 2017 Share Posted November 21, 2017 Looks like a problem at the source: Error while decoding stream #0:1: Invalid data found when processing input Link to comment Share on other sites More sharing options...
revengineer 128 Posted November 21, 2017 Author Share Posted November 21, 2017 Ok, that is what I thought. Is is possible to prevent emby to create 0-byte mkv files in this case? Link to comment Share on other sites More sharing options...
revengineer 128 Posted November 24, 2017 Author Share Posted November 24, 2017 Any feedback on this request? The problem is unfortunately frequent with my provider and cleaning up the 0-byte files is a lot of work. So, to reiterate not creating an mkv file if the stream does not connect would really help. Link to comment Share on other sites More sharing options...
Luke 37273 Posted November 24, 2017 Share Posted November 24, 2017 It's something we can look at for a future update, thanks. Link to comment Share on other sites More sharing options...
revengineer 128 Posted November 24, 2017 Author Share Posted November 24, 2017 Thanks, the issue is especially bad since the recorded file permissions seem to have changed with v3.2.40. will open separate post on this. 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