mkvtoolnix 4.1.1 released

[Mosu]

I've noticed that the same mpeg-4 asp .avi (dx50, xvid, etc.) muxed in mkv with native and vfw modes, uses more cpu on playback in native mode than vfw mode.

How much more and on what kind of a CPU? (This might be due to the timecodes having to be reordered and frames to be cached, I'm not sure... I don't know how demuxers handle those out-of-order timecodes.)

[Isochroma]

It's probably the splitter's issue, so no need to worry. Athlon XP and some old hi-def material that I encoded (1368x768), before I discovered WMV2.

[madshi]

@Mosu, just noticed that in the latest mkvtoolnix software it's possible to explicitly deny the "default" state of a track. That's VERY nice. Why? Because I want to have subtitles in my movies, but I don't want them to be activated by default. Up until now MPC always showed subtitles by default. I thought it was just a bad decision by MPC. But now actually I understand that mkvtoolnix always marked one subtitle track as default and MPC just obeyed. Now when I mux subtitles to my movies and say "no" for all subtitles, MPC doesn't activate any subtitles by default, anymore. Great!!

There's one bug, though: When I have a MKV movie which has already subtitles in it and if one of the subtitle tracks is already marked as default, I cannot undo the "default" marking, anymore. Even explicitly specifying "--default-track 4:no" doesn't remove the "default" marking. Would you mind looking into this, when you have some time? It isn't urgent, but having this fixed would be nice.

[Mosu]

This feature was neccessary because pretty much all player/splitter developpers were mis-intepreting the Matroska specs. Anyway... I'll look at the bug.

[Palikrovol]

@Mosu, just noticed that in the latest mkvtoolnix software it's possible to explicitly deny the "default" state of a track. That's VERY nice. Why? Because I want to have subtitles in my movies, but I don't want them to be activated by default. Up until now MPC always showed subtitles by default. I thought it was just a bad decision by MPC. But now actually I understand that mkvtoolnix always marked one subtitle track as default and MPC just obeyed. Now when I mux subtitles to my movies and say "no" for all subtitles, MPC doesn't activate any subtitles by default, anymore. Great!!


What's the difference between 'default' and 'yes' in the "Default track flag"?

[Mosu]

What's the difference between 'default' and 'yes' in the "Default track flag"?

"Yes" forces this track to be the default track for its kind (audio, video, subtitles). "Default" lets mkvmerge make this decision. If all track of a kind are set to "Default" then mkvmerge will a) honor the source container's "Default Track Flag" (only relevant if you're copying from Matroska files at the moment) and b) mark the first track found of each kind as being the default track if no flag was found in the source containers.

[madshi]

@Mosu: A somewhat strange question. Would it be difficult/time consuming for you to add a feature to mkvmerge, which would allow to:

(1) Extract a specific key frame (eventually with following non-key frames) to a new mkv. And:
(2) Remove a specific range of key frames from the mkv?

If that would be very easy for you to realize that would be a nice feature, cause it would allow to remove advertising out of H.264 videos - which no software can do today. Eventually somebody could even write a little GUI program based on such mkvmerge features which allows cutting of mkv movies.

But if it's not as simple as just doing "splitting" + "joining" (which you already can do) with just some other parameters, then please don't spend time on this. There are probably more important things to spend time on.

[Mosu]

Yeah, it's not as easy as it may sound ;) I've been asked to implement such a "use only these frames" feature from time to time, but it would require a lot of time to implement. So not in the near future.

[madshi]

Ok, thanks... :)

[Jaxel]

okay... I am having one other issue... I have noticed, any period with "no-sound" is recorded by mkvmerge as non-MP3 data. For instance, at the beginning of my video, I may have a few frames of silence... this is what mkvmerge will tell me...

