MKVToolNix v24.0.0 released

[Mosu]

The new GUI sorts the language list by their description as I figured that most users know a language's name but not necessarily its ISO 639-2 code. The code »mis« belongs to the entry »Uncoded languages« which you can find in the new GUI as well (I've just checked).

Keep in mind that the new GUI always sorts »undefined (und)« first followed by the list of common languages (which can be configured in the preferences) in alphabetical order followed by all other languages in alphabetical order.

[LeMoi]

Thanks for the quick answer, indeed, i thought it still was miscellaneous language, that's why I could'nt find it :)

[DMD]

Good morning

Sorry for the trivial question
MI are accustomed to the old interface "mkvmerge GUI", wondering how to avoid the warning every time I launch the program.

http://i58.tinypic.com/2w1tixt.jpg

Thanks

[hubblec4]

this message will removed in next version 8.1.0

[DMD]

THANK YOU :)

lthen I will have to wait download the next version.

[Overdrive80]

Could be implemented any for can change order of attachments?? I ask it because order is important if you use cover art. Thanks.

[Mosu]

Could be implemented any for can change order of attachments?? I ask it because order is important if you use cover art. Thanks.

That is on my TODO list but with a lower priority. Will probably not be implemented in 8.1.0; maybe for 8.2.0. I've opened issue 1276 (https://github.com/mbunkus/mkvtoolnix/issues/1276) for it so that it won't be forgotten.

[Mosu]

this message will removed in next version 8.1.0

Minor nitpick: I will make the GUI show the message only once instead of every time. It won't be removed completely, though.

[kuchikirukia]

I have a video where there's a very clear short speedup right after scene changes when muxing with 8.0, either mkvmerge or mkvtoolnix GUI.

