mkvtoolnix (Matroska toolkit): new release

[Mosu]

(current version: 0.9.7, direct link to Windows binaries: http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.9.7.rar, if you're upgrading from prior 0.8.2 you need a new runtime package (http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-runtime.rar)

ChangeLog from 0.9.6 to 0.9.7:
2004-10-24 Moritz Bunkus <moritz@bunkus.org>
* Released v0.9.7.
* mkvmerge: bug fix: The handling of external timecode files was still not correct but should be OK now.

2004-10-17 Moritz Bunkus <moritz@bunkus.org>
* mmg: Added an error message if the user selects 'mmg' as the 'mkvmerge executable' because that would lead to an infinite number of 'mmg's being spawned.

2004-10-16 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: If LFE is on for DTS then the number of channels is one more than what the DTS frame header says.
* mkvmerge: bug fix: Timecodes for Vorbis were wrong on rare occasions (when reading laced Vorbis from a Matroska file and changing the lacing, e.g. when splitting for the second and all following files).

2004-10-10 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge/mkvinfo/mkvextract: bug fix: The chapter and tag element tables were not always intialized correctly depending on the compiler and the optimization flags used.
* mkvmerge: bug fix: The OGM reader was broken if at least one track was not to be copied from the file (happened between 0.9.5 and 0.9.6).
* mmg: bug fix: After loading saved mmg settings the track input box listed the tracks always coming from the last input file and not from the one they really came from.

2004-10-09 Moritz Bunkus <moritz@bunkus.org>
* mmg: enhancement: Made mmg's main window properly resizable.
* mkvmerge: Rewrote the code for the external timecode files. This also fixes bug 99: The durations for the individual tracks were not correct for those tracks for which --timecodes was used.

2004-10-08 Moritz Bunkus <moritz@bunkus.org>
* mmg: bug fix: Crash when saving chapters from the chapter editor. Same as the mkvinfo issue below but on all OS.
* mkvinfo: bug fix: The chapter and tag element tables were not initialized on Windows resulting in a crash when one of those elements was encountered.)

Heya.

(Some might call it advertizing as I already have such a thread, but it is rather old now and began with version 0.4.4. I think that more users might profit from this new thread.)

Here it is, the newest Incarnation of Evil, uh, I meant mktoolnix release. A lot of bug fixes, a couple of new features. The most prominent new feature is probably... *drummroll* support for zlib compressed VobSubs. Yes, Gabest is working hard on supporting them in his demuxer, so they should become a reality for all of you very soon.

The URL, as always: http://www.bunkus.org/videotools/mkvtoolnix/ and the Windows binaries:
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.7.5.rar

Note: Current versions of libebml and libmatroska introduced new lacing schemes. This means that files will be smaller, but you also need a current version of Gabest's Matroska splitter (at least version 1.0.1.8). You can get it on http://sourceforge.net/projects/guliverkli/. You also MUST disable the internal Matroska splitter if you use MPC (Media Player Classic).

Here's the ChangeLog:
--------------------------------
2003-11-05 Moritz Bunkus <moritz@bunkus.org>
* Released v0.7.5.

* mkvmerge: bug fix: The VobSub .idx parser was dividing by 0 if a track only contained one entry.

* mkvmerge: Fixed the timecode reader code and made it a bit more flexible. Added more documentation for this feature along with an example file (examples/example-timecodes.txt).

* mmg: bug fix: When 'default track' is selected then all other tracks of the same type will have their 'default track' flag cleared.

* mkvmerge: SPU packets belonging to the same timecode are grouped together, and the duration is extracted directly from the SPU stream.

2003-10-29 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: The VobSubs are now stripped of the MPEG program stream, and only the SPU packets are kept.

2003-10-28 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge, mkvextract: The Matroska reader and the OGM reader (mkvmerge) as well as mkvextract will discard empty or 'cleaning only' subtitle packets as they are appear in OGMs in order to mark the end of an entry.

2003-10-27 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: new feature: Added the ability to read timecodes from text files which override the timecodes mkvmerge calculates normally.

2003-10-26 Moritz Bunkus <moritz@bunkus.org>
* mkvextract: bug fix: Add all the mandatory elements when extracting chapters so that the resulting XML can always be used directly with mkvmerge again without having to manually add e.g. ChapterLanguage.

