EBU Logo EBU Logo
0108F - Timestamp Discontinuity
published
0108F v1.0
Item image
TIMESTAMP DISCONTINUITY
Timestamp Consistency
PES/SEI
Meets Requirements
Discontinuity, Mismatch
https://qc.ebu.io/items/0108F/versions/1-0-0/
Check
Report
Summary
EBU QC Id
0108F
Name
Timestamp Discontinuity
Status
published
Category
absolute
Lead editor
Roberto BORGOTALLO
Aliases
frame gaps
Tags
video
Versions
Version Status Edition date Saved by Note
Details
Definition
System shall discover timestamp discontinuities by analyzing the bitstream with contained presentation timestamps.
References

  • ISO/IEC 13818-1

    Remark: For MPEG 2

Examples

  • NO input
    Output: "Timestamp Discontinuity": True
    Output: "Frame Gap Location": at frame 11951, LastTimestamp 00:30:20:50, Next Timestamp 00:30:20:62.

    Remark: If no input is provided, then the default values apply, i.e. system should report even if just one timestamp discontinuity of just one frame gap is found

Input parameters
Name Description
Output parameters
Name Description
Test material
Title Version Download
Remarks
Remarks
Presentation timestamps are generally recovered from the PES for MPEG-2/H.264/H.265 and from SEI messsages for H.264/H.265. Timestamps are not guaranteed to be present in all situations, and if not present, this test should not be performed. If both PES & SEI messages are present for timestamps and the container does not specify which one should take precedence, both should be checked for discontinuity.

Discontinuities typically happen when the frame count increments by one and one of the following situations occurs:
a) timestamp increments by more than one frame;
b) timestamp remains constant or decrements in any manner.

MPEG-2 does allow for direct encoding from tape to transmit the LTC in the time_code section of the gop_header. If this is present, it could be used to check for discontinuities. This is not recommended, though, as the time_code element is mostly deprecated.
User discussions
Title Author Last update