mkvmerge v2.0.0 ('After The Rain Has Fallen') built on Feb 1 2007 08:56:12
'Z:\nh3.demo.Ougi.Part1.avi': Using the AVI demultiplexer. Opening file. This may take some time depending on the file's size.
'Z:\nh3.demo.Ougi.Part1.avi' track 0: Using the MPEG-4 part 10 ES video output module.
'Z:\nh3.demo.Ougi.Part1.avi' track 1: Using the MPEG audio output module.
The file 'Z:\nh3.demo.Ougi.Part1.mkv' has been opened for writing.
The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 315 bytes of non-MP3 data at the beginning.
This corresponds to a delay of 19ms. This delay will be used instead of the garbage data.
The cue entries (the index) are being written...
Muxing took 8 seconds.


Now this isnt a problem, it automatically writes in a 19ms delay to even out the areas of non-MP3 data (which is nothing more than "no-sound"). The problem I have is during the video in between scenes, there are also points of "no-sound". I didn't put these points in, when I was recorded the videos off my PS2, during these times, there was just no-sound playing. So during the encode I get the following:

Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 358 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 252 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 168 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 178 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 101 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 199 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 91 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 344 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 92 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 394 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 159 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 264 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 48 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 147 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 332 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 344 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 368 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 158 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 112 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 347 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 42 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 186 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 80 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 323 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 228 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 253 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 42 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 252 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 416 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 217 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 58 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 364 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 178 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 319 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 51 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 305 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 228 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 203 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 41 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 344 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 134 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 379 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 30 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 42 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 277 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 52 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 319 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 279 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 37 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 299 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 137 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 67 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 403 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 66 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 198 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 72 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 60 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 121 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 147 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 317 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 113 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 146 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.
Warning: The MPEG audio track 1 from 'Z:\nh3.demo.Ougi.Part1.avi' contained 256 bytes of non-MP3
data which were skipped. The audio/video synchronization may have been lost.


Each part is not a lot of data... 100-300 bytes here and there isnt a problem... But when this happens 50 times in a single video, by the end the sound is out of sync. Is there any way to get mkvmerge to ignore these errors and keep these bytes intact? Or possibly replace these bytes with delays equivalent to the timing?

Here is the link to the AVI-VFW video I am trying to mux in mkvmerge...
http://www.crookedjester.com/downloads/nh3.demo.Ougi.Part1.avi

[Mosu]

okay... I am having one other issue... I have noticed, any period with "no-sound" is recorded by mkvmerge as non-MP3 data.

Which is exactly what it is. Your "no sound" is actually filled with bytes, but they're just random or whatever you may call it. Such random stuff is not allowed in Matroska, so mkvmerge skips them. Until now I only encountered such stuff at the beginning of a file but never in the middle, especially not so many occurences.

Each part is not a lot of data... 100-300 bytes here and there isnt a problem... But when this happens 50 times in a single video, by the end the sound is out of sync. Is there any way to get mkvmerge to ignore these errors and keep these bytes intact? Or possibly replace these bytes with delays equivalent to the timing?

Replacing them with silent MP3 frames is possible but risky. Each MP3 frame contains 1152 samples, so depending on the sample rate each MP3 frame is 26ms (44100 Hz) or 24ms (48000 Hz) long. Meaning that depending on the length of garbage found sound could still go out of sync.

What I could do is calculate the gap's length and add that to the timecodes from that point on. I don't know how players will react, but they SHOULD do the right thing. Don't count on me getting this ready in the next few days, though.

Here is the link to the AVI-VFW video I am trying to mux in mkvmerge...
http://www.crookedjester.com/downloads/nh3.demo.Ougi.Part1.avi

Downloading, thanks for the sample.

[LeMoi]

http://www.bunkus.org/videotools/mkvtoolnix/avc-status.html seems to be outdated :)

[Jaxel]

Ah... well I figure, in between each scene in the video is a menu system on the PS2 game... so I cut those menu system scenes out of the final video... I guess when I was cutting the video, I cut in the middle of samples, so the garbage data are split samples in between scenes.

