mkvtoolnix: new version

[Teegedeck]

;) Yes, as I wrote above the display size of the original mkv (the video-track) was maintained although I set a different aspect in mkvmerge. But I haven't checked whether this still is the case with Mosu's latest version. The automatic resizing with these new files just didn't seem to work in (mediaplayer classic), whether I changed the value in the matroska-props or in the muxer, whereas at the same time it worked for files produced with mkvmerge 6.x-produced files.

But as written in my preceding post, I've found out that it always worked in BSplayer and now also works in MPC, again, after I chose the overlay mixer vor video-output in the MPC-prefs. Why MPC acted differently on old and new mkvs eludes me.

BTW, how is aspect stored in mkv, or more precisely, why are display sizes shown in pixels when I chose a floating-point value like 1.85 in mkvmerge?

(And just to keep you entertained, ATM I curiously eyeing how mkvs run at double or triple speed when put onto an XCD and played back with latest MPC's internal XCD-splitter:devil:.)

[Mosu]

Originally posted by Teegedeck
But I haven't checked whether this still is the case with Mosu's latest version.

The latest version should have fixed this issue: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.7.0pre-20030916-2.rar

BTW, how is aspect stored in mkv, or more precisely, why are display sizes shown in pixels when I chose a floating-point value like 1.85 in mkvmerge?

Matroska does not know an aspect ration itself. It knows four attributes per video track: PixelWidth, PixelHeight, DisplayWidth and DisplayHeight. Pixel* are the dimensions of the encoded picture as the encoder/decoder sees them. Display* tells the player which resolution it should prefer when displaying the video, or at least which aspect ratio it should try to use (or at least select by default. The user must have the choice to change that, of course). The aspect ratio is simply DisplayWidth/DisplayHeight.

mkvmerge does not accept these values independently at the moment. This is due to the fact that most people just want to specify an aspect ratio and don't want to mess around with mathematics (e.g. calculating the needed Display* values themselves). mkvmerge will automatically calculate the Display* values depending on the original resolution and the aspect ratio given on the command line. It will always scale the resolution UP, never down. If someone actually wanted to set DisplayWidth and DisplayHeight himself then I can easily add options for that (which are of course mutually exclusive with the --aspect-ratio option).

[hulkenstrong]

How did ppl get AAC+ working?

1: I captured music video from tv.
2: Encoded video to xvid and audio to wav then used nero to produce AAC+ (used vbr streaming present)
3: First tried mkvmerge without gui. Then used gui also tried with AAC+ ticked and without.

Resulst the video freezez on first frame if i skip a few it plays but still only half the sample rate is displayed in coreaacdc 1.0b7.

What am I doing wrong or do I need to update something?

CoreAAC 1.ob7
mkvtoolnix-0.7.0
mkxds-v0.5.0
tried in WMP 6.4 and Bsplayer 086.500 both behave the same way.

[Teegedeck]

whoops, forgot to thank you for your explanation, Mosu! :)

[[Toff]]

Originally posted by hulkenstrong
How did ppl get AAC+ working?
...
What am I doing wrong or do I need to update something?
...
CoreAAC 1.ob7
mkvtoolnix-0.7.0
mkxds-v0.5.0
You need to use Gabest's last (>=1.0.1.7) Matrosk Splitter : http://sourceforge.net/projects/guliverkli/

To create your file the best way is to use mkvmerge (>=0.7.0) and the mp4 file.
(the old way was to use .aac with the −−aac−is−sbr <TrackID> switch)

[hulkenstrong]

Thanks for the information. Now its playing correct. Still a bit confused havent seen matroska splitter mentioned anywhere (and well i did read the other 7 pages quickly in this tread, must have missed it).

[nanga parbat]

hello,

