NON-OFFICIAL Windows-builds of MKVtoolnix.

[aedipuss]

64 bit shows v94.0 here also

[El Heggunte]

Resource Hacker also says "version = 94" 🤔

1 VERSIONINFO
FILEVERSION 94,0,0,0
PRODUCTVERSION 94,0,0,0
FILEOS 0x4
FILETYPE 0x0
{
BLOCK "StringFileInfo"
{
	BLOCK "040904B0"
	{
		VALUE "CompanyName", "Moritz Bunkus"
		VALUE "FileDescription", "mkvtoolnix-gui"
		VALUE "FileVersion", "94.0"
		VALUE "InternalName", "mkvtoolnix-gui"
		VALUE "LegalCopyright", "Released under the GNU Pulic License http://www.gnu.org/licenses/gpl-2.0.html"
		VALUE "OriginalFilename", "mkvtoolnix-gui"
		VALUE "ProductName", "MKVToolNix"
		VALUE "ProductVersion", "94.0"
	}
}

BLOCK "VarFileInfo"
{
	VALUE "Translation", 0x0409 0x04E4  
}
}

[tebasuna51]

In the window title remain v90.0

Is it possible that you didn't overwrite a previous version and are in fact launching that version?
I tested the builds here and they show v94.0.

My fault sorry, it was a link to the last official version than work in my W10.

[jpsdr]

Here is release version 94.0.

Note:
Reverted this commit related to this issue/request.
It uses QStrings new to qt6 and breaks compilation with qt5.

Ah... I'll try this... I didn't underdstood why the "rake" just stopped without telling why... I didn't find any error message...

[jpsdr]

@autodidact
I tried to build the .33 version, it failed. I removed the 2 "date" stuff commits, thinking they broke QT5 (like the commit you removed in previous build), but it's still failing.
If you're able to build last version, i'm interested in the changes you've made.

[autodidact]

@jpsdr
It is the qtmp4 commit which is requiring c++20, a feature which we have reverted previously:
https://codeberg.org/mbunkus/mkvtoolnix/commit/774cc1d06d6157347925df27e1c145a3616e9b5c

If you add back the c++20 support and add this to src/input/r_qtmp4.cpp:

#include <QtCore>

it will fix that problem then you get the problem we had in the first place using C++20 with qt5.
I compiled manually to work around that problem for now.

Or you can revert the above commit.

[autodidact]

Here is release version 95.0.

Qt6 version is here.

[El Heggunte]

Arigatôu gozaimasu ^__^

[manolito]

Thanks autodidact for the new version...

Did my usual torture testing with the 32bit version, no problems.


Cheers
manolito

[KewlioShades]

Thanks autodidact.

Tested 32/64Bit and both are working.

[jpsdr]

@autodidact
It seems the qtmp4 commit created some others issues, there has been a new commit, and after i've been able to build again the QT5 version.
Anyway, again thanks for what you're doing.

[fits79]

@autodidact
Is there any chance to create a guide step by step how to make the latest mkvtoolnix version win7 compatible?
So we can do it our selfs.

[jpsdr]

@fits79
Maybe you can check what i've done on my github.
MKVToolnix, with 2 branches, one for QT5, one for the QT6 Windows 7 compatible.
https://github.com/jpsdr/MKVToolnix-Windows-7
The MXE, used by MKVToolnix, it builds all the QT stuff and things which are used to make MKVToolnix.
2 branches also, QT5 and QT6 Windows 7.
https://github.com/jpsdr/mxe-Windows-7
And the QT6 for Windows 7, with an MKVToolnix specific branch.
https://github.com/jpsdr/QT6_Windows7

But, it's not easy. Unless you have knowledge on linux compiling tricks, QT programming, QT compiling,etc... you'll be like me coming back here with one’s tail between one’s legs asking for help (because i don't have these knowledge) each time something broke.
At each pull request made by Mousu, I cross finger that it didn't break things, and build will go smoothly...

[Brazil]

Qt6 version is here.

Any advantages to use the Qt6 version rather than the Qt5 one ?

[autodidact]

Any advantages to use the Qt6 version rather than the Qt5 one ?

Take a look at the notes for release 94.0.

A feature to remove both the .sub and .idx files after multiplexing was reverted in the qt5 version as it uses qt6 specific code.
The original functionality remains in the qt5 version where only the .sub gets deleted if delete source for multiplexer jobs is enabled.

The qt6 version is more likely to remain full-featured while the qt5 version will possibly lose and/or omit features over time.

[fits79]

@fits79
Maybe you can check what i've done on my github.
MKVToolnix, with 2 branches, one for QT5, one for the QT6 Windows 7 compatible.
https://github.com/jpsdr/MKVToolnix-Windows-7
The MXE, used by MKVToolnix, it builds all the QT stuff and things which are used to make MKVToolnix.
2 branches also, QT5 and QT6 Windows 7.
https://github.com/jpsdr/mxe-Windows-7
And the QT6 for Windows 7, with an MKVToolnix specific branch.
https://github.com/jpsdr/QT6_Windows7

But, it's not easy. Unless you have knowledge on linux compiling tricks, QT programming, QT compiling,etc... you'll be like me coming back here with one’s tail between one’s legs asking for help (because i don't have these knowledge) each time something broke.
At each pull request made by Mousu, I cross finger that it didn't break things, and build will go smoothly...

I don't understand anything at all.
Maybe cause i don't have any knowledge about linux.
So isn't there an easy way or guide to make latest mkvtoolnix versions compatible with win7?

[jpsdr]

I'm affraid not.
And first of all, the building process is under Linux, even if the final result is a Windows executable.

[Brazil]

A feature to remove both the .sub and .idx files after multiplexing was reverted in the qt5 version as it uses qt6 specific code.
The original functionality remains in the qt5 version where only the .sub gets deleted if delete source for multiplexer jobs is enabled.

Not a big deal for me.

The qt6 version is more likely to remain full-featured while the qt5 version will possibly lose and/or omit features over time.

OK, thanks for the info