* mkvmerge: bug fix; Handle audio tracks from Matroska files with the CodecID A_MS/ACM correctly.

2003-10-25 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Changes to use libmatroska's new lacing code.

2003-10-23 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: The VobSub .idx parser was mis-calculating the subtitle entry frame sizes.

* mkvmerge: bug fix: The Vorbis packetizer was miscalculating the number of samples to add/remove when using audio sync.

2003-10-22 Moritz Bunkus <moritz@bunkus.org>
* mmg: new feature: Added a new menu entry "File -> new" which will clear all the current muxing settings.

* mmg: Added support for VobSub subtitles including their compression options. Added the .m4a extension to the 'add file' dialog.

* mmg: bug fix: Made the input boxes for file names (tags and chapters) editable so that their contents can be deleted.

* mkvmerge: Adjusted the compression handling to the final content encoding specs.

2003-10-19 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: new feature: Implemented generic support for frame compression (mostly useful for VobSub subtitles but could also be used for others) and the complete framework for handling content encodings in the Matroska reader.

2003-10-18 Moritz Bunkus <moritz@bunkus.org>
* mkvinfo: new feature: Dump unknown elements recursively.

2003-10-15 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: Made the SRT reader more tolerant regarding empty lines.
----------------------

Have fun! :)

[bilu]

Originally posted by Mosu
The most prominent new feature is probably... *drummroll* support for zlib compressed VobSubs. Yes, Gabest is working hard on supporting them in his demuxer, so they should become a reality for all of you very soon.
Wow... i'd love to see this stuff working :)

Bilu

[Liisachan]

xvid+vorbis=mkv with 0.7.2 plays with MPC6.4.6.7 (&6.4.6.6)
while the same xvid+vorbis=mkv with 0.7.5 doesn't play ;_;
("This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.")

I tested more than one patterns, and always MPC doesnt like MKV files muxed by 0.7.5. Is there anything that breaks backward compatibility?
sample files (http://space34.at.infoseek.co.jp/075.zip)


PS
Only good combination so far is vid+ac3.
vid+aac = MPC crashes; vid+mp3 = wrong audio speed

Doesn't work with MatroskaSplitter 1.0.1.8 either.
However, the resulted files play if you "Disable lacing" in MKV 0.7.5

[Suiryc]

btw forget VirtualDubMod if you want to edit files using the new lacing method or compression/encryption methods.

The new lacing method is incompatible with old libs (and thus current VDM will crash with this new feature). You will have to wait for the next version to support it.

Also VDM doesn't copy all the extra information from the input file (that includes the full tag tree, the full chapter tree, and all elements that it doesn't know - including compression/encryption information about a track).

[gizmotech]

Yes,

This is to be expected. MPC's built in mkv splitter currently is incapable of understanding the new lacing scheme. Please disable it and ensure you have the latest mkv splitter from the http://sourceforge.net/projects/guliverkli/ guliverkli website.

Gizmo

[JagPanzer]

Mosu, tnx for a new release! :) I love Matroska. ;)

[Liisachan]

ok fixed :)
i just had to re-register 1.0.1.8 *phew*....

but i m afraid that is not very nice...
hope wont cause much confusion.......

[Human_USB]

I get MV C++ errors in MPC, ZoomPlayer, and CoreCodec. I have the new splitter and it's just a MKV with a Dvix video and one OGG audio.

[gizmotech]

It actually causes quite a bit of confusion, but only w/ files created w/ this new release (or the earlier Timecode release I used in the VFR Proof of Concept).

I'm actually hoping Gabest might read this and push out an updated version of mpc with an updated mkv splitter in it. I figure that would solve quite a bit of confusion. Either that or remove it completely.

Gizmo.

[Human_USB]

But I have the MPC splitter off and I get the MV C++ errors.... and just not in MPC.

[Human_USB]

Originally posted by Liisachan
xvid+vorbis=mkv with 0.7.2 plays with MPC6.4.6.7 (&6.4.6.6)
while the same xvid+vorbis=mkv with 0.7.5 doesn't play ;_;
("This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.")