as i have not found any working configuration, i will post that here.
i've been trying to use the ar flag with mkvtools(0.7.0pre-20030916-2), created a video only mkv with ar set to 1.825.
mkvinfo reports:
.
.
.
+ A track
+ Track number: 1
+ Track UID: 2791319198
+ Track type: video
+ MinCache: 1
+ Codec ID: V_MS/VFW/FOURCC
+ CodecPrivate, length 40 (FourCC: XVID, 0x44495658)
+ MaxCache: 1
+ Default duration: 40.040ms (24.975 fps for a video track)
+ Video track
+ Pixel width: 560
+ Pixel height: 368
+ Display width: 670
+ Display height: 368
+ Lacing flag: 0
+ Cluster

ar seems to be properly set.
now for playback: i have tried all combinations (i could imagine) of mpc(6465) internal matroska splitter, gabest MatroskaSplitter(20030829), xviddec alone, ffdshow(20030816)/xviddec, ffdshow/libavcodec and setting overlay mixer in mpc...
none of that combinations recognized set ar!
so, is this feature broken or have i overseen one step?
i'd be grateful if anyone could give me a hint.

thanks in advance, nanga.

[bond]

try ticking the overlay mixer option in ffdshow (uses overlay mixer2 not overlay mixer like mpc)...

[nanga parbat]

i have found two possible combinations that put out correct ar:

1) overlay mixer in ffdshow selected and video mixing renderer 9 (windowed) in mpc - video is displayed, but looks terrible, like with a very low resolution.

2) overlay mixer in ffdshow and video mixing renderer 9 (renderless) in mpc - ar correct, but no video (only some greenish gibber)

so both cases are kinda 'unpleasant' ;) to look at, either low res picture or no picture at all...

i don't know if that is a problem of my system or so, normal video displays well.

guidance!

P.S: using mpc internal splitter or gabest splitter doesn't behave any different here, as well as decoding with libavcodec or xvid (via ffdshow).

[Liisachan]

Originally posted by Ramirez
Hi :),in fact none of the 6.x versions worked for me (with SSA) I've always got either unreadable text (jebrish) or the subs simply wasn't displayed, dunno really what could be the problem (same SSA subs muxed in vdub played just fine)

Here is a one of the SSA subs which weren't work for me earlier ; maybe you can dig some info out of this? :)
Sorry no Idea, but I suppose the encoding (charset) was wrong.
I made a clip with Hebrew subs even when mkvmerge was 0.5.0 with GraphEdit, and with mkvmerge 0.6.x, using UTF-16 SSA.
Did you try UTF-* ???

As a side note, your SSA has Encoding=177 and Ive just found specifying this param is critically important for Win98....
If you make your SSA in UTF-* then everything works fine for win 2x/xp with Encoding=0. But if encoding=0 and if the codepage is not "Windows 1252" Code Page (English, French, German, etc.), then the resulted file doesnt play properly on Win98 (tho ok on WinXP/2000) even tho it is stored in UTF-8 and technically "Encoding" is seamless...

[Mosu]

Hey ho,

after looking at my webserver's logs for the last couple of days and seeing that the latest pre-version had about twice as many downloads as the latest official release (0.7.0) I decided it was time to release a new thingy.

No, not really - but now I've finished all that I wanted to finish before releasing 0.7.1. It is a combination of bug fixes and new features, most prominent among them the new chapter editor that has been included in the GUI.

First the URLs:
http://www.bunkus.org/videotools/mkvtoolnix/
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.7.1.rar

Please read the new mkvmerge-gui.html that I've created. It is a first shot and is not really a good guide, but it'll explain some things that I don't want to repeat here (e.g. about the capabilities of the chapter editor).

I've changed some critical code in the heart of the muxer which has not been tested excessively. I've done my best to test all combinations of the changed options/new options, but I'm really looking forward to your feedback - especially to feedback about the chapter editor and mmg's new guide.

