NON-OFFICIAL Windows-builds of MKVtoolnix.

[autodidact]

Yikes! I didn't sanitize the files. I shouldn't post at 3AM.
I adjusted the instructions above.

Are you asking if the patches should have already addressed the issue? We are having to make a Windows 7 version of qt6 possible.

[jpsdr]

What i meant is that what there is at https://github.com/crystalidea/qt6windows7.git is supposed to provide a Windows 7 compatible QT6, and they have provided a supposed 6.8.1 Windows 7 compatible version code.
So, i was just surprised when you said the issue is that there is some code not Windows 7 compatible.

[autodidact]

What i meant is that what there is at https://github.com/crystalidea/qt6windows7.git is supposed to provide a Windows 7 compatible QT6, and they have provided a supposed 6.8.1 Windows 7 compatible version code.
So, i was just surprised when you said the issue is that there is some code not Windows 7 compatible.

Yes, and I was surprised when I saw how mkvtoolnix behaved when built with the latest patches.
Looking at the code I don't think it necessarily needs to be patched since support for older Windows is still there.
It also seems likely that the problem didn't exhibit to the patch maintainers, though I see someone has made them aware of it with 6.8.0 and it is labeled as a bug.
https://github.com/crystalidea/qt6windows7/issues/26

The use of directwrite and which version is based on testing during building and in our cross-compiling environment it finds support
for the latest version so doesn't use the fallback. So we configure the build for our needs.

[jpsdr]

According the issue, it seems specific to Windows 8.1, and working properly under Windows 7, also, a fix was just commited.
When you said that mkvtoolnix wasn't working properly, it was under Windows 7 ?
Didn't have time yet to continue testing build...

[autodidact]

Tested on Windows 7 and 8.1, it malfunctioned on both.

This open issue is from Windows 7 and shows what I saw on Windows 7.
https://github.com/crystalidea/qt6windows7/issues/32

On Windows 8.1 it was a blank interface, no text.

[autodidact]

Here is release version 90.0.

[LouieChuckyMerry]

As always, thank you, autodidact; I truly appreciate your effort.

[Ennio]

Thanks @autodidact for the latest version

[El Heggunte]

🚀

[KewlioShades]

Thanks, autodidact, appreciate your work.

[tebasuna51]

Thanks for that version, seems needed also for old W10 versions

[autodidact]

Thanks for that version, seems needed also for old W10 versions

Interesting. The screenshot shows exactly what I saw when I first started testing qt 6.8.1 on Windows 7.

The default font rendering in qt 6.8.x is using very recent directwrite3 features which I guess haven't been added to early Windows 10 versions. Looks like Mosu may have to make changes to his list of supported versions?

Just to note, the qt6 version in post #177 should also work directly on your version of Windows.

[autodidact]

From what I can tell the code changes in this commit from a year ago started showing up in release 6.8.0:
https://github.com/qt/qtbase/commit/0916415ef7e909b7347c790c509280ae524482b7

One example is the change from IDWriteFactory3 to IDWriteFactory6.
Microsoft documentation says IDWriteFactory6 requires a minimum of Windows 10 Build 16299:
https://learn.microsoft.com/en-us/windows/win32/api/dwrite_3/nn-dwrite_3-idwritefactory6

[tebasuna51]

Thanks, both versions (QT5 and QT6-MOD) work fine in W10 Version 1607 Build 14393 2016-08-02

[Baldrick]

Thanks, both versions (QT5 and QT6-MOD) work fine in W10 Version 1607 Build 14393 2016-08-02

THanks for the information! I have updated the download other versions with that information, https://www.videohelp.com/software/MKVToolNix#download