Download MKVToolnix 80.0

Moritz Bunkus has released version 80 of MKVToolNix. This open source program allows viewing, editing and converting matroska files. Sound tracks and subtitles can be added, removed or set as default. MKVToolNix is ​​a collection of separate command-line tools, but a graphical user interface is also included. Downloads are available for Windows, macOS and various Linux distributions. The following changes and improvements have been made in this release:

MKVToolNix v80.0 released

Time for another release. I'm still in a bit of a coding slump (or rather: preoccupied with all the amazing games that have come out this year); therefore this release is really, really small. I'll likely do one more bug fix release this year that'll be around this size as well. But let's see how things shake out.

New features and enhancements

• MKVToolNix GUI: if the system's locale uses one of the Han scripts, the GUI will force Arabic numerals to be used in spin boxes. This prevents Suzhou numbers from being used which seems to be the default on Windows systems sold in China. Implements #3624.

Bug fixes

• build system: fixed detection of Qt6 if clang is used for compilation on Linux. In that case Qt's qmake added a gcc-specific option that clang doesn't understand, -mno-direct-extern-access. configure will now pass the parameter -spec linux-clang to qmake so that it uses the correct compiler flags.
• build system: fixed the use of mktemp to be more portable to eg macOS. Fixes #3608.
• mkvmerge: if a video aspect ratio was given with –aspect-ratio-factor, the code would apply a second factor based on the pixel resolution, resulting in much too large values ​​for the DisplayWidth element. For example, with a pixel resolution of 720×520 & an aspect ratio factor of 1/1 the result should be 720×520, but instead it was 900×520. Up until release 76.0 this has only happened when a track order was given (which unfortunately includes all invocations with MKVToolNix GUI as it always includes the track order). Starting with release 77.0 this has always happened due to the automatic sorting of tracks implicitly creating a track order, even if none was given.