MKVToolNix v24.0.0 released

[kuchikirukia]

Ok, if anyone is looking for the missing EVR.DLL, MFPLAT.DLL, MF.DLL, and MFCORE.DLL needed to get mkvtoolnix working, I've uploaded them here: http://s000.tinyupload.com/?file_id=...35202073920387

[VAMET]

Dear Friends

So as far as I understand AACS 2.0 has been cracked. There is also first UHD 1:1 copy over Internet with Dolby Atmos. There is an information, that UHD has the same structure as BD. Here is an information about .m2ts file. This is a very good information for people, who would like to backup their UHD Blu-ray movie collection from physical disc to HDD. My question, will MKVToolNix be able to convert such copies to .mkv files or there is need to be update of MKVToolNix?

Thank you in advance for any help and support.

Sincerely

[sneaker_ger]

Mkvmerge can read HEVC from (m2)ts but for a definite answer someone needs to actually test it. Also, reading the playlists or just the m2ts might be different.

[hello_hello]

I wasn't expecting MKVToolNix to run on XP forever, although for it to stop working so it can go "ding"....

If MKVToolNix used PowerShell to make ding noises, there'd be no need to download additional dlls (because XP obviously isn't a good enough reason) but as a bonus it could continue working on XP too. I've never written a single line of code so I know nothing about writing software, but it only took a minute with google to work out the command line required to go "ding".

powershell -c (New-Object Media.SoundPlayer "C:\Windows\Media\ding.wav").Play(); Start-Sleep -s 5; Exit;

Mind you, I was under the impression "sounds" went out of fashion with instant messenger programs, Incredimail & Windows 98. Not that I'd know. One of the first things I do after installing Windows is disable most of the sounds. Pop up messages/windows/tooltips are far more civilised.

[sneaker_ger]

Mkvtoolnix is MultiOS. You don't have the PowerShell on Linux or Mac. It uses the Qt framework's function for sound so it works on all of them with the same code.

[hello_hello]

Fair enough, although according to the log of changes, MKVToolNix only fires up the brass band for a fanfair when shutting down Windows and Linux, so I guess it can't always work the same way. Whether Mosu wants to make changes for the Windows version so MKVToolNix doesn't require the installation of a media player to mux MKVs would be up to him. I don't know how hard it'd be, or how hard it'd be to switch back to DirectX. Aren't other operating systems devoid of WMP and Media Foundation along with Power Shell? I'm asking because I know nothing about Qt or how it works, so I don't know how the same code translates to other operating systems.

* MKVToolNix GUI: implemented several built-in actions that can be executed either on special events or once via the "watch jobs" tool. These are: playing an audio file (implemented for all operating systems); hibernating, sleeping and shutting down the computer (only implemented for Windows and for Linux systems using systems).

[Midzuki]

As I already said, the actual problem will only be solved when a sufficient quantity of XP users have pestered the QT framework developers.
Playing sounds on Windows requires only the Multimedia API.
Even Visual Basic 4 could use it

[nevcairiel]

No serious and self-respecting developer is going to listen to any​ amount of XP users. You need to accept that old OS means running old software.

[hello_hello]

Any self respecting developer would probably know around 3% of desktops connected to the internet (according to the last stats I read) still run XP. There's probably many more that don't see the internet. That's still a lot of desktops. More than any flavour of Linux. Probably more than all Linux flavours combined. Around half the number of PCs running Apple's operating system, way more than Vista, more than Windows 8, and then there's the other supported operating systems such as NetBSD that a couple of people use. That's probably why programs such as Firefox still support XP, because people still use it. In fact XP support is probably still more common than a lack of it. Aside from Handbrake, LSmash, Pale Moon and MKVToolNix, all the open source software I've been using for years still supports XP. Oh and ffmpeg.... there's someone still building XP friendly versions, but not as regularly as the normal releases. If you want to mux an MKV though....

Doesn't LAV Filters still support XP, or does MPC-HC use a modified version to make it XP friendly?

