playback hiccups

[sub]

Yep, that original file has continuity errors, indicating missing packets.

If it's very reproducible, try temporarily switching to the local drive for a test, to see if it behaves any different. This at least help with narrowing down on the drive option.

[Allan]

What could cause an invalid PTS timestamp? Could it be invalid due to corrupt video?

[Allan]

Yep, that original file has continuity errors, indicating missing packets.

If it's very reproducible, try temporarily switching to the local drive for a test, to see if it behaves any different. This at least help with narrowing down on the drive option.

The same program, which consistently has a few hiccups, will record tonight to the internal drive.

I was thinking "this could be a bit complicated. It would be great if I can configure nextPVR to record only that program to a different location". So I looked, and it can! And it was easy. The backend is very nice work, and very well thought out.

[Allan]

Update:

Last night, I recorded the same program that pretty reliably has several hiccups, but to the internal SD rather than to the external hard drive. The recording was perfect.

I also recorded a program on a strong local channel, to the external hard drive. Hiccups.

Looking increasingly like there is a problem writing the data stream to the default (external) drive, but I will continue testing with the same program. BTW, ran diagnostics on external. No errors.

[Allan]

recording to the internal drive has been perfect in three tests. A further record to the default drive has had hiccups.

[Allan]

Update. It was definitely a disk related issue. Now sorted out.

I was able to record to another volume on the same external drive with no hiccups, so I backed up and erased the default "TV" volume and the adjacent volume, and created a new TV volume. In case the location on the disk, closest to the hub, contributed to the problem, I created the new TV volume away from the hub. Restored data. No hiccups since.

Thanks for your help tracking down this issue.