NON-OFFICIAL Windows-builds of MKVtoolnix.

[Ennio]

Thanks for the latest version.

[EDIT] Just downloaded the package and running mkvtoolnix-gui.exe.
How can it be that my preferences are already exactly like I set them in the installed version. Being a portable, does it "peek" somewhere?

Unless you manually create a text-file named "mkvtoolnix-gui.INI", the program will look for its settings in Windows's Registry.

Updating to latest version 70.0.0 caused losing all Preference settings. I noticed a mkvtoolnix-gui.ini file was auto-added in the installation folder at first time use.
I suppose the new Win7 builds will not look for its settings in Windows's Registry anymore and I will have to keep that ini file?

[El Heggunte]

Updating to latest version 70.0.0 caused losing all Preference settings. I noticed a mkvtoolnix-gui.ini file was auto-added in the installation folder at first time use.
I suppose the new Win7 builds will not look for its settings in Windows's Registry anymore and I will have to keep that ini file?

Not sure whether there really is something new about the preferences and the .INI file...
I only know that it's better ALWAYS use the MKVtoolnix archive(s) and NEVER use the installer...
And before doing the manual upgrades, I always copy the .INI file to a backup-folder inside the MKVtoolnix directory,
just in case something wrong happens.

[autodidact]

The main settings store is %USERPROFILE%\AppData\Local\bunkus.org\mkvtoolnix-gui\mkvtoolnix-gui.ini and has user read/write permissions. That is probably where your previous settings are. If there is an .ini next to the executable, it probably preferentially reads from that file.

[fits79]

So for us still using win7 what we must do so the latest version of this program still work at win7?
From where we must download any new version of the program?

[autodidact]

So for us still using win7 what we must do so the latest version of this program still work at win7?
From where we must download any new version of the program?

The author of the program has chosen to drop support for older Windows versions. I am a user of such versions so it seems to me like there are three choices:

1. Continue to use the last official version from the author that works on your preferred operating system.
2. Compile the author's code yourself with parameters that maintain compatibility with your preferred operating system.
3. Make use of the download options presented in this thread which have already been compiled for use on your preferred operating system.

[fits79]

The 2nd choice is easy?

If it doesn't I follow the third

[Ennio]

The main settings store is %USERPROFILE%\AppData\Local\bunkus.org\mkvtoolnix-gui\mkvtoolnix-gui.ini and has user read/write permissions. That is probably where your previous settings are. If there is an .ini next to the executable, it probably preferentially reads from that file.

Indeed, this one holds my previous settings. Why it wasn't read and loaded at first start-up, is probably because I used the installer to update. Which - according to El Heggunte - isn't the best way.

Anyways, I copied the file next to the exe and my settings are back again. Will keep a back-up for future issues.

Thanks, guys.

[El Heggunte]

The main settings store is %USERPROFILE%\AppData\Local\bunkus.org\mkvtoolnix-gui\mkvtoolnix-gui.ini and has user read/write permissions. That is probably where your previous settings are. If there is an .ini next to the executable, it probably preferentially reads from that file.

Thanks for informing the uninfomed.

Mosu implemented the ".INI file" option for Windows some years ago because I pestered him 😇
So I thought that the default behavior of storing the settings in the Registry had not been discarded, just like MPC-HC and MPC-BE do.
Now it's evident that I was wrong. 😳

[autodidact]

The 2nd choice is easy?

I think you will have to make that determination for yourself.

[autodidact]

Mosu implemented the ".INI file" option for Windows some years ago because I pestered him 😇

Thanks for doing that! I happen to like that feature.

[autodidact]

Here is release version 71.0.0.

[manolito]

Thanks autodidact for prompt service, much appreciated...

Just noticed that Mosu made some last minute updateds after the initial release. Are those updates already part of your release?

Thanks again...
Manolito

[autodidact]

Hi Manolito.

Unfortunately the post 71.0.0 commits are not in the release I uploaded. If there is a general need/want for those recent commits I will make new compiles and modify the original post. Hopefully there will be some additional feedback on the matter that will help guide my decision.

[manolito]

Thanks autodidact for the prompt reply

personally I do not think that I need this update, I leave this to other users.

Cheers
manolito

[Ennio]

Here is release version 71.0.0.

Awesome! Thanks for this quick release, autodidact

[hubblec4]

many thanks autodidact!

[El Heggunte]

First of all, many thanks for the new build.

Secondly:

Hi Manolito.