(Criticism like 'hey you don't know squat about writing good documentation' is not helpful - I already know that ;))

Anyway, here's the ChangeLog since the last release:

--------------------------
2003-10-03 Moritz Bunkus <moritz@bunkus.org>
* Released v0.7.1.
* Added a guide for mmg including some pictures.

2003-10-01 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Changed the lacing strategy again. New defaults are NOT to write duration elements for all blocks, NOT to use time slices and to USE lacing for most audio tracks. This will save some space. The downside is that the laced frames 'lose' their precise timecode information. Current demuxers don't care and will work nevertheless. More sophisticated applications that make use of these advanced information (duration elements, time slices) are not available at the moment. All these options can be toggled by the user with the new/modified options --disable-lacing, --enable-durations and --enable-timeslices.

2003-09-29 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: new feature: Attachments are kept when reading Matroska files.

2003-09-28 Moritz Bunkus <moritz@bunkus.org>
* mmg: new feature: Added a (nearly) full-featured chapter editor.

2003-09-26 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: XML chapters were not parsed correctly.

2003-09-24 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix/new feature: Rewrote the complete MP3 handling. Now files with ID3 tags (both v1 and v2) are handled correctly. All MPEG-1 audio files (all layers) should be handled correctly now.

2003-09-23 Moritz Bunkus <moritz@bunkus.org>
* mkvextract: new feature: Support for extract HE-AAC tracks to .aac files. Bug fix: Missing elements (default values) are handled correctly for audio tracks.

2003-09-19 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bugfix: If attachments were given with path components then the path component wasn't discarded for the attachment's description on Windows (normally only the file name should be used as the attachment's name).

* mmg: Fixed wrong order of the options --chapters, --chapter-language and --chapter-charset.

2003-09-17 Moritz Bunkus <moritz@bunkus.org>
* mmg: Added a lot of checks on the data given by the user so that invalid data is reported by mmg and not by mkvmerge.
* mmg: Made the app a GUI app which gets rid of the "DOS box" on Windows.

2003-09-16 Moritz Bunkus <moritz@bunkus.org>
* mmg: bugfix: Moved the aspect ratio and FourCC input fields from the global tab to the input tab where they belong to.
* mkvmerge: new feature: RealAudio can be read from Matroska files.
* mkvmerge: bugfix: RealVideo was not read correctly from Matroska files.
* mkvmerge: bugfix: The SRT reader would abort if there was more than one empty line between subtitle entries line.
* mkvextract: bugfix: Proper BOMs are written according to the desired charset when extracting text subtitles.

[ssjkakaroto]

thx for the upd8 mosu :)

[HomiE FR]

Thanks Mosu. I'll test it and report any bug I can find (even though I usually don't find any ;) ).

[Yuuhi]

I've tried the last versions, especially the chapter editorn and works great!!! TNX mosu!!! ;)

[Mosu]

Thanks for all the praise. Hmm... still no bug reports? Damn! :)

[unplugged]

Man, your work really rocks, mkvtoolix is so rich and powerful that matroska will gain much more popularity thanks to its features already applicable!
Is there one thing that mkvmerge can't do??? :p

Hope you and others will have time to work together with VdubMod team to co-improve entire the tools.

[DKDIB]

I noticed a couple of problems.
___

1- When I import a .mkv file with multiple audio streams, only the last one will be in the new Matrsoka (and I selected all strems, of course ;) ).

I did some tests using Matroskas with the follow audio streams:
mp3 128 + mp3 192;
mp3 192 + mp3 128;
mp3 128 + mp3 192 + mp3 128;
Vorbis 155 + Vorbis 127;
Vorbis 155 + mp3 128;
mp3 192 + Vorbis 127.



2- Even if I selected the default flag on an audio stream, there' s no default audio track in the output file (I checked it using Matroska Shell Extension 1.6).

It' ll happen with any kind of audio stream.
___

Sorry for my bad english. :(

[Mosu]

Originally posted by DKDIB
1- When I import a .mkv file with multiple audio streams, only the last one will be in the new Matrsoka (and I selected all strems, of course ;) ).

Ah yes, that was a bug in the GUI (how the GUI created the command line for mkvmerge, to be precise). I've already fixed it, and the next release (coming tomorrow, I think ;)) will contain this fix.

