MKVToolNix v83.0 released

[Mosu]

Originally Posted by Liisachan

By which I'm guessing that an auto-written BPS is for a track in MKV, and not for the actual audio data, but I'd like to confirm this. TYIA.

mkvmerge uses a generic algorithm for calculating a track's BPS: it takes the maximum sum of a packet's timestamp and its duration, subtracts from that the minimum timestamp of all packets, and uses that as the track's duration. Then it divides the number of bytes written as frame payload for that track and divides it by that duration.

That algorithm works in mkvmerge's core; it's codec-agnostic and only works on packet timestamps/durations and not on actual number of samples (because it doesn't have access to that type of information).