MKVToolNix v99.0 released

[Perenista]

About my previous comment: that's odd, it wasn't working before... Now it is.

After the update, I noticed another issue:

Using: Windows 11, 64-bit...

Looks like this new MKVTOOLNIX is broken in terms of visuals, dark mode... it was OK before, now it looks like this:

https://i.postimg.cc/1XTjhDdB/MMM.jpg

That blue font for the english track was not what I saw before... same for the grey background...

Also, when we check the box "disable dark mode" it does not stay ticked... even after we restart the app. I am using some sort of dark mode config here...

EDIT: Yep, confirmed to be broken. Restarted Windows, nothing changed. Some sort of regression happened with the visuals of this app. I'll try to get an older version and install in another folder, to show how it looked like.

Oh, OK, just checked your changelog... what exactly was fixed?

Just installed 75.0.0 and it's OK:

https://i.postimg.cc/sDdqVCD4/CORRECT.jpg

https://i.gifer.com/origin/51/51d8642b88d1f052bcda12f2b86ebb0a_w200.gif

How can we fix this?

[Mosu]

Meh. Unfortunate I didn't notice this before the release. There are two separate issues: the link being too dark and the fact that the "disable dark mode" checkbox is still shown on Windows 11 as you cannot turn it off anymore there. I'll address both soon.

You cannot really do anything about it on your end. Either live with it or downgrade.

[Mosu]

Turns out this is a bug in Qt 6.5.0 which hardcodes that dark blue for the dark mode. I've filed an issue for it (https://bugreports.qt.io/browse/QTBUG-113305).