[tjf]

For long time I have problem with asigning language to a subtitle. The last version where it worked properly was 1.7.

I have x264 video, with AC3 audio, chapters and two srt subtitle streams. English and Czech. Here is the screenshot and command line output for v 1.7:

http://www.volny.cz/tfojta/mkv/170.png

"mkvmerge" -o "E:\Movies\Ice Age\Ice Age1.mkv" --language 1:eng --track-name "1:Ice Age" --default-track 1 --aspect-ratio 1:1.911 -d 1 -A -S "E:\Movies\Ice Age\Ice Age.mkv" --language 0:eng -a 0 -D -S "E:\Movies\Ice Age\Ice Age T02 3_2ch 448Kbps DELAY 0ms.ac3" --language 0:eng -s 0 -D -A "E:\Movies\Ice Age\English.srt" --language 0:cze -s 0 -D -A "E:\Movies\Ice Age\Czech.srt" --track-order 0:1,1:0,2:0,3:0 --chapters "E:\Movies\Ice Age\chapters.txt"

And this is from 2.0. Notice the missing language properties in the command line.

http://www.volny.cz/tfojta/mkv/200.png

"mkvmerge" -o "E:\Movies\Ice Age\Ice Age.mkv" --language 1:eng --track-name "1:Ice Age" --default-track 1 --aspect-ratio 1:1.911 -d 1 -A -S "E:\Movies\Ice Age\Ice Age.mkv" --sync 0:0 -a 0 -D -S "E:\Movies\Ice Age\Ice Age T02 3_2ch 448Kbps DELAY 0ms.ac3" --language 0:eng -s 0 -D -A "E:\Movies\Ice Age\English.srt" -s 0 -D -A "E:\Movies\Ice Age\Czech.srt" --track-order 0:1,1:0,2:0,3:0 --chapters "E:\Movies\Ice Age\chapters.txt"

Is it a bug or am I doing something wrong?

Tomas

[Mosu]

For long time I have problem with asigning language to a subtitle. The last version where it worked properly was 1.7.

...

I cannot reproduce this on Windows. Please tell me exactly what you've done. Meaning each and every mouse click, track change, whatever.

[tjf]

I cannot reproduce this on Windows. Please tell me exactly what you've done. Meaning each and every mouse click, track change, whatever.


Input files:
Add -> select file "Ice age.mkv"
Add -> select file "English.srt"
Add -> select file "Czech.srt"

Tracks:
highlight SRT (ID0, type: subtitles) from English.srt ...

General track options
Language: select English

Tracks:
highlight SRT (ID0, type: subtitles) from Czech.srt ...
Language: select Czech

I see no change in Command line (the Czech parameter is not added)

"mkvmerge" -o "E:\Movies\Ice Age\Ice Age.mkv" --language 1:eng --default-track 1 --display-dimensions 1:45x34 -d 1 -A -S "E:\Movies\Ice Age\Ice Age.mkv" --language 0:eng -s 0 -D -A "E:\Movies\Ice Age\English.srt" -s 0 -D -A "E:\Movies\Ice Age\Czech.srt" --track-order 0:1,1:0,2:0

If I switch away in tracks and return to the Czech.srt, the Language in General track options says 'und (Undetermined)'

Tomas

[Mosu]

Thanks for the info. Last question: Which mkvmerge build is your 2.0.0 build? Unicode / non-Unicode? Exact version information (you can find this under "Help" -> "About" -> "...built on DATE")?

[tjf]

Thanks for the info. Last question: Which mkvmerge build is your 2.0.0 build? Unicode / non-Unicode? Exact version information (you can find this under "Help" -> "About" -> "...built on DATE")?

unicode, Jan 13 2007 20:06:07

[tomos]

Hi,

I'm wondering if there is any way to get mkvmerge to see DD+ audio tracks correctly? At the moment, it sees them as video tracks for some reason.

when i drop the track in i get:

