Log in

View Full Version : Matroska calculator?


pogo stick
14th April 2004, 05:08
Is there any Matroska calculator? Could be very useful for me.
I need to know mkv filesizes after muxing with up to 3 aac.
Or if there is no calculator, how can I calculate it manually?

scrat
14th April 2004, 08:40
hey!

DVDtoMKV is a nice program that also can calculate the bitrate for the video codec in a mkv-file. It supports up to 10 audio-files.


cu, scrat

pogo stick
14th April 2004, 09:25
Yes, program is nice.
But still no aac support in calculator and calculating aac as some other audio is not accurate. It's not big problem of course, but I think counting can be done correctly. I just don't know how.

ChristianHJW
14th April 2004, 14:01
Originally posted by pogo stick Yes, program is nice.
But still no aac support in calculator and calculating aac as some other audio is not accurate. It's not big problem of course, but I think counting can be done correctly. I just don't know how. ... i am sorry to tell you that a precise overhead calculation for matroska is not so easy to do :( .... i guess alexnow has done the most in this respect, have a look at http://alexnoe.matroska.org , i guess he has some calculation hidden in the code somewhere ....

alexnoe
14th April 2004, 14:13
http://www-user.tu-chemnitz.de/~noe/Video-Zeug/AVIMux%20GUI/en_estimate_overhead.html#overhead_mkv

and in avi-mux gui source code in matroska.cpp

Such a calculator would be as accurate as a random number generator if you can't define precice muxing settings...

pogo stick
15th April 2004, 23:24
OK, then I'll roll some dice. :D
Thanks for replies anyway.
Oh, and thanks to all Matroska developers for their work.
By the way, can we expect menu support soon?
I know, many people are waiting for it and I don't want to push.
I am curious if it planed on near future.
And when it will be implemented will it be something that every player would handle using right splitter?
Or player will have to be able to do some advanced features like it is with mp4?

jkwarras
28th April 2004, 09:43
For me, after having create a huge collection of DVDRips in Matroska in the past months :) , my 'cheap' conclusion is that Matroska doesn't add overhead to the file (at least not a big one < 1MB in most cases).

So, that's what I do: Audio + Video + Subs + attachments = Filesize.mkv :D

Regards

alexnoe
28th April 2004, 12:33
Of course, you have to find
overhead of matroska - overhead of source files
:sly:

pogo stick
29th April 2004, 10:26
I noticed that when I mux avi(XviD) with mp4(aac) then mkv file coming out smaller then avi + mp4.
And difference becoming bigger if video length is longer.
If avi + mp4 is about 1200 MB then mkv is about 1198 MB.
So my 'even cheaper' conclusion is that it's not overhead. It's underhead then. :)

jkwarras
29th April 2004, 13:39
Originally posted by pogo stick
So my 'even cheaper' conclusion is that it's not overhead. It's underhead then. :)

I've also noticed that with all sort of muxing: avi + aac or avi + mp3 vbr or avi + ogg, etc.... usually it seems to reduce the filesize +- 2-3 MB, depends on length of the movie. Matroska rocks :D

Griniaris
29th April 2004, 15:33
This is so because EBML- and fixed lacing is used when you mux in matroska. You can do a test if you like trying to disable lacing and see the difference... :D I too believe that Matroska is the best container at the moment from the overhead point of view.

bond
29th April 2004, 16:30
Originally posted by pogo stick
I noticed that when I mux avi(XviD) with mp4(aac) then mkv file coming out smaller then avi + mp4well of course, in contrary to mkv avi wasnt designed having mpeg-4 (or mp3 or aac) storage in mind
the same goes for .mp4 of course ;)

Atamido
29th April 2004, 17:32
Originally posted by Griniaris
This is so because EBML- and fixed lacing is used when you mux in matroska. In Matroska there are three types of lacing. EBML, Fixed, and Xiph(guess where that came from ;)). When writing, most muxers will autodetect which method has the lowest overhead at any given point. If possible, Fixed has the lowest overhead, and will be used for audio with fixed frame sizes like MP3. Vorbis has random frame sizes and is most likely going to be using the Xiph method. Check here (http://matroska.org/technical/specs/index.html#lacing) if you are just really curious for more info.