2- Even if I selected the default flag on an audio stream, there' s no default audio track in the output file (I checked it using Matroska Shell Extension 1.6).

This is a bug in the Shell Extension. The problem is that Matroska elements whose value is equal to their default value are not written to the file. For the 'default track' flag the value 'true' is the default. The result: Only for those tracks whose default flag is not set the defaultflag is actually written with a value of 'false'.

Now the Shell Extension does not yet handle these default values properly and thinks that, if the element is absent (for the 'true' case), that it is 'false'. In the other cases the element IS present but set to false. So for all tracks it'll show 'false'.

If you want to make sure that the default track is written correctly you should use mkvinfo. It will NOT show any 'Default Track' entry for the default tracks and 'Default Track: false' for all the other tracks of a kind.

Thanks for the report.

[Mosu]

Originally posted by unplugged
Man, your work really rocks, mkvtoolix is so rich and powerful that matroska will gain much more popularity thanks to its features already applicable!
Is there one thing that mkvmerge can't do??? :p

Thanks for the praise :) But yes, there are still things that mkvmerge does not handle. The most important one (in my opinion) is concatenating files ( = appending file 1 to file 2). At the moment only Avimux GUI can do that properly.

Among the other things I'd say are important is 'proper' support for B-Frames, reading MPEG4 video from MP4 files aaaaaaaand.... ummm... There are more things, most of them minor, though :)

[Atamido]