- Encoded video in MeGUI 2525 (muxed with 7.7): Fine (And if you mux it with 8.0 from that it's fine)
- Cut with AVIdemux: Fine
- Remuxed with 8.0: 20 seconds in there's a series of cuts to pans with clear jerks in MPC-HC

- Muxed the AVI with 7.7 and it's good.

Manually setting the frame rate doesn't help.

Remuxing the bad 8.0 mkv in 7.7 also outputs a bad video.

[Mosu]

Can you please open an issue on github (https://github.com/mbunkus/mkvtoolnix/issues/) and upload a sample file before muxing to my FTP server (https://github.com/mbunkus/mkvtoolnix/wiki/FTP-server), please? I'm completely booked with working on the new GUI at the moment, and I will most likely forget about your issue otherwise. Thanks.

[bartonnen]

I usually mux by first dragging in a video file and then an audio file - now with the new v8 GUI an "Adding or appending files" dialog appears.

Can we please have an option to either default to "adding", "appending" or "ask".

In my case I only ever want to add files.

[bartonnen]

With the job queue panel can we please have action buttons like in the old GUI: at least a START button and a DELETE button.

[Mosu]

I usually mux by first dragging in a video file and then an audio file - now with the new v8 GUI an "Adding or appending files" dialog appears.

Can we please have an option to either default to "adding", "appending" or "ask".


That's already on my TODO list for the next release (https://github.com/mbunkus/mkvtoolnix/issues/1259). The default setting will be to not show that dialog.

[Mosu]

With the job queue panel can we please have action buttons like in the old GUI: at least a START button and a DELETE button.

Starting all pending jobs is available from the »Job queue« menu. Deleting jobs is available from the context menu (right-click on a job for that menu, or select multiple jobs and then right-click for deleting them).

I explicitly do not want to plaster buttons for some functions all over the GUI.

[bartonnen]

Starting all pending jobs is available from the »Job queue« menu. Deleting jobs is available from the context menu (right-click on a job for that menu, or select multiple jobs and then right-click for deleting them).

I explicitly do not want to plaster buttons for some functions all over the GUI.

OK - that's fair enough. How about adding a keyboard shortcut for "Start all pending jobs"?

How is the context menu "Start jobs automatically" supposed to work? It seems to be greyed-out unless I have some files selected and then it seems to do the same as the menu option "Start all pending jobs".

The name "Start jobs automatically" makes it sound like jobs will start as soon as they're added to the list.

Also, any chance of having the "Enter job description" dialog be optional? The default job name is always acceptable to me.

[Mosu]

OK - that's fair enough. How about adding a keyboard shortcut for "Start all pending jobs"?

That I'm definitely open to. I'll open an issue for it.

How is the context menu "Start jobs automatically" supposed to work? It seems to be greyed-out unless I have some files selected and then it seems to do the same as the menu option "Start all pending jobs".

The name "Start jobs automatically" makes it sound like jobs will start as soon as they're added to the list.

The context menu entry can be used for re-enabling the selected jobs that have failed before (e.g. due to missing permissions on the destination folder). After re-enabling those jobs the queue will be started automatically (if it hasn't been running at that moment). Note that only one job can be running at the same time, meaning that if the queue is currently running and you select »start jobs automatically« from the context menu then those jobs will be started by the queue once the current job finishes. The queue is run from top to bottom, so there may be other jobs inbetween.

What I'm trying to say is that »Start jobs automatically« does not mean »start them right now«; it only schedules them to be run automatically once the queue gets to them.

The menu entry »start pending jobs« on the other hand will also start the jobs that are currently in state »pending manual start«. It will not touch jobs that have failed for one reason or another.

Also, any chance of having the "Enter job description" dialog be optional? The default job name is always acceptable to me.

Can do, will open another issue for it.

[bartonnen]

That I'm definitely open to. I'll open an issue for it.

...

Can do, will open another issue for it.

Awesome - thanks :thanks:

[Carpo]

Little naming issue if i use MKVToolNix GUI

Say I mux Batman, givng it the name Batman.mkv

it muxes correctly

if i select clear files and than add Batman Returns.264 and Batman Returns.ac3 - the ouput file name changes to Batman(1).mkv, instead of Batman Returns.mkv.

If I use mkvmerge GUI the output name is indeed changed correctly when I add Batman Returns.264, not a big bug, just means you have to double check the output name.

[Mosu]

That's due to the GUI not clearing the output file name properly. See this issue (https://github.com/mbunkus/mkvtoolnix/issues/1254) that I've already fixed.

[Carpo]

ah okay, I have only just started to use the new GUI so wasn't sure if it had been reported, my bad

[Lenmaer]

That new gui is just awful and painful to use. I guess, I’ll then have to forever stay on older versions.
Too bad no one listens to us…
That’s it then with updating mkvtoolnix.

[Mosu]

As I don't want to copy & paste my answer as Lenmaer has has question: see here (https://www.bunkus.org/blog/2015/06/mkvtoolnix-v8-0-0-released/#comment-24965).

[sl1pkn07]

finaly Qt instead of wxGTK!!

thanks a lot!

[Lenmaer]

As I don't want to copy & paste my answer as Lenmaer has has question: see here (https://www.bunkus.org/blog/2015/06/mkvtoolnix-v8-0-0-released/#comment-24965).

Well, I answered you on your blog. But to make it short, fansub groups will forever stick with 7.9.0. We (Several group leaders) had a discussion before 7.9.0 was released and agreed to forever stick with the latest version having the old gui.

[Mosu]

And I've replied there as well. Let's keep this discussion on the blog where it started, ok? No need to cross-post for us here for each reply.

[Mosu]

finaly Qt instead of wxGTK!!

thanks a lot!

You're quite welcome. I've already had a complaint from the other side, though: »oh no, Qt, it doesn't fit nicely into Gnome« ;)

Well, that's the crux of all those toolkit libraries on Linux: they just don't fit well into foreign desktop environments (GTK in KDE, Qt in Gnome etc.). No way to please everyone.

[Zenitram]

Well, I answered you on your blog. But to make it short, fansub groups will forever stick with 7.9.0. We (Several group leaders) had a discussion before 7.9.0 was released and agreed to forever stick with the latest version having the old gui.

As usual, some people code and some other do critisism "it was better in the past" without coding (and without real argument / improvement ideas).
And as usual, such people will stay with the last "lovely" version, and some time later they'll switch to the newest version without saying anything when they'll need improvements from a newest version (else other group leaders, using the newest version, would be prefered by the end users)

Nothing new, this is the classic pain of people who create something.

[Lenmaer]

All we are saying is that new gui looks nice but totally unadapted for heavy users. It's perfect for casual users like yourself, Zenitram.

[Mosu]

Again, please name the issues that make it unsuitable for heavy users. I would REALLY like to have it work well for almost everyone, but if you don't share what you think is broken or not working well then I cannot fix it.

[Zenitram]

No way to please everyone.

There is a way: the native UI of each target (Qt, GTK, Cocoa...). It is "only" more work (and obviously, lot of people complain but nobody offers to develop and maintain the code :D ).

Good move.

[stax76]

Being also a open source programmer and having programmed much GUI code for CLI tools I find Lenmaer's feedback somehow frustrating...

[foxyshadis]

Lenmaer, if you want to post something constructive, you're free to. Ranting isn't called for though, especially given that the new is a work in progress that's steadily improving.

[Chetwood]

But to make it short, fansub groups will forever stick with 7.9.0.
A fitting quote from Angel:

And yet, somehow, I just can't seem to care.

[Mosu]

Folks, please stay civil; bashing isn't constructive either. I do appreciate the support, but Lenmaer and I did have a discussion about his two most important grievances over on my blog (search for his nick there) (https://www.bunkus.org/blog/2015/06/mkvtoolnix-v8-0-0-released/#comments), and both of them will be addressed; one already has.

[Kurtnoise]

Hi Mosu,

The current GUI says that a new version 8.1.0 is available but the downloads still link to 8.0.0. Is it normal ?

[Mosu]

Meh… I've uploaded that update info file too early. The new release is still building (will be a couple of hours until it's done). Thanks for pointing it out.

Edit: I've fixed the information on the server.

[Mosu]

Hey,

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.

Here are the usual links: the MKVToolNix home page (https://www.bunkus.org/videotools/mkvtoolnix/), the Windows installer and portable version (http://www.fosshub.com/MKVToolNix.html) and the source code (https://www.bunkus.org/videotools/mkvtoolnix/source.html).

All binaries that I provide have been uploaded already.

Here's the full ChangeLog (https://www.bunkus.org/videotools/mkvtoolnix/doc/ChangeLog) since the previous release:

2015-06-27 Moritz Bunkus <moritz@bunkus.org>
* 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 (https://github.com/mbunkus/mkvtoolnix/issues/1266).

2015-06-26 Moritz Bunkus <moritz@bunkus.org>
* MKVToolNix GUI: new chapter editor feature: added a function for generating a certain number of evenly spaced sub-chapter. Implements #1291 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1301).

2015-06-25 Moritz Bunkus <moritz@bunkus.org>
* 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 <moritz@bunkus.org>
* 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 (https://github.com/mbunkus/mkvtoolnix/issues/1263).
* MKVToolNix GUI: merge tool bug fix: fixed a crash when enabling/disabling chapters coming from an appended file. Fixes #1293 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1290).

2015-06-23 Moritz Bunkus <moritz@bunkus.org>
* MKVToolNix GUI: bug fix: fixed reading the »default track« flag of tracks from added Matroska files. Fixes #1281 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1257).
* MKVToolNix GUI: merge tool bug fix: fixed automatic output file name re-generation when the mux status of tracks changes. Fixes #1253 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1288).
* MKVToolNix GUI: job queue enhancement: added the shortcut Ctrl+R for the menu entry »start all pending jobs«. Implements #1287 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1254).
* mmg: bug fix: the deprecation warning will only be shown once. Fixes #1252 (https://github.com/mbunkus/mkvtoolnix/issues/1252).
* Installer for Windows: enhancement: associated the .mtxcfg files with MKVToolNix GUI. Implements #1258 (https://github.com/mbunkus/mkvtoolnix/issues/1258).
* MIME and desktop files: enhancement: added file associations for .mtxcfg with MKVToolNix GUI. Implements #1258 (https://github.com/mbunkus/mkvtoolnix/issues/1258).

2015-06-22 Moritz Bunkus <moritz@bunkus.org>
* 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 (https://github.com/mbunkus/mkvtoolnix/issues/1209).

2015-06-21 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: fixed recognition of (E)AC3 audio tracks using a FourCC of »ec-3«. Fixes #1272 (https://github.com/mbunkus/mkvtoolnix/issues/1272).
* MKVToolNix GUI: merge tool bug fix: fixed attachments not being merged into the file in certain situations. Fixes #1260 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1256).
* MKVToolNix GUI: merge tool bug fix: the jobs created when appending files were incorrect resulting in an error message from mkvmerge. Fixes #1271 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1247).
* MKVToolNix GUI: merge tool bug fix: the output/destination file name is cleared when all files are removed. Fixes #1265 (https://github.com/mbunkus/mkvtoolnix/issues/1265).
* MKVToolNix GUI: merge tool bug fix: fixed command line escaping for empty arguments. Fixes #1270 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/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 (https://github.com/mbunkus/mkvtoolnix/issues/1262).

2015-06-20 Moritz Bunkus <moritz@bunkus.org>
* Build system: fixed inclusion of desktop files for the two GUIs for Debian/Ubuntu packages. Fixes #1255 (https://github.com/mbunkus/mkvtoolnix/issues/1255).

Have fun.

[bartonnen]

Well, version 8.1 is much better - thanks for all your hard work Mosu.

I did find one issue though - with "Clearing setting automatically" set to "remove input files", after adding a job to the queue the settings are all cleared as expected and the name on the tab reverts to "<no output file>".

If I then try to exit the app (or close the tab) - I get the following warning:

"The file »<no output file>« has been modified. Do you really want to close? All changes will be lost."

[Mosu]

That's somewhat expected. The functionality »remove input files« does NOT revert the setting into a pristine state. The tool tip in the preferences hints at this. It only removes the input files, the tracks, and it clears the output file name and the file/segment title if and only if those two have been set automatically (enabled in the preferences). The other controls (e.g. split settings, chapters, attachments…) aren't touched.

This is definitely intentional behavior. It allows users to mux several files sharing common settings in succession quickly.

If your use case is to start over with pristine settings after muxing then set the option in the preferences to »create new settings« – that's what the option is there for.

[DMD]

Good morning

Sorry for the trivial question
MI are accustomed to the old interface "mkvmerge GUI", wondering how to avoid the warning every time I launch the program.

http://i58.tinypic.com/2w1tixt.jpg

Thanks

(Release 8.1.0) The warning appears only when you first start.

Thanks

[sneaker_ger]

The warning should only appear once in 8.1.0. Did you already try a second time?

[DMD]

I confirm, The warning appears only when you first start.

sorry

[TheShadowRunner]

yeah thank god (Mosu) for deprecation_warning_shown.

[mood]

Thanks Mosu for your hard work ;)

[DMD]

Thank you personally, Mosu for the great work and the time devoted to the development of this amazing program that I use for many years.

My request of previous posts, was motivated only by the fact that with the old interface knew by heart the settings.

But this is not a problem to get used to the new interface, which is very beautiful, functional and makes more professional program.
(In the next release could also be eliminated)

Thanks for allowing us to have this program and continues always so. http://www.ntacalabria.it/smile/tifosi/img/10.gif http://www.ntacalabria.it/smile/tifosi/img/11.gif

[stax76]

There is a merge/append feature in StaxRip, for VOB files StaxRip appends with DGIndex but with other files it just uses mkvmerge, occasionally something goes wrong and StaxRip ask the user then to send me the log file, usually I reply then telling to merge/append it manually somehow or not split in the first place. What I will improve in the future is writing MediaInfo for every part to be appended to the log file. Maybe Mosu, sneaker_ger or someone else might have a idea what's the problem. What actually returns a error is mp4box but there might already a problem with the mkvmerge output because MediaInfo doesn't output proper MediaInfo, after mkvmerge appends mkvextract is used to demux for which again is no proper MediaInfo available, StaxRip usually writes full MediaInfo of the output and input files to the log file after every processing step.

------------------------------------------------------------
Merge source files
------------------------------------------------------------

"C:\-Video\StaxRip\Tools\MKVToolNix\mkvmerge.exe" -o "G:\foo\1.mp4-muxed_merged.mkv" "G:\foo\1.mp4-muxed.mp4" + "G:\foo\2.mp4-muxed.mp4" + "G:\foo\3.mp4-muxed.mp4" + "G:\foo\4.mp4-muxed.mp4" + "G:\foo\5.mp4-muxed.mp4"

mkvmerge v7.9.0 ('Birds') 64bit
'G:\foo\1.mp4-muxed.mp4': Using the demultiplexer for the format 'QuickTime/MP4'.
'G:\foo\2.mp4-muxed.mp4': Using the demultiplexer for the format 'QuickTime/MP4'.
'G:\foo\3.mp4-muxed.mp4': Using the demultiplexer for the format 'QuickTime/MP4'.
'G:\foo\4.mp4-muxed.mp4': Using the demultiplexer for the format 'QuickTime/MP4'.
'G:\foo\5.mp4-muxed.mp4': Using the demultiplexer for the format 'QuickTime/MP4'.
'G:\foo\1.mp4-muxed.mp4' track 0: Using the output module for the format 'AVC/h.264'.
'G:\foo\1.mp4-muxed.mp4' track 1: Using the output module for the format 'AAC'.
'G:\foo\2.mp4-muxed.mp4' track 0: Using the output module for the format 'AVC/h.264'.
'G:\foo\2.mp4-muxed.mp4' track 1: Using the output module for the format 'AAC'.
'G:\foo\3.mp4-muxed.mp4' track 0: Using the output module for the format 'AVC/h.264'.
'G:\foo\3.mp4-muxed.mp4' track 1: Using the output module for the format 'AAC'.
'G:\foo\4.mp4-muxed.mp4' track 0: Using the output module for the format 'AVC/h.264'.
'G:\foo\4.mp4-muxed.mp4' track 1: Using the output module for the format 'AAC'.
'G:\foo\5.mp4-muxed.mp4' track 0: Using the output module for the format 'AVC/h.264'.
'G:\foo\5.mp4-muxed.mp4' track 1: Using the output module for the format 'AAC'.
No append mapping was given for the file no. 1 ('G:\foo\2.mp4-muxed.mp4'). A default mapping of 1:0:0:0,1:1:0:1 will be used instead. Please keep that in mind if mkvmerge aborts with an error message regarding invalid '--append-to' options.
No append mapping was given for the file no. 2 ('G:\foo\3.mp4-muxed.mp4'). A default mapping of 2:0:1:0,2:1:1:1 will be used instead. Please keep that in mind if mkvmerge aborts with an error message regarding invalid '--append-to' options.
No append mapping was given for the file no. 3 ('G:\foo\4.mp4-muxed.mp4'). A default mapping of 3:0:2:0,3:1:2:1 will be used instead. Please keep that in mind if mkvmerge aborts with an error message regarding invalid '--append-to' options.
No append mapping was given for the file no. 4 ('G:\foo\5.mp4-muxed.mp4'). A default mapping of 4:0:3:0,4:1:3:1 will be used instead. Please keep that in mind if mkvmerge aborts with an error message regarding invalid '--append-to' options.
Warning: The track number 0 from the file 'G:\foo\4.mp4-muxed.mp4' can probably not be appended correctly to the track number 0 from the file 'G:\foo\3.mp4-muxed.mp4': The codec's private data does not match (lengths: 43 and 38). Please make sure that the resulting file plays correctly the whole time. The author of this program will probably not give support for playback issues with the resulting file.
Warning: The track number 0 from the file 'G:\foo\5.mp4-muxed.mp4' can probably not be appended correctly to the track number 0 from the file 'G:\foo\4.mp4-muxed.mp4': The codec's private data does not match (lengths: 38 and 43). Please make sure that the resulting file plays correctly the whole time. The author of this program will probably not give support for playback issues with the resulting file.
The file 'G:\foo\1.mp4-muxed_merged.mkv' has been opened for writing.
Progress: 0%
Appending track 0 from file no. 1 ('G:\foo\2.mp4-muxed.mp4') to track 0 from file no. 0 ('G:\foo\1.mp4-muxed.mp4').
Appending track 1 from file no. 1 ('G:\foo\2.mp4-muxed.mp4') to track 1 from file no. 0 ('G:\foo\1.mp4-muxed.mp4').
Progress: 30%
Appending track 0 from file no. 2 ('G:\foo\3.mp4-muxed.mp4') to track 0 from file no. 1 ('G:\foo\2.mp4-muxed.mp4').
Appending track 1 from file no. 2 ('G:\foo\3.mp4-muxed.mp4') to track 1 from file no. 1 ('G:\foo\2.mp4-muxed.mp4').
Progress: 58%
Appending track 0 from file no. 3 ('G:\foo\4.mp4-muxed.mp4') to track 0 from file no. 2 ('G:\foo\3.mp4-muxed.mp4').
Appending track 1 from file no. 3 ('G:\foo\4.mp4-muxed.mp4') to track 1 from file no. 2 ('G:\foo\3.mp4-muxed.mp4').
Appending track 0 from file no. 4 ('G:\foo\5.mp4-muxed.mp4') to track 0 from file no. 3 ('G:\foo\4.mp4-muxed.mp4').
Appending track 1 from file no. 4 ('G:\foo\5.mp4-muxed.mp4') to track 1 from file no. 3 ('G:\foo\4.mp4-muxed.mp4').
Progress: 89%
Progress: 100%
Progress: 100%
The cue entries (the index) are being written...
Muxing took 2 seconds.

------------------------------------------------------------
Environment
------------------------------------------------------------

StaxRip version : 1.3.1.0
OS : Windows 7 Professional N
Language : Serbian (Cyrillic, Serbia)
CPU : Intel(R) Core(TM)2 Duo CPU E4700 @ 2.60GHz
GPU :
LAV Filters : LAV Filters 0.65

------------------------------------------------------------
Source file MediaInfo
------------------------------------------------------------

G:\foo\1.mp4-muxed_merged.mkv

Matroska : 250 MiB, 46mn 55s646*480 (4:3), at 25.000 fps, AVC (Main@L3) (CABAC / 3 Ref Frames)44.1 KHz, 2 channels, AAC (LC)

------------------------------------------------------------
Demux audio using mkvextract
------------------------------------------------------------

"C:\-Video\StaxRip\Tools\MKVToolNix\mkvextract.exe" tracks "G:\foo\1.mp4-muxed_merged.mkv" 1:"G:\foo\1.mp4-muxed_merged temp files\1.mp4-muxed_merged - ID2.aac" --ui-language en

Extracting track 1 with the CodecID 'A_AAC' to the file 'G:\foo\1.mp4-muxed_merged temp files\1.mp4-muxed_merged - ID2.aac'. Container format: raw AAC file with ADTS headers

Start: 14:38:35
End: 14:38:39
Duration: 00:00:03

ADTS : 43.0 MiB44.1 KHz, 2 channels, AAC (Version 4) (LC)

------------------------------------------------------------
Mux AAC to M4A
------------------------------------------------------------

"C:\-Video\StaxRip\Tools\MP4Box\MP4Box.exe" -add "G:\foo\1.mp4-muxed_merged temp files\1.mp4-muxed_merged - ID2.aac:name= " -new "G:\foo\1.mp4-muxed_merged temp files\1.mp4-muxed_merged - ID2.m4a"

------------------------------------------------------------
Error Mux AAC to M4A
------------------------------------------------------------

Mux AAC to M4A failed with exit code -1073741701

[hubblec4]

Hi Mosu

With a doubleclick on the mtxcfg and the new gui open, like you promised. :-)
But a doubleclick on a second mtxcfg and nothing happens. with the drag&drop it works and a new tab is created.

[Mosu]

If an instance is running already then the second config should have been opened in that already-running instance. I definitely remember having tested that on Windows, too. Will have to re-test tonight.

[hubblec4]

If an instance is running already then the second config should have been opened in that already-running instance.

After few new tests: The second mtxcfg open a new tab sometimes. (But mostly nothing happens)

[hubblec4]

I found a small issue in the chapter editor.
when i load a xml file with drag&drop, all "save" option keeps grey and can't be used.