Cypheros Transportstream Forum

English-speaking Support => TS-Doctor 2.x => Thema gestartet von: Utwen am September 10, 2019, 23:29:40

Titel: PES error for all teletext packets on two of Yle's channels
Beitrag von: Utwen am September 10, 2019, 23:29:40
I'm in Finland.

Recordings from two channels: "Yle TV2 HD" and "Yle Teema & Fem HD" generate PES ERROR for every packet in the teletext stream.

Log says that "Teletext PES format not DVB conform! Ignoring PES format errors.". Only TSDoctor doesn't ignore them completely, but floods the log file instead.

If omit the teletext from the cut, there is no error.

The third Yle channel "Yle TV1 HD" doesn't have the problem, and neither does any channel from any other company.

This problem exists in both programs recorded using a DVB-C device from cable (Elisa's network) as well as .ts recordings downloaded from the IPTV service Elisa Viihde, so it seems likely that the incompatibility is present in the original stream. It's also present on old DVB-T2 HD recordings from as early as 2015, so Elisa is probably not the culprit, either.

I'm using DVBViewer to record locally, to a .ts file, preserving all streams except EIT EPG Data.

This is what it looks like in the log file (complete log included in attachments):

...
Cut in  at PCR: 00:00:01.300 (01:53:12.090)
Cut out at PCR: 00:00:07.720 (01:53:18.510)
First packet  : 00001B53
Last packet   : 0000C532
PES ERROR  : For PID 1389 -01:53:10.790 PES packet 00000001 is invalid (ControlBitsPTS,MarkerBit1PTS,MarkerBit2PTS,MarkerBit3PTS), starting with TS packet 00000002
PES ERROR  : For PID 1389 -01:53:10.825 PES packet 00000002 is invalid (ControlBitsPTS,MarkerBit1PTS,MarkerBit2PTS,MarkerBit3PTS), starting with TS packet 000000EF
PES ERROR  : For PID 1389 -01:53:10.895 PES packet 00000003 is invalid (ControlBitsPTS,MarkerBit1PTS,MarkerBit2PTS,MarkerBit3PTS), starting with TS packet 000001E9
PES ERROR  : For PID 1389 -01:53:10.930 PES packet 00000004 is invalid (ControlBitsPTS,MarkerBit1PTS,MarkerBit2PTS,MarkerBit3PTS), starting with TS packet 000002E5
PES ERROR  : For PID 1389 -01:53:10.965 PES packet 00000005 is invalid (ControlBitsPTS,MarkerBit1PTS,MarkerBit2PTS,MarkerBit3PTS), starting with TS packet 000003EC
PES ERROR  : For PID 1389 -01:53:10.999 PES packet 00000006 is invalid (ControlBitsPTS,MarkerBit1PTS,MarkerBit2PTS,MarkerBit3PTS), starting with TS packet 000004FE
...


It would only be a nuisance, if it didn't flood the log file until it exceeded the 20M limit and stopped logging. You won't be able to see any errors that matter after than point.




Attachments:

I edited short segments from cable recordings (TV1 & TV2) and an Elisa Viihde download (Teema & Fem). Logs for these are included in the attached logs.zip.
(TV1 doesn't have the PES errors - I included it for comparison purposes.)

Also included are samples (sized under 1 MB) from each source file, made by raw cutting.

[Dateianhang durch Administrator gelöscht]
Titel: Re: PES error for all teletext packets on two of Yle's channels
Beitrag von: Cypheros am September 11, 2019, 00:34:37
We will check that.
Titel: Re: PES error for all teletext packets on two of Yle's channels
Beitrag von: Cypheros am September 11, 2019, 16:40:26
Teletext stream is not respecting MPEG standards.

The PES packet header has "PTS DTS flag" set to 2, what means PTS is present. The 5 bytes of the PTS are "00 00 00 00 00" and that's permitted. For example the 6th and the 1th bit of the first byte have to be set.
To respect the MPEG standards the PTS DTS flag should be 0 or the PTS should be valid.

For a detailed description of the PES header look here: http://dvd.sourceforge.net/dvdinfo/pes-hdr.html (http://dvd.sourceforge.net/dvdinfo/pes-hdr.html)

We will try to prevent the flooding of the log in the next TS-Doctor version.
Titel: Re: PES error for all teletext packets on two of Yle's channels
Beitrag von: Utwen am September 11, 2019, 17:18:54
Thank you for looking into this so quickly. That solution would be perfect.
Titel: Re: PES error for all teletext packets on two of Yle's channels
Beitrag von: Cypheros am September 17, 2019, 02:34:07
New version is online and should solve the problem.