Originally posted by Mosu
The most important one (in my opinion) is concatenating files ( = appending file 1 to file 2). At the moment only Avimux GUI can do that properly.
Hey, the Matroska Stream Editor (http://forum.doom9.org/showthread.php?s=&threadid=62204) can do that too. :)

[DKDIB]

Mosu wrote:
> I've already fixed it [...]
> [...]
> If you want to make sure that the default track is written
> correctly you should use mkvinfo. [...]

Thanks a lot (or "arimicio") Mosu!!! :D

[raistlin2k]

Is it possible to add Vobsub-subs as attachments?
Do we have to wait for an updated vobsub-playback-filter for that to work? Or is it already working?

Thanks
Raist

[Dragon Shenron]

I tried to mux and split a 2h 15min movie and I experienced a problem. 1st pass went well, but after muxing the 1st part of the movie (during the 2nd pass), the 2nd part of the movie woudn't mux, the GUI just reported an error and the .mkv file was just 1.11 KB big (the 1st part works well). The log doesn't mention much, just that it opened the 2nd mkv for writing and that's all (I don't have the log anymore, I deleted it :( )
The inputs were:
1. avi -> XviD
2. ac3 -> 384 Kbps
3. srt subtitle
4. ogg type chapters

Splitting was set to size 705M.
0.7.0 version doesn't have this problem, just 0.7.1.

[Mosu]

Originally posted by Dragon Shenron
I tried to mux and split a 2h 15min movie and I experienced a problem. ...
0.7.0 version doesn't have this problem, just 0.7.1.

Thanks for the bug report. I'll investigate. This is probably due to the muxer changes I described earlier. Could you please re-mux, save the log and send it to me? moritz@bunkus.org

Thanks

[Mosu]

Originally posted by raistlin2k
Is it possible to add Vobsub-subs as attachments?
Do we have to wait for an updated vobsub-playback-filter for that to work? Or is it already working?

Thanks
Raist

VobSub-as-attachments will probably not work anytime soon, because we want to have 'proper' VobSub muxing instead (VobSub just being another track just like any other text subtitle track). Both would/will require changes to the VobSub playback filter, and Gabest seems to busy like never before, so I cannot give you a timeframe. Sorry.

[KpeX]

I was unable to mux 1 AC3 and 1 avi with mkvmerge 0.7.1, AC3 was a DVD source demuxed with besweet [ i.e. besweet -core ( -input "besweet.lst" -substream 0x80 -payload -output "file.ac3" ) -ota ( -d auto ) ], error message was 'invalid mp3 header value for the version' (no idea what that means). My commandline was something like "mkvmerge -o "output.mkv" "movie.avi" "soundtrack.ac3". The AC3 muxes fine with VdubMod, and I could demux the AC3 from the VdubMod-muxed MKV file with MKVExtract just fine.

[Chez_Wimpy]

So far I have been able to mux speex audio streams that were encoded with wav headers, however I would like to add them without the extra step. Is it possible to add support for muxing .spx directly to mkvtoolnix?

Thanks a lot. Great tool, even more so for CLI phobic people like me!

-CTB

[Mosu]

Originally posted by KpeX
I was unable to mux 1 AC3 and 1 avi with mkvmerge 0.7.1,
....

Thanks for the report. Could you please download http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.7.2-pre1.rar and see if it fixes your problem?

Thanks.

[KpeX]

Originally posted by Mosu
Could you please download http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.7.2-pre1.rar and see if it fixes your problem?

Yep, works fine with the new pre-version. Thanks for your work Mosu :D

[Brother John]

I started using matroska lately and after some muxing trouble with VDubMod I tried mkvtoolnix. Well, what can I say? Great work, Mosu!
However there are two things I'd like to address:

1. Are there any plans for frame accurate splitting in mkvmerge? Though splitting by time and limiting number of output files to 2 works ok that's the one feature I really miss.

2. How about including a manifest file (http://people.freenet.de/brotherjohn/mmg_manifest.zip) for mmg in the windows package? That way the GUI would fully support Win XP's visual styles while not hurting older versions of Windows. I'm running mmg with the manifest file right now without any problems. Feels just like created specifically for XP.

[Mosu]

Originally posted by Brother John
I started using matroska lately and after some muxing trouble with VDubMod I tried mkvtoolnix. Well, what can I say? Great work, Mosu!

Thanks :)

1. Are there any plans for frame accurate splitting in mkvmerge? Though splitting by time and limiting number of output files to 2 works ok that's the one feature I really miss.

Probably not. The problem is that frame-accurate splitting can only be achieved by re-encoding at the start of each file (from the second file on) if that file does not start with a key frame. Otherwise video would be distorted. mkvmerge is only a converter on the container level and will never include video codecs - and without video codecs no re-encoding.

However, I could include the option to split after 'n' frames, or after given set of frame numbers and try to find the closest key frame - much like I'm handling splitting at the moment. That wouldn't be frame accurate, but you could give the number of frames.

2. How about including a manifest file (http://people.freenet.de/brotherjohn/mmg_manifest.zip) for mmg in the windows package? That way the GUI would fully support Win XP's visual styles while not hurting older versions of Windows. I'm running mmg with the manifest file right now without any problems. Feels just like created specifically for XP.

Looks interesting. Me being a Linux guy I haven't even heard of such files before. What do they do exactly, or what does Windows XP derive from the information that this file provides? I can include it, sure, I'd just like to know a bit more about that mechanism :)

[Latexxx]

Originally posted by Mosu
Looks interesting. Me being a Linux guy I haven't even heard of such files before. What do they do exactly, or what does Windows XP derive from the information that this file provides? I can include it, sure, I'd just like to know a bit more about that mechanism :)

It just gives the program a crappy winxp outfit. Without the manifest file the buttons etc. in the program will have the tradiotional windows look. So the only difference is how your program does look like. All winxp pros don't even bother to keep the candy-looking interface turned on. It's slow and looks like crap. Include the manifest file if you don't want to get messages like "why doesn't this look like windows?" from l33t users.

[Mosu]

Originally posted by Latexxx
It just gives the program a crappy winxp outfit. Without the manifest file the buttons etc. in the program will have the tradiotional windows look. So the only difference is how your program does look like. All winxp pros don't even bother to keep the candy-looking interface turned on. It's slow and looks like crap. Include the manifest file if you don't want to get messages like "why doesn't this look like windows?" from l33t users.

