After updating PLEX Media Server to 1.7.3.3937 on Debian 8. My DVR recordings are getting stuck at “Recording – 100% complete”. I am running a HDHomeRun CONNECT, Firmware 20170512beta1.
removed my comment regarding similar behavior, and moved to the Plex DVR (Beta) section.
I intermittently get this on 1.7.3.3937, Windows 10. 7 of the last 10 recordings are stuck at 100% complete and not available in the library.
I’m getting this intermittently as well. Any resolution?
Also having this issue which is making the DVR unusable for me. Any traction from Plex on this issue? Still happening after an upgrade to 1.8.0.4109.
I am experiencing the same exact issue as above. Eventually (a day later) the recordings will pop up as available to watch, but only 6 seconds of a 30 minute show was successfully recorded. I am on server version Version 1.9.2.4285 on Windows 10. HD Homerun. DVR service is the only reason I’m paying for plex. If this cannot be resolved I’ll have to cancel and use HD Homerun’s DVR service.
@adamtaguirre said:
I am experiencing the same exact issue as above. Eventually (a day later) the recordings will pop up as available to watch, but only 6 seconds of a 30 minute show was successfully recorded. I am on server version Version 1.9.2.4285 on Windows 10. HD Homerun. DVR service is the only reason I’m paying for plex. If this cannot be resolved I’ll have to cancel and use HD Homerun’s DVR service.
Try the newest version (1.9.3) it’s been updated to fix a lot of the issues people are having with tuners.
Version 1.9.3.4290 is still not working
Do you have a postprocessing script running on your Plex DVR?
@tech4life said:
Do you have a postprocessing script running on your Plex DVR?
No
Same. No post processing script. Still happening.
Patch Testing & Sample Media
Greetings! We’re knee-deep in our investigation with this issue and would like to make a call out for additional sample media where the issue is successfully reproduced, or “caught in the act.” Additionally, we’d like to put together a small group of users who would be willing to install a patch to test the potential fix. For this testing we’re going to focus only on the Mac platform with HDHomeRun tuners, though we know the issue exists on other others (the final fix will go out to all platforms). If you meet the following requirements, please read on for how to provide us with appropriate sample media and logs.
Requirements
- OS: macOS Sierra or High Sierra
- PMS. v1.9.4 (latest Plex Pass release)
- HDHomeRun Connect, Prime, or Extend
- OTA (over-the-air) transmission only
- If using an Extend, disable on-device transcoding
- You can consistently reproduce the issue
- Basic knowledge of the command-line interface
- All regions welcome
Steps for providing sample media
Please follow these steps in the order provided.
- Restart your server, and allow the EPG to load (if it’s been ~18 hours since a server restart)
- If you had the EPG reload, then restart your server again (this keeps the logs clean, as there won’t be the EPG refresh this time) - otherwise you can skip this step
- While the show you want to use for testing is airing, launch Terminal and run the following command. This will begin recording a raw feed from your tuner. If you are not sure what the URL is, generate PMS logs, open
Plex Media Server.log, and search forfinal URL is.
curl http://tunerip:port/auto/channel > /users/outputpath/plexSamples/samplefile.ts- e.g.:
curl http://10.0.1.20:5004/auto/v40.1 > /users/kinoCharlino/desktop/samplefile.ts
- Record the same show in Plex Web by going to Program Guide -> Watch Now (filter the “Discover” dropdown), then find the show and click the small record button at the bottom of the poster art
- With the same show on the same channel being recording using 2 tuners (raw feed + Plex), wait for the recording to fail
- Once the recording has failed, stop the recording in Plex Web
- Stop the raw feed recording by pressing Control + C in Terminal. The .ts file will then complete saving to your selected location
- Generate PMS logs in Plex Web by going to Settings -> Server -> Help
- Upload your logs and sample media to your favorite file hosting/sharing service (such as Dropbox or Google Drive) and PM @kinoCharlino with the download links
Testing the patch
Once we have received sample media and logs verifying the same issue from several users, I’ll reach out about installing a special patch to test the potential fix.
Edit
If you’re having difficulty locating locating the tuner URL for the Curl command, try recording a few minutes of the problematic challenge and then create the logs. You can then use the URL from that log to record for creating your test sample.
It just happened to me. I’ve got a 2012 Mac mini running macOS High Sierra. I was at least under the impression I was running Plex Server 1.9.3 (when I killed the process and restarted, Server had reverted to 1.5.4, and required an update.) I have an HD HomeRun PRIME with a CableCARD (so I don’t think I’d be eligible for the test group above).
Last night I recorded four shows, including three simultaneously using the PRIME’s three tuners. All showed up in my library just fine – I’ve been able to watch them without a hitch. But tonight, two shows got stuck on Recording - 100% more than an hour after they should have finished.
The lights on the front of my PRIME showed that as far as it was concerned, those two tuners were still in use. And when I checked the server status up in my Mac’s menu bar, it said that there were five transcoding sessions running – so, maybe the three from last night, plus the two 100% errors from this evening?
I tried to end all the sessions using the option in the Plex menu on the Mac menu bar, but the server hung; I ended up having the kill the process and restart the server.
I am running a post-processing script to edit out commercials – the standard PlexPostProcessing.py you can find online. It’s worked fine on numerous recordings. Also possibly worth noting:
- The server seemed to be endlessly trying to scan the TV Shows library. I cancelled the scan; the shows did not appear, and I was not able to restart the scan until I rebooted the server.
- I had my Transcoding settings set to 2 simultaneous sessions and “Prefer higher quality encoding.” I’ve told Plex to auto-transcode programs while recording in the DVR settings.
Hope this helps somehow!
I canceled my plex pass subscription until this is resolved.
One thing i will say is that I ran into this awhile ago and it ended up being low reception at the TV antenna. All I had to do is re-position the Antenna and add a RG6 amplifier and that resolved the issue for me.
@tech4life said:
One thing i will say is that I ran into this awhile ago and it ended up being low reception at the TV antenna. All I had to do is re-position the Antenna and add a RG6 amplifier and that resolved the issue for me.
This is true, one of the underlying causes is poorer reception/signal quality. Engineering believes they have the root cause nailed down after a lot of reproducing and testing. It’s been a challenge getting failed results consistently, but they’ve made solid progress. Essentially what’s happening is the recording is not terminating and saving properly due to the session continuing to request segments, because the calls to halt the recording fail, leading the operation to not complete. That’s a huge oversimplification of what’s happening. 
@kinoCharlino said:
@tech4life said:
One thing i will say is that I ran into this awhile ago and it ended up being low reception at the TV antenna. All I had to do is re-position the Antenna and add a RG6 amplifier and that resolved the issue for me.This is true, one of the underlying causes is poorer reception/signal quality. Engineering believes they have the root cause nailed down after a lot of reproducing and testing. It’s been a challenge getting failed results consistently, but they’ve made solid progress. Essentially what’s happening is the recording is not terminating and saving properly due to the session continuing to request segments, because the calls to halt the recording fail, leading the operation to not complete. That’s a huge oversimplification of what’s happening.
Thank you for the update on your progress. I look forward to testing out a potential fix. Any idea on when we might see a patch for this? I understand if you cant tell us right now.
@Swatkats said:
Thank you for the update on your progress. I look forward to testing out a potential fix. Any idea on when we might see a patch for this? I understand if you cant tell us right now.
I’ve been asking the same thing! Engineering generally doesn’t provide hard ETAs on fixing bugs, and in this case hasn’t provided me one either.
So we’ve nailed down the root cause. It’s a bit more involved than the highlights I mentioned earlier (involves PMS receiving corrupted timestamps, which sets off a chain of events). Patch in progress. It’s definitely signal related and definitely fixable 
This problem has been fixed in an update. I am marking this as [SOLVED].