I tested more than one patterns, and always MPC doesnt like MKV files muxed by 0.7.5. Is there anything that breaks backward compatibility?
sample files (http://space34.at.infoseek.co.jp/075.zip)


PS
Only good combination so far is vid+ac3.
vid+aac = MPC crashes; vid+mp3 = wrong audio speed

Doesn't work with MatroskaSplitter 1.0.1.8 either.
However, the resulted files play if you "Disable lacing" in MKV 0.7.5

I get this too.... but I have splitter 1.0.1.8 and I registered it. I think the new splitter needs an installer or something.

-Jason

[Atamido]

You MUST register the latest splitter. (1.0.1.8)
You MUST register the latest VSFilter. (2.29)
If you are using MPC, you MUST disable the built in Matroska splitter.

If you fail to do any of these things, the fill will NOT play.

[Human_USB]

I did not know I had to get the new VSplitter. I'm trying that now.


Thanks
Jason


*EDIT*

Using Matroska Splitter 20031015 (1.0.1.8), regsvr32 MatroskaSplitter.ax with it placed into System32 and using VSFilter 20030829 (2.29), regsvr32 VSFilter.dll with it placed into System32 and I turned off the MPC MKV splitter and I still get the error.



Help

[Liisachan]

@Human_USB
like i had posted up above, i re-registered 1.0.1.8 and my problem had already been fixed. I once installed 1.0.1.8 a while ago, which had also fixed my problem with MP2 audio, but an older filter was re-registered by somone while I didn't know (possibly by MatroskaMP4Pack.exe). SO I was wrongly believing that I was using 1.0.1.8 when I wrote "1.0.1.8 didn't work!" Actually I was using an older filter when I first disabled MPC's inner filter.

On top ot that, I didn't notice that critical Note ("Current versions of libebml...") in the first post by Mosu; I first read about the new version not here but in the list, and the mail posted in the list didn't have that note.

Anyway, IDX+SUB support is a great step forward. Probebly that's the very reason I didn't read the Note carefully--I was too excited :) :D and impatiently wanted to try it. I guess the install pack 0.7, which will install the newer splitter, will be out after Gabest releases a new VSFilter with IDX+SUB support.