I see. Thanks for the explanation. I'll skip that file, then :)

[Brother John]

frame accurate splitting: should have been more precise, sorry. Of course by »frame accurate« I mean »key frame accurate«. The option I'm looking for is something like: »split the file at frames no 10000, 20000 and 30000 or closest keyframe«.

The manifest file:
Latexxx basically said what it does. Without manifest mmg has the traditional look with rectangular buttons etc. even if the new WinXP look is activated.
I don't want to argue about crappy or not or slow or not. But as mmg does not have any problems with the XP styles why not include a manifest file and leave the choice to every individual user: WinXP look globally enabled --> mmg looks XP-ish, WinXP look disabled --> mmg looks traditional.

Btw: I like the skinning ability (though not the default style) and it doesn't feel slower than Win2k.

[Atamido]

Originally posted by Brother John
frame accurate splitting: should have been more precise, sorry. Of course by »frame accurate« I mean »key frame accurate«. The option I'm looking for is something like: »split the file at frames no 10000, 20000 and 30000 or closest keyframe«. You can do this by hand using the Matroska Stream Editor.

[Mosu]

Originally posted by Brother John
frame accurate splitting: should have been more precise, sorry. Of course by »frame accurate« I mean »key frame accurate«. The option I'm looking for is something like: »split the file at frames no 10000, 20000 and 30000 or closest keyframe«.

Yes, that's definitely doable. Can't say anything on the timeframe, though, I'm rather busy these days. Anyway I've put it on my todo list.

The manifest file:
WinXP look globally enabled --> mmg looks XP-ish, WinXP look disabled --> mmg looks traditional.

Ok, if it's honoring the user setting then including it will not hurt anyone.

[Mosu]

Heya,

I've just released version 0.7.2 of mkvtoolnix. It is mainly a bug fix release but has some internal changes that may or may not work for you ;) Anyway, due to the bugs that I've fixed I strongly recommend that you upgrade to 0.7.2.

The URLs:
http://www.bunkus.org/videotools/mkvtoolnix/
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.7.2.rar

The ChangeLog since 0.7.1:
--------------------------
2003-10-14 Moritz Bunkus <moritz@bunkus.org>
* Released v0.7.2.
* mkvmerge: bug fix: If 'no linking' and splitting was active mkvmerge would abort on the start of the second output file due to timecodes that were calculated incorrectly.
* mkvmerge: Implemented some speedups for a couple of container formats and track types (mainly AVI reader, MP3/AC3/AAC packetizers). Especially noticeable when splitting is active as well.

2003-10-12 Moritz Bunkus <moritz@bunkus.org>
* mkvextract: bug fix: Support for extracting SBR AAC (previous 'fix' did not actually fix this).
* mkvextract: bug fix: All extracted subtitles where written to the first output file given, not to the one they were supposed to be written to.

2003-10-11 Moritz Bunkus <moritz@bunkus.org>
* mmg: bug fix: The 'abort' button was doing nothing under Windows.

2003-10-06 Moritz Bunkus <moritz@bunkus.org>
* mmg: bug fix: Audio, video and subtitle track selection was translated into the wrong command line options.
* mkvmerge: Replaced the avilib based AVI reading functions with AVI classes from Cyrius.
-----------------------------

Have fun :)

[Mosu]

Originally posted by KpeX
I was unable to mux 1 AC3 and 1 avi with mkvmerge 0.7.1,
...

I'm pretty sure I've fixed that in version 0.7.2 (http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.7.2.rar).

[cca]

As I 'm downloading your new version of mkvtoolnix Mosu, I want to bring to your attention a bug that is still present in mkvtoolnix-0.7.2-pre1 and since there is no mention of it in the changelog I assume it is present in 0.7.2 also. The .SRT subtitle parser is still stalling when an empty line is encountered in the SRT text file. This bug was supposed to be fixed in 0.7.1 but I 'm still experiencing the bug. Can you look at it? Thanks.

