I checked mine again and about 12 shows have recorded without incident since the move to 1.8.0. However I haven’t had a single storm in that time either which I think may be related. (clear broadcast signal versus corrupt signal)
I’m running Version 1.8.0.4109 since yesterday morning and have 19 shows that started recording and are now hung. Mac OS on server and HD Homerun Extend Version 20161119. Perhaps I need to upgrade my firmware? Not sure if that’s going to help.
@kamererhouse said:
I checked mine again and about 12 shows have recorded without incident since the move to 1.8.0. However I haven’t had a single storm in that time either which I think may be related. (clear broadcast signal versus corrupt signal)
Yeah, that’s about how many good recordings I had before things went south. I’m curious if you tried live TV during that time?
@kamererhouse said:
I checked mine again and about 12 shows have recorded without incident since the move to 1.8.0. However I haven’t had a single storm in that time either which I think may be related. (clear broadcast signal versus corrupt signal)
I think you are on to something here. I’m on 1.8.0.4109 on Windows 10. It was working reliably again until this evenings storms. My transmission sources are 35 and 75 miles away so the channels I receive reliably on a given night can fluctuate. Tonight I checked the server and since the weather blew in this early afternoon I had half a dozen stuck recordings still in the grab folder yet showing 100% complete. I can’t see how this is not still a beta feature. The reliability took a huge step back with the live tv builds past 1.6. With the expense of adding a plex pass for a year and another hdhomerun for more tuners the Tivo Romeo with 4 tuners at $400 with lifetime guide data is looking more and more attractive.
Speaking of alternates to hdhomerun, I’ve been thinking about the Tablo DVR which is supposedly compatible with Roku for live and recorded TV, along with some kind of Plex plugin. Haven’t seen many reviews on it or comments from owners though.
@“Dean Junk” - I did not try the live TV during the recordings.
Version 1.8.0.4109 Windows 10. HDHomeRun Extend Model: HDTC-2US Firmware: 20170612beta1. Rebooted before bed last night and it worked for a little while again but today it’s back to the same thing…
Curious if Plex developers even acknowledge this bug? From looking around these forums it looks pretty widespread since the 1.7 versions.
Can you guys look in your HDHOMERUN logs. I am having similar issues and I noticed some errors like this:
no video data
20170726-09:00:06 Tuner: tuner0 http stream ended (requested time reached)
Open a web browser on you local network where your tuners are and type, http://my.hdhomerun.com. This gets you to the admin interface for your turners.
@arejay73 said:
Can you guys look in your HDHOMERUN logs. I am having similar issues and I noticed some errors like this:no video data
20170726-09:00:06 Tuner: tuner0 http stream ended (requested time reached)Open a web browser on you local network where your tuners are and type, http://my.hdhomerun.com. This gets you to the admin interface for your turners.
Yeah, that is interesting, here are some of mine
@daveleast said:
@arejay73 said:
Can you guys look in your HDHOMERUN logs. I am having similar issues and I noticed some errors like this:no video data
20170726-09:00:06 Tuner: tuner0 http stream ended (requested time reached)Open a web browser on you local network where your tuners are and type, http://my.hdhomerun.com. This gets you to the admin interface for your turners.
Yeah, that is interesting, here are some of mine
Do any of those errors correspond to a recording failure at all in your case?
@arejay73 said:
@daveleast said:
@arejay73 said:
Can you guys look in your HDHOMERUN logs. I am having similar issues and I noticed some errors like this:no video data
20170726-09:00:06 Tuner: tuner0 http stream ended (requested time reached)Open a web browser on you local network where your tuners are and type, http://my.hdhomerun.com. This gets you to the admin interface for your turners.
Yeah, that is interesting, here are some of mine
Do any of those errors correspond to a recording failure at all in your case?
I think it impacted all the recordings since I did the 1.8.x update. Spot checking my drive, it doesn’t appear that any of the recordings finished successfully and it also looks like it has stopped recording completely. Nothing is recording today. Here is my recording schedule as of right now. (And yes, I do watch the Lone Ranger 
)
Can report a failed recording last night on 1.8.0.4109 on an Nvidia Shield TV PMS. I had lucked out with a couple good recordings on 1.7.xxx in the days before joining the beta.
I am seeing the same issues. Plex 1.8.0.4109. Ubuntu 16.04 LTS. HD HomeRun. It will record for about 45 seconds to 3 minutes and then quit. Oddly enough watching Live TV (Android or Apple) works great.
This is what I see in the logs. Something kills the recording.
Aug 05, 2017 08:24:54.292 [0x7faaa7ffe700] DEBUG - Jobs: ‘/usr/lib/plexmediaserver/Plex Transcoder’ exit code for process 5614 is 0
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - Jobs: ‘/usr/lib/plexmediaserver/Plex Transcoder’ exit code for process 5614 is 0
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - DVR:Recorder: Asked to stop recording ‘9News Saturday Morning - Episode 08-05’.
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - DVR:Recorder: Stopping transcode session.
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - Killing job.
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - Signalling job ID 5613 with 9
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - Job was already killed, not killing again.
Aug 05, 2017 08:24:54.293 [0x7faa913fe700] DEBUG - Stopping transcode session 1390da31-cfbb-4d36-930d-279203f3fe5a
Aug 05, 2017 08:24:54.294 [0x7faaa7ffe700] DEBUG - JobManager: child process killed by signal: 9 (Killed)
Aug 05, 2017 08:24:54.294 [0x7faa913fe700] DEBUG - DVR:Grabber: Freed a tuner (now 1 available)
Aug 05, 2017 08:24:54.294 [0x7faa913fe700] DEBUG - DVR:Grabber: Recording for ‘9News Saturday Morning - Episode 08-05’ stopped with status complete.
Aug 05, 2017 08:24:54.295 [0x7faa913fe700] DEBUG - DVR:Grabber: Using recording status.
Well I got my first hung recording last night after dozens of good recordings on the 1.8.0.4109 release. It’s not a failed recording though. It is stuck at 100% for the last 10 hours.
01:01:24.243 [0x7f54e0b35700] DEBUG - completed 96% - Recording
01:02:03.245 [0x7f54ded11700] DEBUG - completed 97% - Recording
01:02:42.247 [0x7f54e0b35700] DEBUG - completed 98% - Recording
01:03:21.249 [0x7f54dfbff700] DEBUG - completed 99% - Recording
01:03:28.863 [0x7f54ded11700] DEBUG - EPG[onconnect]: Purging 8 airings which completed in the past.
01:03:29.006 [0x7f54ded11700] DEBUG - Destroying metadata item 638 (Starved)
01:03:29.079 [0x7f54ded11700] DEBUG - Destroying metadata item 700 (Consenting Adults)
01:03:29.116 [0x7f54ded11700] DEBUG - Destroying metadata item 625 (The Gift)
01:03:29.133 [0x7f54ded11700] DEBUG - Destroying metadata item 715 (Dead Stop)
01:03:29.154 [0x7f54ded11700] DEBUG - Destroying metadata item 725 (Light at the End of the Journey)
01:04:00.061 [0x7f54e0b35700] DEBUG - DVR:Grabber: Cancelling operation for ‘Star Trek: Enterprise - E4 - Dead Stop’ with status complete.
01:04:00.061 [0x7f54e0b35700] DEBUG - DVR:Grabber: Operation was active, stopping recorder.
01:04:00.251 [0x7f54dfbff700] DEBUG - completed 100% - Recording
01:04:29.012 [0x7f54cf3ff700] DEBUG - BPQ: onConsiderProcessing: Idle (true)
01:04:29.012 [0x7f54cf3ff700] DEBUG - BPQ: [Idle] -> [Processing]
01:04:29.016 [0x7f54cf3ff700] DEBUG - BPQ: generating queue items from 0 generator(s)
01:04:29.016 [0x7f54cf3ff700] DEBUG - BPQ: generated 0 item(s) for queue
01:04:29.017 [0x7f54cf3ff700] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
01:04:29.017 [0x7f54cf3ff700] DEBUG - PlayQueue: 0 generated IDs compressed down to a 2 byte blob.
01:04:29.103 [0x7f54cf3ff700] DEBUG - BPQ: [Processing] -> [Idle]
01:04:29.103 [0x7f54cf3ff700] DEBUG - BPQ: garbageCollect - sync - forced - 1
01:04:29.103 [0x7f54cf3ff700] DEBUG - Sync: starting Sync garbage collection: 1, forced
01:04:29.103 [0x7f54cf3ff700] DEBUG - Sync: finished Sync garbage collection: 1
01:04:29.103 [0x7f54cf3ff700] DEBUG - BPQ: garbageCollect - version - forced - -1
01:04:29.104 [0x7f54cf3ff700] DEBUG - Versions: garbage collecting
01:04:29.108 [0x7f54cf3ff700] DEBUG - Versions: garbage collected in 0.0 seconds
01:07:01.354 [0x7f54ded11700] DEBUG - EPG[onconnect]: Next thing to start/end is at 2017-08-05 05:30:00 (in 1380 seconds)
That’s the end of the failed recording. Trying to look back at the last good recording the main difference is that there are transcoder lines each second during the entire recording. Those transcoder lines don’t appear at all during the failed recording. In fact, the good recording doesn’t seem to show the “completed xx% - Recording” lines at all.
Just had two more 1 hour recordings today that appeared to complete, but when I checked them they were only 20-30 minutes in length. In fact looking back through the shows earlier in the week, every show on my weakest channel is missing the ending at various cut off points. Some are 50 minutes long, some under 20 minutes.
Just to be clear, I think this is a problem with Plex, not just a weak channel. This weak channel has glitches some times, but it’s not completely unwatchable and programs like Windows Media Center work fine. For some reason these new releases of Plex don’t seem to be able to handle even the slightest error in the stream now.
EDIT 1: Another interesting bit. The last show to “complete” early was still airing, Plex just thought it was finished. When I deleted the 20 minute file from the library and re-scanned, Plex immediately started recording the remainder of the show again. Weird.
EDIT 2: The resumed recording seemed to complete just fine, even after I started up a live view of the same program and did some live pause/rewind actions to try and break it.
I would like to hear some thoughts from the developers on this. Why would Plex just give up on an episode and not try to resume.
17 shows recording today on my 2 tuner HDHR…
Deleted the tuner again until I see any updates. 
Is anyone from Plex looking at this thread?
What is killing the DVR? Why was it asked to stop recording? I have updated my Silicon Dust Extend today with the newest firmware and the issue got slightly better. I can record a couple minutes.
DVR:Recorder: Asked to stop recording ‘9News at 10pm - Episode 08-09’.
Aug 09, 2017 22:22:45.945 [0x7f6e31bff700] DEBUG - DVR:Recorder: Stopping transcode session.
Aug 09, 2017 22:22:45.945 [0x7f6e31bff700] DEBUG - Killing job.
Aug 09, 2017 22:22:45.945 [0x7f6e31bff700] DEBUG - Signalling job ID 1280 with 9
Aug 09, 2017 22:22:45.945 [0x7f6e31bff700] DEBUG - Job was already killed, not killing again.
Aug 09, 2017 22:22:45.946 [0x7f6e31bff700] DEBUG - Stopping transcode session f37643eb-49c1-4f32-bcf5-4f670f18fd3d
Aug 09, 2017 22:22:45.946 [0x7f6e56fff700] DEBUG - JobManager: child process killed by signal: 9 (Killed)
Aug 09, 2017 22:22:45.947 [0x7f6e31bff700] DEBUG - DVR:Grabber: Freed a tuner (now 2 available)
Aug 09, 2017 22:22:45.947 [0x7f6e31bff700] DEBUG - DVR:Grabber: Recording for ‘9News at 10pm - Episode 08-09’ stopped with status complete.
Aug 09, 2017 22:22:45.947 [0x7f6e31bff700] DEBUG - DVR:Grabber: Using recording status.
Aug 09, 2017 22:22:45.947 [0x7f6e31bff700] DEBUG - Activity: updated activity d1d5ddf2-81fa-4b62-99c6-227f8d626683 - completed 100% - Recording
Aug 09, 2017 22:22:45.947 [0x7f6e31bff700] DEBUG - DVR:Grabber: Scheduling ‘9News at 10pm - Episode 08-09’ for assimilation.
@jreiter1975 There’s a log entry indicating that your server’s internet connection was interrupted, which may indicate that your server dropped off the network for some reason. If the connection between the tuner and server was interrupted, maybe that could have caused your issue? (Bit of a guess there on my part)
Do you happen to allow partial airings for that show?
@DaveBinM I saw that error too. I will have to look into that. To my knowledge there isn’t a problem going between the tuner and server. I can test that pretty easy.
The problem seemed to start after the latest Plex upgrade but that could be coincidental. I do allow partial recording and I had manually recorded that show.
Looks like 1.8.1 has fixed my issues. Been running it since it was released and it’s been just as stable as 1.61.
