0040X - Video Duration
v2.0
published
0040X
v2.0
VIDEO DURATION
EBU Test Items 0040F & 0040W
Crosscheck Values
Matches
Crosscheck Mismatch
https://qc.ebu.io/items/0040X/versions/2-0-0/
Check
Report
Summary
- EBU QC Id
- 0040X
- Name
- Video Duration
- Status
- published
- Category
- absolute
- Lead editor
- Friedrich Gierlinger
- Aliases
- duration run time playtime
- Tags
- video
Versions
| Version | Status | Edition date | Saved by | Note |
|---|
Details
- Definition
- System shall check the calculated video duration is consistent with the signalled video duration in the bitstream and the wrapper.
- References
-
-
EBU QC Test Item 0040F
-
EBU QC Test Item 0040W
-
- Examples
-
-
The video duration signalled in the metadata (00:02:30:00) is NOT the same as the one calculated based on the video frames in the bitstream (00:01:30:01).
-
Input parameters
| Name | Description |
|---|
Output parameters
| Name | Description |
|---|
Test material
| Title | Version | Download |
|---|
Remarks
- Remarks
-
Wrappers usually contains information that allows to know this duration. MXF for example has a field "duration" that more precisely counts the number of edit units (for D10 this coincides with video frames), the wrapper also contains the framerate so it is possible in this case to calculate our wanted duration with a simple multiplication.
Wrappers can sometimes contain wrong information leading to a wrong duration.
A playable bitstream level MUST contain the information necessary to calculate our duration. If it is playable there is a way to establish the duration.
Bitstream is the layer where the duration can be determined more reliably. It can be calculated in several ways depending on the format of the coding, but our specs don't want to enter into these details.
For most of the cases also a crosscheck between audio and video duration is feasible and probably useful! While systems should strive to report audio errors in relation to the relative video time (frames), it is understood that this may not always be possible, and in some cases, audio errors could be reported in HRS:MIN:SEC.MSC relative to a start time of zero.
User discussions
| Title | Author | Last update |
|---|