[Liisachan]

I didn't realize there were already "Options that only apply to VobSub subtitle tracks" Does sub+idx already work in MKV?

[Mosu]

Originally posted by Liisachan
I didn't realize there were already "Options that only apply to VobSub subtitle tracks" Does sub+idx already work in MKV?

No, it's deactivated ;) Activating it and getting it right won't be a problem, but there still ain't a playback filter that's able to play VobSubs in mkv.

[Mosu]

Originally posted by cca
As I 'm downloading your new version of mkvtoolnix Mosu, I want to bring to your attention a bug that is still present in mkvtoolnix-0.7.2-pre1 and since there is no mention of it in the changelog I assume it is present in 0.7.2 also. The .SRT subtitle parser is still stalling when an empty line is encountered in the SRT text file. This bug was supposed to be fixed in 0.7.1 but I 'm still experiencing the bug. Can you look at it? Thanks.

Sure, will do. Could you please send me the .SRT file in question? moritz@bunkus.org Thanks.

[KpeX]

Originally posted by Mosu
I'm pretty sure I've fixed that in version 0.7.2 (http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.7.2.rar).

Correct, sorry for the late reply Mosu, this bug is confirmed squashed in 0.7.2.

[Liisachan]

The doc says "AAC audio files (only those with ADTS headers before each packet)" works, but it seems mkvmerge can already handle AAC without ADTS headers too (I happened to find it when I was trying to mux a .m4a file created by the AAC encoder come with Apple iTunes.)

1. Is such a .m4a "officially" supported by mkvmerge?
2. If so, I'd like to see "*.aac *.mp4 *.m4a" as the filemask for AAC in mmg

And here's a very small request for better usability:
3. Would like to have File > New in mmg, which would just clear all the forms (needed when you want to make more than one Matroska files in succession)

[Mosu]

Originally posted by Liisachan
The doc says "AAC audio files (only those with ADTS headers before each packet)" works, but it seems mkvmerge can already handle AAC without ADTS headers too (I happened to find it when I was trying to mux a .m4a file created by the AAC encoder come with Apple iTunes.)

Could you send me the first meg of that file via email please (moritz@bunkus.org)? Technically it should be impossible to handle such files so I'm more than curious what kind of a file this is.

1. Is such a .m4a "officially" supported by mkvmerge?

No, because without the headers I can detect neither the number of channels nor the sampling frequency, the AAC profile or the packet boundaries.

And here's a very small request for better usability:
3. Would like to have File > New in mmg, which would just clear all the forms (needed when you want to make more than one Matroska files in succession)

Good point, I'll add that. Thanks.

[Liisachan]

a small sample by iTunes, itunes.m4a, has just been sent to you.
I could even use this trick. to convert m4a to "normal" aac:

mkvmerge -o tmp.mka in.m4a
mkvextract tracks tmp.mka 1:_out.aac

_out.aac has a lot of headers like "FF F1 50 xx xx xx FC" periodically, while in.m4a doesn't have such things (I think)

[Mosu]

Originally posted by Liisachan
a small sample by iTunes, itunes.m4a, has just been sent to you.

Thanks. I'll take a look at it.

[ChristianHJW]

Originally posted by Mosu No, because without the headers I can detect neither the number of channels nor the sampling frequency, the AAC profile or the packet boundaries. .... you can, from the MP4 headers ?

[Mosu]

Originally posted by ChristianHJW
.... you can, from the MP4 headers ?

If the source file is a MP4 file then yes (and I guess that is what Liisachan has, although its extension is .m4a and not .mp4). If it's "only" the raw AAC packets then that's not possible.

In short: It's probably a .mp4 and I'll add .m4a to the GUI's file selection dialog.

[Liisachan]

using mp4creator60 and/or mp4UI, you can extract "AAC (ADTS)" from a "normal" .mp4 audio file, while you can only get "Raw MPEG-4 Audio File (*.bin)" from iTunes' m4a. I'd bet they are different.