[nevcairiel]

It does, but mostly because it didn't break yet, once it does break (or present a blocker in any other way) it'll likely just not get fixed/removed. Also, since you listed Firefox, they just discontinued XP support
Such statistics are largely bogus anyway, the majority of those are work PCs that are for some reason not upgrading. The percentage of actual home users running XP willingly is extremely small.

In any case, you can just fork Open Source software and fix it yourself, don't expect developers to spend time fixing things for an OS thats over 15 years old and over 3 years unsupported, probably a gaping security hole by now.

[hello_hello]

Originally Posted by nevcairiel

Such statistics are largely bogus anyway, the majority of those are work PCs that are for some reason not upgrading. The percentage of actual home users running XP willingly is extremely small.

I tend to suspect it's the other way round. There's four PCs in this house, each used regularly, but the older two never see the internet and only one sees it regularly.

Originally Posted by nevcairiel

In any case, you can just fork Open Source software and fix it yourself, don't expect developers to spend time fixing things for an OS thats over 15 years old and over 3 years unsupported, probably a gaping security hole by now.

I'm quite fond of the "unsupported" and "security" justifications. The number of people using an OS never rates a mention. Maybe some programs with internet access could be squeezed into the "security" category, but we're muxing MKVs here.

I didn't know Firefox had dropped XP support. Not that I was planning to upgrade it in a hurry either. I'm on the last ESR release that permits installing unsigned extensions, and I was planning to ride that out. By then I'll definitely have the new PC built and hopefully be running Linux. No Windows 10 for me.

[isidroco]

Seems too much hassle for enabling "Ding" when done. I think it's a lot to loose (XP compatibility and obligation to install horrible Windows Media Player) for a useless option. It would be better to disable sound alltogether, or else enable to run an external program when done, so users can run a player if desired.

PS: Here in Argentina there we are still a lot of users with XP which runs well and security holes aren't used by virus anymore, it's easier to convince users to install anything.

[qyot27]

Originally Posted by hello_hello

Aside from Handbrake, LSmash, Pale Moon and MKVToolNix, all the open source software I've been using for years still supports XP.

There's nothing about L-SMASH that stops it from working on XP.

[hubblec4]

Hi Mosu

Is it possible to remove the Dialog-Normalization from audio streams (AC3) when MKVmerge mux directly from an m2ts-file or the mpls file?
Or is it to much work?

[hello_hello]

Originally Posted by qyot27

There's nothing about L-SMASH that stops it from working on XP.

It definitely went through an XP unfriendly stage a while back. There's even an XP specific link at the bottom of the Avisynth Lsmash page, so I figured that must be it for XP and haven't re-checked it since. Even MeGUI uses that version when running on XP. The changelog says bye bye to XP support with revision 833.

Obviously you have it working, although if you are using rev 1450 as your screenshot indicates, I can't find it. The latest version I found is r929 here and it's not working for me. I have the Microsoft Visual C++ 2015 Redistributable installed but the following error still occurs. Is there a special incantation I need to use, or a secret handshake, or a different version?

Cheers.

LoadPlugin: Unable to load "E:\LSMASHSource.dll", Proc not found. Update library version?

[qyot27]

Originally Posted by hello_hello

It definitely went through an XP unfriendly stage a while back. There's even an XP specific link at the bottom of the Avisynth Lsmash page, so I figured that must be it for XP and haven't re-checked it since. Even MeGUI uses that version when running on XP. The changelog says bye bye to XP support with revision 833.

Obviously you have it working, although if you are using rev 1450 as your screenshot indicates, I can't find it. The latest version I found is r929 here and it's not working for me. I have the Microsoft Visual C++ 2015 Redistributable installed but the following error still occurs. Is there a special incantation I need to use, or a secret handshake, or a different version?

Cheers.

LoadPlugin: Unable to load "E:\LSMASHSource.dll", Proc not found. Update library version?