I should soon love the new lacing too if it makes files more compact and functional, and I always admir their (dev ppl's) creativity.

That said, I really do hope that coming newer filters (1.0.1.9+) and all the related components can parse the old files too forever, because I already have some MKV files that have "the old structure" and I already , ah, presented some of my MKV files to...somone else, so I can't remux all the files to let them have the new lacing sysytem...I mean, what I really fear is hearing someday "the system in libmatroska 0.5.x is obsolete and playing back such old MKV files will be no more supported." But maybe only a few ppl think that way.:confused:

[Human_USB]

@Liisachan

I re-registered using the newest stuff off SF.net and I still can't play. I'm think it's just my computer now acting dumb. I tryed everything in this topic and still no luck. Unless I missed something I will wait for 1.0.1.9 or a installer for all this crap.



I've been waiting for VOBSUB support and now that is somewhat work, I'm waiting for menus.

[Atamido]

Originally posted by Liisachan
I should soon love the new lacing too if it makes files more compact and functional, and I always admir their (dev ppl's) creativity.

That said, I really do hope that coming newer filters (1.0.1.9+) and all the related components can parse the old files too forever, because I already have some MKV files that have "the old structure" and I already , ah, presented some of my MKV files to...somone else, so I can't remux all the files to let them have the new lacing sysytem...I mean, what I really fear is hearing someday "the system in libmatroska 0.5.x is obsolete and playing back such old MKV files will be no more supported." But maybe only a few ppl think that way.:confused: A quick explanation of the way that lacing worked will show that old files are fine. Originally the lacing system used by Matroska was the lacing system designed by Xiph for Vorbis. You have a normal Block with a timecode. There is a bit set in the Block that indicates lacing is being used. Next you have the number of laced packets. (The spec allows for up to 255, but libmatroska only writes up to 8.) Next you have the size of each laced packet, and then the packets themselves to the end of the block. It actually turned out to be only slightly more efficient for a lot of codecs and not really worth the hassle. Recently a few ideas were tossed around such as storing the the size of the packets as an EBML number as it would be more efficient for larger packet sizes.

Also, there was an idea to set a flag if all of the packets were the same size. This would mean a single bit and the number of packets in the lace. Then all of the sizes are known because you know the total size and the number of equal size packets.

Some tests were performed and it was discovered that codecs with larger packets were more efficient with the EBML numbers. And codecs with fixed packet sizes, like AC3, were super efficient with the fixed size flag.

So, three settings were made for lacing. The original setting is still the Xiph lacing. This means that all of the old files that were made with Xiph lacing are still valid and this lacing is still being used. The next is for EBML lacing, and the last is for fixed size lacing.

When muxing, the muxer automatically determines for each block which lacing scheme would be most efficient. So most streams will likely have a mix of all three. See here (http://www-user.tu-chemnitz.de/~noe/Video-Zeug/AVIMux%20GUI/en_overhead_comparison.html) for a list of different overheads and see how much of a difference the new system made from the Xiph-only system that was used previously.

[Mosu]

Pamel has effectively said all that I would have said ;) Yes, we knew there would be some confusion regarding the new lacing, but we hoped that with Gabest's 1.0.1.8 it would work all right. I hope he'll update MPC soon so that at least the need for deactivating its internal Matroska handling code disappears.

A workaround is to disable lacing on mmg's 'global' tab. Of course this will make files larger.

[Lobuz]

Small question. What is the status of adjusting mkv tools to handle audio targeted applications? Using CUE sheets from CD with audio image, or many files collected in album. With additional stuff (covers,lirycs etc.). What about muxing APE or other audio codecs? Would be nice to have support for mka in foobar player too.

Regards
Lobuz

[Liisachan]

Originally posted by Pamel
When muxing, the muxer automatically determines for each block which lacing scheme would be most efficient. So most streams will likely have a mix of all three.

Thank you for clarification. So the "old lacing" is actually a special case of the new extended lacing system, using always only one of the three types for all the blocks, and so automatically will be supported by new persers who know all the three types, right? Good to know. Thanx so much. So the lacing system has actually not totally changed but rather "generalized"...And that overhead comparison (http://www-user.tu-chemnitz.de/~noe/Video-Zeug/AVIMux%20GUI/en_overhead_comparison.html) you pointed out is really convincing :cool:

[ivanova]

Anyone tested the idx/sub in matroska yet? It muxes fine, but I haven't been able to play it. OR do we have to wait for a new matroska splitter?

[KpeX]

Originally posted by ivanova
Anyone tested the idx/sub in matroska yet? It muxes fine, but I haven't been able to play it. OR do we have to wait for a new matroska splitter?
You need to wait for a new vsfilter.dll, which I believe Gabest is working on.

[Liisachan]

Tested embedded SUB/IDX with Splitter 1.0.1.9, MPC 6.4.6.8, VSFileter 2.30,

Both MPC (build-in filters) and WMP with VSFilter etc. do work!

Thankyou very much, Gabest and Mosu!!!!!!!:D :) :D

[ivanova]

I assume you got these recent versions from
http://sourceforge.net/projects/guliverkli/ . It seems to be down
right now. Will try again later. Good to know it works ;)

[Latexxx]

Sourceforge seems to be down but this (http://heanet.dl.sourceforge.net/guliverkli/) seems to work.

[ivanova]

:) :) Thanks Latexxx !!

[ivanova]

Vobsub seems to work well. But I could only get one subtitle stream to work. Others aren't selectable, with MPC matroska splitter and the DS one. I had to select 'use regular offscreen plain surfaces' in the VMR 7/9 settings in MPC otherwise the subtitles would not display.

Good work!! ;)

[Liisachan]

to me, selectable subs work fine. I tested:
(1) American movie with English and Japanese subs
(2) HK DVD for Anime with Chinese and English subs
Everything is as easy as multi-sub by SSA.
(Of cource not so beautiful as ssa tho)

Tested: MPC, TCMP, WMP9 on Win 2k JPN and Win XP Eng :)

The only problem I found so far is, "Delay (in ms)" in MMG doesn't work for a VobSub track (so i think).

[Mosu]

Originally posted by Liisachan
The only problem I found so far is, "Delay (in ms)" in MMG doesn't work for a VobSub track (so i think).

