@DaveBinM said:
Okay, thanks. I’ll do some digging and see what I can find.
Hey, @DaveBinM, hopefully this observation might help with your digging. Here’s what I’ve been able to figure out so far…
I’ve been going through a number of my “skipping” video files using video editing software and I think I’ve found what might be the issue. It appears that, beginning approx. 30 minutes into the 2nd 1-hour show, a “loop glitch” (for lack of a better term) gets started. What I’ve found is that for every approx. 2.002 seconds of recording, the last .067 is a full “repeat” of the prior 1.935 seconds! It’s like the DVR is taking 1.935 seconds and repeating it all crammed into the last .067 second! Then the loop starts again over each 2.002 seconds of video! (approx., of course).
Reason I believe this is what’s happening is that I was able to “save” five shows that were recorded like this by very painstakingly editing out those .067 second repeats! While not perfect every edit, it at least made my recordings watchable! (and trust me, this is VERY time-consuming for 30-minutes of video! If you don’t have patience, don’t try it !!) lol !!
Hope this helps with your digging!! We’re all hoping you Plex Ninjas can get this glitch fixed asap!! (especially me, because my eyes are bugged out from fixing the five already!! ) B)
PS: to your question, yes, my Plex Server is on NAS … OTA with Hdhomerun Extend…
I need to add to this thread that I’m seeing the same thing. Not on all recordings, but some. I use the HDHR Prime and it doesn’t matter if it’s MPEG2 or H.264 channels. It does it exactly 30 minutes in. It start repeating very short clips of the audio.
Back to back recordings on the same channel seems to be the key, I think. It’s always does it on the second recording half way into it. Plex server version 1.10.1.4561.
@Nonna07 said:
Great work, Joe!! What you found makes sense. My “looped” recordings are over 10g each. (normally 6g)
Thanks, Nonna!! This has been driving me crazy as well so just trying to help to get it resolved!
@DaveBinM … not sure if this helps, but prior to the “loop glitch”, it appears that the DVR is creating the recording with the i-frames at regular intervals of 2.002 seconds. This timing was how I was able to find the “.067 second repeats” and edit them out.
Thanks everyone for reporting and providing details for this issue in this thread. I just wanted to give you an update to let you know that engineering is investigating this issue and “hot on the heels” on the root cause.
Not sure if it matters, but I record using the HDHR Extend with “High Quality” setting so that the Extend is transcoding the video to H.264 (AVC) format. Not sure if that has anything to do with the 2.002 seconds timing or not, just thought I’d mention it.
Not sure if it matters, but I record using the HDHR Extend with “High Quality” setting so that the Extend is transcoding the video to H.264 (AVC) format. Not sure if that has anything to do with the 2.002 seconds timing or not, just thought I’d mention it.
I’m using the HDHR Prime and on cable some channels are MPEG2 and others are H.264. The both do it.
@kinoCharlino said:
Thanks everyone for reporting and providing details for this issue in this thread. I just wanted to give you an update to let you know that engineering is investigating this issue and “hot on the heels” on the root cause.
Hi @KinoCharlino, Has engineering had any luck finding/fixing this issue? I see there are a few other threads running in the forum that appear to be adding the same thing. Just curious if any progress has been made. Thanks!
@JoeKurtz said:
Hi @KinoCharlino, Has engineering had any luck finding/fixing this issue? I see there are a few other threads running in the forum that appear to be adding the same thing. Just curious if any progress has been made. Thanks!
We’ve got a fix for this in testing right now that should take care of this. No ETA when it will get merged with master and get released, though.
@JoeKurtz said:
Hi @KinoCharlino, Has engineering had any luck finding/fixing this issue? I see there are a few other threads running in the forum that appear to be adding the same thing. Just curious if any progress has been made. Thanks!
We’ve got a fix for this in testing right now that should take care of this. No ETA when it will get merged with master and get released, though.
Thanks for the updates, @kinoCharlino. Hopefully it gets released before the OTA network shows come back from their holiday breaks!
@kinoCharlino said:
We’ve got a fix for this in testing right now that should take care of this. No ETA when it will get merged with master and get released, though.
Definitely, thanks for the update! I agree, hoping it can be released before the shows come back from holiday breaks!
you may add me as well. I hope this is the condition identified as a fix is forthcoming. HDHomeRun, 2nd show same channel (back to back), about 30 minutes in on second show. Obvious synchronization issues and subtle looping gets progressively worse to being unwatchable. This happened on 12/7 and again on 12/19. Is there a version of the Plex Server that I can fall back until this fix is released ? Please advise.
I’ve noticed this behavior as well…I only notice it on the HD programming…and I believe (but am not positive) when the same tuner does the capture. Sometimes I have the recording start a minute early and assume that in those cases the second show uses the 2nd tuner. I don’t have any back-to-back same tuner recordings coming up, but I do have some back-to-back shows where I start a minute early. If I remember, I’ll post back here.
I have the exact same behavior happening. Back-to-back shows on same channel, second episode begins to screw up half way through the show. Win 10, HDHomeRun PRIME, PMS 1.11.0.4633
@JoeKurtz said:
Hi @KinoCharlino, Has engineering had any luck finding/fixing this issue? I see there are a few other threads running in the forum that appear to be adding the same thing. Just curious if any progress has been made. Thanks!
We’ve got a fix for this in testing right now that should take care of this. No ETA when it will get merged with master and get released, though.
Is the fix in the latest 1.11.0.4666 release on 12/28 by any chance?
