MKVToolNix v24.0.0 released

[Mosu]

Progress bar is not working anymore, instead of it I have this message :

I just verified that it still works for me on my German Windows 7 64bit.

[Mosu]

Ah ok, it only happens with the French translation. Interesting. I'll check it out.

[LeMoi]

Indeed, if i go back to english version, progress bar is working fine

[Mosu]

Fixed in http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-4.5.0-build20110208-324-setup.exe

[Abs62]

Mkvmerge GUI 4.5.0 occasionally crashes on exit - exception 0xc0000005 in wxmsw28u_core_gcc_custom.dll. Start mmg.exe -> press Ctrl+Q -> crash. Next time start mmg.exe -> press Ctrl+Q -> OK.
WinXP SP3 (x86) eng.
4.4.0 work OK.

[Motenai Yoda]

into the stereoscopy tag there isn't options for frame interleaved?

[Mosu]

No, because the specs don't contain such a value. If you want more information I have to refer you to the devel mailing list and the discussions about this topic over the last weeks: http://lists.matroska.org/pipermail/matroska-devel/

[Mtz]

4.5.0
Is possible that saving on external HDD (using USB cable connection) to result in sometimes corrupted files? Saving on internal HDD I never had problems, but on two external HDD sometimes the result is like this:

---
ERR080: Unknown element [BB] at 8539975200 size 17
ERR080: Unknown element [BB] at 8539975219 size 17
ERR080: Unknown element [BB] at 8539975238 size 17
ERR080: Unknown element [BB] at 8539975257 size 17
ERR080: Unknown element [BB] at 8539975276 size 17
ERR080: Unknown element [BB] at 8539975295 size 17
ERR080: Unknown element [BB] at 8539975314 size 17
ERR080: Unknown element [BB] at 8539975333 size 17
ERR080: Unknown element [BB] at 8539975352 size 17
ERR080: Unknown element [BB] at 8539975371 size 17
ERR080: Unknown element [BB] at 8539975390 size 17
ERR080: Unknown element [BB] at 8539975409 size 17
ERR080: Unknown element [BB] at 8539975428 size 17
ERR080: Unknown element [BB] at 8539975447 size 17
ERR080: Unknown element [BB] at 8539975466 size 17
ERR080: Unknown element [BB] at 8539975485 size 17
ERR080: Unknown element [BB] at 8539975504 size 17
ERR080: Unknown element [BB] at 8539975523 size 17
ERR080: Unknown element [BB] at 8539975542 size 17
ERR080: Unknown element [BB] at 8539975561 size 17
ERR080: Unknown element [BB] at 8539975580 size 17
ERR080: Unknown element [BB] at 8539975599 size 17
ERR080: Unknown element [BB] at 8539975618 size 17
ERR080: Unknown element [BB] at 8539975637 size 17
ERR080: Unknown element [BB] at 8539975656 size 17
ERR080: Unknown element [BB] at 8539975675 size 17
ERR080: Unknown element [BB] at 8539975694 size 17
ERR080: Unknown element [BB] at 8539975713 size 17
ERR080: Unknown element [BB] at 8539975732 size 17
ERR080: Unknown element [BB] at 8539975751 size 17
ERR080: Unknown element [BB] at 8539975770 size 17
ERR080: Unknown element [BB] at 8539975789 size 17
ERR080: Unknown element [BB] at 8539975808 size 17
ERR080: Unknown element [BB] at 8539975827 size 17
ERR080: Unknown element [BB] at 8539975846 size 17
ERR080: Unknown element [BB] at 8539975865 size 17
ERR080: Unknown element [BB] at 8539975884 size 17
ERR080: Unknown element [BB] at 8539975903 size 17
ERR080: Unknown element [BB] at 8539975922 size 17
ERR080: Unknown element [BB] at 8539975941 size 17
ERR080: Unknown element [BB] at 8539975960 size 17
ERR080: Unknown element [BB] at 8539975979 size 17
ERR080: Unknown element [BB] at 8539975998 size 17
ERR080: Unknown element [BB] at 8539976017 size 17
ERR080: Unknown element [BB] at 8539976036 size 17
ERR080: Unknown element [BB] at 8539976055 size 17
ERR080: Unknown element [BB] at 8539976074 size 17
ERR080: Unknown element [BB] at 8539976093 size 17
ERR080: Unknown element [BB] at 8539976112 size 17
ERR080: Unknown element [BB] at 8539976131 size 17
ERR080: Unknown element [BB] at 8539976150 size 17
ERR080: Unknown element [BB] at 8539976169 size 17
ERR080: Unknown element [BB] at 8539976188 size 17
ERR080: Unknown element [BB] at 8539976207 size 17
ERR080: Unknown element [BB] at 8539976226 size 17
ERR080: Unknown element [BB] at 8539976245 size 17
ERR080: Unknown element [BB] at 8539976264 size 17
ERR080: Unknown element [BB] at 8539976283 size 17
ERR080: Unknown element [BB] at 8539976302 size 17
ERR080: Unknown element [BB] at 8539976321 size 17
ERR080: Unknown element [BB] at 8539976340 size 17
ERR080: Unknown element [BB] at 8539976359 size 17
ERR080: Unknown element [BB] at 8539976378 size 17
ERR080: Unknown element [BB] at 8539976397 size 17
ERR080: Unknown element [BB] at 8539976416 size 17
ERR080: Unknown element [BB] at 8539976435 size 17
ERR080: Unknown element [BB] at 8539976454 size 17
ERR080: Unknown element [BB] at 8539976473 size 17
ERR080: Unknown element [BB] at 8539976492 size 17
ERR080: Unknown element [BB] at 8539976511 size 17
ERR080: Unknown element [BB] at 8539976530 size 17
ERR080: Unknown element [BB] at 8539976549 size 17
ERR080: Unknown element [BB] at 8539976568 size 17
ERR080: Unknown element [BB] at 8539976587 size 17
ERR080: Unknown element [BB] at 8539976606 size 17
ERR080: Unknown element [BB] at 8539976625 size 17
ERR080: Unknown element [BB] at 8539976644 size 17
ERR080: Unknown element [BB] at 8539976663 size 17
ERR080: Unknown element [BB] at 8539976682 size 17
ERR080: Unknown element [BB] at 8539976701 size 17
ERR080: Unknown element [BB] at 8539976720 size 17
ERR080: Unknown element [BB] at 8539976739 size 17
ERR080: Unknown element [BB] at 8539976758 size 17
ERR080: Unknown element [BB] at 8539976777 size 17
ERR080: Unknown element [BB] at 8539976796 size 17
ERR080: Unknown element [BB] at 8539976815 size 17
ERR080: Unknown element [BB] at 8539976834 size 17
ERR080: Unknown element [BB] at 8539976853 size 17
ERR080: Unknown element [BB] at 8539976872 size 17
ERR080: Unknown element [BB] at 8539976891 size 17
ERR080: Unknown element [BB] at 8539976910 size 17
ERR080: Unknown element [BB] at 8539976929 size 17
ERR080: Unknown element [BB] at 8539976948 size 17
ERR080: Unknown element [BB] at 8539976967 size 17
ERR080: Unknown element [BB] at 8539976986 size 17
ERR080: Unknown element [BB] at 8539977005 size 17
ERR080: Unknown element [BB] at 8539977024 size 17
ERR080: Unknown element [BB] at 8539977043 size 17
ERR080: Unknown element [BB] at 8539977062 size 17
ERR080: Unknown element [BB] at 8539977081 size 17
ERR080: Unknown element [BB] at 8539977100 size 17
ERR080: Unknown element [BB] at 8539977119 size 17
ERR080: Unknown element [BB] at 8539977138 size 17
ERR080: Unknown element [BB] at 8539977157 size 17
ERR080: Unknown element [BB] at 8539977176 size 17
ERR080: Unknown element [BB] at 8539977195 size 17
ERR080: Unknown element [BB] at 8539977214 size 17
ERR080: Unknown element [BB] at 8539977233 size 17
ERR080: Unknown element [BB] at 8539977252 size 17
ERR080: Unknown element [BB] at 8539977271 size 17
ERR080: Unknown element [BB] at 8539977290 size 17
ERR080: Unknown element [BB] at 8539977309 size 17
ERR080: Unknown element [BB] at 8539977328 size 17
ERR080: Unknown element [BB] at 8539977347 size 17
ERR080: Unknown element [BB] at 8539977366 size 17
ERR080: Unknown element [BB] at 8539977385 size 17
ERR080: Unknown element [BB] at 8539977404 size 17
ERR080: Unknown element [BB] at 8539977423 size 17
ERR080: Unknown element [BB] at 8539977442 size 17
ERR080: Unknown element [BB] at 8539977461 size 17
ERR080: Unknown element [BB] at 8539977480 size 17
ERR080: Unknown element [BB] at 8539977499 size 17
ERR080: Unknown element [BB] at 8539977518 size 17
ERR080: Unknown element [BB] at 8539977537 size 17
ERR080: Unknown element [BB] at 8539977556 size 17
ERR080: Unknown element [BB] at 8539977575 size 17
ERR080: Unknown element [BB] at 8539977594 size 17
ERR080: Unknown element [BB] at 8539977613 size 17
ERR080: Unknown element [BB] at 8539977632 size 17
ERR080: Unknown element [BB] at 8539977651 size 17
ERR080: Unknown element [BB] at 8539977670 size 17
ERR080: Unknown element [BB] at 8539977689 size 17
ERR080: Unknown element [BB] at 8539977708 size 17
ERR080: Unknown element [BB] at 8539977727 size 17
ERR080: Unknown element [BB] at 8539977746 size 17
ERR080: Unknown element [BB] at 8539977765 size 17
ERR080: Unknown element [BB] at 8539977784 size 17
ERR080: Unknown element [BB] at 8539977803 size 17
ERR080: Unknown element [BB] at 8539977822 size 17
ERR080: Unknown element [BB] at 8539977841 size 17
ERR080: Unknown element [BB] at 8539977860 size 17
ERR080: Unknown element [BB] at 8539977879 size 17
ERR080: Unknown element [BB] at 8539977898 size 17
ERR080: Unknown element [BB] at 8539977917 size 17
ERR080: Unknown element [BB] at 8539977936 size 17
ERR080: Unknown element [BB] at 8539977955 size 17
ERR080: Unknown element [BB] at 8539977974 size 17
ERR080: Unknown element [BB] at 8539977993 size 17
ERR080: Unknown element [BB] at 8539978012 size 17
ERR080: Unknown element [BB] at 8539978031 size 17
ERR080: Unknown element [BB] at 8539978050 size 17
ERR080: Unknown element [BB] at 8539978069 size 17
ERR080: Unknown element [BB] at 8539978088 size 17
ERR080: Unknown element [BB] at 8539978107 size 17
ERR080: Unknown element [BB] at 8539978126 size 17
ERR080: Unknown element [BB] at 8539978145 size 17
ERR080: Unknown element [BB] at 8539978164 size 17
ERR080: Unknown element [BB] at 8539978183 size 17
ERR080: Unknown element [BB] at 8539978202 size 17
ERR080: Unknown element [BB] at 8539978221 size 17
ERR080: Unknown element [BB] at 8539978240 size 17
ERR080: Unknown element [BB] at 8539978259 size 17
ERR080: Unknown element [BB] at 8539978278 size 17
ERR080: Unknown element [BB] at 8539978297 size 17
ERR080: Unknown element [BB] at 8539978316 size 17
ERR080: Unknown element [BB] at 8539978335 size 17
ERR080: Unknown element [BB] at 8539978354 size 17
ERR080: Unknown element [BB] at 8539978373 size 17
ERR080: Unknown element [BB] at 8539978392 size 17
ERR080: Unknown element [BB] at 8539978411 size 17
ERR080: Unknown element [BB] at 8539978430 size 17
ERR080: Unknown element [BB] at 8539978449 size 17
ERR080: Unknown element [BB] at 8539978468 size 17
ERR080: Unknown element [BB] at 8539978487 size 17
ERR080: Unknown element [BB] at 8539978506 size 17
ERR080: Unknown element [BB] at 8539978525 size 17
ERR080: Unknown element [BB] at 8539978544 size 17
ERR080: Unknown element [BB] at 8539978563 size 17
ERR080: Unknown element [BB] at 8539978582 size 17
ERR080: Unknown element [BB] at 8539978601 size 17
ERR080: Unknown element [BB] at 8539978620 size 17
ERR080: Unknown element [BB] at 8539978639 size 17
ERR080: Unknown element [BB] at 8539978658 size 17
ERR080: Unknown element [BB] at 8539978677 size 17
ERR080: Unknown element [BB] at 8539978696 size 17
ERR080: Unknown element [BB] at 8539978715 size 17
ERR080: Unknown element [BB] at 8539978734 size 17
ERR080: Unknown element [BB] at 8539978753 size 17
ERR080: Unknown element [BB] at 8539978772 size 17
ERR080: Unknown element [BB] at 8539978791 size 17
ERR080: Unknown element [BB] at 8539978810 size 17
ERR080: Unknown element [BB] at 8539978829 size 17
ERR080: Unknown element [BB] at 8539978848 size 17
ERR080: Unknown element [BB] at 8539978867 size 17
ERR080: Unknown element [BB] at 8539978886 size 17
ERR080: Unknown element [BB] at 8539978905 size 17
ERR080: Unknown element [BB] at 8539978924 size 17
ERR080: Unknown element [BB] at 8539978943 size 17
ERR080: Unknown element [BB] at 8539978962 size 17
ERR080: Unknown element [BB] at 8539978981 size 17
ERR080: Unknown element [BB] at 8539979000 size 17
ERR080: Unknown element [BB] at 8539979019 size 17
ERR080: Unknown element [BB] at 8539979038 size 17
ERR080: Unknown element [BB] at 8539979057 size 17
ERR080: Unknown element [BB] at 8539979076 size 17
ERR080: Unknown element [BB] at 8539979095 size 17
ERR080: Unknown element [BB] at 8539979114 size 17
ERR080: Unknown element [BB] at 8539979133 size 17
ERR080: Unknown element [BB] at 8539979152 size 17
ERR080: Unknown element [BB] at 8539979171 size 17
ERR080: Unknown element [BB] at 8539979190 size 17
ERR080: Unknown element [BB] at 8539979209 size 17
ERR080: Unknown element [BB] at 8539979228 size 17
ERR080: Unknown element [BB] at 8539979247 size 17
ERR080: Unknown element [BB] at 8539979266 size 17
ERR080: Unknown element [BB] at 8539979285 size 17
ERR080: Unknown element [BB] at 8539979304 size 17
ERR080: Unknown element [BB] at 8539979323 size 17
ERR080: Unknown element [BB] at 8539979342 size 17
ERR080: Unknown element [BB] at 8539979361 size 17
ERR080: Unknown element [BB] at 8539979380 size 17
ERR080: Unknown element [BB] at 8539979399 size 17
ERR080: Unknown element [BB] at 8539979418 size 17
ERR080: Unknown element [BB] at 8539979437 size 17
ERR080: Unknown element [BB] at 8539979456 size 17
ERR080: Unknown element [BB] at 8539979475 size 17
ERR080: Unknown element [BB] at 8539979494 size 17
ERR080: Unknown element [BB] at 8539979513 size 17
ERR080: Unknown element [BB] at 8539979532 size 17
ERR080: Unknown element [BB] at 8539979551 size 17
ERR080: Unknown element [BB] at 8539979570 size 17
ERR080: Unknown element [BB] at 8539979589 size 17
ERR080: Unknown element [BB] at 8539979608 size 17
ERR080: Unknown element [BB] at 8539979627 size 17
ERR080: Unknown element [BB] at 8539979646 size 17
ERR080: Unknown element [BB] at 8539979665 size 17
ERR080: Unknown element [BB] at 8539979684 size 17
ERR080: Unknown element [BB] at 8539979703 size 17
ERR080: Unknown element [BB] at 8539979722 size 17
ERR080: Unknown element [BB] at 8539979741 size 17
ERR080: Unknown element [BB] at 8539979760 size 17
ERR080: Unknown element [BB] at 8539979779 size 17
ERR080: Unknown element [BB] at 8539979798 size 17
ERR080: Unknown element [BB] at 8539979817 size 17
ERR080: Unknown element [BB] at 8539979836 size 17
ERR080: Unknown element [BB] at 8539979855 size 17
ERR080: Unknown element [BB] at 8539979874 size 17
ERR080: Unknown element [BB] at 8539979893 size 17
ERR080: Unknown element [BB] at 8539979912 size 17
ERR080: Unknown element [BB] at 8539979931 size 17
ERR080: Unknown element [BB] at 8539979950 size 17
ERR080: Unknown element [BB] at 8539979969 size 17
ERR080: Unknown element [BB] at 8539979988 size 17
ERR080: Unknown element [BB] at 8539980007 size 17
ERR080: Unknown element [BB] at 8539980026 size 17
ERR080: Unknown element [BB] at 8539980045 size 17
ERR080: Unknown element [BB] at 8539980064 size 17
ERR080: Unknown element [BB] at 8539980083 size 17
ERR080: Unknown element [BB] at 8539980102 size 17
ERR080: Unknown element [BB] at 8539980121 size 17
ERR080: Unknown element [BB] at 8539980140 size 17
ERR080: Unknown element [BB] at 8539980159 size 17
ERR066: The SeekPoint at 87 references an unknown Cues at 8539840950
WRN0C0: First Block for video track #1 in Cluster at 12261830 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 13812631 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 15441105 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 24265883 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 26600904 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 28321522 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 31532622 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 78165442 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 118489390 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 212408880 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 310223640 is not a keyframe
WRN0C0: First Block for video track #1 in Cluster at 312052713 is not a keyframe

