mkvtoolnix 4.1.1 released

[hubblec4]

Originally Posted by Mosu

There are two changes for package maintainers and folks building their own copy from the source: 1. the two new translations I've mentioned and 2. mkvtoolnix requires the new releases libebml v0.8.0 and libmatroska v0.9.0 available at http://dl.matroska.org.

hi mosu

is there anywhere a compiled build?

i can download there the source code only.

[Mosu]

Binary packages for libEBML and libMatroska for Debian, Ubuntu, OpenSuSE and Fedora Core are available from http://www.bunkus.org/videotools/mkv...downloads.html

[hubblec4]

Originally Posted by Mosu

Binary packages for libEBML and libMatroska for Debian, Ubuntu, OpenSuSE and Fedora Core are available from http://www.bunkus.org/videotools/mkv...downloads.html

...and for windows? or dont need the new libEBML and libMAtroska for windwos?

[Mosu]

You only need the two libraries if you're building mkvtoolnix from source. That's why that line was prefixed with "note for package maintainers".

[hubblec4]

ahja ok thanks

[roozhou]

@Mosu

Where can i find documentation for the "hidden" options in mkvmerge? e.g. --engage native_mpeg4

[Mosu]

Originally Posted by roozhou

@Mosu

Where can i find documentation for the "hidden" options in mkvmerge? e.g. --engage native_mpeg4

There's almost none because those are development options. I usually don't support them, meaning that I probably won't help you with any problems arising from their usage.

mmg has a dialog for adding arbitrary command line options ("Muxing" -> "Add command line options"). That dialog contains all the available hacks and a short description for each, but that's about all the documentation there is.

[Mosu]

Great news for free multimedia in general and Matroska in particular: Google open-sources VP8 and choses Matroska for their new WebM project

[Keiyakusha]

Hi Mosu!
Not so long ago I discovered (official?)tool called mkvalidator. Not sure why I need it but I tried it just out of curiosity and found that it displays a lot of warnings for files muxed with mkvmerge. like this: "WRN0C0: First Block for video track #1 in Cluster at 69826954 is not a keyframe" However there is also some errors sometimes.
So the question is, does this validator actually valid?

[Mosu]

mkvalidator is developed by Steve Lhomme (robux4), one of the co-creators of Matroska. Yes, its analysis is mostly valid, however it's also a very new tool and there are bugs and inconsistencies it doesn't account for. It would be best if you could talk to robux4 directly, e.g. on IRC (irc.corecodec.com, channel #matroska).

For example, mkvalidator assumes ideal files in which each cluster starts with a key frame in order to make seeking as fast as possible. This is technically unnecessary, and mkvmerge will never write such files, because its current way is not really worse and supported by all readers anyway. That's why it's only a warning in mkvalidator, not an error. It basically says "this file might be improved".

[Mosu]

Here's a build with support for reading VP8 from and writing it to IVF files: http://www.bunkus.org/videotools/mkv...-255-setup.exe

[Selur]

Afaik atm it's only possible to specify on which timecodes a new files should be created, which would result in three output files instead of one when trying to extract a stream from timecode X to timecode Y;
-> Is there already a way to call mkvmerge just create one file and extract just a portion of a stream?
if not: Would be nice if this could be added as a feature in an upcoming version.

[Mosu]

No, it's not possible. I know it would be a nice feature to have, but I won't spend any time on that at the moment or in the near future. Patches are always welcome -- I'm not against such a feature, it just won't be me who'll implement it any time soon.

[moviefan]

Is there any support for H264 streams with open-gop planned? There are some problems with seeking which is probably caused by a missing support for open-gop in mkv. The problem and its possible cause are explained here: http://forum.doom9.org/showpost.php?...&postcount=178.

[Mosu]

I know of the problem but have no plans of working on that at the moment. Patches are MORE than welcome, but I neither have the expertise nor the time to do this myself just now.

[moviefan]

OK. Do you know of any other mkv muxer that can handle open-gop?

[Mosu]

I don't, maybe others do.

[moviefan]

I've just asked in the x264 thread in IRC about the open-gop issue and kierank said it would be an easy thing to adapt to open-gop.

[16:54] kierank: he needs to flag the frame as a keyframe if there's a recovery point sei

I would create a patch if I had any experience in developing media related software. Does this information help and would you change your mind based on this to implement open-gop support? It seems to be easy and if you know what kierank is saying...

[Mosu]

mkvmerge already marks the next frame after a recovery point SEI as a key frame. So if it doesn't work for you it's something else.

[GuilhermeAraujo]

Is it possible to add the job start time in the output? When working with large files, it'd be good to know how long has passed since it started and to estimate how long it'll take to finish.