View Full Version : mkvtoolnix (Matroska toolkit): new release
Pages :
1
2
3
4
5
6
7
8
[
9]
10
11
12
13
14
15
16
17
18
19
20
Mosu
8th February 2004, 16:30
Originally posted by filewalker
I noticed that MKVMerge doesn't read the language information from the file.
Further the chapter information (created from DVDecrypter)is also lost in the muxed MKV file.
Yep, mkvmerge does not read those yet.
filewalker
8th February 2004, 16:53
Originally posted by Mosu
Yep, mkvmerge does not read those yet.
Thanks for confirmation.
I noticed it because I'm now transferring all my old OGM files to MKV.
It works well with the mentioned workaround (open OGM in VDMod, save it as MKV, open this MKV in MKVMerge, add language info to the streams & attachments and save it as MKV)
I just wanted to point it out...for better OGM input support in the future. :)
Cu filewalker
Mosu
8th February 2004, 17:38
Originally posted by filewalker
I just wanted to point it out...for better OGM input support in the future. :)
How do those language tags look? "LANGUAGE=German" ? If so, then I won't be able to convert them properly because there is no 1:1 conversion between a language name and a ISO639-2 code which are used in Matroska. If it's some useful ISO639 code (e.g. "LANGUAGE=ger") then I can.
filewalker
8th February 2004, 18:08
I made a screenshot from VDMod stream comments:
http://www.geocities.com/filewalker666/OGM_language.gif (copy& paste in a new fresh browser window - Geocities doesn't allow direct linking).
I hope it shows you the answear to your question... :rolleyes:
edit:
but Suiryc or Belgabor can give you surely an answer...
Cu filewalker
Mosu
8th February 2004, 19:37
Originally posted by filewalker
I hope it shows you the answear to your question... :rolleyes: ]
Thanks, it does answer my question. Could you please try this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.8.2-build20040208-1.rar
Thanks.
pixolex
8th February 2004, 19:40
Originally posted by Mosu
It does work for me if you use "Chapter Editor -> Load" and then select a Matroska file. Does it not work for you? What does happen? Nothing at all (meaning no chapters are being loaded)? If you run mkvinfo on the file (with at least one '-v'), do the chapters show up then?
BTW: You should use a build newer than 0.8.2 because I've rewritten the chapter editor after 0.8.2.
:rolleyes: it's my fault :o it works like that...i just put in my head that when i open a mkv file the chapters would open automaticaly in chapters editor...sorry :(
Other question...it's not possible join two mkv files, like a 2cd rip to put in a DVD, with mkvtoolnix isn't it?
Mosu
8th February 2004, 19:49
Originally posted by pixolex
:rolleyes: it's my fault :o it works like that...i just put in my head that when i open a mkv file the chapters would open automaticaly in chapters editor...sorry :(
No problem at all :)
Other question...it's not possible join two mkv files, like a 2cd rip to put in a DVD, with mkvtoolnix isn't it?
That's correct. You have two choices: VirtualDubMod and AVIMux-GUI.
filewalker
8th February 2004, 19:57
Originally posted by Mosu
Thanks, it does answer my question. Could you please try this build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.8.2-build20040208-1.rar
Thanks.
If I try to open any .OGM file, an error message pops up:
'mkvmerge-i'failed. Return code: -1073741819
Cu filewalker
Mosu
8th February 2004, 20:04
Originally posted by filewalker
If I try to open any .OGM file, an error message pops up:
'mkvmerge-i'failed. Return code: -1073741819
Cu filewalker
Hmm, that's usually a segmentation fault. Could you please upload the first 1MB of the file? Thanks.
filewalker
8th February 2004, 20:37
I tested a little bit with my OGM files:
I can open most of my OGM files with your latest build. :)
But with some movies which were muxed with old VDMod versions (about 1 year ago or older)I get this error message in MKVmerge.
I noticed that if I open such an OGM file in the newest VDMod and cut out 1 Mb and save it as OGM again, this new muxed OGM opens fine in MKVmerge...therefore I can't send you 1 Mb of such an old OGM file. :rolleyes:
With the OGM files, which were opened in MKVMerge I noticed that:
chapters are now adopted from the OGM file to MKV! :) cool!
the language title of the streams shows "none"
Cu filewalker
Mosu
8th February 2004, 20:41
Originally posted by filewalker
I noticed that if I open such an OGM file in the newest VDMod and cut out 1 Mb and save it as OGM again, this new muxed OGM opens fine in MKVmerge...therefore I can't send you 1 Mb of such an old OGM file. :rolleyes:
You can. Just use VDubMod's hex editor and safe the first MB of such a file. That way VDubMod will not remux anything.
filewalker
8th February 2004, 21:20
Now I opened the OGM file with the Hex editor from VDMod...but I can't save anything ("save" is greyed out).
I'm not familiar with this hex editor...can you tell my step by step what I should do after opening the OGM file in hex editor? :rolleyes:
Cu filewalker
alexnoe
8th February 2004, 21:26
Are you sure you disabled read-only in the opending dialog when opening the file?
filewalker
8th February 2004, 21:53
I opened the file in the "read only" mode, but there's no opening dialog which asks me to disable this mode.
I searched all options in VDMod but I haven't found an option to disable "read only".
Any idea?
Mosu
8th February 2004, 21:57
Originally posted by filewalker
I opened the file in the "read only" mode, but there's no opening dialog which asks me to disable this mode.
I searched all options in VDMod but I haven't found an option to disable "read only".
Any idea?
If you're really having trouble you could also just start uploading the file to my FTP server and cancel the upload after about 1 MB :)
filewalker
8th February 2004, 22:21
It's up...it's called "From_Hell.ogm"
Mosu
8th February 2004, 23:59
Originally posted by filewalker
It's up...it's called "From_Hell.ogm"
Thanks, works now with http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.8.2-build20040208-2.rar It'll convert the chapters, the LANGUAGE and the TITLE tags. The TITLE tag will also used as the segment title ( = Matroska file title) if none was set.
DKDIB
9th February 2004, 16:33
Filewalker wrote:
> I'm not familiar with this hex editor...can you tell [...]
Some months ago, when Gabest released his AVI Splitter, I wrote "a couple of scissor" (in Python) to produce broken AVI.
Installer (http://digilander.libero.it/dkdib/Software/Scissors.exe) (Win/WinNT)
Source (http://digilander.libero.it/dkdib/Software/Scissors%20--%20Source.7z) + scripts to make Win/WinNT installer (Any Python-powered platform)
filewalker
9th February 2004, 16:53
Originally posted by Mosu
Thanks, works now with http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.8.2-build20040208-2.rar It'll convert the chapters, the LANGUAGE and the TITLE tags. The TITLE tag will also used as the segment title ( = Matroska file title) if none was set.
:)
I tested it now...wow...it works like a charme!
Language & chapter info is now adopted from the OGM file to MKV file...really great!!! :)
(What is a little bit confusing is that "language" shows none, although it's there.)
THANKS for your work! :)
Cu filewalker
Mosu
9th February 2004, 23:18
Heya,
it's been a couple of days since 0.8.2, and here's 0.8.3. A lot has changed internally, and I hope I haven't broken too many things ;) So far there have been really useful bug reports, so I hope it's ok. This release features bug fixes and new features, though these aren't major. Please read the ChangeLog (see below) for a full explanation.
The mkvtoolnix homepage:
http://www.bunkus.org/videotools/mkvtoolnix/index.html
The source code:
http://www.bunkus.org/videotools/mkvtoolnix/sources/mkvtoolnix-0.8.3.tar.bz2
Windows binaries:
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.8.3.rar
Those Windows users updating from a version prior to 0.8.2 need to
re-download the runtime package:
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-runtime.rar
The ChangeLog since 0.8.2:
2004-02-09 Moritz Bunkus <moritz@bunkus.org>
* Released v0.8.3.
2004-02-08 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: new feature: The LANGUAGE, TITLE tags and chapters are being kept when reading OGM files.
* mkvmerge: Changed the meaning of '--global-tags'. They now apply to the complete file.
2004-02-07 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: VobSub durations were not converted from ms to ns precision resulting in VERY short packets :)
2004-02-01 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: The change from ms to ns precision broke subtitle handling from OGM.
2004-01-31 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Made "do not link files when splitting" the default, just like in mmg.
* mkvmerge: new feature: Enabled reading of AAC from OGMs.
* mkvmerge: The VobSub reader will not discard packets that exceed a certain size (64KB) anymore.
* mkvmerge: Improved some internal memory freeing decisions. This should help with files/sections in which are only few keyframes.
2004-01-30 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Changed the two-pass splitting into a one-pass splitting. The resulting files will always be a little bit larger than the desired size/length, but this shouldn't matter.
2004-01-25 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: Segfault when using external timecode v1 files.
2004-01-24 Moritz Bunkus <moritz@bunkus.org>
* mmg: Rewrote the chapter editor. It now makes a lot more sense: You can have multiple names for one chapter entry, and for each name there's only one language/country association.
2004-01-23 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: bug fix: The AAC-in-Real stuff again.
2004-01-22 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Changed the complete timecode handling from ms precision to ns precision. Expect some things to be broken by this change.
* mkvmerge: bug fix: Fixed a couple of memory leaks, especially in the QuickTime/MP4 parser.
2004-01-21 Moritz Bunkus <moritz@bunkus.org>
* mmg: Added some more extensions for RealMedia files.
* mkvmerge: bug fix: Proper handling for AAC read from RealMedia files (sample rate/output sample rate were not assigned correctly).
Have fun :)
Rash
10th February 2004, 03:55
Amazing! Thanks Mosu. ;)
pixolex
10th February 2004, 11:42
2004-01-30 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Changed the two-pass splitting into a one-pass splitting. The resulting files will always be a little bit larger than the desired size/length, but this shouldn't matter.
@mosu
Who long? can you say :)
thanks!
Mosu
10th February 2004, 11:59
Originally posted by pixolex
2004-01-30 Moritz Bunkus <moritz@bunkus.org>
* mkvmerge: Changed the two-pass splitting into a one-pass splitting. The resulting files will always be a little bit larger than the desired size/length, but this shouldn't matter.
@mosu
Who long? can you say :)
thanks!
Until the next keyframe after the size/duration has been reached. Usually, for 'normal' files with 'sensitive' key frame intervals, this shouldn't be more than 1 or 2mb. But you will probably not have any problems with that anyway because modern CD burners can overburn a CD, and a 700MB CD can easily contain at least 703MB. So if you split aftter 700MB you're still safe even if mkvmerge will produce files that are slightly larger.
Another reason why this is really not so big an issue. The most common scenario is that you have a file, e.g. 1400MB big, that you want to chop down into two 700MB pieces. At the moment you'd probably chose '--split 700MB --split-max-files 2' so that you get at most 2 files. This way the old mkvmerge would produce one file that is slightly smaller than 700MB and a second that wil be slightly larger. The new mkvmerge will instead make the first file a bit larger and the second one a bit smaller.
So basically not a lot changes, and in most cases you're better off because there's only one pass. If you don't like the size of the resulting files you can still adjust the --split parameter and try again.
P0l1m0rph1c
10th February 2004, 16:41
The version numbers were wrong (still said 0.8.2) when 0.8.3 was out? Is that already corrected?
Mosu
10th February 2004, 16:57
Originally posted by P0l1m0rph1c
The version numbers were wrong (still said 0.8.2) when 0.8.3 was out? Is that already corrected?
Someone has told me that already yesterday evening and I uploaded a new build which should have the right version number. When did you donwload your copy?
filewalker
10th February 2004, 19:51
Cool, thanks for the new version! :)
OT:
just a reminder:
During conversion from OGM to MKV I noticed & remembered that it was possible for OGM muxing to use the 'comments' tags, but this comments aren't adopted to MKV (both in MKVMerge and VDMod).
The default name is "english" instead.
Please note that when transmuxing OGMs into MKVs these have to be set manually, because neither VdubMod nor mkvmerge will copy the OGM comments into the track name element for the MKV. Read here (http://forum.doom9.org/showthread.php?s=&threadid=65600) for the info.
Cu filewalker
Mosu
10th February 2004, 20:03
Originally posted by filewalker
OT:
just a reminder:
During conversion from OGM to MKV I noticed & remembered that it was possible for OGM muxing to use the 'comments' tags, but this comments aren't adopted to MKV (both in MKVMerge and VDMod).
'comments' tags ??? mkvmerge will now convert the following comments for tracks read from OGM files if they were present:
1) CHAPTERxx... and CHAPTERxxNAME... will be converted to chapters,
2) LANGUAGE=... will be converted into the track language,
3) TITLE=... will be converted into the track name (what VDubMod calls 'title'). Additionally, if the source track is a video track, this title will be used as the segment title as well.
The default name is "english" instead.
Default name?
filewalker
10th February 2004, 20:30
In former days I used VDMod for OGM muxing.
In the "stream comments" window I used following:
Watch this picture for better understanding:
http://www.geocities.com/filewalker666/OGM_language_tag.gif
language (from dropdown list)
"user defined" and beside this line it was possible to write what you wanted into the "value" line.(and this value line was displayed by the player)
If I had only used the pre-difened possibilities from the dropdown list, then it would work with MKVMerge.
In my case,after converting to MKV with MKVMerge, English(USA) is listed in my player instead of "Spanish"
But I think that this "self-titleing" by hand is not a standard...so I have no problem with it...
Cu filewalker
Mosu
10th February 2004, 20:37
Ok, now I know what the problem is. My problem is that the list of languages I use for mkvmerge/mmg was copied from the ISO639 norm and often contains multiple names for one language. In your case, "Spanish", my list contains "Spanish; Castilian". As the language given in the OGM file must match one in the list exactly this will fail. I should probably clean up the list a bit and resolve this by using two separate entries, one called 'Spanish', one 'Castilian'. Or something like that.
filewalker
10th February 2004, 20:45
I should probably clean up the list a bit and resolve this by using two separate entries, one called 'Spanish', one 'Castilian'. Or something like that.
What I wanted to say is that it's possible that you can write what you want in the value line, e.g "Spanisch (Dialekt Andalusisch bla bla bla)"
...and the player displays "Spanisch (Dialekt Andalusisch bla bla bla)"
:rolleyes: I think that it's not really easy for you, if no standard is used.:rolleyes:
Cu filewalker
Mosu
10th February 2004, 20:51
You can try this new build: http://www.bunkus.org/videotools/mkvtoolnix/win32/pre/mkvtoolnix-0.8.3-build20040210-1.rar It'll recognize at least all the languages given in iso639.cpp (or in mmg in the appropriate drop down boxes) - and it'll split each entry that contains a ";" into the individual parts and compares those as well. So "Spanish" should now be converted correctly.
However, if you have some other contents (e.g. "LANGUAGE=that fucking cool language, dude!") then it won't work, of course, as Matroska only uses the ISO639-2 codes an d not free form strings.
Mosu
10th February 2004, 20:51
Originally posted by filewalker
What I wanted to say is that it's possible that you can write what you want in the value line, e.g "Spanisch (Dialekt Andalusisch bla bla bla)"
...and the player displays "Spanisch (Dialekt Andalusisch bla bla bla)"
Right, those won't/cannot be converted automatically.
filewalker
10th February 2004, 21:28
wow!:eek: you're really fast!
:) yep, it works if "LANGUAGE=Spanish"...it's converted correctly.
The player shows "Castilian;Spanish"
Right, those won't/cannot be converted automatically.
I was afraid of this answer...
but your solution helps me, nevertheless...because I mostly used the german names for the languages e.g. "Englisch" instead of "English"...("Deutsch" instead of "German" :( )
Cu filewalker
pixolex
11th February 2004, 01:27
Originally posted by Mosu
Until the next keyframe after the size/duration has been reached. Usually, for 'normal' files with 'sensitive' key frame intervals, this shouldn't be more than 1 or 2mb. But you will probably not have any problems with that anyway because modern CD burners can overburn a CD, and a 700MB CD can easily contain at least 703MB. So if you split aftter 700MB you're still safe even if mkvmerge will produce files that are slightly larger.
Another reason why this is really not so big an issue. The most common scenario is that you have a file, e.g. 1400MB big, that you want to chop down into two 700MB pieces. At the moment you'd probably chose '--split 700MB --split-max-files 2' so that you get at most 2 files. This way the old mkvmerge would produce one file that is slightly smaller than 700MB and a second that wil be slightly larger. The new mkvmerge will instead make the first file a bit larger and the second one a bit smaller.
So basically not a lot changes, and in most cases you're better off because there's only one pass. If you don't like the size of the resulting files you can still adjust the --split parameter and try again.
Thanks :)
Mosu
11th February 2004, 09:42
Heya,
due to a very unfriendly bug I have to release 0.8.4 not two days after 0.8.3. Nash reported that when reading Matroska files durations were omitted which is fatal for any subtitle track (both VobSubs and text subs). This is the only change, but I strongly encourage you to update.
The mkvtoolnix homepage:
http://www.bunkus.org/videotools/mkvtoolnix/index.html
The sources:
http://www.bunkus.org/videotools/mkvtoolnix/sources/mkvtoolnix-0.8.4.tar.bz2
Windows binaries:
http://www.bunkus.org/videotools/mkvtoolnix/win32/mkvtoolnix-0.8.4.rar
The ChangeLog since 0.8.3:
2004-02-11 Moritz Bunkus <moritz@bunkus.org>
* Released v0.8.4.
* mkvmerge: bug fix: When reading Matroska files the durations attached to blocks were lost (e.g. for subtitle tracks).
mikeX
11th February 2004, 20:01
hi mosu, first of all many thanks for your great job
the bug in 0.8.3 doesn't seem to happen here with a file i remuxed...(unless it happens on random parts of the movie)
i have a small (i hope) request:
if it's possible could mmg-gui set the FourCC field to the value it reads from a matroska file (if any) (it can read the value right?), or generally reset (blank) the field when sellecting a different video stream (i mean it does so for the 'Language', 'Cue', etc fields).
'Cause if i (it could happen to anyone really) for example forget to change it manually and mux a video with different codecID i end up with unplayable files.
Mosu
11th February 2004, 20:07
Originally posted by mikeX
i have a small (i hope) request:
if it's possible could mmg-gui set the FourCC field to the value it reads from a matroska file (if any) (it can read the value right?), or generally reset (blank) the field when sellecting a different video stream (i mean it does so for the 'Language', 'Cue', etc fields).
'Cause if i (it could happen to anyone really) for example forget to change it manually and mux a video with different codecID i end up with unplayable files.
Ah yes, this little bug - I always forget to fix it. Hopefully I'll remember it now :)
mikeX
12th February 2004, 01:57
:D nice!
while you 're at it, i remember getting some weird sync problems with ssa subtitles
this is not a bug report really, just checking if anyone else has experienced the same, since i can't really reproduce it atm (big repartioning/format in progress)
actually it's very likely that mkvtoolnix is not to blame, since the original subtitles were in microdvd sub format, exported to ssa with u96 v0.1.9.16 (when i exported the same subs to srt there were no problems however)
it occured with 0.8.1 or 0.8.2 (can' remember correctly) and recently with some other subs and version 0.8.3 (all win versions)
it looked as if the subtitles gradually lost sync
hmmm, come to think of it, iirc they played in sync when opened separately through media player classic (i'm no too sure though)...
well, if anyone else has experienced this or if it's a known problem i could try reproducing it in a couple of days, if that would help debuging
if on the other hand i'm the only one with it, it's probably a u96 bug...
thanks for your time ;)
Mosu
12th February 2004, 09:24
Originally posted by mikeX
:D nice!
while you 're at it, i remember getting some weird sync problems with ssa subtitles
You should check if mkvtoolnix is messing with the timecodes. If not then either U96 or some part of the playback chain (player, filters etc) is to blame.
In order to check you can run 'mkvinfo -v yourfile.mkv > output.txt' and search in output.txt for the blocks belonging to the subtitle track. They'll have a timecode and a duration attached to them, and these should match the ones given in the .ssa file. If they do match then mkvmerge is doing its job correctly.
mikeX
12th February 2004, 11:32
thanks a lot, will do as soon as i can and report back :)
lighty
13th February 2004, 23:10
500 posts in this thread?!
I guess it would be a good thing to open a new thread or to separate this one into multiple topics.
Mosu
14th February 2004, 00:34
Originally posted by lighty
500 posts in this thread?!
I guess it would be a good thing to open a new thread or to separate this one into multiple topics.
Hehe, you've probably got a point ;) I just don't to cludder the forum with too many mkvtoolnix posts. But the next release will get a new thread if no one objects.
pixolex
14th February 2004, 14:24
@Mosu
Hy! :)
Just for curiosity...what are the new features you are planing to implement in futures realeases of MKVTOOLNIX. There are any public TO DO list or wish list? :)
Thanks for this indispensable tool!
filewalker
14th February 2004, 15:17
Hi,
I have a further problem with OGM -->MKV conversion.:rolleyes: it seems to be a problem during splitting process of OGM in VDMod. So maybe you can help here...
I muxed an 1400Mb OGM in VDMod and the splitted it in two 700 Mb files for burning.
I noticed now that both splitted parts contain all chapter points and all are listed in the chapter list(player), though only the half of the chapter points are real.
Is it possible that MKVMerge checks the time durations of the chapter points with the movie duration and that only the corresponding chapter points are adopted to new muxed MKV file.
I hope you understand for what I aimed at...
Cu filewalker :)
Griniaris
14th February 2004, 16:54
Filewalker look at this (http://forum.doom9.org/showthread.php?threadid=70347). Maybe it helps you. It is about matroska chapters but maybe it also works for ogm chapters...
filewalker
14th February 2004, 18:20
@Griniaris
Well, that's a different story.
Your thread is about the "link files" feature in MKVmerge, which isn't supported from any player atm.
My problem is that many of my old OGM movies are muxed with VDMod and were splitted in 2 parts for burning on 2 CDs.
(apparently it's a bug in VDMod if you splitt a movie with chapters - it's not a mistake of MKVmerge which adopt the OGM as it's created by VDMod)
e.g. a movie has 10 chapters. After splitting with VDMod both parts show all 10 chapters in the player (though the first part has only 5 chapters in reality, and the second part has the next 5 chapters in reality.
If I playback the first part of the movie, I can jump between the first 5 chapters without problems, but if I jump to e.g. chapter 7, the player stops because this chapter is on the second part(CD)of the movie.
Cu filewalker
Mosu
14th February 2004, 19:19
Originally posted by filewalker
e.g. a movie has 10 chapters. After splitting with VDMod both parts show all 10 chapters in the player (though the first part has only 5 chapters in reality, and the second part has the next 5 chapters in reality.
At the moment mkvmerge will just use all the chapters as they are if no splitting is used, and it will throw away and adjust chapters if splitting is active. I think you could use some kind of workaround: When muxing your OGM file activate splitting but chose a size that's definitely larger than your source file, e.g. use --split 1400m for a 700m file. Maybe that'll make mkvmerge throw away the chapters that don't apply. (maybe = I haven't tested it)
Mosu
14th February 2004, 19:25
Originally posted by pixolex
@Mosu
Hy! :)
Just for curiosity...what are the new features you are planing to implement in futures realeases of MKVTOOLNIX. There are any public TO DO list or wish list? :)
Thanks for this indispensable tool!
No, at the moment I don't have a proper TODO list. I have one in my sources, but I don't bother updating it...
Things that come to mind are (in random order):
1) Proper support for native B frame handling,
2) Support for appending files,
3) Support for processing only parts of a file (e.g. from timecode x to timecode y),
4) Support for reading MPEG4 video from MP4 files (depends on 1)),
5) Rewrite mmg to support Unicode enabled versions of wxWindows and thus allowing the use of Unicode in all fields,
6) Add a tag editor to mmg (similar to the chapter editor - it should be able to edit tags in Matroska files and XML tag files that can be used with mkvmerge),
7) Fix bugs,
8) Produce new bugs...
The problem with 1-5 is that they're very time consuming. 6 might happen sooner. Maybe 3, too.
Any wishes/suggestions?
Apart from that - what I want to program next is probably a Matroska output module for transcode, a Linux/Unix video processing tool.
filewalker
15th February 2004, 00:24
Originally posted by Mosu
At the moment mkvmerge will just use all the chapters as they are if no splitting is used, and it will throw away and adjust chapters if splitting is active. I think you could use some kind of workaround: When muxing your OGM file activate splitting but chose a size that's definitely larger than your source file, e.g. use --split 1400m for a 700m file. Maybe that'll make mkvmerge throw away the chapters that don't apply. (maybe = I haven't tested it)
Thanks for this workaround.:)
The first part shows the right chapters perfectly.:)
The second part shows again the same chapters as in the first part, and it begins from 1 again (not continued).
Do you know a trick that the second part of the movie shows continued chapters? ...that would be perfect.
Cu filewalker
Mosu
15th February 2004, 00:32
Originally posted by filewalker
Do you know a trick that the second part of the movie shows continued chapters? ...that would be perfect.
Nope, sorry.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.