MKVToolNix v83.0 released

[manolito]

Originally Posted by Mosu

I simply don't support such low resolutions.

I hope you don't mind if I call this attitiude "ARROGANT". Not everyone is in the situation to be able to afford a state of the art computer, graphics card and monitor like you.

[kuchikirukia]

Originally Posted by Mosu

Thanks for the suggestions. I won't implement any of them as they aren't going in a direction I want to take the GUI in. I simply don't support such low resolutions.

Resolution doesn't really do anything since nearly everybody scales their UI up to make it visible. My phone is 1080p and its screen is completely full from top to bottom with 20 icons. My desktop, on the other hand, can fit 50 icons on the taskbar and still have 1920x1050 area left over. It's screen size that gives real estate and most people aren't running something like this:



The GUI would fit nicely in around 5% of that screen. But for the majority of us it takes up a third of our screens.

[Perenista]

What is going on?

First this https://forum.doom9.org/showpost.php...&postcount=370

Now this, with the MKVExtractGUI2.exe:

[Mosu]

MKVExtractGUI2.exe is not part of MKVToolNix. It's a third-party application.

[Mosu]

Originally Posted by manolito

I hope you don't mind if I call this attitiude "ARROGANT".

I very much mind. It isn't arrogant, it is necessary and normal. Every software developer out there places certain restrictions on what they support in their software, be it operating systems & their versions, the hardware (virtual or physical) its run on, or even the time of day it is run. It's simple logistics: every development team out there has a limited set of resources, both regarding money (in order to buy all the different equipment they have to support) and time (implementing stuff & hunting bugs takes a lot of time). Both of those resources are finite; hence decisions are made with respect to what a useful subset of all the requirements are that they can support with their current level of resources so that the most number of people benefit from it. It's always a trade-off.

MKVToolNix is basically a one-person project regarding coding — me. My time is very finite, and I have to chose carefully where to spend my time. And I've been spending my time on this fine piece of software that I offer you completely free of charge, free of any type of commitment, and I've been doing that for more than 15 years now. I've been gifting you countless hours of my time, no small amount of my wit, and you even get the whole source code to do with as you please.

And still you have the gall to call me arrogant when I decline to spend more of my free time on this piece of software, for which I'm not compensated, which I couldn't make a living off even if I wanted to, which solely benefits persons other than myself? Really? Statements such as yours are _the_ reason I and other open source software developers & maintainers often burn out.

All of this over an enhancement request? Really? It wasn't that the software didn't work form them; no, they simply didn't want to spend heir time scrolling in order to push buttons. But you expect me to spend my time improving your life. Don't get me wrong, it's 100% fine to ask about such a feature. That isn't arrogant. But not accepting me declining to do something for you for free? That is.

Apart from all of that: I wasn't kidding when I said that the suggestions lead in a direction I didn't want to take the GUI in. For example, I don't like using abbreviations all over the place. Abbreviations that may be obvious to you often aren't to other users. Placing buttons in the task bar is something I honestly haven't ever seen any program do — as a first-time user I would be very confused about them; even more so as those buttons only apply to the multiplexer tool whereas the whole status bar applies to all tools.

I simply don't consider those suggestions to be good, I don't consider them to be significantly helpful to a significant number of people, and I consider them to be detrimental or confusing to others. Not a good combination.

[LeMoi]

Originally Posted by Mosu

Thanks for the suggestions. I won't implement any of them as they aren't going in a direction I want to take the GUI in. I simply don't support such low resolutions.

Thanks

[lvqcl]

This reminds me of some discussions such as this and this.
To quote a reddit user frome that thread:

Wow reading the comments there are a lot of people who feel entitled to someone else's time and work.

@Mosu: just disregard them.

Originally Posted by Mosu

Placing buttons in the task bar is something I honestly haven't ever seen any program do — as a first-time user I would be very confused about them; even more so as those buttons only apply to the multiplexer tool whereas the whole status bar applies to all tools.

+1.

[manolito]

Originally Posted by Mosu

I very much mind. It isn't arrogant, it is necessary and normal.

Sorry, I did not intend to insult you. All your points about providing free software are valid, and I am very grateful for software like MKVToolNix. And of course it is your baby, you are free to take it into any direction you want.

To make my view clear, I am a strong believer in sustainabilty, I believe that repairing hardware is better than throwing it into the trash bin. I believe that noone needs a new smartphone every year, and the same is true for computers and TVs and cars and whatever...

So remarks like "I simply will not support such low resolutions" or "I will not support such ancient OS like Win XP" do offend me. Apple was the company who introduced this attitude a long time ago, and this is the reason why I do not own any Apple products. Will your next move be to drop 32-bit support?

