mbc0 68 Posted November 9, 2017 Posted November 9, 2017 Hi, I realize this maybe a tvheadend issue but thought I would ask anyway as emby is causing my tvheadend to crash. If I playback a recorded program with plex, Kodi or anything else it plays fine but if I go to recorded tv/recordings on emby and then play I just get the spinning circle and my tvheadend crashes and reboots! here is the log when it crashes (tvheadend log) how do I go about uploading my emby log as it is full of my wan address? I have put the part of my emby log when it causes the crash below and removed personal info ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:12:58.297 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:12:58.297 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:12:58.774 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:12:58.774 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:12:59.994 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:12:59.994 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:00.183 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:00.183 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:02.396 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:02.396 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:02.611 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:02.611 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:06.809 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:06.809 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:06.992 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:06.992 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:15.238 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:15.238 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:15.452 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:15.452 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:16.699 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:16.699 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:16.829 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:16.829 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:18.064 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:18.064 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:18.254 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:18.254 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:20.482 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:20.482 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:20.692 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:20.692 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:24.913 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:24.913 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 4042017-11-09 20:13:25.123 [ INFO]:http: 192.168.0.33: using ticket AD0A2E088CAB3AD5C577508EE57EB29C8C085725 for /dvrfile/19974030522017-11-09 20:13:25.123 [ ERROR]:http: 192.168.0.33: HTTP/1.1 GET /dvrfile/1997403052 -- 404 EMBY LOG ***************************************************************************************************************************************************** EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True2017-11-09 20:12:56.604 Info App: Cannot DirectPlay due to unknown content bitrate2017-11-09 20:12:56.604 Info App: Cannot DirectStream due to unknown content bitrate2017-11-09 20:12:56.604 Info App: Profile: Unknown Profile, Path: http://192.168.0.33:8096, isEligibleForDirectPlay: False, isEligibleForDirectStream: False 2017-11-09 20:12:56.604 Info App: Cannot DirectPlay due to unknown content bitrate2017-11-09 20:12:56.604 Info App: Cannot DirectStream due to unknown content bitrate2017-11-09 20:12:56.604 Info App: Profile: Unknown Profile, Path: http://192.168.0.33:8096, isEligibleForDirectPlay: False, isEligibleForDirectStream: False 2017-11-09 20:12:56.622 Info App: Opening recording stream from TVHclient LiveTvService, external recording Id: 19974030522017-11-09 20:12:56.632 Info MediaEncoder: /config/ffmpeg/20170308/ffprobe -analyzeduration 3000000 -i "http://192.168.0.33:9981/dvrfile/1997403052?ticket=AD0A2E088CAB3AD5C577508EE57EB29C8C085725"-threads 0 -v info -print_format json -show_streams -show_format 2017-11-09 20:12:57.090 Error LiveTvMediaSourceProvider: Error probing live tv stream *** Error Report *** Version: 3.2.36.0 Command line: /usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe -programdata /config -restartpath /usr/lib/emby-server/restart.sh Operating system: Unix 4.9.30.0 64-Bit OS: True 64-Bit Process: True User Interactive: False Mono: 4.8.1 (Stable 4.8.1.0/22a39d7 Sun Oct 1 17:55:43 UTC 2017) Processor count: 8 Program data path: /config Application directory: /usr/lib/emby-server/bin System.Exception: ffprobe failed - streams and format are both null. at Emby.Server.MediaEncoding.Encoder.MediaEncoder+<GetMediaInfoInternal>d__65.MoveNext () [0x00159] in <d4e216c372ba4c8d8adf41d75e895a4e>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at Emby.Server.Implementations.LiveTv.LiveStreamHelper+<AddMediaInfoWithProbe>d__5.MoveNext () [0x000e5] in <0bb88f0681a247a5a2c745f82f71172e>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at Emby.Server.Implementations.LiveTv.LiveTvMediaSourceProvider+<OpenMediaSource>d__11.MoveNext () [0x002a9] in <0bb88f0681a247a5a2c745f82f71172e>:0 System.Exception at Emby.Server.MediaEncoding.Encoder.MediaEncoder+<GetMediaInfoInternal>d__65.MoveNext () [0x00159] in <d4e216c372ba4c8d8adf41d75e895a4e>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at Emby.Server.Implementations.LiveTv.LiveStreamHelper+<AddMediaInfoWithProbe>d__5.MoveNext () [0x000e5] in <0bb88f0681a247a5a2c745f82f71172e>:0 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at System.Runtime.CompilerServices.ConfiguredTaskAwaitable+ConfiguredTaskAwaiter.GetResult () [0x00000] in <dbb16e0bacdc4a0f87478e401bc29b6c>:0 at Emby.Server.Implementations.LiveTv.LiveTvMediaSourceProvider+<OpenMediaSource>d__11.MoveNext () [0x002a9] in <0bb88f0681a247a5a2c745f82f71172e>:0 2017-11-09 20:12:57.090 Info LiveTvMediaSourceProvider: Live stream info: {"Protocol":"Http","Id":"0","Path":"http://192.168.0.33:9981/dvrfile/1997403052?ticket=AD0A2E088CAB3AD5C577508EE57EB29C8C085725","Type":"Default","IsRemote":false,"ReadAtNativeFramerate":false,"IgnoreDts":false,"IgnoreIndex":false,"GenPtsInput":false,"SupportsTranscoding":true,"SupportsDirectStream":false,"SupportsDirectPlay":true,"IsInfiniteStream":false,"RequiresOpening":false,"RequiresClosing":true,"SupportsProbing":true,"LiveStreamId":"41c95b6de5174f82acbc56fe82d0a2f8_0","RequiresLooping":false,"MediaStreams":[{"NalLengthSize":"0","IsInterlaced":true,"IsDefault":false,"IsForced":false,"Type":"Video","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false},{"DisplayTitle":"","IsInterlaced":false,"IsDefault":false,"IsForced":false,"Type":"Audio","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false}],"Formats":[],"RequiredHttpHeaders":{}}
Luke 42078 Posted November 9, 2017 Posted November 9, 2017 Ok, was just curious if I could redirect you towards native support but we don't natively support that. Thanks.
mbc0 68 Posted November 9, 2017 Author Posted November 9, 2017 ok, I have just found that if I go to livetv/recordings it causes the crash, but if I go to library "recordings1" I can see the same video (but with coverart and metadata) and it plays fine! where did this recordings1 folder come from and how come I seem to have 2 locations? is the livetv/recordings just looking at tvheadend and not emby? Cheers
Luke 42078 Posted November 9, 2017 Posted November 9, 2017 well, i would actually suggest that anyway. you must have created a library pointing to your tvheadends recording folder. Truthfully this is now our recommended approach for existing recordings with plugins.
mbc0 68 Posted November 9, 2017 Author Posted November 9, 2017 ah, I think I must have done that a while ago and forgot! :-D yes it seems to work well through the recording library, so that is the way forward, not to use the livetv/recordings method... will that be removed/adjusted at some point?
Luke 42078 Posted November 9, 2017 Posted November 9, 2017 I would like to remove it but but it can be hard to do that because people will feel like something is being taken away when it's not.
mbc0 68 Posted November 9, 2017 Author Posted November 9, 2017 haha I can imagine the forum flood now ;-)
pünktchen 1409 Posted November 9, 2017 Posted November 9, 2017 I would like to remove it but but it can be hard to do that because people will feel like something is being taken away when it's not.This would only work if the media item deletion of the Emby library also triggers the delete function of the live tv api. Otherwise you are you are only deleting the recording file. But when the user is looking at the original software of the external tv backends or Kodi, then the recordings are still listed there because they are still in the backends database.
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