Expose unsupported MP4/MOV edit-list features through the API
Author: VardiakCreated Sep 11, 2026Updated Sep 11, 2026
Mediabunny logs warnings when an MP4/MOV edit list (elst box) contains unsupported instructions, such as multiple media edits or a media_rate other than 1.
We would like to detect these cases and fall back to HTML video playback, since decoding can succeed while these instructions are ignored.
Logs aren't the right interface for this. Applications should be able to query unsupported features for an input or track directly, without matching warning messages.
Would you consider exposing this information through the API? This would preserve the current best-effort behavior while letting consumers decide when to use a fallback.
Happy to contribute if this sounds useful.
Source: Vanilagy/mediabunny