MKVToolNix v24.0.0 released

[Boulder]

Thanks, works perfectly

[kuchikirukia]

Before I go and make an account to ask the Mediainfo guy, I thought I'd ask the mkv experts here.
Mediainfo currently doesn't support showing individual audio/video bitrates when combined in MKV. It does in MP4. Is there a limitation of the MKV container that prevents this information being discovered, or is this a feature that Mediainfo could support?

[sneaker_ger]

To find out such information parsing of the complete Matroska file might be necessary so it can't be done within a few seconds by MediaInfo for every file (there are tricks for good estimates but they only work for specific files). Newer mkvmerge versions write the tracks' bitrates as tags and the MediaInfo author has said he has reading these tags (and other Matroska improvements) on his to-do list. So there is no need to contact him.

[kuchikirukia]

Cool. Thanks!

[hubblec4]

Hi Mosu

Is it possible to add a feature, so that mkvmerge options files can be loaded in the new gui like the mtxcfg.file?

[Mosu]

I'm afraid that's way too difficult to implement. Option files, just like command line arguments, are pretty free in the order they can do things. I also don't see much of a use-case for this (meaning only a very small number of people would actually use such a feature). I have an idea what you would use it for (generating option files instead of .mtxcfg files like you're trying to do at the moment), but to be honest the amount of work would be daunting.

Sorry.

[Boulder]

What do you mean? DTS-HD MA files work just fine.

[P.J]

Originally Posted by Boulder

What do you mean? DTS-HD MA files work just fine.

Yes, the problem was another thing

[hubblec4]

Originally Posted by Mosu

I'm afraid that's way too difficult to implement. Option files, just like command line arguments, are pretty free in the order they can do things. I also don't see much of a use-case for this (meaning only a very small number of people would actually use such a feature). I have an idea what you would use it for (generating option files instead of .mtxcfg files like you're trying to do at the moment), but to be honest the amount of work would be daunting.

Sorry.

no problem.
I thought so that it will be too complicated.
Creating a mtxcfg file is done in my chapterEditor(next rev), but for muxing separete mkv-parts(split by timecodes), i can just create such mtxcfg file for the cutting-process when is done.
(scan the mkv-parts with mkvmerge --identify-for-mmg)

Maybe i can create an option and cmd file for the mkv-parts.
mkvmerge: when i use such option file, mkvmerge will scan the mkv-parts automaticly? There are no settings in the option file for --identify-for-mmg(properties).

[Mosu]

File identification is always and automatically done by mkvmerge for each input file. The step with »mkvmerge --identify… yourfile.ext« is separately only so that the GUI can retrieve certain parameters to use (container type, track types, current properties like language, title, track name…).

[hubblec4]

thats sounds good, so i can use the option and cmd file for the separate muxing process.
split option: split by parts based on timecodes works perfect and i need one mtxcfg file only.

[RDF]

I am reporting to have the same problem with Windows 10 (64bit) as HassiD. For some reason I am still able to use the old gui version.

I'm liking the new GUI version so far. At first, I hate it but I got used to it very quickly. Please verify this problem in Windows 10 (64bit) when you can. I really want to keep using the new GUI because it's easier to edit chapters with it.

Thanks you.

[Mosu]

Problem is that I don't have Windows 10 yet, nor do I want to upgrade my sole Windows machine to it just yet...

[Chetwood]

And rightfully so: https://i.imgur.com/iHge6RJ.jpg.

Slighty OT as mentioned in the other thread but since you've brought it up...

[Mosu]

@RDF: I've opened an issue for it and will investigate it, but as I don't have Windows 10 yet (nor an idea what the cause might be) I cannot say when I'll be able to fix it.

[bartonnen]

Originally Posted by RDF

I am reporting to have the same problem with Windows 10 (64bit) as HassiD. For some reason I am still able to use the old gui version.

I know this doesn't help - but I have Windows 10 64bit and the new GUI runs fine for me. Maybe because I just upgraded directly from Win 8.1 and haven't done a clean Win 10 install.

[Mosu]

@RDF: You might give pre-builds 838 or 839 a try. Note that I haven't tried them myself, but they've been built with a newer version of the GUI toolkit library I'm using (Qt 5.5.0 instead of 5.4.2).

[Atak_Snajpera]

Originally Posted by Mosu

Problem is that I don't have Windows 10 yet, nor do I want to upgrade my sole Windows machine to it just yet...

You can test your app on virtual machine. I'm using free Vware player with win10. You can easily download iso from torrent sites. (key/activation is not required for trial mode)

[amayra]

if you add mkv extract this well be great

[Mosu]

That is on the TODO list but still a couple of months off.