ERR0C3: Unknown track #11553 in Cluster at 314010403
ERR0C3: Unknown track #49 in Cluster at 314010403
ERR0C3: Unknown track #46 in Cluster at 314010403
ERR0C3: Unknown track #11400 in Cluster at 314010403
ERR0B2: Block at 314642666 is using an unknown track #11553
ERR0B2: Block at 314657956 is using an unknown track #49
ERR0B2: Block at 314690708 is using an unknown track #46
ERR0B0: SimpleBlock at 314690846 track #12 is laced but the track is not
ERR0B1: SimpleBlock at 314690846 track #12 is not a keyframe
ERR0B2: Block at 314712493 is using an unknown track #11400
ERR0A1: The Cluster PrevSize -?99462574776 at 314618053 should be 74869
ERR0A2: The Cluster position 233 at 314658125 should be 314010351
WRN800: The segment has Clusters but no Cues section (bad for seeking)
WRN0D0: There are 1548660 bytes of void data

file created with libebml v1.2.0 + libmatroska v1.1.0 / mkvmerge v4.5.0 ('Speed of Light') built on Feb 1 2011 02:10:32

---

The file is 8GB.
I think bug started with 4.4.0

Both HDD are checked from windows 7 and no errors.

[invincible]

Hi! Mosu, How to play mk3d? any codec to do it?

