MKVToolNix 1.6.0 has been released

[Mosu]

Mosu, you try out mkvmerge with custom colored subtitles yet?

No, not yet, but I haven't forgotten it either. Will do that tonight.

[neo_anderson]

has anyone else experinced a little sluggish playback when avc (nerodigital) video is muxed in mkv container?

[Mosu]

has anyone else experinced a little sluggish playback when avc (nerodigital) video is muxed in mkv container?

If you've muxed such a file with mkvmerge/mmg then I suggest you try the latest build from http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/ I had to fix an issue with wrong references that Haali noticed. Maybe it doesn't fix your problem, but maybe it does. Who knows? :)

[azsd]

I have an Anamorphic encoded mp4 file with dimensions 480x560,I wan't to it play at 480x280 framesize, when I set Display width/height to 480 and 280,the muxed file played as 960x560.

is the mkvmerge can set the frame size in mkv container?
Is the "--display-dimensions" only used the frame size to calculates AR?

thx

[TNM]

Hi, I have a question. If the audio is longer than the video, is there a way for mkvtoolnix to cut off the audio just when the video ends? you know, like the way vdub/mod does it..

[azsd]

--default-duration <TID:Xms|us|ns>
Force the default duration of a track to X.
is this arg may set the during of the audio track

[Mosu]

I have an Anamorphic encoded mp4 file with dimensions 480x560,I wan't to it play at 480x280 framesize, when I set Display width/height to 480 and 280,the muxed file played as 960x560.

is the mkvmerge can set the frame size in mkv container?
Is the "--display-dimensions" only used the frame size to calculates AR?

thx

If you set display width and display height then on playback the video should be resized to that exact size. If it doesn't then the player/filter/decoder is at fault. Unfortunately I have no clue about what you have to do on Windows in order to get that working. Someone mentioned "overlay" in combination with "ffdshow", but again that may be totally wrong :)

[Mosu]

Hi, I have a question. If the audio is longer than the video, is there a way for mkvtoolnix to cut off the audio just when the video ends? you know, like the way vdub/mod does it..

No, mkvmerge does not support this.

[Mosu]

is this arg may set the during of the audio track

Nope. That option does something else.

[niamh]

azsd : it could be directvobsub at fault. check the picture resizing in "general" (if it loads at playback, of course). It's defaulted to double if smaller than 384x288

[Liisachan]

MMG is not Unicode enabled.
For instance, MMG failes to open a file when the filename is a French/Korean mix, saying
--------------------
File identification failed

File identification failed for 'C:\????.avi'. Return code: 2
--------------------

???? is what originally is a French/Korean mix, but it is displayed as "???" literally.
Is this a known limitation?

[Mosu]

MMG is not Unicode enabled.

Knowing you I won't ask if you've used the Unicode build ;) But maybe you could tell me how I could create such a file name myself with my German keyboard and which Windows components I have to install so that I can check it out.

Is this a known limitation?