Unfortunately the post 71.0.0 commits are not in the release I uploaded. If there is a general need/want for those recent commits I will make new compiles and modify the original post. Hopefully there will be some additional feedback on the matter that will help guide my decision.

IMHO we all can wait until Mosu releases version 72.
Below is a copy of his post @ Doom9 regarding the latest and minor ""fixes"" for the version 71 series:

Heyo.

I've just released a new minor update, v71.1.
It solely fixes the "configure" script not having the correct requirements wrt. to libEBML & libMatroska.
It also fixes several issues in the XML DTDs, but those aren't actually used in MKVToolNix itself.
Functionality wise v71.1 is the same as v71.0.
If you aren't a Linux package maintainer, feel free to skip this release.

<!-- SNIP -->

Here are the NEWS since the previous release:

Version 71.1.0 "Fortitude" 2022-10-09
Bug fixes

    Chapters DTD: added the new edition & chapter elements from Matroska v5.
    Chapters DTD: fixed EditionUID being mandatory. mkvmerge can auto-generate it if it's missing from the XML file.
    Chapters DTD: fixed the "example-chapters-1.xml" not validating against the DTD.
    Chapters DTD: corrected the old name "EditionManaged" to "EditionFlagOrdered".
    Chapters DTD: fixed "ChapLanguageIETF" missing its element declaration & "ChapterLanguage" being required.
    XML DTDs: fixed elements representing binary data not allowing the "format" attribute.

Build system changes

    bug fix: configure accidentally tested for libEBML ≥ 2.0.0 & libMatroska ≥ 2.0.0,
even though the actual requirements are 1.4.4 & 1.7.1 respectively.

[autodidact]

Okay, we'll let the 71 release stand as-is.

Thank you all for your responses!

[fits79]

Here is release version 71.0.0.

Is there an easy way to make compatible with win7 the latest version of mkvtoolnix?


And why the creator of this program stop support win7?

[autodidact]

Is there an easy way to make compatible with win7 the latest version of mkvtoolnix?


And why the creator of this program stop support win7?

The answers to your questions have been covered in this thread already. Maybe I am misunderstanding your questions?

The author of mkvtoolnix uses qt to develop the software and recently moved from version 5 which is compatible with Windows 7, to version 6 which is not.
The ONLY way to make the latest versions compatible with Windows 7 is to compile the code yourself with version 5. At least as long as the rest of the code base remains compatible.

As for why, only the author can answer fundamentally. Technically it is because the latest qt version becomes the focal point of development and concern for compatibility with legacy operating systems is non-existent.

[fits79]

The procedure to make the latest mkvtoolnix version compatible with win7 is it hard?
Can you teach us so we can do this on my owns?

[autodidact]

The procedure to make the latest mkvtoolnix version compatible with win7 is it hard?
Can you teach us so we can do this on my owns?

You may not find it hard if you have:
1. Some general experience with compiling code.
2. Access to, and familiarity with Linux.

Get started by installing the necessary dependencies in your Linux build environment. Dependencies listed here:
https://gitlab.com/mbunkus/mkvtoolnix#2-installation

Then follow the specific instructions for the Windows build, which can be found here:
https://gitlab.com/mbunkus/mkvtoolnix/-/blob/main/Building.for.Windows.md

This is the same procedure used by the official release except you have control over which qt version is used during compilation.

[fits79]

Unfortunatelly i don't any knowledge about compiling code any knowledge at all.
Isn't there any automatic procedure to do and make the latest version of mkvtoolnix win7 compatible??????
And i don't have linux to only win7.


And if isn't there any easy way to make my own any latest mkvtoolnix win7 compatible is there any site/link that i can download the latest mkvtoolnix version win7 compatible compiled?

[autodidact]

There is no automatic procedure.

There are several builds posted in this thread that have been compiled for compatibility with Windows 7 that you can download.
How latest do you require? Post #71 above has version 71.0.0. Click on one of the attached files to download.

If you have other requirements than what has been provided you can certainly make a request.

[fits79]

The latest version is 71.1.0

So there isn't any site I can download the latest version every time that it is compatible with win7???

[autodidact]

I don't know of any other site that has Windows 7 compatible builds.

[fits79]

If you know or find any site that has released any new version of mkvtoolnix compatible with win.Please inform us

[autodidact]

Here is release version 72.0.0.

[manolito]

Thanks very much for the prompt update, much appreciated

Cheers
manolito

[Ennio]

Here is release version 72.0.0.

Awesome. Thanks @autodidact