startTimeMicros
Where this container's timeline begins, in microseconds. It is 0 for most mp4 files, and commonly around 1.4s for MPEG-TS.
This is the offset between the two timelines KiteFFmpeg deals in. Timestamps it reports (StreamInfo, FrameInfo.pts) are absolute and include this value. Timestamps it accepts (seekMicros, extractFrame's atMicros, Transcoder.transcode and Remuxer.remux trim bounds) are relative to the start of the content, so 10_000_000 always means ten seconds in. Subtract this from a frame's own pts to move it onto the timeline those parameters use.
Where this container's timeline begins, in microseconds. It is 0 for most mp4 files, and commonly around 1.4s for MPEG-TS.
This is the offset between the two timelines KiteFFmpeg deals in. Timestamps it reports (StreamInfo, FrameInfo.pts) are absolute and include this value. Timestamps it accepts (seekMicros, extractFrame's atMicros, Transcoder.transcode and Remuxer.remux trim bounds) are relative to the start of the content, so 10_000_000 always means ten seconds in. Subtract this from a frame's own pts to move it onto the timeline those parameters use.
Where the container's timeline begins, in microseconds. This is the offset between the absolute timeline libavformat uses and the content-relative timeline the public API uses. The expect declaration in commonMain describes both timelines in full.
toRelativeMicros and toAbsoluteMicros are the only two places that apply this offset.
Where this container's timeline begins, in microseconds. It is 0 for most mp4 files, and commonly around 1.4s for MPEG-TS.
This is the offset between the two timelines KiteFFmpeg deals in. Timestamps it reports (StreamInfo, FrameInfo.pts) are absolute and include this value. Timestamps it accepts (seekMicros, extractFrame's atMicros, Transcoder.transcode and Remuxer.remux trim bounds) are relative to the start of the content, so 10_000_000 always means ten seconds in. Subtract this from a frame's own pts to move it onto the timeline those parameters use.
Where this container's timeline begins, in microseconds. It is 0 for most mp4 files, and commonly around 1.4s for MPEG-TS.
This is the offset between the two timelines KiteFFmpeg deals in. Timestamps it reports (StreamInfo, FrameInfo.pts) are absolute and include this value. Timestamps it accepts (seekMicros, extractFrame's atMicros, Transcoder.transcode and Remuxer.remux trim bounds) are relative to the start of the content, so 10_000_000 always means ten seconds in. Subtract this from a frame's own pts to move it onto the timeline those parameters use.