First, transport streams were originally intended for very long broadcasts (days or weeks. Think television stations). TS uses 33 bits to store 90kHz ticks. This makes timesamp rollovers very common (about once a day). Because the timestamp rolls over so frequently, It is generally not a good idea to rely on the time stamps as anything other than an arbitrary tick on a ever moving clock with a start time at an unknown point in the past. Think of an analog clock, and remove all markings. Without the orientation, you can not use it to tell time. But you can still use it to measure time. In other words the timestamps only have meaning relative to other timestamps in the stream. They do not exist for human convenience. They exist so the decoder can do its job.

But as to why not start at 0 anyway. TS stores pts and dts as separate values, where as other containers use a dts+cts to determine pts. So, If you have a stream with out of order (B) frames, you will encounter frames that must be decoded before time 0, and displayed after. In other words, you will have negative (rolled over) dts values at the start of the stream. To simplify the decoders job, some value larger then the largest possible cts (pts-dts) is added to the pts/dts to bring them into the positive range at the start. This is common practice, and left up to the decoder/player to apply the logic as to what time is displayed to the user.

https://stackoverflow.com/questions/27532571/start-timestamp-of-pts-time-in-an-mpeg-ts-stream-is-not-zero

This reverts commit ac73b3ec.

AudioGapDetector: data export structure, refs #33406

See merge request !3

Paul GOULPIE authored Feb 24, 2021 and Florent Thiery committed Feb 24, 2021

Addition of a data structure (dictionary), allowing the reuse of results in library mode.

implement gap detector, fixes #33158

See merge request !2

add way to ignore specific errors fixes #32219

add --ignore-list argument ; if set, ignored errors will still be printed but will not trigger a non-0 exit code

See merge request !1