Until that's fixed I've also implemented a workaround in MKVToolNix. You can use the latest continuous builds (https://mkvtoolnix.download/windows/continuous/64-bit/76.0/) which contain the fix.

[Selur]

I got a problem with setting the SAR for av1 content.
Using:
mkvmerge --ui-language en -o "G:\Output\2023-05-02@05_31_22_6810__06.mkv" --global-tags "J:\tmp\mkvtags_2023-05-02@05_31_22_6810__06.xml" -d 0 --default-track 0:yes --default-duration "0:50/1fps" --aspect-ratio-factor 0:16/15 --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "J:\tmp\Naruto DVD Folge 4_15 sec_new_1_2023-05-02@05_31_22_6810_03.av1"
MediaInfo reports:
Video
Count : 381
Count of stream of this kind : 1
Kind of stream : Video
Kind of stream : Video
Stream identifier : 0
StreamOrder : 0
ID : 1
ID : 1
Unique ID : 7344196294740375732
Format : AV1
Format : AV1
Format/Info : AOMedia Video 1
Format/Url : http://aomedia.org/
Commercial name : AV1
Format profile : Main@L3.1
Codec ID : V_AV1
Codec ID/Url : http://aomedia.org/
Duration : 15280.000000
Duration : 15 s 280 ms
Duration : 15 s 280 ms
Duration : 15 s 280 ms
Duration : 00:00:15.280
Duration : 00:00:15:14
Duration : 00:00:15.280 (00:00:15:14)
Bit rate : 3263008
Bit rate : 3 263 kb/s
Width : 720
Width : 720 pixels
Height : 576
Height : 576 pixels
Sampled_Width : 720
Sampled_Height : 576
Pixel aspect ratio : 1.000
Display aspect ratio : 1.250
Display aspect ratio : 5:4
Frame rate mode : CFR
Frame rate mode : Constant
Frame rate : 50.000
Frame rate : 50.000 FPS
FrameRate_Num : 50
FrameRate_Den : 1
Frame count : 764
Color space : YUV
Chroma subsampling : 4:2:0
Chroma subsampling : 4:2:0
Bit depth : 10
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.157
Delay : 0
Delay : 00:00:00.000
Delay : 00:00:00:00
Delay : 00:00:00.000 (00:00:00:00)
Delay, origin : Container
Delay, origin : Container
Stream size : 6232346
Stream size : 5.94 MiB (100%)
Stream size : 6 MiB
Stream size : 5.9 MiB
Stream size : 5.94 MiB
Stream size : 5.944 MiB
Stream size : 5.94 MiB (100%)
Proportion of this stream : 0.99822
Default : Yes
Default : Yes
Forced : Yes
Forced : Yes
colour_description_present : Yes
colour_description_present_Source : Stream
Color range : Limited
colour_range_Source : Stream
colour_primaries_Source : Stream
transfer_characteristics_Source : Stream
Matrix coefficients : BT.470 System B/G
matrix_coefficients_Source : Stream

When using ffmpeg:
ffmpeg -y -r 50/1 -i "J:\tmp\Naruto DVD Folge 4_15 sec_new_1_2023-05-02@05_35_15_9110_03.av1" -vcodec copy -metadata encoding_tool="Hybrid 2023.05.01.1" -map 0:0 -aspect 20:15 -r 50/1 "G:\Output\Naruto DVD Folge 4_15 sec_new.mkv"
MediaInfo properly reports:
Video
Count : 381
Count of stream of this kind : 1
Kind of stream : Video
Kind of stream : Video
Stream identifier : 0
StreamOrder : 0
ID : 1
ID : 1
Unique ID : 15569613067555342625
Format : AV1
Format : AV1
Format/Info : AOMedia Video 1
Format/Url : http://aomedia.org/
Commercial name : AV1
Format profile : Main@L3.1
Codec ID : V_AV1
Codec ID/Url : http://aomedia.org/
Duration : 30560.000000
Duration : 30 s 560 ms
Duration : 30 s 560 ms
Duration : 30 s 560 ms
Duration : 00:00:30.560
Duration : 00:00:30:14
Duration : 00:00:30.560 (00:00:30:14)
Bit rate : 1600545
Bit rate : 1 601 kb/s
Width : 720
Width : 720 pixels
Height : 576
Height : 576 pixels
Sampled_Width : 720
Sampled_Height : 576
Pixel aspect ratio : 1.067
Display aspect ratio : 1.333
Display aspect ratio : 4:3
Frame rate mode : CFR
Frame rate mode : Constant
Frame rate : 25.000
Frame rate : 25.000 FPS
FrameRate_Num : 25
FrameRate_Den : 1
Frame count : 764
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:0
Chroma subsampling : 4:2:0
Bit depth : 10
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.154
Delay : 0
Delay : 00:00:00.000
Delay : 00:00:00:00
Delay : 00:00:00.000 (00:00:00:00)
Delay, origin : Container
Delay, origin : Container
Stream size : 6114084
Stream size : 5.83 MiB (98%)
Stream size : 6 MiB
Stream size : 5.8 MiB
Stream size : 5.83 MiB
Stream size : 5.831 MiB
Stream size : 5.83 MiB (98%)
Proportion of this stream : 0.98010
Default : No
Default : No
Forced : No
Forced : No
colour_description_present : Yes
colour_description_present_Source : Container / Stream
Color range : Limited
colour_range_Source : Container / Stream
colour_primaries_Source : Stream
transfer_characteristics_Source : Stream
Matrix coefficients : BT.470 System B/G
matrix_coefficients_Source : Container / Stream


=> seems like "--aspect-ratio-factor 0:16/15" got ignored.

Cu Selur

[Mosu]

@Selur: thanks, that looks like a bug in the AV1 packetizer. Other packetizers such as the AVC & HEVC ones do honor the aspect ratio given, whereas the AV1 simply ignores it. I have an idea why that is & will look into it.

[Mosu]

Are there any macOS users here that'd like to help me test something? A user over on Reddit asked for file association for the MKVToolNix app. I've implement such in the latest pre-DMG (https://mkvtoolnix.download/macos/pre/). However, I've run into the problem that after installing the application (via dragging & dropping the application to the Applications folder, _not_ the DMG) & running "killall Finder" MKVToolNix is now the default application for its types, taking precedence over thinks such as QuickTime or VLC. This is obviously not what I want; I only want it to be the primary for *.mtxcfg & an alternate for all the others (meaning it should show up in "Open with" but not be the application opened when double-cliking on a file or selecting "Open" from the context menu).

The documentation I've found says that I have to adjust the rank, which I've done for all file types with:

<key>LSHandlerRank</key>
<string>Alternate</string>

(and "Owner" solely for "mtxcfg"), but that doesn't seem to help on my machine.

Luckily things return to normal as soon as you uninstall the application.

I'd like some feedback if possible: does this happen for others, too? Any insight into why?

For those who want to take a look at the Info.plist: see here it is (https://gitlab.com/mbunkus/mkvtoolnix/-/blob/main/packaging/macos/Info.plist).

Thanks!

[Mosu]

I got a problem with setting the SAR for av1 content.

Should be fixed in the latest continuous builds (https://mkvtoolnix.download/windows/continuous/64-bit/76.0/).

[jpsdr]

Hi.
Out of curiosity, is there somewhere an option to get back the previous visual interface ? I don't like this "Fusion"... :(

[Mosu]

No, there isn't. The reason is simple: the older style (called "windowsvista" by Qt) doesn't support dark themes properly.

[jpsdr]

Too bad... :(
Ok, thanks.

[Sakura-chan]

So MKVToolNix will be forever stuck in dark mode with no way to change it back? A shame really. The interface looks horrible in dark mode to me. And having to switch the whole system for one external program doesn't make sense. I like dark mode on Windows itself but I want programs in light mode. For me things I stay little time in or are mostly in the background are good in dark mode, like windows settings, explorer. Programs I spent quite some time with are better in light mode.

All programs with dark modes that I've encountered have a switch, like MKVToolNix did until 75.0.0. Usually a "default", meaning follow system scheme, and a light and dark options, or other colour schemes if the program has them. It's like the most basic of options. Never an issue until today.

Why Fusion doesn't allow for a switch between modes I don't understand. Time to keep and cherish 75.0.0 indefinitely then. I do mostly BD remuxing which has a limited selection of settings/codecs already very mature so I'm not really too bothered. But talk about silly regressions.

[Mosu]

So MKVToolNix will be forever stuck in dark mode with no way to change it back?

No. Please read the corresponding FAQ entry (https://gitlab.com/mbunkus/mkvtoolnix/-/wikis/Dark-mode-issues) for the current state of things.

[Ripman]

Thank you - as usual - for the new version, M. Best…..

[Mosu]

Hey! 😁

It's nearly summer & the weather's nice where I live. So why not do another MKVToolNix release today? 😁 This release mostly fixes the messy situation with the dark application mode on Windows among a lot of other things. Additionally mkvmerge will now sort tracks by their type by default!

Here are the usual links: the MKVToolNix home page (https://mkvtoolnix.download/), the downloads section (https://mkvtoolnix.download/downloads.html) and the source code (https://mkvtoolnix.download/source.html).

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

Here are the NEWS (https://mkvtoolnix.download/doc/NEWS.md) since the previous release:

Version 77.0 "Elemental" 2023-06-04
New features and enhancements

mkvmerge: tracks in the destination file will now be sorted by their type automatically unless the track order is specified with the "--track-order" option. The order is as follows: video tracks first followed by audio & subtitle tracks with other rarely used types of tracks last. Tracks of the same type will be sorted in the same order as their source files occur in the command-line arguments. Note that this doesn't affect file identification. Implements #3545 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3545).
MKVToolNix GUI: multiplexer: the default list colors used for distinguishing source files does not include the darkest tier anymore (the ones where one or two components are set to the value 0x3f) as they're hard to distinguish from each other. Only affects new installations, or when the user presses the "reset to default colors" button. Implements #3533 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3533).
MKVToolNix GUI: multiplexer: the GUI will now check the state of the 'track enabled' flag of all video, audio & subtitle tracks when starting to multiplex or adding a job to the job queue. If there's no track with its flag turned on for a type, the GUI will turn on the flag for the first track of the type. This behavior can be turned off in the preferences. Implements #3535 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3535).
MKVToolNix GUI: header editor: the columns in the tracks/attachments view and the values on the "track type" page will now be updated each time a corresponding property is changed (e.g. when a track's name is changed) instead of showing what's in the file on disk. Implements #3554 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3554).
MKVToolNix GUI: macOS: when you install the application from the DMG it'll register itself as an alternate handler for its supported file types. This allows the use of the "Open with" context menu action in Finder.
MKVToolNix GUI: Windows: a new settings in the preferences lets the user chose whether to use the light or the dark color palette, or to follow the system settings. Part of the fix for #3528 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3528).

Bug fixes

Fixed compilation with fmt v10.0.0.
mkvmerge: fixed several instances of wrong format strings for "fmt::format" used in debug messages. Fixes #3548 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3548).
mkvmerge: AV1 packetizer: the packetizer did not honor the aspect ratio (factor) given on the command-line via the "--aspect-ratio" or "--aspect-ratio-factor" options.
mkvmerge: JSON identification: cropping parameters are reported again even if some of the four values are not present in the file or set to 0. Fixes #3534 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3534).
mkvmerge: Windows: when writing to a network share connected via SMB1 "mkvmerge" was aborting with a error about "create_directory() failed" with existing directories. This was due to a bug in recent versions of the Boost.Filesystem library. The Windows version of MKVToolNix will be built with Boost 1.82.0 from now on which includes the fix. Fixes #3547 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3547).
MKVToolNix GUI: the defunct "disable the dark mode" checkbox was removed from the preferences.
MKVToolNix GUI: language dialog: under certain conditions the controls for the individual components remained disabled when the dialog is opened even though editing of individual components is selected. Part of the fix of #3532 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3532).
MKVToolNix GUI: language dialog: the controls for the individual components weren't re-initialized properly after opening the dialog for the second & all following times, potentially leaving previously selected/entered entries intact, primarily when editing multiple tracks at once. Part of the fix of #3532 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3532).
MKVToolNix GUI: header editor: using the actions from the "modify selected track" context menu only worked if the user right-clicked on the first column in the view. They now work for clicks on any of the columns. See also #3554 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3554).
MKVToolNix GUI: header editor: some of the actions toggling specific flags from the "modify selected track" did not work correctly if the flag wasn't currently present in the file, especially if the underlying value has a default value in the Matroska specs.
MKVToolNix GUI: Windows: the GUI will now always use its own implementation of light & dark palettes instead of relying on Qt. This circumvents two issues with the palette support in Qt 6.5.0: 1. if Windows 11's dark application mode is active, links were displayed in a hard-to-read dark blue. 2. for unknown reasons the the dark palette was not chosen on some Windows 11 installations even though Windows 11's color mode was set to "dark". This is a workaround for #3528 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3528).

Build system changes

The bundled "fmt" library was updated to v10.0.0.
MKVToolNix GUI now uses an external Qt resource file instead of compiling it into the executable. The resource file has reached a size at which the C++ compiler exhausts available virtual memory on some 32-bit architectures. On Windows & macOS the GUI will look for the file in "&lt;folder_with_executables>/data/qt_resources.rcc", and in the directory set with "configure"'s "--datadir" parameter on other systems (which usually means "/usr/share/mkvtoolnix"). The "install" build system commands installs it into that folder.


Have fun 😁

[-QfG-]

Bug in v0.77 (x64 / x86)

If i using the "Header Editor" load a file and then i choose "Segment Information - Title" and set "Add Element" now to Yes/No the Tool crashes. This feature works fine in v0.76.

https://i.imgur.com/CLIWgvZ.png

EDIT Not only the function "Title" is corrupt, all functions under Segment Informations corrupted.

[Mosu]

Already fixed. See this issue (https://gitlab.com/mbunkus/mkvtoolnix/-/issues/3556).

[-QfG-]

Thanks, works fine now with r011 :)

[Kairys]

How to make a Blu Ray Remux? Tell me the procedure for creating a Bluray remux with Dolby Vision 7 from a BDMV container.
I use programs: MakeMKV, MKVToolNix. Do I need to make mkvextract gMKVExtractGUI after MakeMKV or just add MKV to MKVToolNix?

[Mosu]

First use MakeMKV as that'll preserve DV properly when reading from Blu-rays (MKVToolNix doesn't support reading DV from MPEG transport streams yet, nor from HEVC elementary streams). Then remux the MKV created with MakeMKV with MKVToolNix. No need for extraction. In fact extraction of DV & remuxing the extracted streams will be result in non-compliant Matroska files for the moment as, again, MKVToolNix doesn't support readint DV from MPEG TS & HEVC elementary streams.

[Kairys]

Is it better to add soundtracks in AC3 format or is it possible to add MKA (Matroska Audio)?

[Mosu]

There's no codec called "Matroska Audio". "Matroska Audio" can only mean a Matroska container that only contains audio (no video, no subtitles), but the audio codec can be anything (AAC, AC-3, DTS, Opus…).

[hello_hello]

I have a couple of suggestions/requests regarding the MKVToolNix GUI. How hard they'd be to implement, I have no idea.

One of the things I seem to do most when remuxing is to set or change a delay for a stream and also change a stream's name/description. I had to do this for quite a few files today and having to constantly switch tabs makes the process harder, so it made me wonder how hard it'd be to add a Custom tab to the GUI. The idea being the Custom tab could be configured by the user to contain the most used items from any of the other tabs, saving a lot of tab switching.

Another idea would be to make the columns themselves more useful, so appropriate items could be changed "in-place", rather than just passively display what's been entered under a tab. I'm referring to the section of the GUI in the screenshot below. An example would be changing the delay by clicking on the area where -21 is displayed and entering a new value, or by clicking under the default track column to automatically change the default status. That sort of thing.

Cheers.

https://i.imgur.com/IJID3z7.png

PS I still think having a copy of the "Abort Job" button on the multiplexer window would be a good idea. 99% of the time when I need to abort a job it's right after I've started it running from the multiplexer widow only to realize I need to change something, so it'd be handy to be able to stop the job from the same window too.

[Mosu]

Thanks for your suggestions. However, I won't implement them. They're all require a lot of effort to implement correctly, and I'm not keen on doing any of the work. Additionally I consider having an "Abort job" button on the multiplexer to be very bad design as there's no guarantee that the job that'll be aborted has anything to do at all with the current multiplex settings.

[hello_hello]

Thanks for your suggestions. However, I won't implement them. They're all require a lot of effort to implement correctly, and I'm not keen on doing any of the work.

No problem. I suspected as much.

Additionally I consider having an "Abort job" button on the multiplexer to be very bad design as there's no guarantee that the job that'll be aborted has anything to do at all with the current multiplex settings.

I'm an idiot, so for a running job I want to abort, I invariably switch to the Job Queue tab before remembering the Abort button's under the Job Output tab, and by the time I've switched tabs again the job's often finished or almost finished running, so these days I usually just add the modified job to the queue and let it over-write the first output file. :)

What about a situation like that where a second job is added to the queue with the same name as a running job or a job already in the queue? You have to click through a warning about over-writing the first job to show that's you're intention, so would it make sense for any existing job with the same name to be aborted automatically if it's running or prevented from running if it hasn't started, given it'll be over-written anyway? The warning dialogue could possibly have an extra button, one to add the new job to the queue without killing any existing job as it currently works, and another to also stop/abort any existing job with the same output file name, or something like that....

[Selur]

Using mkvmerge v77:
mkvmerge --ui-language en -o "G:\Output\2023-06-15@16_46_50_3010__03.mkv" --global-tags "G:\Output\mkvtags_2023-06-15@16_46_50_3010__03.xml" -d 0 --default-track 0:yes --default-duration "0:50/1fps" --aspect-ratio-factor 0:1150/1053 --fourcc 0:MP4V --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "G:\Output\2023-06-15@16_47_01_0110_02.264"
and
MP4Box -par 1=1150:1053 -add "G:\Output\2023-06-15@16_47_01_0110_02.264"#video:fps=50:name="":lang="" -brand avc1 -itags tool="Hybrid 2023.06.15.1" -tmp "G:\Output" -new "G:\Output\2023-06-15@16_47_01_0110__03.mp4"
both tell the muxer that the PAR should be 1150:1053.

For the mkv 'mediainfo --full' reports:
Width : 692
Width : 692 pixels
Height : 568
Height : 568 pixels
Stored_Width : 704
Stored_Height : 576
Sampled_Width : 692
Sampled_Height : 568
Pixel aspect ratio : 1.331
Original pixel aspect ratio : 1.092
Display aspect ratio : 1.621
Display aspect ratio : 16:10
Original display aspect ratio : 1.331
Original display aspect ratio : 4:3
for the mp4 'mediainfo --full' reports:
Width : 692
Width : 692 pixels
Height : 568
Height : 568 pixels
Stored_Width : 704
Stored_Height : 576
Sampled_Width : 692
Sampled_Height : 568
Pixel aspect ratio : 1.092
Display aspect ratio : 1.329
Display aspect ratio : 4:3
Original display aspect ratio : 1.331
Original display aspect ratio : 4:3

Using ffmpeg as muxer:
ffmpeg -y -r 50/1 -i "J:\tmp\2023-06-15@17_04_11_3410__04.mkv" -vcodec copy -metadata encoding_tool="Hybrid 2023.06.15.1" -map 0:0 -bsf:v h264_mp4toannexb -aspect 1.3305378330 -r 50/1 "G:\Output\par_1150_1053_ffmpeg.mkv" (using DAR instead of PAR since ffmpeg only handles DAR)
I get:
Width : 692
Width : 692 pixels
Height : 568
Height : 568 pixels
Stored_Width : 704
Stored_Height : 576
Sampled_Width : 692
Sampled_Height : 568
Pixel aspect ratio : 1.092
Display aspect ratio : 1.331
Display aspect ratio : 4:3

Using AV-1 and:
mkvmerge --ui-language en -o "G:\Output\2023-06-15@17_09_18_2810_02.mkv" --global-tags "J:\tmp\mkvtags_2023-06-15@17_07_47_7110__04.xml" -d 0 --default-track 0:yes --default-duration "0:50/1fps" --aspect-ratio-factor 0:1150/1053 --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "J:\tmp\av1_mkvmerge_1_2023-06-15@17_07_47_7110_02.265"
Width : 692
Width : 692 pixels
Height : 568
Height : 568 pixels
Stored_Width : 704
Stored_Height : 576
Sampled_Width : 692
Sampled_Height : 568
Pixel aspect ratio : 1.331
Original pixel aspect ratio : 1.092
Display aspect ratio : 1.621
Display aspect ratio : 16:10
Original display aspect ratio : 1.331
Original display aspect ratio : 4:3
vs MP4Box and:
MP4Box -par 1=1150:1053 -add "J:\tmp\av1_1_2023-06-15@17_09_18_2810_02.265"#video:fps=50:name="":lang="" -brand hvc1 -itags tool="Hybrid 2023.06.15.1" -tmp "J:\tmp" -new "G:\Output\2023-06-15@17_09_18_2810__04.mp4"
mediainfo reports:
Width : 692
Width : 692 pixels
Height : 568
Height : 568 pixels
Stored_Width : 704
Stored_Height : 576
Sampled_Width : 692
Sampled_Height : 568
Pixel aspect ratio : 1.092
Display aspect ratio : 1.329
Display aspect ratio : 4:3
Original display aspect ratio : 1.331
Original display aspect ratio : 4:3
with ffmpeg I get the same as with MP4Box.


=> Did something change on how to tell mkvmerge so set a specific par, is something broken?

Cu Selur

[Mosu]

What about a situation like that where a second job is added to the queue with the same name as a running job or a job already in the queue?

Sure, one could add yet even more functionality and special-cases for those types of user errors, but I just don't want to.

[Mosu]

Did something change on how to tell mkvmerge so set a specific par, is something broken?

I don't think so. Did you try earlier versions? How do they behave compared to v77?

[Selur]

I only tested the last two versions (same behaviour), will test more over the weekend.

[Mosu]

If you find one that behaves differently & the next one doesn't, that'd help me a great deal. I really cannot think of the last time I changed aspect ratio handling.

[hello_hello]

Sure, one could add yet even more functionality and special-cases for those types of user errors, but I just don't want to.

Fair enough, but to me it'd just be an extension of checking a file with the same name doesn't already exist on the disk, except instead of a file being over-written, the job in the queue is replaced.

[Mosu]

I'm not against the functionality per se. If you want to implement it & provide patches/a MR for it, I'd be more than happy to merge them.

[Selur]

@mosu: can't reproduce this anymore, will report back in case it pops up again and I can.

[Mosu]

Heyo!

MKVToolNix v78 is out with tons of bug fixes, especially for those crashes in the GUI's header editor & for the GUI hanging when adding files via drag & drop. Both have crept in in version 77. Fortunately they were only annoying but didn't affect existing files.

Here are the usual links: the MKVToolNix home page (https://mkvtoolnix.download/), the downloads section (https://mkvtoolnix.download/downloads.html) and the source code (https://mkvtoolnix.download/source.html).

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

Here are the NEWS (https://mkvtoolnix.download/doc/NEWS.md) since the previous release:

Version 78.0 "Running" 2023-07-02
New features and enhancements

MKVToolNix GUI: header editor: for files that only contain legacy track language elements but no IETF language elements the header editor will now derive the IETF language elements from the legacy elements. See #3557 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3557).
AppImage: the AppImage is now built on AlmaLinux 8 with Qt 6.5.1. This means that the minimum glibc version this AppImage is compatible with has also been bumped, to v2.28. The oldest Debian coming with this version is Debian 10 "Buster"; for Ubuntu it's 18.10 "Cosmic Cuttlefish".
Windows installer: the installer will now remove the file "data\portable-app" if it's present in the installation directory as its presence would signal to the app to run in portable mode, requiring write access to its base directory. This fixes some installation issues that could occur when a user extracted a portable app archive into a folder like "C:\Program Files\MKVToolNix". Also added an installation check for the same issue. See #3558 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3558).

Bug fixes

all: Linux: if initializing the locale system based on the system's settings fails, e.g. if environment variables such as "LC_ALL" have been set to "fr_FR.UTF-8" but the locale for "fr_FR.UTF-8" hasn't been built, MKVToolNix will try to fall back to "en_US.UTF-8" first & "C.UTF-8" second. If neither of the three succeeds, an error message will be shown, and the program will abort. This fixes the programs not catching an exception from the "boost::filesystem" library which doesn't cope with mis-configured locale systems well. Workaround for #3574 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3574).
mkvmerge: sorting tracks by type did not work properly when some tracks weren't copied. Part of the fix of #3567 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3567).
mkvmerge: track numbers in the destination file were assigned out-of-order when the track order in the source files differs from the one in the destination file. Now they're assigned sequentially in the order the tracks appear in the destination file again. Part of the fix of #3567 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3567).
MKVToolNix GUI: under certain circumstances the GUI would try to display error messages from a secondary thread, which isn't allowed in Qt, causing to program to either hang or outright crash. Part of the fix of #3556 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3556) & #3561 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3561).
MKVToolNix GUI: the GUI will check for several potential installation issues wrt. to having write access to certain directories (system's temporary directory, MKVToolNix's file identification cache directory and others) & display proper error messages if not. Part of the fix of #3556 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3556) & #3561 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3561).
MKVToolNix GUI: header editor: fixed the application crashing whenever you change a property below the "segment information" node. This bug was introduced in v77. Fixes #3556 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3556).
MKVToolNix GUI: header editor: when reading files that only contain legacy track language elements but no IETF track language elements, the header editor was showing all tracks as having "English" as the language. This bug was introduced in v77. Fixes #3557 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3557).
MKVToolNix GUI: header editor: when a legacy track language element contains a country code (e.g. "fr-CA"), the header editor was wrongfully using "und" = "undetermined" as the language for that element. Now it'll use the language from the language/country pair, which would be "fr" in the earlier example. Part of the fix of #3557 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3557).
MKVToolNix GUI: header editor: the keyboard shortcuts from the "modify selected track" sub-menu didn't work right after opening a file. They only started working after opening the "header editor" menu. Fixes #3573 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3573).
AppImage: fixed the GUI resources (e.g. icons) not being found.
AppImage: the Qt plugins required for using compose key/dead keys are now included. Fixes #3577 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3577).

Build system changes

The compilation database ("compile_commands.json") is now always built. The variable "BUILD_COMPILATION_DATABASE" is not evaluated anymore.


Have fun 😁

[varekai]

Thanks! Much appreciated!

[Perenista]

I am not sure if this was already questioned here:

If we need to handle multiple MKVs, MKVToolnix while capable of adding mutiple tasks, which happen after the former has already finished, cannot open multiple instances of the program. This is only possible if we install an old version somewhere.

Is this the developer's choice, or something else prevents this idea from working?

I'll explain: sometimes I have to deal with, say, more than 10 different files extracted from the discs, bonus features. So I may have to do the same procedure with all of them, at the same time. I could easily do the 1st, then close in the same MKVToolnix instance, and open the 2nd. But it would also help if I could open 2 windows of that program at the same time.

One example:

VirtualDub2. If I need to check how 2 files are different in the same scene/frame, I need to open 2 instances of that program:

If I click in the icon from my taskbar, it will not do it. Only 1. But if I do it again from the shortcut in my desktop, 2, 3 or more are now active:

https://i.postimg.cc/09sYQBPR/WINDOWS.jpg

The same cannot be said of MKVToolnix, which locks me into 1 instance.

[Mosu]

You can have multiple multiplex jobs open in MKVToolNix GUI at the same time. That's the big difference to the old mkvmergeGUI which didn't have that capability. There's no need for a second instance as you can work on multiple jobs simultaneouslyin the same instance.

[Perenista]

Multiple jobs, yes. Once the 1st ends, the other will start. But how can I open multiple tabs inside MKVToolnix and edit two files at the same time?

[Mosu]

"Multiplexer" menu → "New", or Ctrl+N.

[Mosu]

Heyo!

With up to 31°C outside, it's a good idea to stay inside & do the likely last release of the summer for MKVToolNix, v79.0. Not a lot's happened, but there's support for AV1 with Dolby Vision. Yay!

Here are the usual links: the MKVToolNix home page (https://mkvtoolnix.download/), the downloads section (https://mkvtoolnix.download/downloads.html) and the source code (https://mkvtoolnix.download/source.html).

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

Here are the NEWS (https://mkvtoolnix.download/doc/NEWS.md) since the previous release:

Version 79.0 "Funeral Pyres" 2023-08-20
New features and enhancements

mkvmerge: AV1: added support for reading Dolby Vision from AV1 IVF & OBU streams. Patches by Quietvoid.
mkvmerge: MPEG TS reader: added support for colors in teletext subtitles. Patch by Angela Schmid.
MKVToolNix GUI: multiplexer: when adding files the GUI can automatically enable the "forced display" flag for subtitle tracks if the file name contains the word "forced" delimited by certain characters (configurable). This feature is turned on by default. Implements #3586 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3586).
MKVToolNix GUI: multiplexer: added the option "--stop-after-video-ends" to the dialog for additional command line options. Implements #3594 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3594).
MKVToolNix GUI: multiplexer: when adding Blu-ray playlists the dialog allowing the user to select the playlist to add will now show audio & video track properties as well (pixel dimensions for video; sampling frequency, channels for audio). Implements #3597 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3597).
MKVToolNix GUI: header editor: in order to reduce confusion with users non that versed in Matroska elements, the naming of the two "language" track properties has been changed: the old element is now titled "Language (obsolete)" & the current, IETF BCP 47 based one is simply called "Language".
MKVToolNix GUI: preferences: you can now use the "delete" key to remove entries from simple list widgets for strings (e.g. the list of recently used destination directories).

Bug fixes

mkvmerge: DTS reader: if a DTS stream doesn't start with a DTS core but a sub-stream element (EXSS), the reader will now look for a core. If found, it'll start processing from there instead of from the start. This fixes the timestamp calculation if the sampling frequency in the core & in the extensions are different. Fixes #3602 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3602).
MKVToolNix GUI: multiplexer: the "emphasis" and "stereoscopy" combo-boxes now have a much smaller minimum width, allowing to make the whole "properties" pane much smaller again. Fixes #3581 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3581).
MKVToolNix GUI: macOS: when you install the application from the DMG it'll no longer register itself as an alternate handler for its supported file types. It seems like this overrode existing associations, forcing people to change them manually to whatever they wanted them to be. Additionally this forced the associated file to always be shown with an MKVToolNix icon. The GUI's own ".mtxcfg" files will still be registered. Fixes #3588 (https://gitlab.com/mbunkus/mkvtoolnix/issues/3588).


Have fun! 😁

[varekai]

Many thanks for the update, much appreciated! :)

[tebasuna51]

Thanks Mosu, you are lucky with 31º here we go over 40º

[Mosu]

Yeah I definitely am lucky to have been born where I have been, no doubt about it. Hope y'all can stay hydrated & safe.

[Kairys]

Does the GPU play a role in ripping?
I am curious as does the GPU play a role in ripping? Would spec'ing a higher end GPU card result in better ripping performance?

[Mosu]

For MKVToolNix the GPU doesn't make a difference as it isn't a video encoder. MKVToolNix solely works at the container level. It's speed is limited by I/O speed, RAM speed, and its architecture.

[Selur]

Okay, how to set the PAR to 1:1 on a source?
With v76 using:
mkvmerge --ui-language en -o "G:\Output\2023-08-25@13_36_38_4410__06.mkv" --global-tags "J:\tmp\mkvtags_2023-08-25@13_36_38_4410__06.xml" -d 0 --default-track 0:yes --default-duration "0:24000/1001fps" --aspect-ratio-factor 0:1/1 --fourcc 0:MP4V --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "J:\tmp\2023-08-25@13_36_38_4410_03.264"
worked fine. (tried x264 and 265 encoded content)
mkvtoolnix-64-bit-76.0-revision-055-g212d04d4e and later set the DAR of the source as PAR.

okay, it's not just PAR 1:1, I tried:
mkvmerge --ui-language en -o "G:\Output\2023-08-25@14_13_41_3610__04.mkv" --global-tags "G:\Output\mkvtags_2023-08-25@14_13_41_3610__04.xml" -d 0 --default-track 0:yes --default-duration "0:25/1fps" --aspect-ratio-factor 0:16/11 --fourcc 0:MP4V --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "G:\Output\2023-08-25@14_13_41_3610_03.264" --language 0:aid --default-track 0:yes --forced-track 0:no -a 0 --compression -1:none --no-video --no-subtitles --no-chapters "G:\Output\iId_2_aid_1_2023-08-25@14_13_41_3610_01.mp3" --track-order 0:0,1:1 (also set
--track-order ...')
I uploaded the raw streams and the output to my googleDrive (https://drive.google.com/file/d/1_3tuQwrx0Q-k4h8Tm1m9BCxnBu-B8Ysq/view?usp=drive_link) for you to easily reproduce this.

=> is this a bug, or does setting the PAR work in another way than before, and I missed the change?

PAR seems to be fine if I use '--track-order 0:1,1:2' (offsetting the output numbers by on) => is '--track-order ...' needed for PAR to work?
(Only for x264, x265 encodes this works, for av1 the PAR is broken in this case.)

Cu Selur

[DMD]

Good morning.
Sorry for the stupid question, I don't know if it has been asked already.
I would need to launch multiple instances, is it not possible to do that?
Thank you

[varekai]

Good morning.
Sorry for the stupid question, I don't know if it has been asked already.
I would need to launch multiple instances, is it not possible to do that?
Thank youYes you can start 2, I havn't done that before and don't know if it will work with files added.
Start one as admin and one without and 2 instances will load.

[Mosu]

Good morning.
Sorry for the stupid question, I don't know if it has been asked already.
I would need to launch multiple instances, is it not possible to do that?
Thank you

No, you cannot. You also don't need to as you can easily open several multiplex settings at the same time within that single instance. Working on multiple things simultaneously is very much possible.

BTW: this has been asked & answered (https://forum.doom9.org/showthread.php?p=1990675#post1990675) not even three weeks ago here.

[Mosu]

Okay, how to set the PAR to 1:1 on a source?

This looks a bit buggy. Can you please file an issue over on Gitlab (https://gitlab.com/mbunkus/mkvtoolnix/-/issues/)? Thanks.

[DMD]

No, you cannot. You also don't need to as you can easily open several multiplex settings at the same time within that single instance. Working on multiple things simultaneously is very much possible.

BTW: this has been asked & answered (https://forum.doom9.org/showthread.php?p=1990675#post1990675) not even three weeks ago here.
Thank you very much
I had not read the discussion.