Message
---------------------------
You're adding an AVC/h.264 elementary stream to the output file. mkvmerge cannot determine the number of frames per second for such files itself. Therefore you have to set this parameter yourself on the 'format specific options' page.

If you don't do this then mkvmerge will assume 25 fps.

This message will only be shown once unless you have enabled mmg's warnings on its 'settings' page.

once i OK this, mkvmerge sees the files as:

mpeg-4 part 10 ES (ID 0, type: video)

but this is just the plain audio - no video at all. the ddp files plays fine in mpc

i am using v2 btw,
mkvmerge GUI v2.0.0 ('After The Rain Has Fallen')
built on Jan 13 2007 20:25:47

[Isochroma]

Same here...

[Mosu]

Hi,

I'm wondering if there is any way to get mkvmerge to see DD+ audio tracks correctly? At the moment, it sees them as video tracks for some reason.

What is DD+? Modified AC3 from HD DVDs or something like this?

[tomos]

as far as i know, yes. - well, demuxed from hd-dvds

[madshi]

What is DD+? Modified AC3 from HD DVDs or something like this?
http://en.wikipedia.org/wiki/Dolby_Digital_Plus

[madshi]

@Mosu, just got a bunch of lines like this:

Warning: pr_generic.cpp/generic_packetizer_c::add_packet(): timecode < last_timecode (00:00:00.934 < 00:00:00.984) for 1 of 'D:\Honey.mkv'. This should not have happened. Please contact the author [...] with this error/warning message, a description of what you were trying to do, the command line used and which operating system you are using. Thank you.
Here's the command line:

"mkvmerge" -o "D:\Honey new.mkv" --language 1:eng --default-track 1:yes --display-dimensions 1:1920x1080 -d 1 -A -S "D:\Honey.mkv" --track-order 0:1
Originally I wanted to replace the one and only english AC3 audio track in Honey.mkv with a new one. But I can reproduce the problem just with taking the Honey.mkv and muxing the video only into another mkv. The video is MPEG2. The mkv was created by converting a TS file through Haali's Media Splitter + Matroska Muxer.

[Eragon4ever]

Looks like the message I get when I try to remux a mkv created with "--engage native_mpeg4" enabled. (see page 5)

[har-vas]

Hello all. I would like to ask for/propose some features regarding mkvmerge.
1. I like very much the (very flexible) Chapter Editor and I am using it, but I think that it would be great if it had the possibility to directly import chapters from an IFO file (like it does from .mkv files). Now I am using the well-known (and abandoned?) ChapterXtractor for that purpose and then import the .txt file in Chapter Editor. So is it possible to directly import chapters from a DVD in Chapter Editor? Is this feature in author's plans for the future?
2. What about a Tag Editor? I imagine a new tab in mmg with a list of all the official tag names (maybe in groups), so that you have just to select a tag, enter the value for it, then select another tag (either as a child of the previous or in the same level with it), enter the value for it etc. Also a syntax check function would be necessary (to verify integrity). Now I have to edit manually a text file to handle my tags...
3. Also I would like to be restored the "allow_avc_in_vfw_mode" hack, but this is something that the author has ruled out. Personally, I am using many mkv files with x264 VfW video streams (created by GordianKnot 0.35), mainly TV captures, which finally I load in VirtualDubMod to throw out ads or to isolate a small part of the video. I was very disappointed when I saw that this feature went away in MKVtoolnix 2.0. I respect the developer's decision (who always knows what is better of course), but as an end-user I would like to receive an explanation. Why an optional program's feature, which someone could freely decide to use, went away? Was it so bad feature, a source of other problems maybe? Or was just a tactical decision to stop even the last support for x264 VfW?
4. Anyway, is there any alternative solution for easy post-editing native x264 streams stored in matroska? Thanks.

[bob0r]

Arg, still no H.264 MBAFF support? :/

[Mosu]

