poydeep.blogg.se - Mkvtoolnix gui template

MKVTOOLNIX GUI TEMPLATE CODE
MKVTOOLNIX GUI TEMPLATE WINDOWS

mkvmerge: AVI reader: fixed reading AVI files that contain vprp video properties header chunks reading aborted too early.

MKVToolNix GUI: header editor: users can now reorder tracks by dragging & dropping.

The information is also shown on the track overview page on the right.

MKVToolNix GUI: header editor: a new column has been added to the tree view showing the status of the “track enabled” flag.

MKVToolNix GUI: the spinner in the bottom right corner will now be hidden when no jobs are currently running.

MKVTOOLNIX GUI TEMPLATE WINDOWS

This means that the GUI will be scaled appropriately if Windows is set to 125%, 150% or 175% instead of being too small or too large. MKVToolNix GUI: only on Windows: when compiled with Qt ≥ 5.14 and Before this change it wasn’t possible to match such tracks via language codes. AVIs) will be treated as if they did have one set to und (“undetermined”) as that is the language the track will have in the Matroska file anyway. a und,en) all tracks that do not have a language property (due to their container not providing one, e.g. mkvmerge: when using language codes for track selection (e.g.

mkvmerge: AC-3 parser: E-AC-3 with BSID values > 10 and ≤ 15 are recognized now, too.

Here are the NEWS since the previous release: New features and enhancements

The other Linux binaries are stil being built and will be available over the course of the next couple of hours. The Windows and macOS binaries as well as the Linux AppImage are available already.

MKVTOOLNIX GUI TEMPLATE CODE

You can download the source code or one of the binaries. Anyway, here’s a new release with a couple of small improvements. I’m therefore glad that some users posted a couple of bug reports & feature requests that turned out to be small enough for me to fix & implement quickly: sometimes such small wins are desperately needed.īut that’s probably more than you wanted to know. improving Dolby Vision support further or implementing support for VVC/H.266. There are several topics on my TODO list that are rather big & require lots of work, e.g. The last couple of months have been pretty quiet regarding MKVToolNix as I’m still struggling to find time, motivation & energy for after-hour coding in general and work on MKVToolNix in particular.