... | ... | @@ -19,7 +19,7 @@ However, there are several cases in which it simply does not match up – and it |
|
|
- With interlaced content a single Matroska packet might not store a whole frame but only one of its two fields. In such cases the duration of a field is obviously only half of the duration of a full frame. Therefore the reverse `1 / default duration` is more like double the value the user would expect as a frame rate.
|
|
|
* With variable frame rate (e.g. if an external timecode file is used) video the default duration is calculated in a totally different way. mkvmerge calculates the duration for all frames according to the timecode file, counts how often each duration occurs and then uses the duration that occurs the most as the new default duration. This may be a value that doesn't even reverse to any of the often-used frame rates that people are used to.
|
|
|
|
|
|
Unfortunately there are a lot of tools out there that simply present this number `1 / default duration` as the alleged frame rate even though Matroska doesn't provide that information (the frame rate). MediaInfo is one of them – though this is due to a [bug in the Matroska specs causing confusing among developers](https://github.com/mbunkus/mkvtoolnix/issues/778).
|
|
|
Unfortunately there are a lot of tools out there that simply present this number `1 / default duration` as the alleged frame rate even though Matroska doesn't provide that information (the frame rate). MediaInfo is one of them – though this is due to a [bug in the Matroska specs causing confusing among developers](https://gitlab.com/mbunkus/mkvtoolnix/issues/778).
|
|
|
|
|
|
MediaInfo also provides an "original frame rate" for some video codecs, especially h.264. The information displayed there is also not provided by the Matroska container. Instead MediaInfo gets this directly from the h.264 bitstream. Matroska has nothing to do with it.
|
|
|
|
... | ... | |