What is h.264 MBAFF?

[ExarKun634]

What is h.264 MBAFF?Man, you just aren't up on your HDTV terms, are you? (Just kidding)

Apparently, it stands for MacroBlock-level Adaptive Frame/Field, and it referes to a method of coding interlaced MPEG4AVC/H264 content.

It's of importance right now, because it is how BBC-HD is broadcasting their MPEG4AVC/H264 content.

[Mosu]

Man, you just aren't up on your HDTV terms, are you? (Just kidding)

;) I don't have HDTV capable equipment and will not have for quite some time. Therefore I'm not really interested in it, hence I don't know these terms.

Apparently, it stands for MacroBlock-level Adaptive Frame/Field, and it referes to a method of coding interlaced MPEG4AVC/H264 content.

It's of importance right now, because it is how BBC-HD is broadcasting their MPEG4AVC/H264 content.

Sample files? How is storage different from normal h264? How can I recognize what type of stream it is? Can mp4box handle them correctly?

[Borbus]

You can get a sample of BBC-HD from here: http://www.gigasize.com/get.php/23058/BBC_HD1.ts

It was posted by another doom9 user a while ago.

There are more in this thread: http://forum.doom9.org/showthread.php?t=115667

[Mosu]

Transport streams are not supported. Only elementary streams. Any way to get the ES from the TS?

[madshi]

Transport streams are not supported. Only elementary streams. Any way to get the ES from the TS?
Sure. There are several ways. E.g. by using GraphEdit (Elecard Demuxer -> Dump) or by using mplayer with command line commands. Or by using Haali's Media Splitter + Haali's Matroska Muxer + mkvExtract.

[bob0r]

Yup LOL i gave all those samples.....and you are like what are they? :p

It also seems haali dsmux (and so h264tsto) have problems with BIG files...... i am not a coder so i should not complain, but i am dutch so i will:

Its pathetic big files are still an issue today :/

mkv still SUCKS on MAC..... progress is really crappy....... i wish i never learned about all this HD stuff :D

Ok thanks for the replies!

[Mosu]

Hello all. I would like to ask for/propose some features regarding mkvmerge.
1. I like very much the (very flexible) Chapter Editor and I am using it, but I think that it would be great if it had the possibility to directly import chapters from an IFO file (like it does from .mkv files). Now I am using the well-known (and abandoned?) ChapterXtractor for that purpose and then import the .txt file in Chapter Editor. So is it possible to directly import chapters from a DVD in Chapter Editor? Is this feature in author's plans for the future?

I'll probably implement this. I already have code which uses libdvdread and retrieves the chapters; it's "just" a matter of integrating into mmg.

2. What about a Tag Editor?

No. Not enough time.

3. Also I would like to be restored the "allow_avc_in_vfw_mode" hack, but this is something that the author has ruled out. Personally, I am using many mkv files with x264 VfW video streams (created by GordianKnot 0.35), mainly TV captures, which finally I load in VirtualDubMod to throw out ads or to isolate a small part of the video. I was very disappointed when I saw that this feature went away in MKVtoolnix 2.0. I respect the developer's decision (who always knows what is better of course), but as an end-user I would like to receive an explanation. Why an optional program's feature, which someone could freely decide to use, went away? Was it so bad feature, a source of other problems maybe? Or was just a tactical decision to stop even the last support for x264 VfW?

I've re-added this feature.

[Mosu]

http://en.wikipedia.org/wiki/Dolby_Digital_Plus

Thanks. There will be no support for DD+ for the time being because a) I cannot find any specs, b) I don't have any means of playing back such a file (neither hardware nor software).

[Mosu]

Hey users,

here's mkvtoolnix 2.0.2. A couple of bug fixes, especially in the h.264, some minor new features is about all. If you compile it yourself make sure to get libmatroska 0.8.1 which this release depends upon from http://dl.matroska.org/downloads/libmatroska/