Uuuuuuups... Correct ;) Will work in the next release ;)

[Human_USB]

I get this error "Warning: vobsub_packetizer: Could not extract the duration for a SPU packet." when I muxed a idx into a MKV. The subtitles don't show so I'm guessing the error is stopping the subtitles.

Thanks
Jason

[Mosu]

Originally posted by Human_USB
I get this error "Warning: vobsub_packetizer: Could not extract the duration for a SPU packet." when I muxed a idx into a MKV. The subtitles don't show so I'm guessing the error is stopping the subtitles.

That's a warning and not an error (just like the message says), and it shouldn't make the subs disappear.

[Kurtnoise]

10x Mosu by the way for your work....

Any chance to have Universal Subtitles Format (USF) in the next release ?? It could be great for muxing directly in .mkv files ;)

[Mosu]

Originally posted by Kurtnoise13
10x Mosu by the way for your work....

Any chance to have Universal Subtitles Format (USF) in the next release ?? It could be great for muxing directly in .mkv files ;)

Very, very unlikely. The problem is that we're still discussing how to store USF in Matroska. USF is based on XML, and Matroska is based on EBML, a binary form of XML. So we think that we should not just copy the USF text into Matroska but transform the USF elements into Matroska elements. This is a lot of work, and as I said we're still not clear how to do that (or if we do it at all).

[Latexxx]

I got this:

Using AVI demultiplexer for F:\ANIMATRIX\matr.avi. Opening file. This may take some time depending on the file's size.
+-> Using video output module for video track ID 0.
Using AC3 demultiplexer for F:\ANIMATRIX\animatrix AC3 T01 3_2ch 384Kbps DELAY -80ms.ac3.
+-> Using AC3 output module for audio stream.
Using VobSub subtitle reader for 'F:\ANIMATRIX\VTS_01_0.idx' & 'F:\ANIMATRIX\VTS_01_0.sub'.
+-> Using VobSub subtitle output module for subtitle track 3 (language: fi).
Opened 'F:\ANIMATRIX\animatrix.mkv' for writing.
progress: 224/13794 frames (1%)
progress: 446/13794 frames (3%)
progress: 668/13794 frames (4%)
progress: 891/13794 frames (6%)
progress: 1113/13794 frames (8%)
progress: 1335/13794 frames (9%)
progress: 1557/13794 frames (11%)
progress: 1779/13794 frames (12%)
progress: 2002/13794 frames (14%)
progress: 2224/13794 frames (16%)
progress: 2446/13794 frames (17%)
progress: 2668/13794 frames (19%)
progress: 2891/13794 frames (20%)
progress: 3113/13794 frames (22%)
progress: 3335/13794 frames (24%)
progress: 3557/13794 frames (25%)
progress: 3779/13794 frames (27%)
progress: 4002/13794 frames (29%)
progress: 4223/13794 frames (30%)
progress: 4444/13794 frames (32%)
Error: vobsub_packetizer: Inconsistent data in the SPU packets (next_ctrlblk: 2192, packet_size: 2336, data_size: 2306)


The subtitles are available here[link removed; if somebody wants them please pm me].

[Kurtnoise]

Originally posted by Mosu
Very, very unlikely. The problem is that we're still discussing how to store USF in Matroska. USF is based on XML, and Matroska is based on EBML, a binary form of XML. So we think that we should not just copy the USF text into Matroska but transform the USF elements into Matroska elements. This is a lot of work, and as I said we're still not clear how to do that (or if we do it at all).

Ok, I understand. But, just look this picture : http://kurtnoise.free.fr/mkv_usf.gif.....It works fine for me in MPC. :cool:

[Blueseb]

WOAH! new splitter rocks :D
I had the same error as Latexxx, that's caused from the sub track being longer than the video, I cut them via vobsub and remuxed and it works fine

[Mosu]

Originally posted by Kurtnoise13
Ok, I understand. But, just look this picture : http://kurtnoise.free.fr/mkv_usf.gif.....It works fine for me in MPC. :cool:

Don't assume that it will be supported later. There's no official way to store USF in Matroska yet, so things might (and probably will) change.

[Mosu]

Originally posted by Latexxx
I got this:

...



Thanks. I've downloaded the subs and will see what I can do about it.