That's LSMASHSource, which had the toolset in its MSVC project explicitly changed from v120_xp to v120 (before moving up again to v140). L-SMASH itself has no restrictions like that: nothing in its configure script does it, and its MSVC project still uses v120_xp. LSMASHSource doesn't have the option of being built with MinGW, since it's not a C-plugin, but unless there's something deeper in the code, all it would take is overriding the default when you open it up in Visual Studio and forcing the use of the XP toolset before building it like usual.

But I'd rather not continue derailing the MKVToolNix thread about this.

[Mosu]

To make it perfectly clear: I'm not going to spend any time on XP-related problems. There's zero chance you'll change my mind. That means the code I'm using will stay as it is. If you (the general "you", not anyone in particular) want to continue using XP, that's your prerogative. Mine is not spending any time on it.

Now can we please stop the whole XP discussion? Thanks.

[Mosu]

Originally Posted by hubblec4

Is it possible to remove the Dialog-Normalization from audio streams (AC3) when MKVmerge mux directly from an m2ts-file or the mpls file?
Or is it to much work?

At the moment mkvmerge has no code whatsoever for removal of dialog normalization. I don't have any plans of implementing such a feature either. Maybe sometime in the future, though — I'm not ruling it out (unlike XP support, for example). If you want to improve the chances of that happening, I'd ask you to open an issue over on Github for it. Otherwise I will almost certainly forget about it again.

[hello_hello]

Originally Posted by Mosu

To make it perfectly clear: I'm not going to spend any time on XP-related problems. There's zero chance you'll change my mind. That means the code I'm using will stay as it is. If you (the general "you", not anyone in particular) want to continue using XP, that's your prerogative. Mine is not spending any time on it.

I don't think anyone considered the possibility that happening, only discussing if it'd be a reasonable idea.

Originally Posted by Mosu

Now can we please stop the whole XP discussion? Thanks.

It had pretty much come to a close already.
Aside from XP though, several posters expressed concern over having to download additional WMP dlls, so would you consider changing things to remove that need.... if it can be done without unwanted side effects such as restoring XP compatibility?

No offence, because your work on MKVTYoolNix is definitely appreciated, but I can imagine potential users downloading the program, seeing an error message when they try to run it, and uninstalling. I've done the same thing over the years if I didn't have my heart set on using a program and it wasn't keen to run.

If an error tells me in plain English how to fix the problem I'll usually give it a try, unless it's instructing me to install itunes or upgrade WMP, but even a missing dll error would have me contemplating if I really want to use a program. I suspect many people will skip the contemplation step and go straight to posting about what a piece of crap MKVToolNix is in a forum or two while they uninstall it.

Was there a big demand for a muxing program that goes "ding"? I suspect the number of "sound advocates" would be very low compared to the number of people using errrr....XP....... I mean.... compared to the number of Windows7/10 users that won't get past the installation stage, albeit for a perfectly legitimate and unrelated to XP reason.

Don't mention XP. I mentioned it once, but I think I got away with it.

[Mosu]

No, I'm not changing frameworks/the methods for sound playback. I'm using what my GUI toolkit of choice is offering regarding cross-platform multimedia playback because that's the most sane, most foolproof, least painful, most debugged method of doing such things in a cross-platform way.

I've set up an FAQ entry for that already. If people uninstall the program without searching for the solution, then that's their loss, not really mine, as I'm not trying to make money of this thing called MKVToolNix anyway.

Was there a big demand for a muxing program that goes "ding"?

Playing a sound when muxing finishes has been requested by users time and again.

I've actually typed up quite a long answer listing all the possible choices you have, why I do or do not do certain things, why my choices are the way they are, but all that boiled down to being angry and venting. That's not productive. Therefore I've snipped it.

So my summary is:

I'm satisfied with the system requirements MKVToolNix v11.0.0 has, which is: Windows 7 or newer with the Media Foundation framework.

Edit: fixed requirements