The usual links...
...to the home page:
http://www.bunkus.org/videotools/mkvtoolnix/
...the source code:
http://www.bunkus.org/videotools/mkvtoolnix/sources/mkvtoolnix-2.0.2.tar.bz2
...the Windows Unicode enabled binaries:
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-unicode-2.0.2-setup.exe

More binaries for Linux and other OS are available from the home page.

Here's the ChangeLog since 2.0.0:

-----------------------------------------------------------
2007-02-21 Moritz Bunkus <moritz@bunkus.org>
* Released v2.0.2.

2007-02-19 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Reintroduced the "--engage allow_avc_in_vfw_mode" hack.

2007-02-06 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: Fixed suppoert for DTS-in-WAV files which are encoded with 14 bits per word.

2007-02-03 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: enhancement: Added support for DTS files which use only 14 out of every 16 bits and which are not stored inside a WAV file.

2007-01-30 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge, mmg: Changed the default for the "NALU size length" to "4" and added a warning if "3" is used.
* mkvmerge: bug fix: File type detection for Qt/MP4 files which start with a "wide" atom has been fixed.
* mmg: bug fix: The "NALU size length" drop down box is now also enabled for h.264 tracks read from AVIs and for h.264 tracks stored in "VfW compatibility mode" in Matroska files.

2007-01-28 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge, mmg: new feature: Extended the option "--default-track" so that it can be forced to "off" allowing the user to create a file for which no track has its "default" flag set. Fix for bug #224.

2007-01-17 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: Fixed the wrong "default duration" if the user used "--default-duration ...23.976fps".

2007-01-16 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: The AVC/h.264 ES reader was losing frames if the file size was an exact multiple of 1048576 bytes.
* mkvmerge: bug fix: The AVC/h.264 ES packetizer produced invalid CodecPrivate data if the AVCC did not contain the aspect ratio information. Fix for Bugzilla bug #225.
* mkvmerge: bug fix: The Matroska reader passes the correct track number down to the AVC/h.264 ES packetizer in the case of "AVC in Matroska stored in VfW mode".
* mkvmerge: bug fix: Fixed a crash (segmentation fault) in the AVC/h.264 ES handling code.

2007-01-15 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge, mkvextract, mkvinfo: new feature: Added support for using CodecState for signaling changes to CodecPrivate. It is used for MPEG-1/-2 video if it is turned on with "--engage use_codec_state".
-----------------------------------------------------------

Have fun.

Regards,
Mosu

[madshi]

Thanks!!

[bob0r]

1: If you have muxed H.264 previously with nal 3, you open .mkv the nal box is greyed.... do i need to demux/remux to get it fixed or.... ?

2: H.264 MBAFF still not working right?
I get this:
Error: 'I64d' is not a valid file ID in '--track-order 0:I64d,1:I64d'.

cli: "mkvmerge" -o "G:\cap\pride.mkv" --default-duration 0:25fps -d 0 -A -S I:\cap\pride.h264 --sync 0:-698 -a 0 -D -S I:\cap\pride.ac3 --track-order 0:I64d,1:I64d

3:
Weird visual bugs also:
http://x264.nl/mkv2.0.2.visual.bugs.gif

[Yong]

i dont have the visual bug,
http://img143.imageshack.us/img143/8177/clipboard01lt5.gif
im using vista transformation pack 6.0 in XP SP2. ;)
Try change to other visual style and see if the problem still persist.

[Eragon4ever]

1: If you have muxed H.264 previously with nal 3, you open .mkv the nal box is greyed.... do i need to demux/remux to get it fixed or.... ?
See my post and his reply.
http://forum.doom9.org/showthread.php?p=947768#post947800

[Mosu]

mkvmerge does not support re-adjusting the NALU size length of natively muxed h.264 tracks yet. I'm planning to implement that, though I cannot say when I'll get this done.

[tomos]

