mkvtoolnix 1.4.0 is out with everything you want

[asasadad_1]

Thanks for noticing. My usual test files worked fine... I'll look into it.

thanks,both mkvtoolnix-unicode-1.4.2-build20050624-1 and mkvtoolnix-unicode-1.4.2-build20050624-2 can mux .m2v files again , but a .m2v file is showed as mpeg 1 in "tracks:" box,no problem in mkvtoolnix-unicode-1.4.2-build20050523-2.

[Mosu]

thanks,both mkvtoolnix-unicode-1.4.2-build20050624-1 and mkvtoolnix-unicode-1.4.2-build20050624-2 can mux .m2v files again , but a .m2v file is showed as mpeg 1 in "tracks:" box,no problem in mkvtoolnix-unicode-1.4.2-build20050523-2.

Thanks, found the problem, fixed in http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.4.2-build20050626-5.rar

[Great Dragon]

Please upload such a file to my FTP server (see signature).
Done.
SSA/original.ssa, extracted.ssa

[Elic]

Mosu
Do you plan to make support OGG Vorbis audiotracks with multiple logical streams (aka "chained streams"), please? I have a big problem with such files - see http://forum.doom9.org/showthread.php?p=678252.

[Mosu]

Mosu
Do you plan to make support OGG Vorbis audiotracks with multiple logical streams (aka "chained streams"), please? I have a big problem with such files - see http://forum.doom9.org/showthread.php?p=678252.

No, sorry. That you may officially simply concatenate two complete ogg files sucks, IMHO, because it makes seeking either completely slow or completely unreliable. It's also not easy AT ALL to find all the streams in such a file. The only way is to parse the file completely. And honestly, that's not what I would want to do -- e.g. read a 700 MB file twice, once for finding all headers, the second time for muxing it.

[Mosu]

Done.
SSA/original.ssa, extracted.ssa

Thanks, but unfortunately (or fortunately) I don't have a problem here. Meaning that I can mux original.ssa into a Matroska file, extract it again, and the Dialog: lines are all present including the text.

So please download the latest build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.4.2-build20050626-5.rar Extract it into your mkvtoolnix installation directory overwriting existing files and try again. It should work.

[Great Dragon]

Thanks, but unfortunately (or fortunately) I don't have a problem here.
Thanx. Latest build works fine. No blank lines after extraction ;)

[Mosu]

Thanx. Latest build works fine. No blank lines after extraction ;)

Good to know. Thanks for the feedback.

[karl_lillevold]

hmm, I cannot seem to get mkvmerge --default-duration to work in 1.4.2, while in 1.4.1, I did not need to use it. Framerate ends up being 0.0 fps w 1.4.2, no matter what I use for --default-duration, and without the option as well. Any advice? Source is RM video + audio and subtitles, but I have tested RM video only too, with no difference. Any advice?

[Mosu]

hmm, I cannot seem to get mkvmerge --default-duration to work in 1.4.2, while in 1.4.1, I did not need to use it. Framerate ends up being 0.0 fps w 1.4.2, no matter what I use for --default-duration, and without the option as well. Any advice? Source is RM video + audio and subtitles, but I have tested RM video only too, with no difference. Any advice?

Hmmm it works here. Have you tried the latest build http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-unicode-1.4.2-build20050626-5.rar ?

[karl_lillevold]

Sorry, my mistake: I had the option _after_ the input file, so it was ignored. Initially I thought I could tag it on the end of everything, since the track number is specified in the argument I did not realize it had to be in front of the input file (too used to the GUI, where in 1.4.1 I did not need this option, for some reason).

[Mosu]

Sorry, my mistake: I had the option _after_ the input file, so it was ignored. Initially I thought I could tag it on the end of everything, since the track number is specified in the argument I did not realize it had to be in front of the input file (too used to the GUI, where in 1.4.1 I did not need this option, for some reason).

The reason you need this option now is what you yourself have told me: That the FPS field in the RealMedia headers indicate the maximum FPS of a file and should therefore not be used for Matroska's "default duration" field.

[karl_lillevold]

The reason you need this option now is what you yourself have told me: That the FPS field in the RealMedia headers indicate the maximum FPS of a file and should therefore not be used for Matroska's "default duration" field.
Yes, I remember that discussion, and for a number of versions I had to use it. Then for some odd reason, and I don't remember exactly which version it started in, but I know that in 1.4.1, when I did not use that option, the Matroska framerate ended up being set to 23.976044 even though I believe maxFrameRate was set to something else (30). Anyway, requiring the option is the clearly how it needs to be, so thanks for your replies.