MKVToolNix v8.1.0 released


I’ve released MKVToolNix v8.1.0 just eight days after 8.0.0. It incorporates a big amount of feedback on the new MKVToolNix GUI from users. Major bugs have been squashed, many usability enhancements have been implemented and even a couple of new features were added. If you’re using 8.0.0 I urge you to upgrade.

As this release comes so quickly after the last one I have also decided to keep the old GUI around until at least 8.3.0 (the prior plan was to drop it after 8.2.0).

Changes for package maintainers: nothing’s changed since v8.0.0.

You can download the source code or one of the binaries.

Here’s the full ChangeLog since the previous release:

  • 2015-06-27 Moritz Bunkus <>
    • Released v8.1.0.
    • mmg: bug fix: fixed handling of the characters [ and ] in container and track properties.
    • MKVToolNix GUI: merge tool enhancement: moved the »output file name« controls below the three tabs so they’re always visible. Also added an option in the preferences to move them back inside the »output« tab. Implements #1266.
  • 2015-06-26 Moritz Bunkus <>
    • MKVToolNix GUI: new chapter editor feature: added a function for generating a certain number of evenly spaced sub-chapter. Implements #1291.
    • MKVToolNix GUI: merge tool bug fix: fixed various menu entries not working correctly after closing a tab or switching to another one. Fixes #1301.
  • 2015-06-25 Moritz Bunkus <>
    • MKVToolNix GUI: new chapter editor feature: implemented loading chapter entries from Blu-ray playlists.
    • MKVToolNix GUI: job queue enhancement: added menu entries for acknowledging both warnings and errors at the same time.
  • 2015-06-24 Moritz Bunkus <>
    • MKVToolNix GUI: merge tool bug fix: if »automatically set the file title« is enabled then the title field will be cleared after all source files have been removed.
    • MKVToolNix GUI: new watch jobs tool feature: the first tab showing the output of the current job has been changed to show the output of all jobs that have been run since the GUI’s been started. This can be turned off in the preferences so that only the output of the currently running job is shown again. Implements #1263.
    • MKVToolNix GUI: merge tool bug fix: fixed a crash when enabling/disabling chapters coming from an appended file. Fixes #1293.
    • MKVToolNix GUI: new merge tool feature: added an option to set a directory relative to the first input file as the default output directory. Implements #1261.
    • MKVToolNix GUI: merge tool bug fix: it was possible to set the »default track flag« to »yes« for multiple tracks of the same type. Fixes #1289.
    • MKVToolNix GUI: enhancement: the »open file« dialogs for the chapter and header editor tools will use the same directory that was last used in the merge tool. Fixes #1290.
  • 2015-06-23 Moritz Bunkus <>
    • MKVToolNix GUI: bug fix: fixed reading the »default track« flag of tracks from added Matroska files. Fixes #1281.
    • MKVToolNix GUI: new feature: added a check box to the track/chapters/tags/attachments list. This offers an additional way of toggling the »mux this« state of entries, same as the drop down box on the right and as double-clicking on the item already did. Implements #1277.
    • MKVToolNix GUI: merge tool bug fix: when appending files with multiple tracks of a type (e.g. multiple audio tracks) then all tracks of that kind would get assigned to the first track of that kind of the file they’re appended to. Now the second audio track from the appended file is appended to the second audio track of the existing file, the third to the third etc. Fixes #1257.
    • MKVToolNix GUI: merge tool bug fix: fixed automatic output file name re-generation when the mux status of tracks changes. Fixes #1253.
    • MKVToolNix GUI: new feature: added an option for always using the suggested description and not asking the user when adding a job to the queue. Implements #1288.
    • MKVToolNix GUI: job queue enhancement: added the shortcut Ctrl+R for the menu entry »start all pending jobs«. Implements #1287.
    • MKVToolNix GUI: new feature: added an option to always treat files dragged & dropped external applications as being added circumventing the question what to do with them (add, append or add as additional parts). This option is enabled by default changing the default behavior from release 8.0.0. Implements #1259.
    • MKVToolNix GUI: new feature: added an optional action after starting a job or adding one to the queue. This can be either to create whole new settings or to only remove all input files. Implements #1254.
    • mmg: bug fix: the deprecation warning will only be shown once. Fixes #1252.
    • Installer for Windows: enhancement: associated the .mtxcfg files with MKVToolNix GUI. Implements #1258.
    • MIME and desktop files: enhancement: added file associations for .mtxcfg with MKVToolNix GUI. Implements #1258.
  • 2015-06-22 Moritz Bunkus <>
    • MKVToolNix GUI: new feature: implemented command line handling. You can open configuration files, add files to merge jobs, open files in the chapter or header editors. Implements #1209.
  • 2015-06-21 Moritz Bunkus <>
    • mkvmerge: bug fix: fixed recognition of (E)AC3 audio tracks using a FourCC of »ec-3«. Fixes #1272.
    • MKVToolNix GUI: merge tool bug fix: fixed attachments not being merged into the file in certain situations. Fixes #1260.
    • MKVToolNix GUI: merge tool bug fix: fixed showing existing attachments present in source files in the »tracks, chapters, tags and attachments« list. Fixes #1256.
    • MKVToolNix GUI: merge tool bug fix: the jobs created when appending files were incorrect resulting in an error message from mkvmerge. Fixes #1271.
    • mkvpropedit: bug fix: fixed a warning about »edit specifications resolving to the same track« when changing the track properties and setting tags for the same track simultaneously. Fixes #1247.
    • MKVToolNix GUI: merge tool bug fix: the output/destination file name is cleared when all files are removed. Fixes #1265.
    • MKVToolNix GUI: merge tool bug fix: fixed command line escaping for empty arguments. Fixes #1270.
    • MKVToolNix GUI: merge tool bug fix: fixed creating files without a title if one of the input files contains a file title. Fixes #1264.
    • MKVToolNix GUI: bug fix: if the job removal policy is set to »remove even if there were warnings« then jobs that were muxed without warnings weren’t removed. Fixes #1262.
  • 2015-06-20 Moritz Bunkus <>
    • Build system: fixed inclusion of desktop files for the two GUIs for Debian/Ubuntu packages. Fixes #1255.