[Human_USB]

Ok.... I got it working. But a few subtitles were missed by the muxer. When it playes only Line 62 and line 68-69 play. I going to try to mux again.


62
00:06:02,862 --> 00:06:03,886
Torigai?

63
00:06:05,131 --> 00:06:08,294
Torigai! Hey, are you okay?! Hey!

64
00:06:09,335 --> 00:06:10,666
Torigai!

65
00:06:12,739 --> 00:06:14,507
Look after Mamoru for me!

66
00:06:14,507 --> 00:06:15,641
Where are you going?!

67
00:06:15,641 --> 00:06:17,577
Don't worry.

68
00:06:17,577 --> 00:06:19,067
I'll go get...

69
00:06:19,946 --> 00:06:21,379
...help right away!


*EDIT*

I tryed muxing again and still some subtitles were missed. I will try a new dvd and see if it's just this dvd.

[Mosu]

Originally posted by Human_USB
Ok.... I got it working. But a few subtitles were missed by the muxer. When it playes only Line 62 and line 68-69 play. I going to try to mux again.

You should run 'mkvinfo -v yourfile.mkv > report.txt', open report.txt in your favourite text editor, and see if the subtitle track contains entries for the timestamps for those lines that you don't see appearing (63 - 67).

If there are these entries then it's not mkvmerge which is broken.

[Human_USB]

I have the report file but what am I looking for...... all I see is stuff like this;



| + Block group
| + Block (track number 1, 1 frame(s), timecode 825.367s)
| + Frame with size 438
| + Reference block: -42.000ms
| + Block group
| + Block (track number 2, 1 frame(s), timecode 825.391s)
| + Frame with size 729
| + Block duration: 1661.000ms
| + Block group
| + Block (track number 1, 1 frame(s), timecode 825.408s)
| + Frame with size 440
| + Reference block: -41.000ms
| + Block group
| + Block (track number 1, 1 frame(s), timecode 825.450s)
| + Frame with size 534
| + Reference block: -42.000ms



Also I tryed a new DVD and I had some subtitles not show on that one too.

-Jason

[Mosu]

Originally posted by Human_USB
I have the report file but what am I looking for...... all I see is stuff like this;

[list]

| + Block group
| + Block (track number 1, 1 frame(s), timecode 825.367s)
| + Frame with size 438
| + Reference block: -42.000ms


What you're looking for are lines similar to these but with "track number 3" (I'm guessing that track number 3 is the subtitle track, if not search for "track number n" where n is your subtitle track number). If there are such lines with the timecodes that match the ones on your .srt file (entries 63-67) then the subtitles are muxed correctly.

You can also compress report.txt and send the compressed file to me (moritz@bunkus.org) so that I can take a look at it.

[raistlin2k]

IT WORKS!!:) :)

BUT, actually MPC shows only the Language name given by LCID code, not the "name"-tag containing individual data like "comment by Ridley Scott", shouldn't the (any) player show this one as well in the stream-select-dialog?? Otherwise I see only "English" 2 times, quite useless.:confused:

Raist

[Mosu]

Originally posted by raistlin2k
IT WORKS!!:) :)

BUT, actually MPC shows only the Language name given by LCID code, not the "name"-tag containing individual data like "comment by Ridley Scott", shouldn't the (any) player show this one as well in the stream-select-dialog?? Otherwise I see only "English" 2 times, quite useless.:confused:

Raist

Which name? Could you send me your .idx file, please? (moritz@bunkus.org)

Thanks.

[KpeX]

Wow, MKVToolnix / Matroska continues to become more and more versatile. Kudos to Mosu, Gabest, and the rest of the team.

Is there any guideline for what kind of compression ratio can be achieved with zlib compressed vobsub's ?

[Human_USB]

E-Mail sent..... hope you get it.

[raistlin2k]

Originally posted by Mosu
Which name? Could you send me your .idx file, please? (moritz@bunkus.org)

Thanks.

Mosu, why the IDX file?

I'm talking about the "name"-tag of audio-streams. Sorry that I didn't write this in my last post clearly.

Your GUI for mkvmerge shos a tooltip over the name-tag that it an be used for things like "director's comment" so I did so, but no players shows this at all.

