Tuner card died -- looking for recommendations

[johnsta]

> This is unlikely to be anything NextPVR is doing. It's just
> copying the digital stream supplied by the device. Often players
> will look at the first timestamp in a .ts file, and the last
> timestamp in the file, to determine the duration, and this is
> ultimately used while skipping etc. It's likely something like the
> broadcaster has spliced together different content during this
> show, and the end timestamp is smaller than the start timestamp,
> so VLC can't determine the duration, so reports 00:00. Transport
> stream files from broadcast sources are notorious for having these
> types of issues.

> Ultimately though, I do try to make sure NextPVR's own player can
> handle these types of scenarios, so you should get a more accurate
> duration reported there.

Is there any way to find these start/end timestamps? If I know
where they are in the TS file, then I can write a program to:

- Compare them to determine whether the file is ok

- Change them to repair the file.

Every time I google something like "ts file header" or "mpeg file
header," I get led into a Byzantine path through containers and packet
formats, but there's never any clear description of how I get the time
fields I want.

If there's no simple way to get this information, can you point me to
an online document that explains how to do it without having to become
an mpeg expert?

Thanks, John

[sub]

Is there any way to find these start/end timestamps? If I know
where they are in the TS file, then I can write a program to:

- Compare them to determine whether the file is ok

- Change them to repair the file.

Every time I google something like "ts file header" or "mpeg file
header," I get led into a Byzantine path through containers and packet
formats, but there's never any clear description of how I get the time
fields I want.

If there's no simple way to get this information, can you point me to
an online document that explains how to do it without having to become
an mpeg expert?

Thanks, John

Unfortunately the transport stream files are not easy to work with. They're layers up layers of complicated stuff. Your best bet is to use something like ffprobe.exe to extract frame information.