Random skipping in recordings

[racameron]

Well, since it only happens for live recordings of TVE streams, it points to two possibilities:

1. Network issues with the source stream. The skipping is caused by an error in the source stream or an interruption in the network; it is not noticed in recorded content because the recording can stitch the interruptions together, whereas they are always experienced when live.
2. Hard drive issues with your DVR drive. Since the TVE stream is first written to your DVR drive before it is either sent to disk for recording or streaming to a client, the additional write/read operations are causing issues.

If someone else wants to jump in, feel free. But as of now, it's all just a WAG.

[crackers8199]

@racameron

Network issues with the source stream. The skipping is caused by an error in the source stream or an interruption in the network; it is not noticed in recorded content because the recording can stitch the interruptions together, whereas they are always experienced when live.

this is the opposite of what i'm seeing. watch live is fine (except for the occasional buffer, if i skip back a few seconds i don't even have that problem because the buffer always stays ahead of the current pointer). recordings are the issue.

@racameron

Hard drive issues with your DVR drive. Since the TVE stream is first written to your DVR drive before it is either sent to disk for recording or streaming to a client, the additional write/read operations are causing issues.

this also seems unlikely, because again there are no issues watching live (even when transcoding). when transcoding, the buffer is on the server right? so that would mean i should expect to see the same thing happening with live viewing if it were a hard drive issue...but i'm not.

[racameron]

Well, you seem to be the only person experiencing these issues. So I guess it goes back to my original thought about too many layers of abstraction. Have you checked with the Proxmox forums? Changed the OS in your Proxmox VM to something else? Change your storage drivers? Maybe look at Podman instead of Docker, or just ditch the container all-together if you're already running in a VM.

There are just too many unknowns. The only real way to really find out what is going on is start from a minimal installation—bare metal, no VMs or containers—and then piece-by-piece add your layers back in until you start experiencing the problem. Since your server is already hosting other services for your network, that's not really practical. But, it's probably the only way to get to a solution.

I doubt I can offer any additional help in my role as arm-chair/Monday-morning quarterback. Good luck.