I had 3 recordings last night that had quite a bit of pixelation and when the video comes back, it was like the audio and the video had to catch up with each other - rendering these portions of the video unwatchable. Commercial skip also did not work for these recordings. This is what I am currently using for the set up:
DVR: Intel Core i7-6600U CPU @2.6GHz 2.81 GHz; Installed RAM: 16.0 (15.9 usable); 64-bit operating system, x64 based processor.
External Hard Drive: Seagate expansion 2 tb portable hard drive, stkm2000400
Can you post the relevant log entries?
Let me know if this is what you meant:
at=2025-01-20T18:59:00.9154483-06:00 loc=752 pkt=5 pid=80 what=pat_and_pmt offset=0 length=940 contiguous=false changed=true packets=2
at=2025-01-20T19:00:03.0456586-06:00 loc=54636184 pkt=290619 pid=80 what=pat_and_pmt offset=54462096 length=174276 contiguous=false changed=true packets=2
at=2025-01-20T20:29:00.1162051-06:00 loc=0 skipped=60
at=2025-01-20T20:29:00.3225146-06:00 loc=556728 pkt=2962 pid=80 what=pat_and_pmt offset=93120 length=463796 contiguous=false changed=true packets=2
at=2025-01-20T20:33:00.0553771-06:00 indexer=ads edl="unsupported value type" disconts="unsupported value type"
This was the log for another recording:
at=2025-01-20T20:29:00.1157005-06:00 loc=0 skipped=60
at=2025-01-20T20:29:00.3225146-06:00 loc=556728 pkt=2962 pid=80 what=pat_and_pmt offset=93120 length=463796 contiguous=false changed=true packets=2
at=2025-01-20T20:33:00.054869-06:00 indexer=ads edl="unsupported value type" disconts="unsupported value type"
at=2025-01-20T21:00:02.8264785-06:00 loc=1921265308 pkt=10219497 pid=80 what=pat_and_pmt offset=1921153824 length=111672 contiguous=false changed=true packets=2
at=2025-01-20T21:59:00.1585782-06:00 loc=0 skipped=64
at=2025-01-20T21:59:00.2693077-06:00 loc=288080 pkt=1533 pid=80 what=pat_and_pmt offset=79024 length=209244 contiguous=false changed=true packets=2
at=2025-01-20T22:00:02.7298376-06:00 loc=62113572 pkt=330392 pid=80 what=pat_and_pmt offset=62066572 length=47188 contiguous=false changed=true packets=2
at=2025-01-20T22:00:02.7298376-06:00 loc=5553769348 pkt=29541327 pid=80 what=pat_and_pmt offset=5553722348 length=47188 contiguous=false changed=true packets=2
at=2025-01-20T22:03:00.0548264-06:00 indexer=ads edl="unsupported value type" disconts="unsupported value type"
You would need to.post the logs relavent to the recording that had issues. Should be a summary line saying stats etc.
I'm not sure where to find that, aside from what I posted earlier. The "details" of the recording say that 7% of the recording was impacted by network issues
There you go... Give some details on your network topology and I'll try and offer some help
I have 1 GB fiber, the computer is currently connected via wifi to the router. Using an ATT router.
Try connecting the server via ethernet
Sounds good. I'll try this. I did notice that other recordings that happened last night seemed to also have these issues.
Aside from the network - does my computer and external hard drive seem adequate for hosting, or are there any hardware changes that I should consider?
Specs are more than enough. As long as the drive is USB3 then you should be fine. I have 3 drives totaling 25TB connected via USB3 and they work great