[Mosu]

Such questions are probably better posted to the Matroska users mailing list. I cannot help you with 3D video issues/questions as I have pretty much no knowledge about that topic.

[Mosu]

4.5.0
Is possible that saving on external HDD (using USB cable connection) to result in sometimes corrupted files? Saving on internal HDD I never had problems, but on two external HDD sometimes the result is like this:

Check if header removal compression is the culprit. If not then I cannot help you.

[Chumbo]

@Mosu,
Is there a way to set a default globally for items like Compression on the Extra options tab? For me, it's tedious since I have to set this on every file for every track since my players don't support this so I have to disable it. If not, any chance, when you have time, to add a settings file where we can set a global default for items like this please? Thank you for considering it.

[Mosu]

Look at the preferences.

[Chumbo]

Look at the preferences.
Oy! How did I miss that? I need to have my eyes checked. Thank you.

By the way, when I was searching the help I noticed that I can't use a "find" from within. I searched on "compression" and it found it supposedly, but the content is very large and I could not use a search from within the content window.

What help system do you use for the F1 help? I finally resorted to just pulling up the html file from the doc folder. Maybe add an option to pull up the HTML help instead? ;)

Thanks again.

[Mosu]

What help system do you use for the F1 help? I finally resorted to just pulling up the html file from the doc folder. Maybe add an option to pull up the HTML help instead? ;)