The problem with MKVToolNix is that over the years it has become a de-facto standard for dealing with MKV files. A lot of other software relies on it, and this "monopoly" is well earned (some MKV related things can be done with FFmpeg, but it is no match to MKVToolNix). But I believe that such a monopoly brings some obligations, even for free software.

So I do thank you very much for providing such a great tool like MKVToolNix, but I still wish that you would consider supporting users with older hardware or Operating Systems.


Cheers
manolito

[kuchikirukia]

Could we get an options page for changing keybinds? Resizing hiding the buttons wouldn't matter if I could just bind "mux" to mouse3 instead of CTRL-R.

[Mosu]

Originally Posted by kuchikirukia

Could we get an options page for changing keybinds? Resizing hiding the buttons wouldn't matter if I could just bind "mux" to mouse3 instead of CTRL-R.

I have no intentions of implementing configurable key bindings. I would accept patches that implement this (= I'm not against such functionality, I just won't spend time on it myself).

[Dulus_No]

Something's wrong with kerning on v29.0.0: http://www.framecompare.com/image-co...rison/W67WNNNX
OS is Windows 8 x64, font is Segoe UI.
System information: https://pastebin.com/h4e0RECr

[mkver]

Same here on Win 7 x64. I only noticed it after reading your post. Using the continuous builds it seems that the commits from November 4th are to be blamed (or maybe it is an update to the other components that happened at the same time): g4fc889a6f works well, ge8342d4d9 does not. Disabling High DPI scaling seems to not affect this.

[Mosu]

I regularly update all the libraries I use for building MKVToolNix at the start of the month. The result is probably due to a newer version of one of the libraries involved in font rendering (Qt, freetype, pango, harfbuzz…). It's something you'll have to live with for the time being.

Edit: MKVToolNix doesn't mess with font settings apart from the most basic information. All it does is set the font's family name and its point size. The rest is up to the aforementioned libraries.

[varekai]

@kuchikirukia

It's screen size that gives real estate and most people aren't running something like this:

That picture is so cool, it's a keeper! Thansk!

[nautilus7]

Kerning with windows 10 is ok.

[Anakunda]

Originally Posted by mkver

The --no-chapters option is actually an input file option, not an output file option, i.e. it discards chapters already in your input file, but leaves chapters that you explicitly add during the muxing process (e.g. by using a chapters file) alone. In this case this means that any chapters in your w64 file (there aren't any and I don't believe that w64 is able to contain chapters anyway) would be discarded.
I'll open an issue for the real problem (that PCM is not split sample-accurately, but only block-accurately), but I don't think that he will fix this. After all, this just affects PCM.

I'm only curious if the issue was already fixed in latest version. No mention in change logs. Are the dev at least aware of the oddness?

[Mosu]

I am aware of it, but I'm not willing to spend time on it.

[hello_hello]

Originally Posted by kuchikirukia

I have some UI suggestions that might improve the usability of the GUI.

The SendTo folder should be your best friend. If you use a program regularly, there should be a shortcut for it in the SendTo folder (especially if there's no other Explorer menus). Mostly, have have to create them yourself though. I'm on XP, but my SendTo folder is almost a mini start menu (it contains sub-folders for less up/down scrolling, so many of the shortcuts can't be seen in the screenshot below).



And.... there's much better file management programs than Explorer, and some are free. The "Lite" version is free.
https://www.zabkat.com/alldown.htm

[Selur]

Hi!
Got a file created with VideoReDo which contains S_DVBSUB subtitles.
Trying to extract the subtitles using:

"I:\Hybrid\64bit\mkvextract.exe" tracks "C:\Users\Selur\Desktop\Beispiel_DVB_SUBS.mkv" 3:"E:\Output\Beispiel_id_3_lang_de"

I get:

Error: Extraction of track ID 3 with the CodecID 'S_DVBSUB' is not supported.

Is there a trick to extractin/handling those subtitles? Or is this a missing feature? (only saw support for S_DVBSUB in mkvmerge mentioned in the changelog)

Cu Selur

[mkver]

There is no defined "raw" format for DVB subtitles; only the packetization inside transport streams (as PES packets) and inside Matroska is defined. Therefore you can't really extract these subtitles, because there is no format to extract them to. (One could of course create such a format. One could e.g. declare the stream of PES packets to be the raw format, similar to vobsubs. But the difference to vobsubs is that the latter is an established format, whereas the former would be a new creation by MKVToolNix. And why create such a format? It makes no sense. If you want to keep only the DVB subtitles inside a Matroska file, simply remux the file with only the DVB subtitles selected.)