MKVToolNix v74.0 released

[r0lZ]

Hi Mosu.
A user of BD3D2MK3D has this error with mkvmerge: CreateEventA not found in library api-ms-win-core-synch-l1-2-0.dll. I suppose it's because he uses an unsupported version of Windows. Car you confirm? Or is it an outdated library?
Original thread at VideoHelp here.

[lvqcl]

Originally Posted by r0lZ

I suppose it's because he uses an unsupported version of Windows.

https://forum.doom9.org/showthread.p...54#post1971554 and several posts below it.

[Mosu]

Originally Posted by r0lZ

Hi Mosu.
A user of BD3D2MK3D has this error with mkvmerge: CreateEventA not found in library api-ms-win-core-synch-l1-2-0.dll. I suppose it's because he uses an unsupported version of Windows. Car you confirm? Or is it an outdated library?
Original thread at VideoHelp here.

Sounds like they're running Windows version not supported by MKVToolNix, e.g. 7.

[r0lZ]

Yes. I have just received confirmation that Win7 is his OS.
Thanks.

[kedautinh12]

Originally Posted by r0lZ

Yes. I have just received confirmation that Win7 is his OS.
Thanks.

Win7 can use this ver
https://forum.doom9.org/showthread.php?t=184092&page=4

[r0lZ]

Indeed. Thanks.

[Mosu]

Hey y'all!

MKVToolNix v74 is out. This is another one in a longer line of small-ish bug fix releases. Nothing too earth shattering. Anyway, have fun with it.

Here are the usual links: the MKVToolNix home page, the downloads section and the source code.

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 since the previous release:

Version 74.0.0 "You Oughta Know" 2023-02-12
New features and enhancements

• mkvmerge: SRT handling: added a hack called "--engage keep_whitespaces_in_text_subtitles" which disables stripping whitespaces from the start & end of each line of SRT entries during muxing. Part of the implementation of #3470.

Bug fixes

• all: Windows: UNC paths of type "\\?\C:\…" are supported again by switching back to Boost's file system library instead of using C++17's file system library. Fixes #3058.
• mkvmerge: AVC/H.264 & HEVC/H.265 packetizers: when appending tracks the pixel dimensions will be checked & muxing will be aborted if they don't match. Fixes #3480.
• mkvmerge: file type detection: file types that can be detected unambiguously by their content (e.g. Matroska, MP4, WAV…) will now preferred in the detection order over file types based on their extension. Prevents certain cases of mis-detection, e.g. DTS in WAV but with a file name extension of ".dts" being detected as the wrong type of DTS. Fixes #3462.
• mkvmerge: SRT handling: whitespaces will now be stripped from the start & the end of each line of each entry, not just from the end of the last line. Part of the fix of #3470.
• mkvextract: SRT extraction: whitespaces will not be stripped from the start & end of the whole entry anymore. Part of the fix of #3470.
• MKVToolNix GUI: multiplexer: when adding multiple files that include certain file types (chapters, segment info and tag files) and when the choice where to add them is "all files to a single new tab", these certain file types will now be added in the newly added tab as well instead of the current tab that had already been open. Fixes #3469.
• build system: fixed compatibility with Ruby 3.2.0 by using "FileTest.exist?" instead of "File.exists?", "Dir.exists?" & "FileTest.exists?" which were removed in that release.

Build system changes

• MKVToolNix is now using & requiring Boost's "file system" and "system" libraries again instead of C++17's file system library. This is due to gcc's library not supporting UNC paths of types "\\?\C:\dir\file.ext".

Have fun 😁

[Ripman]

Hi M. Thanks for the new v74 release.

Sometimes I use the gui to generate an options file. I noticed that sometimes the gui will put the —display-dimensions option with a width X height argument in the options file.

I never use the —display-dimensions from the command line. Is the option required? What happens if not used?

I did read the man page but didn’t see anything explicit about the questions I asked. Just wondering. I’m thinking if the option is not present, mkvmerge uses what it sees in the video stream.

Thanks again. Best…..

[Mosu]

In general mkvmerge will always set the display dimensions on the output file. If they're provided via a CLI option, then those will be used. Otherwise, if they're provided by the source container (Matroska), those values will be used. Otherwise, the pixel dimensions will be used. Therefore you only need to set the parameters if they're different from the ones derived by the scheme outlined earlier. The goal for mkvmerge is to preserve as much information as possible verbatim by default.

That being said, the GUI has slightly different use case & different goal. One of its purpose is to make the user more aware of settings that are set somewhere in the source file. In the case of e.g. the movie's title that title is therefore shown in the appropriate line edit. The same goes for the display dimensions: if the source container provides display dimensions, those values are shown in the track's display width & height line edits — so that the user can easily see that they're set & what they're set to. Last, the GUI doesn't try to reduce the command line to the smallest possible CLI. It simply gives all the options for which some control is set in the GUI. Therefore sometimes those options are redundant.

For example, if you add a Matroska file with a video track whose pixel dimensions and display dimensions are both 1000x600. In such a case you wouldn't need to specify "--display-dimensions 0:1000x600" as that would be mkvmerge's default to use anyway. The GUI doesn't care, though; it doesn't try to recreate all of mkvmerge's internal decision making & adds "--display-dimensions 0:1000x600" anyway.

[NVF]

First, thanks so much for the tool.

I've gotten time stamp error warnings in the past (.srt overlaps if I understood them correctly) but no longer. Any help understanding and/or fixing this issue would be appreciated.

Thanks.