pub fn frame_num_range_line(before: u64, range: u64) -> Option<String>Expand description
The line saying the frame_num range an H.264 key frame carries, where it differs from the
one the stream carried before (0 for none yet); None where it is the same or unknown (0).
The range sets which losses cost a key frame (ReferenceWindow), and it is the encoder’s
own sequence parameter set that says it: a VA-API driver codes its own, so the same session
can carry 65536 values where pixelflux writes the set and 128 where radeonsi does. Said once
per change, so the log carries what each stream ran on.