I was working on integration of some commercial removal tools into the post processing flow for the DVR functionality. I was recording two 1 hour shows via my HDHomeRun (dual tuner), and noticed that, at the conclusion of the one hour, the post-processing started as expected, by running the post-processing script. The part I did not expect was that the status of the tuner still showed that both tuners were “recording”. The post-processing took about 20 minutes total, after which time the media was added to my library, and then the tuner showed that it was no longer recording. In this case, nothing else was scheduled to record immediately after, but had there been, the tuners would have not been available.
Is there any way to, at the conclusion of the actual need of the TV Tuner, that they could be freed up for additional recordings, while still allowing the post-processing to run and complete as needed? During busy prime-time hours, I can anticipate that I may have back-to-back-to-back recordings, and keeping a tuner occupied longer than needed would result in some shows not being recorded.
Try scheduling several recordings now so you can see if it will be an issue. I would schedule 4 shows that are back to back, 2 at 3:00 and 2 at 3:30. This will let you see if the tuners are still tied up during Post Processing. I don’t believe they are actually still being used and other shows can grab one of the tuners. Just think Plex does not update the tuner status until after Post Processing.
Thanks! That clears it up. It’s also supported by seeing that after doing back to back recordings, I have 2 tuners but showing 4 recording now…
@cabersc said:
Thanks! That clears it up. It’s also supported by seeing that after doing back to back recordings, I have 2 tuners but showing 4 recording now…
This is likely related to the issue reported in this thread.
https://forums.plex.tv/discussion/274585/issue-with-tuners-and-recordings/p1
Currently the only “fix” seems to be rolling back to an earlier version of PMS. Several are mentioned as working in the thread. I’m on 1.5.6 which doesn’t have the issue. Some have reported later versions working, but I havn’t tried them. I know the most recent release has the issue still.
One issue I discovered this evening with rolling back is I see some DB error messages in my Plex Media Server log:
Jun 30, 2017 20:01:48.977 [8620] INFO - SQLITE3:B0088E6A, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Everything appears to be working but apparently the database changed between version 1.7.5 and 1.6.1. Uninstalled 1.7.5 and installed 1.6.1 the other night.
