4 people 6a11a1302c Fix CTS=0 in fragmented fMP4 with multiple tracks (#317) ...

* Fix CTS=0 in fragmented fMP4 with multiple tracks

When muxing fragmented MP4 with both video and audio tracks,
compositionTimeOffset (CTS) was zero for all video samples, causing
B-frame content to display in decode order instead of presentation
order (visible judder).

Root cause: During finalize(), interleaveSamples(true) triggers
finalizeFragment() via the cross-track keyframe check in
addSampleToTrack. This writes the trun box before processTimestamps
has computed correct decodeTimestamp values, so CTS = PTS - DTS = 0.

Fix: Call processTimestamps() for all tracks at the start of
finalizeFragment(). This is safe because processTimestamps is a no-op
when the timestampProcessingQueue is empty.

Video-only fragmented muxing was unaffected because the single-track
case never triggers the cross-track keyframe check during
interleaveSamples.

Co-Authored-By: Claude Opus 4.6 <[email protected]>

* Fix the problem at the actual root

* Oopsie doopsie

---------

Co-authored-by: Claude Opus 4.6 <[email protected]>
Co-authored-by: Vanilagy <[email protected]>

2026-03-06 09:56:53 +00:00

..

browser

Make test more resilient

2026-03-04 17:12:40 +01:00

node

Fix CTS=0 in fragmented fMP4 with multiple tracks (#317)

2026-03-06 09:56:53 +00:00

public

Add support for reading/writing non-square pixel video frames (fixes #309)

2026-02-25 17:16:33 +01:00