Thanks
Raist

P.S. Do you still want my IDX-file?
P.P.S. Just tried to convert several OGM + IDX into MKV, noticed that it doesn't work with one movie where there is only one sub inside the .SUB, under stream 8.:confused:

[Mosu]

Originally posted by KpeX
Is there any guideline for what kind of compression ratio can be achieved with zlib compressed vobsub's ?

You will usually get a reduction to 40-50% of the original size:

10338304 2003-10-29 18:09 vs/ally1.sub
6740374 2003-11-10 19:15 nocomp.mkv
4576954 2003-11-10 19:15 zlibcomp.mkv


Explanation: VobSubs, when extracted with VSRip, still contain a complete MPEG PS (or was it TS?). Additionally this stream uses padding up to 2kb block boundaries wasting a lot of space (well on a DVD it doesn't matter, but for us it does). We only need the SPU packets so we discard the MPEG PS. The resulting SPU packets are put into a Matroska file either uncompressed (nocomp.mkv) or compressed with zlib at its best compression setting (zlibcomp.mkv).

So just by discarding the SPU packets we gain approx. 35%. The SPU packets themselves can be compressed further down to ~66% of their original size.

I haven't done extensive checking but other streams should result in similar numbers. This VobSub contains of eight streams for a 42minutes episode of Ally McBeal.

[Mosu]

Originally posted by raistlin2k
Mosu, why the IDX file?

I'm talking about the "name"-tag of audio-streams. Sorry that I didn't write this in my last post clearly.

Uuups. I though there was some obscure "name" tag in the .idx for the VobSub file which mkvmerge did not convert to a Matroska track name.

No, I don't need the .idx then :)

Your GUI for mkvmerge shos a tooltip over the name-tag that it an be used for things like "director's comment" so I did so, but no players shows this at all.

Sorry, I don't know enough about Windows, DirectShow etc. in order to place blame. It's either the splitter's or the player's fault, obviously.

P.P.S. Just tried to convert several OGM + IDX into MKV, noticed that it doesn't work with one movie where there is only one sub inside the .SUB, under stream 8.:confused:

Is this .idx+.sub small? If so, can you send it to me please? moritz@bunkus.org

Thanks.

[Pasqui]

Hi Mosu,
using mkvtoolnix 0.7.5, I got the following error while muxing a XviD video, a vorbis audio and a VobSub file:

Using AVI demultiplexer for D:\XMEN2_DISC1\VIDEO_TS\X-Men 2.avi. Opening file. This may take some time depending on the file's size.
+-> Using video output module for video track ID 0.
Using OGG/OGM demultiplexer for D:\XMEN2_DISC1\VIDEO_TS\XMen2 AC3 T01 3_2ch 448Kbps DELAY -24ms - New - [10.11.2003] - [12.46.09].ogg.
OGG/OGM demultiplexer (D:\XMEN2_DISC1\VIDEO_TS\XMen2 AC3 T01 3_2ch 448Kbps DELAY -24ms - New - [10.11.2003] - [12.46.09].ogg): using Vorbis output module for stream 19749.
Using VobSub subtitle reader for 'D:\XMEN2_DISC1\VIDEO_TS\X-Men 2.idx' & 'D:\XMEN2_DISC1\VIDEO_TS\X-Men 2.sub'.
+-> Using VobSub subtitle output module for subtitle track 1 (language: en).
+-> Using VobSub subtitle output module for subtitle track 2 (language: fr).
Opened 'D:\XMEN2_DISC1\VIDEO_TS\X-Men 2.mkv' for writing.
progress: 176/192449 frames (0%)
progress: 350/192449 frames (0%)
progress: 523/192449 frames (0%)
.
.
.
progress: 109774/192449 frames (57%)
progress: 109943/192449 frames (57%)
progress: 110100/192449 frames (57%)
mkvmerge FAILED with a return code of -2147483641.

Any idea of what's going on ?
BTW, thanks for your great tools !

Pasqui.

EDIT: the failure seems related to the zlib compression because the multiplexing was successful without compression.

EDIT2: the error appears randomly: after several tries and failures at different percentage done, I successfully muxed the file with subtitles compressed.

[Human_USB]

@Mosu


Did you get the file?