I use the one provided by the GUI toolkit I use: wxwidgets. No, I don't like it much either, but it's cross-platform and not a lot of work to set up. Therefore I'm not really keen on changing it or implementing platform-specific help systems.

[Mosu]

Hey,

I've released mkvtoolnix v4.6.0. It contains a couple of bug fixes as well as a few new features.

There are two important changes for package maintainer:

1. There’s a new translation available, Turkish.

2. mkvtoolnix requires boost 1.36 or newer for compilation.

Here are the usual links...

...to the home page: http://www.bunkus.org/videotools/mkvtoolnix/

...to the source code: http://www.bunkus.org/videotools/mkvtoolnix/sources/mkvtoolnix-4.6.0.tar.bz2

...to the Windows installer and 7zip archive: http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-unicode-4.6.0-setup.exe
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-unicode-4.6.0.7z

All binaries that I provide myself have already been uploaded.

Here's the full ChangeLog since release 4.5.0:

------------------------------------------------------------
2011-03-09 Moritz Bunkus <moritz@bunkus.org>
* Released v4.6.0.

2011-03-08 Moritz Bunkus <moritz@bunkus.org>
* build system: Fixed building the Qt version of mkvinfo's GUI (again). Fix for bug 576.

2011-02-17 Moritz Bunkus <moritz@bunkus.org>
* mmg: bug fix: If the header editor finds 'language' elements with ISO-639-1 codes (e.g. "fra" instead of "fre" for "French") then it will map the code to the corresponding ISO-639-2 code. Fix for bug 598.
* mmg: bug fix: Fixed one of the issues causing mmg to report that it is configured to use an unsupported version of mkvmerge when the reported version was actually empty.
* mkvmerge: enhancement: HD-DVD subtitles are recognized as being an unsupported file format. This makes the error message presented to the user a bit clearer. Fix for bug 600.