Have fun.

31 thoughts on “MKVToolNix v8.1.0 released

    1. mosu Post author

      True, there’s no code for remembering such settings yet. I’ll open an issue for it.

  1. Ruben

    I will reply here instead of in the past version article. You said I didn’t address particular concerns about the new GUI and I just said something like “it’s shit” (your words, not mine). Don’t take me wrong, I appreciate your work and I didn’t criticize the new GUI just for the sake of it. My critique was and is well intentioned.

    It’s hard to see it if you are the one thinking the changes and implementing them. Here are is my constructive criticism:

    – The purpose of having something done quickly and with less click is harder in the new GUI than it was on the old one. You talk about having a wider version instead of taller but the fact is that the split divider in the main tab is awful and doesn’t show the full line of input files or tracks at once like the old one.

    – The left navigation items are ugly and the menu bar for just the 5 of them takes valuable space. The black background looks bad. Maybe you can try to rework this and put them in other place, preferably without any sort of background or button shading background.

    – If the workflow for more than one job is to have a queue, which is a good approach, why have tabs to have more than one file open at a time. This is something that takes screen space when many of the users add jobs to the queue and then open another one and so on. I don’t think many work with more than one job at a time.

    – You can use a proper menu toolbar for the left navigation items and perhaps you can work on the tab for files and replace them with the menu items there’s. Just a thought.

    I look forward to seeing the GUI improved. Regards.

    1. mosu Post author

      You did indeed not say »it’s shit«, and I’m sorry for putting words in your mouth. But you only stated that several things are bad without giving any reason at all resulting in what I considered to be »generic unspecific complaints« – something I cannot work with.

      Today you did indeed make specific and justified complaints, and I thank you for that.

      About your points.

      1. The wider version was a result of user requests. Obviously there are problems with both approaches. You preferred the wider one while others couldn’t work with that and vice versa.

      However, I’m planning to improve on this by a) making the splitter remember its position over restarts and b) implementing an optional layout more similar to the one used by mmg (file list on top, track list in the middle, preferences on the bottom). See issues 1306 and 1304. I have’t fully thought out how to do the layout in the top-down version yet, though, and it’s not that easy to implement in a maintainable way, so don’t expect this to arrive within a week.

      Another improvement in the long run may be that I plan on making the order of the columns presented in the file and track lists configurable. This doesn’t have a high priority at the moment either, though.

      2. The items being ugly is in the eyes of the beholder. Same for the dark background. I’m not opposed to changing the looks but this is not an area I’m going to spend any time on in the near future.

      The tool selector has so much space for a reason: I have concrete plans for three more tools (extraction, info and a tag editor). I’ll think about giving you an option to hide it in the future (the functions are reachable via the »MKVToolNix GUI« menu already; I could add another menu entry for toggling the tool selector). I’ll add an issue for that.

      3. and 4. Having more than one tab open at the same time was again done upon user request. As a matter of fact this was one of the more often requested features. Having actual tabs gives the user more much better visual feedback which file (s)he is currently working on, so I don’t really want to remove the tabs.

      One option could be to make the placement configurable: Qt supports placing the tabs on the left instead of on the top. I don’t know whether or not that would be an improvement for you, though.

      1. Ruben

        Thanks for the reply. I look forward to those improvements.

        About the left side menu and the background you don’t need to work on it, just use the default control look for each platform, in case it’s possible.

        Support for progress visualization in the Windows taskbar icon is a must. I hope you implement it soon.

        1. mosu Post author

          Well, your »must have« are another person’s »don’t care« :) It is on my TODO list. I’ll open an issue for it.

          Note that the »stacked layout« feature I’ve talked above has been downgraded to medium priority for me (= will likely not be implemented in 8.2.0) as Lenmaer, the most vocal proponent of such a layout, said that he and his fellow guys would stay with mmg after all. I will implement that optional stacked layout in due time.

          Saving the splitter positions has already been implemented.

          I’ll also open lower-priority issues for making the tool selector background something else than black and for moving the tab headers to the side instead of the top.

          Having issues is good :) It means it’s easier to remember that such requests exist.

  2. Lenmaer

    Well, since 8.1.0 it’s starting to become better.
    Not everything suggested is implemented yet which I do understand.
    There’s one thing that I forgot to address and I don’t see it suggested on github.
    It’s the attachments, having them shown in main window now isn’t ideal, especially for us fansubbers who mux lots of fonts, lots of scrolling when you have to remux a file, also more chances of accidentally unselecting a font and doing errors. The behavior of mmg was much more practical with its split screen in another tab. You could also easily compare the fonts you already had muxed in that way. Now you have to browse tabs.

    1. mosu Post author

      It was also a source of confusion for other users. They complained that it was unclear which attachments came from where. It’s also confusing to have both types in the same list once I implement re-ordering of new attachments. Why? Because the order of existing attachments cannot be changed (!). mkvmerge simply doesn’t support that. So having both in the same list would require existing attachments to be always at the top, clearly marked as being from somewhere else, and moving them around would have to be impossible. It wouldn’t do anything to clear up the confusion.

      This is something that I’m unlikely to change.

      And of course not everything suggested has been implemented yet; I cannot do magic, after all ;)

      1. Lenmaer

        Well they don’t need to moved around.
        Just in the attachment tab, have two windows, like mmg did with checkboxes.
        Top windows would have the attachments already muxed in, bottom window, the new ones to be muxed in, and all with checkboxes.
        The old mmg right now shows the path of each attachment, so if users really get confused on what belongs to what, then they must really be dumb, because it’s easy to see. ^^

        1. mosu Post author

          I’m sorry, but like I said this is not something that I’m willing to change at the moment.

  3. chessplayer

    Crash on second run

    Hi, my scenario is that I usually cut TV recordings and pack them into mkvs, where I normally wait until I have a few to process. I will then set everything up for the first one, mux it, remove the file and replace it by the next recording. This works great in the old mkvmerge GUI, but in the new mkvtoolnix GUI, I consistently get a crash when I try to drag & drop the second file to the sources section. I believe it did work once, but then it crashed during mux.

    So, for the time being, I much prefer to use the old GUI and sincerely hope you will leave the latest version in your package forever, even if you do not actively support it anymore …

    My system: Ubuntu 14.04, mkvtoolnix from your ppa updated this morning.

    1. mosu Post author

      Crashes are obviously bugs that I will fix. Just to be clear: you set up your mux settings, hit »start muxing«, remove the source files from the job, then you drag & drop a file from an external application (e.g. a file manager) onto the merge job and MKVToolNix GUI crashes?

      1. chessplayer

        Almost (but maybe you mean the same): I try dragging the file from the file manager to the then empty source area, then it crashes.

        1. mosu Post author

          That’s what I meant, yes. I haven’t been able to reproduce such a crash (I tried for ten minutes an hour ago) on my Arch Linux yet, though, so I don’t know whether or not I’ll be able to find the issue. Likely not, especially as I currently don’t have an Ubuntu installation sitting around here (at least not one with a working graphical setup – only my build system which is run from a chroot from which I cannot run graphical programs).

          1. mosu Post author

            Thanks for the offer. A full stack backtrace might be helpful. For that you’ll have to compile the application with debugging settings, though.

            Generelly: download the source tarball; unpack it; install build dependencies (sudo apt-get build-dep mkvtoolnix ); run »./configure --enable-debug --disable-wxwidgets«; compile with »./drake apps:mkvmerge apps:mkvtoolnix-gui«; install gdb (sudo apt-get install gdb).

            Then run the newly-compiled GUI from inside gdb:

            gdb src/mkvtoolnix-gui/mkvtoolnix-gui

            Do your thing. As soon as it crashes gdb will return to the gdb prompt. At this prompt execute one command:


            Let it show all lines, then copy me that output. It will probably consist of quite a number of lines; you should send me an email with them to (and not post them here on the blog).

  4. JunkyardCat

    I’m very pleased with the new GUI on v8.1. With 8.0 the open with menu didn’t actually open the file with Windows 7 x64, now that it’s working again I have no issues with it at all.
    My typical usage is adding/removing subs and/or audio tracks, occasionally extracting subs or audio, so my experience may not reflect some of the more hardcore users. For me it’s outstanding at this point. Thanks for all the hard work and constant refining.

  5. zz

    Uhmmm are you planning to remove the wxwidgets GUI? When I moved to Linux, I was very pleased to find that mkvtoolnix, audacity, aegisub, use the same GUI toolkit, a fairly small one. Qt is a little big

    1. mosu Post author

      Yes, the wxWidgets-based GUI will be dropped. No, I’m not going to reconsider. Sorry.

  6. Tyler

    Can you add more batch options?

    Like say i have 20 files all with the same track layout, and want to remove 1 track from each and change a setting on another.

    Be nice not to have to do it for every file individually.

    1. mosu Post author

      I’m sorry, but I won’t add batch muxing capabilities to the GUI. See here for the reasons. Individual requirements like yours are best served by learning a tiny bit of scripting and automating mkvmerge’s usage to your hearts content.

  7. David

    Is there any way to automatically remove items from the input list once you add them to the job queue? This was the way it worked with MKVMERGE GUI before, but now you have to add the job, and then delete the files before loading in the next ones.

    1. mosu Post author

      With v8.1.0 you can change the behavior in the preferences. Look for the option »Clearing settings automatically« on the »Merging« tab.

  8. rob

    Hello, thanks for a great line-up of programs! I normally use CLI, so this is very helpful.

    On this new mkvtoolnix(lubuntu), I have a couple of pains. I would like to set the default track flag of audio to initialize as ‘yes’, In most cases I only have one audio, but if there is multiple I can set the secondaries to no and not have to reorder the list.

    I would like to set the default track flag of subtitles to initialize as ‘no’. I rarely have a ‘yes’ default unless the audio is not an understandable language.

    And :) when adding external audios and subs, would there be a way to reorder the list into a preferred sequence instead of adding each file separately. I just added about 20 subs to one video and I found I must add them independently to my preference.

    Thanks again for the superb software, it does save me a lot of time over CLI.

    1. mosu Post author

      > I would like to set the default track flag of audio to initialize as ‘yes’, In most cases I only have one audio, but if there is multiple I can set the secondaries to no and not have to reorder the list.

      There’s usually no need for that. If you leave the settings at their initial values then mkvmerge will already set the »default track« flag to »yes« for the first audio track. See here for an explanation how this process works.

      > I would like to set the default track flag of subtitles to initialize as ‘no’. I rarely have a ‘yes’ default unless the audio is not an understandable language.

      There’s already a feature request for such functionality. I will probably implement it for v8.3.0.

      > And :) when adding external audios and subs, would there be a way to reorder the list into a preferred sequence instead of adding each file separately. I just added about 20 subs to one video and I found I must add them independently to my preference.

      I don’t really understand what you want to achieve. Maybe you could go into more details and provide some examples of what you’re doing and which part of that work the GUI should be able to do for you.

Comments are closed.