NON-OFFICIAL Windows-builds of MKVtoolnix.

[El Heggunte]

Here is release version 76.0.

Note:

The latest code has introduced Qt5 incompatibility. Specifically this commit which uses Qt 6.5.0 to support dark mode functionality on Windows 11.
https://gitlab.com/mbunkus/mkvtoolnix/-/commit/611c900b2dd8f8e7ca9f800ae9fac37b78be887dL
Qt5 does not recognize the references to Windows 11 and as a result the GUI fails to compile. The CLI programs are not affected. This release has that commit reversed. All other features and fixes are up to date.

1) :goodpost: and THANKS! (again)

2) surely it is time for someone (not yourself, evidently) to create a NON-qt mkvtoolnix GUI for Windows...

the dot-NET fanboys should accept the challenge

But if the non-official GUI was written in Java 😈, it could be used by the Linux & Mac OS minorities as well 😏 😇

[manolito]

Thanks autodidact for the prompt delivery...

Tested the 32-bit version under Win7 on a Lenovo T530 notebook, it works fine, but the new qt version is a real step backwards. The settings window is hardly scalable vertically, the position sliders are poorly visible, overall it looks much worse than the previous version. This is nothing anyone can blame autodidact for, but the constant quest for newer and better is really backfiring here. After some serious testing I went back to the previous version 75.0.


I think that Mosu did a sloppy job with this release, hoping for future releases...

Cheers
manolito

[autodidact]

I reversed one commit that was preventing compilation but it looks like this earlier commit began the transition to more fully rely on Qt6 for GUI cosmetics on Windows.

https://gitlab.com/mbunkus/mkvtoolnix/-/commit/7f2e0378d855541f09d44cbfd2f97d2349b9cf18

That includes changing the style from "Windows Vista" to Qt's "Fusion" style. I don't think Mosu is concerned about how this affects Qt5 builds or behavior on Windows 7, unfortunately. It certainly lends weight to El Heggunte's argument.

[Ennio]

Here is release version 76.0

A bit late but again many thanks @autodidact

[r0lZ]

autodidact, can you please add or modify something in the version string to differentiate it from the one of the official release ? I would like to be able to check if a valid version for the current OS is installed from my program BD3D2MK3D, and currently, there is no easy way to do it. Thanks.

[El Heggunte]

autodidact, can you please add or modify something in the version string to differentiate it from the one of the official release ?
I would like to be able to check if a valid version for the current OS is installed from my program BD3D2MK3D, and currently, there is no easy way to do it.
Thanks.

Not sure if this is useful , but...

menu Help --> System information --> Qt

Non-official build says: "Version: 5.15.8".

[autodidact]

autodidact, can you please add or modify something in the version string to differentiate it from the one of the official release ? I would like to be able to check if a valid version for the current OS is installed from my program BD3D2MK3D, and currently, there is no easy way to do it. Thanks.

The Qt version would be the ideal way to differentiate between official and non-official. Depending on how you are comparing, that information may not be readily accessible. Adding NON-OFFICIAL to the version name could be a simple solution and doesn't trigger mismatch version warnings from the GUI:

>mkvmerge.exe -V
mkvmerge v76.0.34 ('Celebration NON-OFFICIAL') 64-bit

If no objections are raised and if no better suggestion is offered, this could be implemented.

[r0lZ]

@autodidact: It's OK for me. Thanks !

@El Heggunte: Thanks for your suggestion, but I need to check the version from the command line. autodidact's modification will be perfect.

[El Heggunte]

@autodidact: It's OK for me. Thanks !

@El Heggunte: Thanks for your suggestion, but I need to check the version from the command line.

I DID NOT say and I DID NOT mean you should use mkvtoolnix-gui for checking which version of Qt was used by the compiler.⬇️

The Qt version would be the ideal way to differentiate between official and non-official.

The problem of course is, professional computer programming REALLY makes people somewhat narrow-minded, sadly.😔

[El Heggunte]

........
I think that Mosu did a sloppy job with this release, hoping for future releases...

Well, if anyone still had any doubts about Mosu becoming less of a Matroska developer and much-more of a Qt poster boy...

https://gitlab.com/mbunkus/mkvtoolnix/-/wikis/Dark-mode-issues

[autodidact]

Here is release version 77.0.

Notes:

Added 'NON-OFFICIAL' to the version name.

Changed the "Fusion" style back to the "windowsvista" style. The Dark Color Palette in Preferences will not work properly in this case. The executable from the alternative_GUI archive is built with the "Fusion" style and the Dark Color Palette works with it. This should be a one-time arrangement to determine the preferred style for next release.

The author has moved a qt_resources file out of the mkvtoolnix-gui executable and into the data folder. If you selectively extract from the release archive and intend to use the GUI, please make sure to select the data folder.

[manolito]

Thanks Autodidact for this new version...

Works nicely, and the old Windows style looks SO much nicer than the latest and greatest "Fusion" style. Tested a couple of conversions (32-bit only), as usual they came out perfectly...


Cheers
manolito

[jpsdr]

Thanks for putting back the old style.

[Ennio]

Thanks @autodidact for the new builds

[LouieChuckyMerry]

I just discovered this thread and wanted to thank autodidact for doing this. Thank you! Jumping from v68 to v77 makes my week.