@ian.spencer said: @kinoCharlino the signal quality in HDHR is just a cheap guide. Has anyone confined this tuner issue with a properly so and tested signal like correct signal level and good MER and BER? I have a very good calibrated setup and you need someone with $2k Meyer to test this properly and I don’t have issue 2 or 3 HDHR connect Australia.
We would be grateful to have you test. I’ll be in touch once a build is ready. As for using the signal quality measurement, I’m pretty confident that engineering is not going solely by that.
@kinoCharlino said:
Thanks guys for your reports and logs. We have been able to reproduce #2 and #3 with single recordings, not back-to-back. The hypothesis engineering is working through right now leads to a different root cause than issue #1 and could have to do with the tuner. We’re digging into it, but know at least issue #1 will be resolved in the next PMS release.
@kinoCharlino just updated today to 1.9.7.4460. The previous version has been working pretty well for the past two days… was hoping this would resolve some of the hickupps.
Then I got a back to back failure again.
about 15 minutes until the end of the second DVR scheduling the PMS refreshed and then stated that both of the shows have been recorded.
While the first recording is only 4minutes long recording is only 15 seconds long.
Any insight here or things you need me to provide to assist in anyway? I have reverted back down to the previous version in hopes of getting back to what I was used to. I do a lot of back to back and would hate to see this be an issue again.
edit
one more again for the next batch.
this one also did not record either of the episodes in full and actually sent some two parts of one of the failed recordings to the finished folder.
Update! This morning’s Beta Channel version of PMS (1.10.0.4516) has several DVR fixes in it. While it doesn’t cover every scenario reported here, it does include the most commonly reported issue, the “100% stuck recording.” There are additional issues covered in this thread and those continue to be actively investigated.
@keytone, update to the Beta Channel version that just got released this morning and try again. Let us know if that happens again.
I installed the update and now any time I try and record the server crashes and has to be restarted. I am running windows 10 and a wintvdualhd tuner. I will try and get the logs and post.
I installed the update and now any time I try and record the server crashes and has to be restarted. I am running windows 10 and a wintvdualhd tuner. I will try and get the logs and post.
I am able to watch live video.
It looks like you’re crashing in the post processor. Can you delete the .grab folder out of your TV library? That should fix your crash. Engineering is investigating further.
I installed the update and now any time I try and record the server crashes and has to be restarted. I am running windows 10 and a wintvdualhd tuner. I will try and get the logs and post.
I am able to watch live video.
It looks like you’re crashing in the post processor. Can you delete the .grab folder out of your TV library? That should fix your crash. Engineering is investigating further.
Thanks! That worked, and so far the commercial deletion is working well.
This new 1.10 version has comskip processing (commercial cutting) built it that can run by default on recordings you already had setup if you didn’t turn it off in the schedule.
I mention this because the recording will stay at 100% while comskip is running. You should be able to bring up a list of tasks/programs running on your computer to see if “Plex Commercial Skipper” is running.
Com skip was disabled. I use a post processing script for that and wanted to leave everything the same. I will collect the logs and send them along. Sorry but what do you mean by PM the logs to you?
I will put a marker in the logs to where the stuck recording failed will that give you the info requested above?
I suggested PM’ing in case the user was worried about posting their logs. I will get the logs directly to the engineers who have been working on this issue, as we’ve been following this together.