2011-02-15 Moritz Bunkus <moritz@bunkus.org>
* build: Boost 1.36.0 or newer is required (up from 1.34.0). Also fixed building with v3 of Boost's filesystem library, e.g. with Boost 1.46.0 Beta 1 or newer.
* mkvpropedit: new feature: Added support for adding, replacing and removing tags.

2011-02-07 Moritz Bunkus <moritz@bunkus.org>
* all: Added a translation for the programs into Turkish by ßouЯock (see AUTHORS).

2011-02-06 Moritz Bunkus <moritz@bunkus.org>
* build system: Fixed compilation if configure choses the internal versions of libebml and libmatroska while older versions are still installed in a location named with "-I..." or "-L..." in CFLAGS/CXXFLAGS/LDFLAGS or with configure's "--with-extra-includes" and "--with-extra-libs" options.
------------------------------------------------------------

Have fun.

Mosu

[b66pak]

thanks a lot...
_

[Chumbo]

Thanks Mosu for your continued efforts.

[Mystiqq]

I'm having weird problem with playback when splitting MKV file that has more than 32 tracks and when linking is used i.e. the file length is screwed somehow and playback is not working properly. I've tested with MPC-HC and KMPlayer, both use the latest Haali Media Splitter, with multiple MKV files and all have the same problem.