Thanks. There will be no support for DD+ for the time being because a) I cannot find any specs, b) I don't have any means of playing back such a file (neither hardware nor software).

:( thanks for looking tho.

[Mosu]

2: H.264 MBAFF still not working right?
I get this:
Error: 'I64d' is not a valid file ID in '--track-order 0:I64d,1:I64d'.

F***! This has nothing to do with h.264 but with the new wxWidgets version I'm compiling against... How I hate this! Get rid of one bug and get a random new one...

Sorry guys, please download this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-unicode-2.0.2-1-setup.exe
It's linked against the older wxWidgets version again.

3:
Weird visual bugs also:

Never seen this myself, cannot do anything about it. If the older wxWidgets doesn't fix it for you then it'll stay that way.

[Isochroma]

Ahh Mosu, I have another delicious file for you!

AVC with OGG in MP4 (132K) (http://www.isochroma.com/Testfiles/Misc/doom9/%5bC1%5dNodame_Cantabile_-_06%5bX264%5d%5bOGG%5d%5bHD%5d%5b479E15D8%5d_001.mp4)

The video remuxes fine with latest MKVMerge, but the audio gives this error and is omitted from the MKV:

Warning: Quicktime/MP4 reader: The audio track 2 is using an unsupported 'object type id' of 221 in the 'esds' atom. Skipping this track.

Why someone would put OGG into MP4 I cannot guess, especially when you've worked so hard to make MKVToolnix the best tool for muxing.

[Mosu]

Yeah, mkvmerge does not support Vorbis-in-MP4 yet. But thanks for the sample; that's always the first thing I need :)

[madshi]

@Mosu, noticed some weird sound in the beginning of some of my MKV movies. After some thinking about it, what does mkvmerge do if I tell it to delay the audio tracks? Does it loop the beginning of the audio track? Or does it add silence? I guess you're looping the sound? That sounds really weird to me. If possible, I'd prefer if you added silence instead, just like delaycut does. Thanks!

[Mosu]

mkvmerge should add silence, but it doesn't support this for all audio formats (only for AC3, MP3, Vorbis if I'm not mistaken). At the moment it creates weird sound for AC3 because it does the wrong thing.

[bob0r]

F***! This has nothing to do with h.264 but with the new wxWidgets version I'm compiling against... How I hate this! Get rid of one bug and get a random new one...

Sorry guys, please download this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-unicode-2.0.2-1-setup.exe
It's linked against the older wxWidgets version again.



Never seen this myself, cannot do anything about it. If the older wxWidgets doesn't fix it for you then it'll stay that way.


Visual bug(s) fixed!

H.264 MBAFF muxing still fails..... hope you can support it soon :(



mkvmerge v2.0.2 ('You're My Flame') built on Feb 21 2007 23:40:43
'I:\cap\pride.h264': Using the AVC/h.264 ES demultiplexer.
'I:\cap\pride.ac3': Using the AC3 demultiplexer.
Track 0 of 'I:\cap\pride.h264': Extracted the aspect ratio information from the MPEG-4 layer 10 (AVC) video data and set the display dimensions to 1964/1080.
'I:\cap\pride.h264' track 0: Using the MPEG-4 part 10 ES video output module.
'I:\cap\pride.ac3' track 0: Using the AC3 output module.
The file 'G:\cap\pride.mkv' has been opened for writing.
'die' called: common.cpp/saferealloc() called from file src/common/common_memory.cpp, line 33: realloc() returned NULL for a size of 183654 bytes.


set the display dimensions to 1964/1080 <-- This makes no sense also, it's 1440x1080 which is displayed as 1920x1080.

[Mosu]

The BBC file you (or someone else) gave me works fine. So how about you upload the pride.h264 file? I'm guessing that it is not an elementary stream but a transport stream. For those mkvmerge accidentally detects a h.264 elementary streams even though it isn't.

Anyway, I won't stick to using wxWidgets 2.6.3 because it causes other bugs.