@kenbury said:
I just configured my first DVR recording and I have hit the 100% recording bug. Is it being addressed?
A few posts up kinoCharlino indicates that it’s being escalated. Are you using OTA?
Add me here as well. I’m using OTA, but with a strong signal…
I don’t know if my logs will help since they aren’t fresh but I had 4 recordings yesterday that say complete, are in the grab folder but are stuck there.
It was raining last night (10/08/2017) and I had a slightly different problem. I had two recordings scheduled on different channels and both were ended early, apparently within minutes of each other.
One at 8:00 - 9:00p which was cut after 32 minutes and one at 8:30 - 9:00p which was cut after 4 minutes.
In the Recording Schedule they both showed complete with no visible aborted error messages.
I have had something like 12 in a row die yesterday and last night, I dropped the logs, do you guys still want them? Linux Ubuntu 16.04 Server, HDHomerun Tuner.
I’m on the list as well and have had to stay on v1.61 for the past few months. I tried a few updates since but all had the 100% bug and I had to revert. I’m not shifting off it until I see in this thread that it has been resolved.
Windows 10, i7, 4 HDHR tuners.
We’re working on validating a patch for a potential fix. I’ll keep you posted.
Windows 10 running latest PMS 1.9.4 with a HDHomeRun. A recording this night remains stuck… very frustrating since it completely ruins the whole DVR thing. I’ve been told that Emby is fine ; I’m giving it a try.
@kinoCharlino: did the latest update (v1.9.4.4325) include a fix, or can we still expect this to happen?
Here’s my log running v1.9.2.4285. Recording schedule shows five shows from last night (10/10/17) stuck at 100% with nothing appearing in the .grab folder or the respective destination folders after a typical and working recording schedule. There were no error messages. Recordings occur on a 24/7-on home server. I cannot recall which previous version did not have this issue, but recently also noticed that shows were not recorded for the full length of time as set up in the schedule.
@chucksense said:
@kinoCharlino: did the latest update (v1.9.4.4325) include a fix, or can we still expect this to happen?
Tried it, got 2 successful recordings, but now 2 hung this morning. Excellent signal on all channels involved.
My system was working perfect, yesterday I added a recording and changed priority of a show and it stopped recording. I changed modern family to only new.
@kinoCharlino said:
We’re working on validating a patch for a potential fix. I’ll keep you posted.
Hope this is imminent, could save many more windows from having hardware thrown through them 
@chucksense said:
@kinoCharlino: did the latest update (v1.9.4.4325) include a fix, or can we still expect this to happen?
Unfortunately the fix is still being worked on. The challenge with this one is consistently replicating the issue. We’ll get a failed recording followed by a bunch of successful recordings on the same channel. We are working on it and hope to get a fix out asap.
@psykix said:
@kinoCharlino said:
We’re working on validating a patch for a potential fix. I’ll keep you posted.Hope this is imminent, could save many more windows from having hardware thrown through them
You and me both!! 
It’s a high priority issue.
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.
Thank you for your efforts to get this squashed. I’m using Windows so someone else will need to volunteer.
QNAP here.
Just to add a bit. macOS was chosen simply so engineering could focus on a single build for the patch testing. Speeds this process up. Once we nail it with certainty, the fix will get rolled out to all PMS platforms.
Looking forward to it. I was running fine for several days after resolving a tuner available conflict with WMC machine. Then had this happen again. Fortunately I have nothing important recording on Plex just yet as all these kinks get worked out. But looking forward to making the switch permanent soon…especially with the new guide coming! Had 5 recordings at once just now, 2 of them wrapped up just fine while a few others started (1 minute padding on either side so there is some overlap). Wish I was on macOS to help, I am on Freenas 11.