Example:

I took the "mewmew" example file from here (http://matroska.free.fr/samples/mewmew/) and extracted the english subtitle file out and added it in mkvmerge until i had 32 tracks in total. I split the file at 3MB and the resulting files works normally. If i added one more track and split again the length would no longer be little under minute long but shows as over minute and half in the player. The segments are somehow mixed when trying to play as linked and playing files individually after the first part does not appear to work at all.

Not sure if the problem is mkvmerge (4.6.0) or splitter, hopefully someone who knows about these things can shed some light into this.

Thanks in advance!

[Mosu]

mkvmerge has no limitation on the number of tracks. I'm pretty sure I've read somewhere that Haali's splitter has a limit of 32 tracks.

[Mystiqq]

mkvmerge has no limitation on the number of tracks. I'm pretty sure I've read somewhere that Haali's splitter has a limit of 32 tracks.

Ah, ok. Thanks! Yea it's right on the unofficial Haali Media Splitter bug thread.

Files with a large number of tracks (>32 ?) won't load.

[Mystiqq]

I'm trying to use mkvinfo to output to a file using verbose level 2 and i'm getting weird results.

mkvinfo -v -v sample.mkv -r info.txt
The entire output file, which is over 200MB, appears consists only the following lines repeated.

+ EBML head at 0
+ EBML head at 0
mm_write_cache_io_c::flush_cache(): requested 18 written 18
+ EBML head at 0
mm_write_cache_io_c::flush_cache(): requested 18 written 18
mm_write_cache_io_c::flush_cache(): requested 79 written 79
+ EBML head at 0
...


However the console outputs normally and console redirection works i.e.

mkvinfo -v -v sample.mkv > info.txt

Possibly a bug of some sort or am i missing something? :confused:

[Mosu]

I can reproduce the problem and will take a look at it, but I don't have an ETA for a fix.

[skampy]

Why does mmg seemingly continue to cause problems when muxing mkv's? I had perfectly fine x264 encode (originally muxed with mmg) that I watched all the way through, then afterwards I decided to add some .srt subtitles to it. Now, after the remux, I discover that there is a 12 second 'jump' that occurs at a certain point in the video. It is now no longer possible to seek to any frame in that 12 second gap on any of the media players I tried (VLC, MPC-HC etc).

If I let it play through to the problem point, it will jump the 12 seconds and be frozen on the last playable frame - the only way to get the video to play again (I can still hear audio though) is to seek sometime after the gap.

Why does this continue to happen with mmg (I've had many similar problems in the past) and why does mmg continue to not throw up any error or even any warning?

Both times this video was muxed was with version 4.4.0.

[GodofaGap]

Well if you aren't going to be more clear (or upload a sample with which you can reproduce the error), it's going to be hard to offer help. I've (re-)muxed dozens of files without any kind of problem.

[skampy]

Not sure how much more 'clear' I can be, I described exactly how the problem occurred.

Anyway, here is the sample you have asked for, it's only 33MB.

http://www.mediafire.com/?t298092fk6lvoph

It's a 20 second section I cut out in which the problem I am talking about occurs about 4-5 seconds into the segment clip.

[sneaker_ger]

Can you rule out any hardware errors? Like running memtest86+ for a night without any warnings? Maybe hard drive or controller errors. Also try if this is a regression, i.e. try older mkvmerge versions.
Try to find out if you can always reproduce the error on the same exact spot and upload both the original and the broken file. Maybe Mosu will take a look at it then.

[skampy]

Can you rule out any hardware errors? Like running memtest86+ for a night without any warnings?

Hardware is stable enough to encode for 40+ straight hours @ 100% CPU utilization.

Maybe hard drive or controller errors. Also try if this is a regression, i.e. try older mkvmerge versions.
Try to find out if you can always reproduce the error on the same exact spot and upload both the original and the broken file. Maybe Mosu will take a look at it then.

I have 10 hard drives, and on the several occasions this has occurred, it has been with different drives across two different controllers. But I won't rule out a controller error - how would I test for errors/problems across a HDD controller?

:thanks:

[GodofaGap]

Not sure how much more 'clear' I can be, I described exactly how the problem occurred.
Not really. Muxing srts is a rather standard operation and if it always fails there are bound to be more complaints.

Anyway, here is the sample you have asked for, it's only 33MB.

http://www.mediafire.com/?t298092fk6lvoph

This file is already broken. It would be nicer to have a working file which to then can be remuxed so that it becomes broken.

[sneaker_ger]

Hardware is stable enough to encode for 40+ straight hours @ 100% CPU utilization.

Even if it does not crash it does not necessarily mean that no errors can occur. Try memtest.

But I won't rule out a controller error - how would I test for errors/problems across a HDD controller?

I don't know myself.

Maybe try to test if you can reproduce the error on the same spot first.
I'm sorry that I'm not of great help, but if nobody is able to reproduce your problem, chances are it won't be fixed. (Assuming that it is indeed a problem with mkvmerge.)

[e.mote]

mkvmerge -q --display-dimensions TID:WxH --cropping TID:L,T,R,B infile -o outfile

Given the command above, which takes effect first, the AR adjustment, or the cropping? Or does it depend on which command is first on the commandline?

Thanks in advance for an answer.

[Mosu]

For mkvmerge the cropping parameters are completely independent of the display dimension parameters. Cropping parameters are simply written into the cropping header fields, and the same is true for display dimension parameters (mkvmerge is not a codec and does not modify the video data).

Edit: I was wrong: The Matroska specs DO mention the order: Cropping first, then scaling (see http://www.matroska.org/technical/specs/notes.html ). Nevertheless I still have no experience with the players and cropping.

[e.mote]

Mosu,

Thanks for the reply. I've no experience with MKV soft-cropping either, because I've yet to find a player that recognizes it. VLC partially sees it, and I've entered a bug report with VLC to that effect.

Given that CoreCodec is a sponsor (is that the right word?) for the MKV format, I'm hoping that CorePlayer will support it as well, and will lobby for such if not.

The below is what I'm trying to do, to better fit a widescreen video onto a 4:3 tablet, by both adjusting the AR and cropping. The MKV container spec allows both, only that cropping isn't well supported at the moment.

2.40 AR image adjustment on a 4:3 screen
http://makeagif.com/i/FrOzIy

[Mosu]

I'm trying to use mkvinfo to output to a file using verbose level 2 and i'm getting weird results.

That has been fixed in this pre-build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-4.6.0-build20110323-332-setup.exe

[73ChargerFan]

Is there a way to feed the video from an avisynth script directly into mkvmerge? It plays (video only) in mpc-hc but mkvmerge says unknown file type.

[sneaker_ger]

No, and even if it was possible the result would be totally uncompressed - probably not what you'd want.

There are softwares that may allow it through a virtual file, though. (But still uncompressed)

[space1999]

Is there a way to feed the video from an avisynth script directly into mkvmerge? It plays (video only) in mpc-hc but mkvmerge says unknown file type.

You may create a fake .AVI file with makeAVIS.exe,
set ffdshow to decode it, and then tell us what happens. :)

Still, I do not see the point of your idea. :confused:

[Mosu]

That will never work, no.

[Mystiqq]

That has been fixed in this pre-build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-4.6.0-build20110323-332-setup.exe

Thanks, I'll try it out.

[mastrandrea]

Hi, I've a little feature request: a "predicted final size" value (maybe in the bottom, near the buttons).
Would it be difficult to sum the sizes of all the streams and output the result before the muxing process?

Thanks!

[Mosu]

Impossible, sorry. mkvmerge (and therefore mmg) has no way to tell the size of each stream to merge before having processed all input files fully.

[LeMoi]

did something change in the way mkvtoolnix muxes subs in latest versions ?
With Windows/VLC :
http://img849.imageshack.us/img849/2561/vlcsnap00328.png

With ubuntu/smplayer (not my screen):
http://oi51.tinypic.com/2n18g29.jpg
See the weird char after the R of ORDINATEUR...

with Debian/smplayer (not my screen):
http://oi55.tinypic.com/muxzpu.jpg
blue big weird chars instead of subs...

mkvtoolnix 4.6.0, subs are extracted from Blu-Ray, and converted in idx/sub with BDSup2Sub 4.0.0. Didn't test with previous versions sorry

[Mosu]

Nothing has changed regarding subs.

[PowerGamer]

I have extracted DTS-HD MA track from BluRay into orig.dtsma using eac3to. I have muxed that track into .mkv using mkvmerge 4.6.0. I have extracted that audio track from created .mkv file into new.dtsma using eac3to.
Both files (orig.dtsma and new.dtsma) have the same byte-to-byte content except orig.dtsma is longer by 2080 bytes.

Why is it so (maybe it has something to do with this warning: "'orig.dtsma' track 0: force_duration_on_last_packet: forcing at 01:21:09.888000000 with 10666.666ms")? Souldn't .dtsma file be the same after muxing/demuxing it from mkv? Is it possible to make mkvmerge to not remove those extra bytes from .dtsma track at the end of the track (so that when I mux and then demux .dtsma track I get exact byte-to-byte identical file)?

EDIT: upon further experimenting it now definitely looks like a bug in mkvmegre (or maybe eac3to). When muxing new.dtsma track into .mkv and then extracting it I get new2.dtsma that is 2080 bytes shorter than new.dtsma. Repeating the same process several times (mux .dtsma obtained at the end of previous iteration into .mkv with mkvmerge, extract .dtsma from created .mkv using eac3to) each time extracted .dtsma file is 2080 bytes shorter than the .dtsma file I muxed into .mkv. This is surely wrong, the question is what program has a bug? If it is mkvmegre, please fix it.

[Mosu]

Why is it so?

Maybe the last few bytes are not a complete DTS packet?

(maybe it has something to do with this warning: "'orig.dtsma' track 0: force_duration_on_last_packet: forcing at 01:21:09.888000000 with 10666.666ms")?

That's not a warning. A warning is prefixed with "Warning:". That's a debugging message you only see because you're running with "-v".

Souldn't .dtsma file be the same after muxing/demuxing it from mkv?

Not neccessarily, no. mkvmerge throws away incomplete packets (each DTS packet has a header stating how long that packet is, if fewer bytes are available in the input file then that packet is considered incomplete) and garbage that it cannot identify as DTS (this is not the case here).

Is it possible to make mkvmerge to not remove those extra bytes from .dtsma track at the end of the track (so that when I mux and then demux .dtsma track I get exact byte-to-byte identical file)?

No.

[PowerGamer]

Mosu, please see the EDIT at my previous post. The behaviour I described (.dtsma file steadily decreasing in size after several mux/demux iterations) surely is not normal?

[Mosu]

Ok, it shouldn't get shorter each time, that's true. I really doubt mkvextract is the culprit. Looks more like mkvmerge thinks there's no full DTS packet available anymore even though there is one when the end of the input has been reached. I'll look into it.

[Mosu]

I cannot reproduce it with two DTS files I have here. Can you please upload (at least a part of) your file somewhere, e.g. to my FTP server?

[PowerGamer]

I cannot reproduce it with two DTS files I have here. Can you please upload (at least a part of) your file somewhere, e.g. to my FTP server?
Uploading that .dtsma file to your ftp now (see my PM). Also, in my testing, mkvextract produced the same output as eac3to when extracting .dtsma track from .mkv file, so yes, the problem is probably in mkvmerge.

[Mosu]

Thanks for the upload. The issue should be fixed in this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-4.6.0-build20110413-335-setup.exe