Only for the non-Unicode build, but I can only test with German Umlauts (which are not ASCII anymore, so it's at least half a test).

[Liisachan]

You can copy and paste a random string from (for instance) a Korean webpage, after installing East Asian Language Support:
e.g. "꽃의 마법사 매리벨.avi"

Another thing:
Apparently Windows OS does unwanted service for stdio when the System Locale is CJK:
it tries to read a UTF-8 string as a legacy multibyte string (without converting properly), and as a result, a part of the UTF-8 string is discarded if that part is illegal as the MB string in question (such as Shift_JIS). UTF-8 is "ASCII-transparent" but NOT CJK-transparent.

Simply put, "Title" stored in MKV may be broken in this utf8.txt:
mkvinfo file.mkv > utf8.txt
Even when the title is in Japanese, and the System Locale is Japanese.
Why? Because that silly DOS Box (standard output) tries to interpret the UTF-8 string passed from mkvinfo as Shift_JIS, and fails.

The similar thing can happen in input too, but I found a workaround for input:
mkvmerge --command-line-charset UTF-8 -o out.mkv @command.utf8

This way, UTF-8 strings (track names, titles) in command.utf8 won't be broken even when direct input wouldn't work. This workaround should work for the above problem about MMG, but still, output is foobared. I'd need something like this so that Windows won't mess with my UTF-8 strings.
mkvinfo file.mkv -o info.txt

[Mosu]

You can copy and paste a random string from (for instance) a Korean webpage, after installing East Asian Language Support:
e.g. "꽃의 마법사 매리벨.avi"

Thanks, Haali tried to coach me through this as well. Unfortunately I cannot reproduce this. I've tried file names with German Umlaute, Arabic and Latin chars as well as the file name you've used as an example. They are all muxed just fine.

Another thing:
...
The similar thing can happen in input too, but I found a workaround for input:
mkvmerge --command-line-charset UTF-8 -o out.mkv @command.utf8

This is what mmg does as well (not only for the charset reason, also because the command line length on Windows is VERY limited). mmg puts all arguments into such a file with a UTF-8 BOM.

This way, UTF-8 strings (track names, titles) in command.utf8 won't be broken even when direct input wouldn't work. This workaround should work for the above problem about MMG, but still, output is foobared.

Well, it does already work here... And mmg already uses such a file. You can check for such a file if you mux but don't close the muxing window. The command file should be in the user's temporary directory (which is usually something like "C:\Documents and Settings\UserName\Local Settings\Temp") and called mmg-mkvmerge-options-... in case you want to take a look at it.

I'd need something like this so that Windows won't mess with my UTF-8 strings.
mkvinfo file.mkv -o info.txt

This is easy to add. That doesn't solve your problem with mmg/mkvmerge, though...

[Liisachan]

It's really weird, but just re-installing MKVToolnix fixed my problem. :confused:
I think I was using Unicode build, because mkvmerge was able to handle a French/Japanese mix even when I was having that MMG problem...but sorry, I wasted your time anyway...

and I was wrong in another thing: out.txt in mkvinfo file.mkv > out.txt is not in UTF-8 but System Code Page. (Is this by design?) If so...
This is easy to add. That doesn't solve your problem with mmg/mkvmerge, though...
...what I'd really want to have is, something like:
mkvinfo file.mkv --output-charset UTF-8 -o utf8.txt

[Mosu]

It's really weird, but just re-installing MKVToolnix fixed my problem. :confused:
I think I was using Unicode build, because mkvmerge was able to handle a French/Japanese mix even when I was having that MMG problem...but sorry, I wasted your time anyway...

Don't worry. I'm on vacation at the moment, and I actually enjoy coding and bug hunting if I'm not as pressed for time as I've been during the last few weeks/months. And I'm just happy that it works for you now.

and I was wrong in another thing: out.txt in mkvinfo file.mkv > out.txt is not in UTF-8 but System Code Page. (Is this by design?) If so...

...what I'd really want to have is, something like:
mkvinfo file.mkv --output-charset UTF-8 -o utf8.txt

The -o part is already done. I'll do the --output-charset option next.

[Liisachan]

If you are going to add that thing, could you please think about this while you're at it?
http://forum.doom9.org/showthread.php?p=691095#post691095
This can be easily done manually, but...
mkvinfo (or mkvextract) timecode file.mkv -o v2.tm

[Mosu]

If you are going to add that thing, could you please think about this while you're at it?
http://forum.doom9.org/showthread.php?p=691095#post691095
This can be easily done manually, but...
mkvinfo (or mkvextract) timecode file.mkv -o v2.tm

Hmm yeah, I'll do that. Anyway, use this for --output-charset and -o:

http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050803-7.rar

[Mosu]

On another matter.

There has always been an issue with mkvmerge's handling of B frames if external timecode files were used. Up until yesterday the order of timecodes in a v2 timecode file had to match how B frames were timestamped, and other timecode file formats weren't useful at all because they screwed up the order of timecodes. For example, the simple frame sequence IPBBP... at 25 FPS required a timecode file like this:

# timecode format v2
0
120
40
80
...

I've fixed mkvmerge now so that it assigns timecodes properly. But this means that timecodes in v2 format files have to be ordered now. For the same example above you now need this file:

# timecode format v2
0
40
80
120
...

The advantage is clear: You do now need to know which frames are what prior to creating such a file. The disadvantage is that old timecode files will not work with mkvmerge >= 1.5.1 (which will be released shortly) anymore. But the advantage clearly outweighs the disadvantage. I will probably include a warning if the timecodes from a v2 file are not ordered, so that users might actually see that there's something wrong ;)

The tool that you, Liisachan, wants for extracting timecodes would of course take this into account and re-order the timecodes as they're read from the Matroska file before outputting them so that mkvmerge will not complain.

[Liisachan]

Hmm yeah, I'll do that. Anyway, use this for --output-charset and -o:

http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050803-7.rar

Thanks for your swift work.
Test results:

mkvinfo -o def.txt = Worked fine, Windows Code Page
mkvinfo --output-charset UTF-8 -o utf8.txt = Worked fine, without BOM

So, practically everything is now possible, but I tested UTF-16 too, and these --output-charset don't work, giving me an almost blank output file.
UTF-16, UTF-16LE, UTF-16BE, UCS-2

And "--output-charset UTF16" will give me this message:

Warning: Could not initialize the iconv library for the conversion from UTF16 to UFT-8. Some strings will not be co
nverted to UTF-8 and the resulting Matroska file might not comply with the Matroska specs (error: 22, Invalid argum
ent).
Warning: Could not initialize the iconv library for the conversion from UFT-8 to UTF16. Some strings cannot be conv
erted from UTF-8 and might be displayed incorrectly (error: 22, Invalid argument).

Maybe iconv doesn't like "UTF16" and it wants a hyphen ("UTF-16")

[Liisachan]

On another matter.

# timecode format v2
0
120
40
80
...

...For the same example above you now need this file:

# timecode format v2
0
40
80
120
...
If all that's needed is 0 120 40 80 --> 0 40 80 20 conversion, technically mkvmerge could just automatically "sort" the timestamps in increasing order, couldn't it?
Afaik, avi2timecode.exe outputs timestamps in increasing order even if the input AVI has b-vops (so mkvmerge1.5.1-compatible?)

[Mosu]

Thanks for your swift work.
Test results:

mkvinfo -o def.txt = Worked fine, Windows Code Page
mkvinfo --output-charset UTF-8 -o utf8.txt = Worked fine, without BOM

Ah yes, the BOM. Hmm... I'll have to add that somehow.

So, practically everything is now possible, but I tested UTF-16 too, and these --output-charset don't work, giving me an almost blank output file.

Yeah. Unfortunately wide char output does not work anywhere in mkv*. Changing that would require some big changes. If I really wanted to do it right I'd use wide strings everywhere instead of UTF-8 coded normal strings. I didn't do that because older gcc versions contained a VERY nasty bug totally preventing the use of wide strings. And changing everything now is... well... a huge task. So for the moment I won't do that. Sorry.

And "--output-charset UTF16" will give me this message:

Warning: Could not initialize the iconv library for the conversion from UTF16 to UFT-8. Some strings will not be co
nverted to UTF-8 and the resulting Matroska file might not comply with the Matroska specs (error: 22, Invalid argum
ent).
Warning: Could not initialize the iconv library for the conversion from UFT-8 to UTF16. Some strings cannot be conv
erted from UTF-8 and might be displayed incorrectly (error: 22, Invalid argument).

Maybe iconv doesn't like "UTF16" and it wants a hyphen ("UTF-16")

Correct. iconv only knows the versions with the hyphen, and I simply pass the string the user enters to iconv.

[Mosu]

If all that's needed is 0 120 40 80 --> 0 40 80 20 conversion, technically mkvmerge could just automatically "sort" the timestamps in increasing order, couldn't it?

Correct, and that's how I've implemented this feature now.

Afaik, avi2timecode.exe outputs timestamps in increasing order even if the input AVI has b-vops (so mkvmerge1.5.1-compatible?)

That is definitely 1.5.1-compatible. So avi2timecode doesn't have to be changed at all (which is good news indeed).

If you want to try out mkvextract's new timecodes_v2 mode then please download (... waiting for the build to finish ...) http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050803-8.rar


The command line should be something like mkvextract timecodes_v2 input.mkv 1:timecodes-track1.txt 2:same-for-track-2.txt

Basically just like the format for the "tracks" extraction mode.

[Liisachan]

I think if you really need to output in UTF-16, you can easily convert UTF-8 to 16 by yourself. (But that's what I just think without knowing the inside of mkv*)

If you want to try out mkvextract's new timecodes_v2 mode then please download (... waiting for the build to finish ...) http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050803-8.rar


The command line should be something like mkvextract timecodes_v2 input.mkv 1:timecodes-track1.txt 2:same-for-track-2.txt as a starter I tested it for a clip with a constant frame rate (23.976fps), but the out put is like
0.000000
42.000000
83.000000

Shouldn't it be
0.000000
41.708375
83.416750
if the fractional part (<1ms) matters...?

[Mosu]

as a starter I tested it for a clip with a constant frame rate (23.976fps), but the out put is like
0.000000
42.000000
83.000000

Shouldn't it be
0.000000
41.708375
83.416750
if the fractional part (<1ms) matters...?

No. I mean yes, that would be correct if the Matroska file in question used nano-second precision for timecodes, but usual Matroska files only use milli-second precision. Audio-only files use sample precision.

[Rayek]

Threads like this one keeps adding to the utter crapability of threads like this one. (http://www.tokyotosho.com/forums/viewtopic.php?t=524) Keep up the good work.

[Mosu]

Threads like this one keeps adding to the utter crapability of threads like this one. (http://www.tokyotosho.com/forums/viewtopic.php?t=524)

Ah yes, GUTB. The one whose first post was such a nice insult to.. well me, effectively. I love suck folks :)

Keep up the good work.

I'm definitely trying to :)

[Mosu]

mkvinfo --output-charset UTF-8 -o utf8.txt = Worked fine, without BOM

It'd be nice if you tried http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050803-9.rar which does include a BOM. Actually I've implemented --output-charset and --redirect-output (as it is now called, not --output anymore, because that is used by mkvmerge for the output Matroska file already) (or short "-r") for all three programs. It might have broken something, though, but I hope it didn't.

Please be careful that you don't download builds after -9 for the time being because I'm experimenting with different wxWidgets versions, and the newer builds that will pop up will be linked against those and won't work with the runtime files that are available.

[Pirks]

I've got a couple of .mov files from a friend, both made in QuickTime 7.0 on his Mac, both with H.264 video and AAC 5.1 audio. Since I don't own a Mac and QuickTime 7.0 for Windows is not very usable at the moment, plus eats almost 100% of CPU while playing these files back, I decided to remux them in Matroska. I downloaded mkvtoolnix 1.5.0 for Windows, Unicode build (I use WinXP) and loaded these .mov files in mmg. They loaded OK, showed two tracks, avc1 video and mp4a audio. The trouble starts when I try to mux these tracks in mkv. So, I set the output file name and then press "Start muxing" button. I do not change any other options, everything is left at default. The muxing window appears and then there's a message immediately printed in the "Warning" pane, saying: "Warning: Quicktime/MP4 reader: The audio track 2 is using an unsupported 'object type id' of 0 in the 'esds' atom. Skipping this track." The resulting mkv is playable, but of course without sound. Well, actually one of these files won't play even video after remuxing, but let's focus on the audio problem for now. I can provide you with more info, or even send you a sample of that file, or its audio track, if you are interested. I don't know yet how to demux AAC 5.1 stream from .mov made by QT 7, and I don't know how to split those mov's, but I'll ask around on doom9 forums if demuxing or cutting a sample for you is necessary.

[Mosu]

The muxing window appears and then there's a message immediately printed in the "Warning" pane, saying: "Warning: Quicktime/MP4 reader: The audio track 2 is using an unsupported 'object type id' of 0 in the 'esds' atom. Skipping this track."

Hmm, I've never had my fingers on a Quicktime file with AAC inside. So yes, it'd be great if you could upload such a file to my FTP server (see my signature).

[thana]

hi mosu!

great to hear that you have some time again for coding (and actually having fun while doing it). and as you said you are looking into new wxwidgets versions anyway, i would like to make a suggestion for mmg:

i think that it would be way more logical for the settings and the chaptereditor to be in seperate windows instead of tabs. as it is right now, it is a bit confusing for first time users that loaded chapters in the chaptereditor are not gonna ending up in the muxed file, and that the chaptereditor actually has no logical connection with the rest of the gui.. by removing 'settings' and 'chaptereditor' and making them available in seperate windows f.e. via entries in the file menu, all tabs that are left then (input, attachments, global) are the ones which actually belong to the muxing-process.. and this is still the main purpose of mmg and should be as straight forward as possible.. i know its probably a lot of work, and not really necessary for the regular users of mmg (as they most probably know these things), but it would actually simplify mmg and make it more accessible for 'newbies'..

what do you think about this?

[Liisachan]

It'd be nice if you tried http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050803-9.rar which does include a BOM. Actually I've implemented --output-charset and --redirect-output (as it is now called, not --output anymore, because that is used by mkvmerge for the output Matroska file already) (or short "-r") for all three programs. It might have broken something, though, but I hope it didn't.

Please be careful that you don't download builds after -9 for the time being because I'm experimenting with different wxWidgets versions, and the newer builds that will pop up will be linked against those and won't work with the runtime files that are available. mkvtoolnix-unicode-1.5.0-build20050803-9.rar and after -9...
you sure work a lot :D
And yes, now the file generated with --output-charset UTF8 has BOM.
Actually, when I said "I got a UTF-8 without BOM" I just reported the fact and I didn't mean "there should be BOM." Although BOM is generally good to reduce ambiguity...

EDIT:
mkvinfo file1.mkv --output-charset UTF-8 > info.txt
gives me CR+CR+LF at the end of each line. Weird. Looks like Windows standard IO service gets in my way, adding an extra CR to each line... Anyway, im going to use -o always, not > nor >> since I don't believe Windows.

[Pirks]

Hmm, I've never had my fingers on a Quicktime file with AAC inside. So yes, it'd be great if you could upload such a file to my FTP server (see my signature).

Just uploaded file oops.mov, muxed in QuickTime 7.0 on a Mac, H.264 video and AAC 5.1 audio. Keep us posted how things are going, I'd really love to get rid of QT movies on my machine. Thanks in advance!

[Mosu]

i think that it would be way more logical for the settings and the chaptereditor to be in seperate windows instead of tabs.

I fully agree. Making the chapter editor "just" another tab was a decision I've come to regret. But I'm not willing to spend that much time with wxWidgets anymore as there are things that have ticked me off time and again.

However, at the moment I'm working with Qt at work, and I'm enjoying it. As Qt 4 also has a GLP port for Windows I'm inclined to port mmg from wxWidgets to Qt 4 in the near future. If I do that (actually I've already started doing the main dialog) then the chapter editor will be in a separate window. Until then I will probably not change it.

[Mosu]

mkvtoolnix-unicode-1.5.0-build20050803-9.rar and after -9...
you sure work a lot :D

Nah. I was just trying to nail a bug that only occured on Windows. But I don't have a development environment on this Windows computer. So I compile on my server, create a new build, download it and test it here on Windows. This accounts for at least half of those builds ;)

And yes, now the file generated with --output-charset UTF8 has BOM.
Actually, when I said "I got a UTF-8 without BOM" I just reported the fact and I didn't mean "there should be BOM." Although BOM is generally good to reduce ambiguity...

Maybe you didn't, but I did think that there should be a BOM :)

EDIT:
mkvinfo file1.mkv --output-charset UTF-8 > info.txt
gives me CR+CR+LF at the end of each line. Weird. Looks like Windows standard IO service gets in my way, adding an extra CR to each line... Anyway, im going to use -o always, not > nor >> since I don't believe Windows.

Ok, so I'll ignore this for the time being. If it bothers you then tell me to fix it.

[Mosu]

Just uploaded file oops.mov, muxed in QuickTime 7.0 on a Mac, H.264 video and AAC 5.1 audio. Keep us posted how things are going, I'd really love to get rid of QT movies on my machine. Thanks in advance!

Thanks. I'll see what I can do.

[Liisachan]

Ok, so I'll ignore this for the time being. If it bothers you then tell me to fix it. Will you try to check if this is something that can be fixed easily? Personally, I could say I wouldn't mind, but obviously you broke something, since this simple commandline:
mkvinfo file.mkv > info.txt
doesn't work anymore on my Win2K as it did (you get CR CR LF as EOL), even without the --output-charset.

[Skaarj]

Forsed subtitles are planned in the near future?

And reproduction simultaneously two sound tracks (the original + translation)?

[Mosu]

Will you try to check if this is something that can be fixed easily? Personally, I could say I wouldn't mind, but obviously you broke something, since this simple commandline:
mkvinfo file.mkv > info.txt
doesn't work anymore on my Win2K as it did (you get CR CR LF as EOL), even without the --output-charset.

That's very strange, because I get the normal CR LF here on Windows XP with cmd.exe and the latest from the pre-directory.

Ah wait, you're right. That's interesting... Will check it.

[Mosu]

Sorry, Liisachan, but Windows is doing stuff that I simply cannot understand. If the only thing I do in my program is

fprintf(stdout, "test\r\n");

and redirect this into a file then it still ends up as CR CR LF just like you saw. Maybe there is something I can do about it, but I don't know what it is.

[Liisachan]

It sounds like fopen("w") vs. fopen("wb")
In ASCII mode or fopen("w"), Windows converts \n to \r\n, hence \r\n to \r\r\n

[Mosu]

It sounds like fopen("w") vs. fopen("wb")
In ASCII mode or fopen("w"), Windows converts \n to \r\n, hence \r\n to \r\r\n

It's not like I fopen stdout myself ;) But I can fix that.

[Mosu]

Everyone creating timecode files please read http://forum.doom9.org/showthread.php?t=98573 Thanks

[thana]

i found two files which can't be read by latest mkvmerge:
>mkvmerge -i G:\Quake4Multi.mp4

Error: Quicktime/MP4 reader: Invalid chunk size 2 at 92.the file can be played without problems with haali-splitter+ffdshow and mplayer/vlc

the other:
>mkvmerge -i G:\Quake4cycle1.mov

Error: File G:\Quake4cycle1.mov has unknown type. Please have a look at the supported file types ('mkvmerge --list-types') and contact the author Moritz Bunkus <moritz@bunkus.org> if your file type is supported but not recognized properly.this one can be played too with quicktime and mplayer. the fourcc seems to be 'JPEG', which is some 'Microsoft - Motion JPEG DIB Format'

i uploaded both files on your ftp

[Mosu]

i found two files which can't be read by latest mkvmerge:
the file can be played without problems with haali-splitter+ffdshow and mplayer/vlc

the other:
this one can be played too with quicktime and mplayer. the fourcc seems to be 'JPEG', which is some 'Microsoft - Motion JPEG DIB Format'

i uploaded both files on your ftp

Fixed file recognition for both files. The first one can now be muxed normally. The second cannot because Motion JPEG tracks are not supported by mkvmerge (nor specified for Matroska if I'm not mistaken).

Please download this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050813-1.rar

[Pirks]

Please download this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050813-1.rar

Is the AAC 5.1 demuxing bug fixed in that build?
Just checking, maybe I should also download and try it :-)

[Mosu]

Is the AAC 5.1 demuxing bug fixed in that build?
Just checking, maybe I should also download and try it :-)

You mean the oops.mov sample? No, it isn't. Those two issues I've fixed were unrelated.

[Mosu]

Is the AAC 5.1 demuxing bug fixed in that build?
Just checking, maybe I should also download and try it :-)

You can download http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050814-1.rar which should work with such files now.

[Mosu]

It sounds like fopen("w") vs. fopen("wb")
In ASCII mode or fopen("w"), Windows converts \n to \r\n, hence \r\n to \r\r\n

Ok, you can try http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.5.0-build20050816-1.rar if you want :)

[Liisachan]

thanks Mosu,
like i said before, mkvinfo v1.5.0 was fine with
mkvinfo file.mkv > info.txt
(info.txt gets \r\n for eol not \r\r\n)
so I thought somethinw was broke after 1.5.0 when you added the -o feature...
glad if that is fixed now :)
i'll test more later, but mkvtoolnix seems to be quite stable now...

another (unrlated) question:
is there any option that I can force mkvmerg to use 64bit-timestamps even for video,
like it did in 0995?