In this guide
Work through one aligned exampleCheck the intended boundary, not just the countValidate the property you intend to changeA media segment covering six seconds can contain several picture groups. Seeing that duration in a playlist does not reveal the encoder’s GOP interval or prove the segment can start decoding independently.
For media you control, verify both encoded structure and packaging against the intended player/platform requirements. For a provider stream, preserve the original context rather than attempting to fix dependencies by editing a playlist.
Work through one aligned example
In an original simplified 30 fps model, a six-second segment spans 180 frame intervals. A sixty-frame GOP interval corresponds to two seconds, so an aligned segment can contain three such intervals. The segment duration remains six seconds; the GOP interval remains two.
This is not a complete bitstream or a promise about every encoder. Scene decisions, exact frame timing and reference structure can alter the observed pattern. The point is that segment duration and GOP count are independent descriptions that must be related explicitly.
Check the intended boundary, not just the count
An independent segment start requires an appropriate decoder-entry structure and configuration for the target system. Apple’s HLS authoring document specifies an IDR frame at video-segment starts. Merely asking a packager for six-second files does not prove that the underlying encoded pictures satisfy that requirement.
A packager can choose supported cut points or produce durations affected by available entry points. If requested and actual durations differ, inspect the encoder and packager settings together. Do not infer a defect solely because a rounded duration label differs from a precise media interval.
Validate the property you intend to change
If an author changes GOP frequency, inspect the actual output rather than only the command line. Forced keyframe timing can be rounded according to encoder time-base behavior, and excessive forcing can affect encoder lookahead. Use current tool documentation and appropriate validators for the target clients.
A useful report contains actual frame rate, GOP/entry-point observations, requested and actual segment durations, initialization context and the relevant requirement. A viewer report should identify a repeatable start or seek failure without claiming control over the source encoding. This keeps file-boundary, decoder-dependency and latency questions separate.
| Original aligned model | Value |
|---|---|
| Frame rate | 30 fps |
| Segment span | 6 seconds / 180 frame intervals |
| GOP interval | 60 frames / 2 seconds |
| Intervals per segment | 3 |
| Independent-start validity | Requires separate structure/context verification |