MKVToolnix Windows 7 "The final Countdown"

[jpsdr]

Hi.

I'm creating this thread to avoid poluting the Mosu thread with more posts.

We can talk here about which versions are working.

Also we know that a not working version at one time doesn't mean it's final, it just happenend.

Nevertheless, the reality is that the true final deadline is comming, and it's very near !

But, in the meantime...

The last i've tested working is 61.

New non officials QT5 builds
You can check here for builds, not sure how often there will be.

[Liisachan]

Yeah, let's talk freely here without annoying Mosu

First off, I was surprised to know there are so many die-hard Win7 users, as I was thinking I was one of only few weirdos who're still using Win7.
Why are you guys avoiding Win10? Privacy concerns, or some kind of compatibility problems? If it's privacy, do you think Linux (migrating to it or using it side by side) is a realistically good option?

Also, don't just use the "lastest" MKVToolnix blindly... Generally, too new versions tend to be less reliable than tried and tested older versions, especially, experimental "continuous" builds. If you do font attachments, I'd suggest Version 57 or before to avoid the font-mime-type mess.

While MKVToolnix is a respectable project, it's not a secret that its GUI is not known for the most intuitive UI. Matroska is sometimes too powerful, too complicated, thus tools tend to become complicated & confusing.
Given that the rigorous rounding is important for Matroska (which doesn't support ntsc 24000/1001 fps explicitly),
https://matroska.org/technical/notes...scale-rounding
the current rounding errors of mkvmerge is less than ideal, although there are workarounds. The fundamental problem here may be that MKVToolnix is practically a one-person project, not developed by a team.

But it's FLOSS, so if someone starts alt. builds (like MPC-HC & MPC-BE), things might become convenient for everyone, more flexible, and perhaps less stressful for Mosu too.

That being said, the problem here is not only about MKVToolnix. Many tools have stopped supporting Win7 already (esp. 32-bit), and more and more tools will stop supporting Win7 sooner or later... So I think Win7 users should start looking for a different option too just in case, which may mean Linux. "MKVToolnix for Win7" would be useful for the time being, though.

For many practical purposes, older versions of mkvmerge are perfectly fine. Essentially they write bit-identical MKV files as written by the newest version. So don't worry too much

EDIT
additional link
https://forum.videohelp.com/threads/...-do-they-exist

[Dogway]

It's a Doom9 thing (the amount of Win7 users), we are a bunch of die hard fans.
Personally I like the OS to be fully under my control, and be sleek and functional.
Things like Cortana, Windows Defender, Candy Crush, Telemetry, "Apps", unavoidable updates... are not things I want on a working environment.

Another bad thing is the lack of DWM, I read you can't disable it so you can't go into FSE anymore.
More:
You have to disable "Control Flow Guard" for extra performance (if you run NVidia Cards).
You also need to "Empty Standby Memory" regularly while gaming (maybe with a task scheduler).
I also read that there are issues with the winsxs folder, maybe due to the amount of updates but it grows very large soon.
Finally the UI is a mess, not only metro is a disaster in itself but it's half metro half classic UI mixed.

I was happy to change to Win11 as it fixes some of the Win10 problems, but then they came with the hardware requirements.

Linux... nvidia driver incompatibilities and no or very bad color management system. Enough to not look any further.

I will install Win10 regardless in a few months, at least until I buy a new PC probably around 2025.

I'm curious to know aside of a GUI what MKVToolnix has better MKV features/support than ffmpeg. To know if it's worth changing, or if ffmpeg has important issues to care about.

[filler56789]

Version 67.0.0.63 is O.K.

[filler56789]

Last_Good one = 67.0.0.76.

[von Suppé]

Originally Posted by filler56789

Last_Good one = 67.0.0.76.

[Liisachan]

Originally Posted by Dogway

It's a Doom9 thing (the amount of Win7 users), we are a bunch of die hard fans.
Personally I like the OS to be fully under my control, and be sleek and functional.

Yeah, you want to own your OS. You don't want your OS to own you. Forced updates would be a real downer. While you're talking about freedom, convenience, practicality, I'd use "privacy" as the keyword, but I guess we're basically saying the same thing here. I'm so ready to migrate to Linux, except I'm kind of "trapped" - some tools that run on Windows are important in my current tool chain, even though I don't need Windows itself. Maybe I could use Win10 locally so that there are no privacy concerns?

Originally Posted by Dogway

I'm curious to know aside of a GUI what MKVToolnix has better MKV features/support than ffmpeg. To know if it's worth changing, or if ffmpeg has important issues to care about.

I'm not 100% sure, but in some cases, I think ffmpeg may delay video frame time stamps to offset the audio delay, which could mess up subtitle timing (esp. karaoke).
[Edit: I say "mess up" as a typesetter, but practically, normal people can't see the difference, even if karaoke color change for one letter is off by 41 ms.]

On the other hand, some MKV writer (ffmpeg too?) can write ebml CRCs, which MKVToolnix can't. Most MKV writers (e.g. Haali's) except MKVToolnix do not have weird rounding errors, where timestamps are not rounded correctly. MKVToolnix also does automatic update checking by default, without asking, without any privacy policy (but almost every tool does that today). So, frankly, it has a few, slightly unsatisfactory elements for me. The GUI i/f is not very intuitive, tbh.

That said, MKVToolnix has a ton of nice things. For example, the --deterministic option can be very handy for debugging in some situations. Info Tool - Element Viewer (hex dump) is extremely convenient when you're studying the inside of an MKV file. And its language code (LanguageIETF) support is nearly perfect, truly admirable. In reality, probably only a few, if any, users need/use complicated language codes, though.

For something basic, like just muxing x264 and aac, perhaps other muxers are as good as mkvmerge is. But all in all, I believe MKVToolnix is the most powerful tool to handle MKV.

[filler56789]

67.0.0.87.

[filler56789]

Originally Posted by manolito

Looks like latest version works under Win7 again?

Yes

mkvtoolnix-64-bit-68.0.0-revision-001-g6a55c58d2

[ssjkakaroto]

Originally Posted by Liisachan

First off, I was surprised to know there are so many die-hard Win7 users, as I was thinking I was one of only few weirdos who're still using Win7.
Why are you guys avoiding Win10? Privacy concerns, or some kind of compatibility problems? If it's privacy, do you think Linux (migrating to it or using it side by side) is a realistically good option?

The mentality of change for the sake of change is plaguing the whole IT world. When I bought my PC Windows 7 was fully supported, so it works perfectly with my hardware.
Security is a non-issue if you know how to get ESU updates (https://docs.microsoft.com/en-us/tro...ty-updates-faq).
Besides some programs that are forcing Windows 10 down our throats, I see no reason to upgrade from a perfectly stable system.

[filler56789]

mkvmerge v68.0.0.36.

[manolito]

Thanks for the Heads-Up...

Mosu just released Version 69.0.0 of MKVToolMix, and this version no longer works under Win7. So the version you posted seems to be the final Win7 compatible version. I did a quick test (32-bit only), and it seems to work fine.

So I updated my ToolNix Repository for ancient versions (for WinXP and Win7, 32-bit only), the link is here:
https://forum.doom9.org/showpost.php...postcount=1585


Cheers
manolito

[hubblec4]

@filler56789

Do you know if this fix is included in the last working version?

[*]mkvmerge: HEVC ES parser: the parser will now parse at least the first full access unit before reporting that it has found all the required headers. Otherwise parsing might stop in the middle of the access unit due to the source reader not providing more data in the first call, leading to the parser not finding the "unspec62" and "unspec63" NALUs required for Dolby Vision. Fixes #3363.

[filler56789]

Originally Posted by hubblec4

@filler56789

Do you know if this fix is included in the last working version?

I cannot check that because 1) I don't split MKV files and 2) I have never played /created /used HEVC streams containing Dolby-Vision, but my answer is:

VERY-UNLIKELY, because...

Moritz Bunkus @mbunkus added: fixed-in-version 69.0.0 — 1 day ago

source: https://gitlab.com/mbunkus/mkvtoolnix/-/issues/3363

[lvqcl]

Originally Posted by manolito

Mosu just released Version 69.0.0 of MKVToolMix, and this version no longer works under Win7.

It seems that it won't work on Win8/8.1 too.

[Video Dude]

Originally Posted by hubblec4

@filler56789
Do you know if this fix is included in the last working version?

The last working Win7 version is mkvtoolnix-64-bit-68.0.0-revision-036-g37903f25c

Look at the g37903f25c and find the corresponding commit on gitlab, which is 37903f25

https://gitlab.com/mbunkus/mkvtoolnix/-/commit/37903f25cf7ea2d0ddd381d8506fc0c2a30f5d2f

So yes, it appears that fix is included. In fact, it was the very last commit for Win7.

[hubblec4]

Thanks Video Dude for this info.

[filler56789]

Originally Posted by Video Dude

The last working Win7 version is mkvtoolnix-64-bit-68.0.0-revision-036-g37903f25c

Look at the g37903f25c and find the corresponding commit on gitlab, which is 37903f25

https://gitlab.com/mbunkus/mkvtoolnix/-/commit/37903f25cf7ea2d0ddd381d8506fc0c2a30f5d2f

So yes, it appears that fix is included. In fact, it was the very last commit for Win7.

Thanks for correcting me. *THUMBS UP*

Too bad no one can trust Mosu anymore.

[filler56789]

SOURCE: https://www.videohelp.com/software/MKVToolNix

Please, can you share those files ?

If you have the following 69.0.007 versions bearing the below SHA-1, they will work with Windows 7/8 and respective server version:
B5D5E22968F947558BFB100EF06D37A1FB3BC7C4 mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6-setup.exe
5F8BB12A7C9FA214E4B63BCFC4EF020E27186A4F mkvtoolnix-32-bit-69.0.0-revision-007-ga64005aa6.7z
254911C993E8685AE514A8B7FD789C200EA6E3C4 mkvtoolnix-64-bit-69.0.0-revision-007-ga64005aa6-setup.exe
86B4EEDFA42A60D74FECBE76FA55BF44A53D400A mkvtoolnix-64-bit-69.0.0-revision-007-ga64005aa6.7z

[jpsdr]

Thanks for the tips.