1MKVMERGE(1) User Commands MKVMERGE(1)
2
6 mkvmerge - Merge multimedia streams into a Matroska(TM) file
7
9 mkvmerge [global options] {-o out} [options1] {file1}
10 [[options2] {file2}] [@options-file.json]
11
13 This program takes the input from several media files and joins their
14 streams (all of them or just a selection) into a Matroska(TM) file; see
15 the Matroska(TM) website[1].
16 Important
18 The order of command line options is important. Please read the
19 section "Option order" if you're new to the program.
20 Global options
22 -v, --verbose
23 Increase verbosity.
24 -q, --quiet
26 Suppress status output.
27 -o, --output file-name
29 Write to the file file-name. If splitting is used then this
30 parameter is treated a bit differently. See the explanation for the
31 --split option for details.
32 -w, --webm
34 Create a WebM compliant file. This is also turned on if the output
35 file name's extension is "webm". This mode enforces several
36 restrictions. The only allowed codecs are VP8, VP9 video and Opus,
37 Vorbis audio tracks. The DocType header item is changed to "webm".
38 For chapters and tags only a subset of elements are allowed.
40 mkvmerge(1) will automatically remove all elements not allowed by
41 the specification.
42 --title title
44 Sets the general title for the output file, e.g. the movie name.
45 --default-language language-code
47 Sets the default language code that will be used for tracks for
48 which no language is set with the --language option and for which
49 the source container doesn't provide a language.
50 The default language code is 'und' for 'undetermined'.
52 Segment info handling (global options)
54 --segmentinfo filename.xml
55 Read segment information from an XML file. This file can contain
56 the segment family UID, segment UID, previous and next segment UID
57 elements. An example file and a DTD are included in the MKVToolNix
58 distribution.
59 See the section about segment info XML files below for details.
61 --segment-uid SID1,SID2,...
63 Sets the segment UIDs to use. This is a comma-separated list of
64 128-bit segment UIDs in the usual UID form: hex numbers with or
65 without the "0x" prefix, with or without spaces, exactly 32 digits.
66 If SID starts with = then its rest is interpreted as the name of a
68 Matroska file whose segment UID is read and used.
69 Each file created contains one segment, and each segment has one
71 segment UID. If more segment UIDs are specified than segments are
72 created then the surplus UIDs are ignored. If fewer UIDs are
73 specified than segments are created then random UIDs will be
74 created for them.
75 Chapter and tag handling (global options)
77 --chapter-language language-code
78 Sets the ISO 639-2 language code that is written for each chapter
79 entry. Defaults to 'eng'. See the section about chapters below for
80 details.
81 This option can be used both for simple chapter files and for
83 source files that contain chapters but no information about the
84 chapters' language, e.g. MP4 and OGM files.
85 The language set with this option is also used when chapters are
87 generated with the --generate-chapters option.
88 --chapter-charset character-set
90 Sets the character set that is used for the conversion to UTF-8 for
91 simple chapter files. See the section about text files and
92 character sets for an explanation how mkvmerge(1) converts between
93 character sets.
94 This switch does also apply to chapters that are copied from
96 certain container types, e.g. Ogg/OGM and MP4 files. See the
97 section about chapters below for details.
98 --chapter-sync d[,o[/p]]
100 Adjust the timestamps of the chapters in the following source file
101 by d ms. Alternatively you can use the --sync option with the
102 special track ID -2 (see section special track IDs).
103 o/p: adjust the timestamps by o/p to fix linear drifts. p defaults
105 to 1 if omitted. Both o and p can be floating point numbers.
106 Defaults: no manual sync correction (which is the same as d = 0 and
108 o/p = 1.0).
109 This option can be used multiple times for an input file applying
111 to several tracks by selecting different track IDs each time.
112 --generate-chapters mode
114 mkvmerge(1) can create chapters automatically. The following two
115 modes are currently supported:
116 • 'when-appending' – This mode creates one chapter at the start
118 and one chapter whenever a file is appended.
119 This mode also works with split modes 'parts:' and
121 'parts-frames:'. For these modes one chapter will be generated
122 for each appended timestamp range (those whose start timestamps
123 are prefixed with '+').
124 Note
126 mkvmerge(1) requires a video or an audio track to be
127 present in order to be able to determine when a new file is
128 appended. If one or more video tracks are muxed the first
129 one is used. Otherwise the first audio track is used.
130 • 'interval:time-spec' – This mode creates one chapter at fixed
132 intervals given by time-spec. The format is either the form
133 HH:MM:SS.nnnnnnnnn or a number followed by one of the units
134 's', 'ms' or 'us'.
135 Example: --generate-chapters interval:45s
137 The names for the new chapters are controlled by the option
139 --generate-chapters-name-template. The language is set with
140 --chapter-language which must occur before --generate-chapters.
141 --generate-chapters-name-template template
143 This sets the name template for chapter names generated by the
144 option --generate-chapters. If the option is not used then default
145 'Chapter <NUM:2>' will be used.
146 There are several variables that can be used in the template that
148 are replaced by their actual values when a chapter is generated.
149 The string '<NUM>' will be replaced by the chapter number. The
150 string '<START>' will be replaced by the chapter's start timestamp.
151 The strings '<FILE_NAME>' and '<FILE_NAME_WITH_EXT>' are only
153 filled when generating chapters for appended files. They will be
154 replaced by the appended file's name without respectively with its
155 extension. Note that only the file's base name and extension are
156 inserted, not its directory or drive components.
157 You can specify a minimum number of places for the chapter number
159 with '<NUM:places>', e.g. '<NUM:3>'. The resulting number will be
160 padded with leading zeroes if the number of places is less than
161 specified.
162 You can control the format used by the start timestamp with
164 <START:format>. The format defaults to '%H:%M:%S' if none is given.
165 Valid format codes are:
166 • %h – hours
168 • %H – hours zero-padded to two places
170 • %m – minutes
172 • %M – minutes zero-padded to two places
174 • %s – seconds
176 • %S – seconds zero-padded to two places
178 • %n – nanoseconds with nine places
180 • %<1-9>n – nanoseconds with up to nine places (e.g. three places
182 with %3n)
183 --cue-chapter-name-format format
185 mkvmerge(1) supports reading CUE sheets for audio files as the
186 input for chapters. CUE sheets usually contain the entries
187 PERFORMER and TITLE for each index entry. mkvmerge(1) uses these
188 two strings in order to construct the chapter name. With this
189 option the format used for this name can be set.
190 If this option is not given then mkvmerge(1) defaults to the format
192 '%p - %t' (the performer, followed by a space, a dash, another
193 space and the title).
194 If the format is given then everything except the following meta
196 characters is copied as-is, and the meta characters are replaced
197 like this:
198 • %p is replaced by the current entry's PERFORMER string,
200 • %t is replaced by the current entry's TITLE string,
202 • %n is replaced by the current track number and
204 • %N is replaced by the current track number padded with a
206 leading zero if it is < 10.
207 --chapters file-name
209 Read chapter information from the file file-name. See the section
210 about chapters below for details.
211 --global-tags file-name
213 Read global tags from the file file-name. See the section about
214 tags below for details.
215 General output control (advanced global options)
217 --track-order FID1:TID1,FID2:TID2,...
218 This option changes the order in which the tracks for an input file
219 are created. The argument is a comma separated list of pairs IDs.
220 Each pair contains first the file ID (FID1) which is simply the
221 number of the file on the command line starting at 0. The second is
222 a track ID (TID1) from that file. If some track IDs are omitted
223 then those tracks are created after the ones given with this option
224 have been created.
225 --cluster-length spec
227 Limit the number of data blocks or the duration of data in each
228 cluster. The spec parameter can either be a number n without a unit
229 or a number d postfixed with 'ms'.
230 If no unit is used then mkvmerge(1) will put at most n data blocks
232 into each cluster. The maximum number of blocks is 65535.
233 If the number d is postfixed with 'ms' then mkvmerge(1) puts at
235 most d milliseconds of data into each cluster. The minimum for d is
236 '100ms', and the maximum is '32000ms'.
237 mkvmerge(1) defaults to putting at most 65535 data blocks and
239 5000ms of data into a cluster.
240 Programs trying to find a certain frame can only seek directly to a
242 cluster and have to read the whole cluster afterwards. Therefore
243 creating larger clusters may lead to imprecise or slow seeking.
244 --clusters-in-meta-seek
246 Tells mkvmerge(1) to create a meta seek element at the end of the
247 file containing all clusters. See also the section about the
248 Matroska(TM) file layout.
249 --timestamp-scale factor
251 Forces the timestamp scale factor to factor. Valid values are in
252 the range 1000..10000000 or the special value -1.
253 Normally mkvmerge(1) will use a value of 1000000 which means that
255 timestamps and durations will have a precision of 1ms. For files
256 that will not contain a video track but at least one audio track
257 mkvmerge(1) will automatically chose a timestamp scale factor so
258 that all timestamps and durations have a precision of one audio
259 sample. This causes bigger overhead but allows precise seeking and
260 extraction.
261 If the special value -1 is used then mkvmerge(1) will use sample
263 precision even if a video track is present.
264 --enable-durations
266 Write durations for all blocks. This will increase file size and
267 does not offer any additional value for players at the moment.
268 --no-cues
270 Tells mkvmerge(1) not to create and write the cue data which can be
271 compared to an index in an AVI. Matroska(TM) files can be played
272 back without the cue data, but seeking will probably be imprecise
273 and slower. Use this only if you're really desperate for space or
274 for testing purposes. See also option --cues which can be specified
275 for each input file.
276 --no-date
278 By default mkvmerge(1) sets the "date" segment information field to
279 the time & date when multiplexing started. With this option that
280 field is not written at all.
281 --disable-lacing
283 Disables lacing for all tracks. This will increase the file's size,
284 especially if there are many audio tracks. This option is not
285 intended for everyday use.
286 --disable-track-statistics-tags
288 Normally mkvmerge(1) will write certain tags with statistics for
289 each track. If such tags are already present then they will be
290 overwritten. The tags are BPS, DURATION, NUMBER_OF_BYTES and
291 NUMBER_OF_FRAMES.
292 Enabling this option prevents mkvmerge(1) from writing those tags
294 and from touching any existing tags with same names.
295 --disable-language-ietf
297 Normally mkvmerge(1) will write the new IETF BCP 47 language
298 elements in addition to the legacy language elements in track
299 headers, chapters and tags. If this option is used, only the legacy
300 elements are written.
301 --normalize-language-ietf mode
303 Enables normalizing all IETF BCP 47 language tags to either their
304 canonical form with mode 'canonical', to their extended language
305 subtags form with mode 'extlang' or turns it off with mode 'off'.
306 By default normalization to the canonical form is applied.
307 In the canonical form all subtags for which preferred values exist
309 are replaced by those preferred values. This converts e.g.
310 'zh-yue-jyutping' to 'yue-jyutping' or 'fr-FX' to 'fr-FR'.
311 For the extended language subtags form the canonical form is built
313 first. Afterwards all primary languages for which an extended
314 language subtag exists are replaced by that extended language
315 subtag and its prefix. This converts e.g. 'yue-jyutping' back to
316 'zh-yue-jyutping' but has no effect on 'fr-FR' as 'fr' is not an
317 extended language subtag.
318 File splitting, linking, appending and concatenation (more global options)
320 --split specification
321 Splits the output file after a given size or a given time. Please
322 note that tracks can only be split right before a key frame.
323 Therefore the split point may be a bit off from what the user has
324 specified.
325 At the moment mkvmerge(1) supports the following modes:
327 1. Splitting by size.
329 Syntax: --split [size:]d[k|m|g]
331 Examples: --split size:700m or --split 150000000
333 The parameter d may end with 'k', 'm' or 'g' to indicate that
335 the size is in KB, MB or GB respectively. Otherwise a size in
336 bytes is assumed. After the current output file has reached
337 this size limit a new one will be started.
338 The 'size:' prefix may be omitted for compatibility reasons.
340 2. Splitting after a duration.
342 Syntax: --split [duration:]HH:MM:SS.nnnnnnnnn|ds
344 Examples: --split duration:00:60:00.000 or --split 3600s
346 The parameter must either have the form HH:MM:SS.nnnnnnnnn for
348 specifying the duration in up to nano-second precision or be a
349 number d followed by the letter 's' for the duration in
350 seconds. HH is the number of hours, MM the number of minutes,
351 SS the number of seconds and nnnnnnnnn the number of
352 nanoseconds. Both the number of hours and the number of
353 nanoseconds can be omitted. There can be up to nine digits
354 after the decimal point. After the duration of the contents in
355 the current output has reached this limit a new output file
356 will be started.
357 The 'duration:' prefix may be omitted for compatibility
359 reasons.
360 3. Splitting after specific timestamps.
362 Syntax: --split timestamps:A[,B[,C...]]
364 Example: --split timestamps:00:45:00.000,01:20:00.250,6300s
366 The parameters A, B, C etc must all have the same format as the
368 ones used for the duration (see above). The list of timestamps
369 is separated by commas. After the input stream has reached the
370 current split point's timestamp a new file is created. Then the
371 next split point given in this list is used.
372 The 'timestamps:' prefix must not be omitted.
374 4. Keeping specific parts by specifying timestamp ranges while
376 discarding others.
377 Syntax: --split
379 parts:start1-end1[,[+]start2-end2[,[+]start3-end3...]]
380 Examples:
382 1. --split parts:00:01:20-00:02:45,00:05:50-00:10:30
384 2. --split parts:00:01:20-00:02:45,+00:05:50-00:10:30
386 3. --split parts:-00:02:45,00:05:50-
388 The parts mode tells mkvmerge(1) to keep certain ranges of
390 timestamps while discarding others. The ranges to keep have to
391 be listed after the parts: keyword and be separated by commas.
392 A range itself consists of a start and an end timestamp in the
393 same format the other variations of --split accept (e.g. both
394 00:01:20 and 80s refer to the same timestamp).
395 If a start timestamp is left out then it defaults to the
397 previous range's end timestamp. If there was no previous range
398 then it defaults to the start of the file (see example 3).
399 If an end timestamp is left out then it defaults to the end of
401 the source files which basically tells mkvmerge(1) to keep the
402 rest (see example 3).
403 Normally each range will be written to a new file. This can be
405 changed so that consecutive ranges are written to the same
406 file. For that the user has to prefix the start timestamp with
407 a +. This tells mkvmerge(1) not to create a new file and
408 instead append the range to the same file the previous range
409 was written to. Timestamps will be adjusted so that there will
410 be no gap in the output file even if there was a gap in the two
411 ranges in the input file.
412 In example 1 mkvmerge(1) will create two files. The first will
414 contain the content starting from 00:01:20 until 00:02:45. The
415 second file will contain the content starting from 00:05:50
416 until 00:10:30.
417 In example 2 mkvmerge(1) will create only one file. This file
419 will contain both the content starting from 00:01:20 until
420 00:02:45 and the content starting from 00:05:50 until 00:10:30.
421 In example 3 mkvmerge(1) will create two files. The first will
423 contain the content from the start of the source files until
424 00:02:45. The second file will contain the content starting
425 from 00:05:50 until the end of the source files.
426 Note
428 Note that mkvmerge(1) only makes decisions about splitting
429 at key frame positions. This applies to both the start and
430 the end of each range. So even if an end timestamp is
431 between two key frames mkvmerge(1) will continue outputting
432 the frames up to but excluding the following key frame.
433 5. Keeping specific parts by specifying frame/field number ranges
435 while discarding others.
436 Syntax: --split
438 parts-frames:start1-end1[,[+]start2-end2[,[+]start3-end3...]]
439 Examples:
441 1. --split parts-frames:137-258,548-1211
443 2. --split parts-frames:733-912,+1592-2730
445 3. --split parts-frames:-430,2512-
447 The parts-frames mode tells mkvmerge(1) to keep certain ranges
449 of frame/field numbers while discarding others. The ranges to
450 keep have to be listed after the parts-frames: keyword and be
451 separated by commas. A range itself consists of a start and an
452 end frame/field number. Numbering starts at 1.
453 If a start number is left out then it defaults to the previous
455 range's end number. If there was no previous range then it
456 defaults to the start of the file (see example 3).
457 If an end number is left out then it defaults to the end of the
459 source files which basically tells mkvmerge(1) to keep the rest
460 (see example 3).
461 Normally each range will be written to a new file. This can be
463 changed so that consecutive ranges are written to the same
464 file. For that the user has to prefix the start number with a
465 +. This tells mkvmerge(1) not to create a new file and instead
466 append the range to the same file the previous range was
467 written to. Timestamps will be adjusted so that there will be
468 no gap in the output file even if there was a gap in the two
469 ranges in the input file.
470 Note
472 Note that mkvmerge(1) only makes decisions about splitting
473 at key frame positions. This applies to both the start and
474 the end of each range. So even if an end frame/field number
475 is between two key frames mkvmerge(1) will continue
476 outputting the frames up to but excluding the following key
477 frame.
478 In example 1 mkvmerge(1) will create two files. The first will
479 contain the content starting from the first key frame at or
480 after 137 up to but excluding the first key frame at or after
481 258. The second file will contain the content starting from 548
482 until 1211.
483 In example 2 mkvmerge(1) will create only one file. This file
485 will contain both the content starting from 733 until 912 and
486 the content starting from 1592 until 2730.
487 In example 3 mkvmerge(1) will create two files. The first will
489 contain the content from the start of the source files until
490 430. The second file will contain the content starting from
491 2512 until the end of the source files.
492 This mode considers only the first video track that is output.
494 If no video track is output no splitting will occur.
495 Note
497 The numbers given with this argument are interpreted based
498 on the number of Matroska(TM) blocks that are output. A
499 single Matroska(TM) block contains either a full frame (for
500 progressive content) or a single field (for interlaced
501 content). mkvmerge does not distinguish between those two
502 and simply counts the number of blocks. For example: If one
503 wanted to split after the 25th full frame with interlaced
504 content one would have to use 50 (two fields per full
505 frame) as the split point.
506 6. Splitting after specific frames/fields.
508 Syntax: --split frames:A[,B[,C...]]
510 Example: --split frames:120,237,891
512 The parameters A, B, C etc must all be positive integers.
514 Numbering starts at 1. The list of frame/field numbers is
515 separated by commas. After the input stream has reached the
516 current split point's frame/field number a new file is created.
517 Then the next split point given in this list is used.
518 The 'frames:' prefix must not be omitted.
520 This mode considers only the first video track that is output.
522 If no video track is output no splitting will occur.
523 Note
525 The numbers given with this argument are interpreted based
526 on the number of Matroska(TM) blocks that are output. A
527 single Matroska(TM) block contains either a full frame (for
528 progressive content) or a single field (for interlaced
529 content). mkvmerge does not distinguish between those two
530 and simply counts the number of blocks. For example: If one
531 wanted to split after the 25th full frame with interlaced
532 content one would have to use 50 (two fields per full
533 frame) as the split point.
534 7. Splitting before specific chapters.
536 Syntax: --split chapters:all or --split chapters:A[,B[,C...]]
538 Example: --split chapters:5,8
540 The parameters A, B, C etc must all be positive integers.
542 Numbering starts at 1. The list of chapter numbers is separated
543 by commas. Splitting will occur right before the first key
544 frame whose timestamp is equal to or bigger than the start
545 timestamp for the chapters whose numbers are listed. A chapter
546 starting at 0s is never considered for splitting and discarded
547 silently.
548 The keyword all can be used instead of listing all chapter
550 numbers manually.
551 The 'chapters:' prefix must not be omitted.
553 Note
555 The Matroska(TM) file format supports arbitrary deeply
556 nested chapter structures called 'edition entries' and
557 'chapter atoms'. However, this mode only considers the
558 top-most level of chapters across all edition entries.
559 For this splitting mode the output filename is treated differently
561 than for the normal operation. It may contain a printf like
562 expression '%d' including an optional field width, e.g. '%02d'. If
563 it does then the current file number will be formatted
564 appropriately and inserted at that point in the filename. If there
565 is no such pattern then a pattern of '-%03d' is assumed right
566 before the file's extension: '-o output.mkv' would result in
567 'output-001.mkv' and so on. If there's no extension then '-%03d'
568 will be appended to the name.
569 Another possible pattern is '%c' which will be replaced by the name
571 of the first chapter in the file. Note that when '%c' is present,
572 the pattern '-%03d' will not be added automatically.
573 --link
575 Link files to one another when splitting the output file. See the
576 section on file linking below for details.
577 --link-to-previous segment-UID
579 Links the first output file to the segment with the segment UID
580 given by the segment-UID parameter. See the section on file linking
581 below for details.
582 If SID starts with = then its rest is interpreted as the name of a
584 Matroska file whose segment UID is read and used.
585 --link-to-next segment-UID
587 Links the last output file to the segment with the segment UID
588 given by the segment-UID parameter. See the section on file linking
589 below for details.
590 If SID starts with = then its rest is interpreted as the name of a
592 Matroska file whose segment UID is read and used.
593 --append-mode mode
595 Determines how timestamps are calculated when appending files. The
596 parameter mode can have two values: 'file' which is also the
597 default and 'track'.
598 When mkvmerge appends a track (called 'track2_1' from now on) from
600 a second file (called 'file2') to a track (called 'track1_1') from
601 the first file (called 'file1') then it has to offset all
602 timestamps for 'track2_1' by an amount. For 'file' mode this amount
603 is the highest timestamp encountered in 'file1' even if that
604 timestamp was from a different track than 'track1_1'. In track mode
605 the offset is the highest timestamp of 'track1_1'.
606 Unfortunately mkvmerge cannot detect which mode to use reliably.
608 Therefore it defaults to 'file' mode. 'file' mode usually works
609 better for files that have been created independently of each
610 other; e.g. when appending AVI or MP4 files. 'track' mode may work
611 better for sources that are essentially just parts of one big file,
612 e.g. for VOB and EVO files.
613 Subtitle tracks are always treated as if 'file' mode were active
615 even if 'track' mode actually is.
616 --append-to SFID1:STID1:DFID1:DTID1[,...]
618 This option controls to which track another track is appended. Each
619 spec contains four IDs: a file ID, a track ID, a second file ID and
620 a second track ID. The first pair, "source file ID" and "source
621 track ID", identifies the track that is to be appended. The second
622 pair, "destination file ID" and "destination track ID", identifies
623 the track the first one is appended to.
624 If this option has been omitted then a standard mapping is used.
626 This standard mapping appends each track from the current file to a
627 track from the previous file with the same track ID. This allows
628 for easy appending if a movie has been split into two parts and
629 both file have the same number of tracks and track IDs with the
630 command mkvmerge -o output.mkv part1.mkv +part2.mkv.
631 +
633 A single '+' causes the next file to be appended instead of added.
634 The '+' can also be put in front of the next file name. Therefore
635 the following two commands are equivalent:
636 $ mkvmerge -o full.mkv file1.mkv + file2.mkv
638 $ mkvmerge -o full.mkv file1.mkv +file2.mkv
639 [ file1 file2 ]
641 If multiple file names are contained in a pair of square brackets
642 then the second and all following files will be appended to the
643 first file named within the brackets.
644 This is an alternative syntax to using '+' between the file names.
646 Therefore the following two commands are equivalent:
647 $ mkvmerge -o full.mkv file1.mkv + file2.mkv
649 $ mkvmerge -o full.mkv '[' file1.mkv file2.mkv ']'
650 =
652 For certain file types (MPEG program streams = VOBs) mkvmerge(1)
653 normally looks for files in the same directory as an input file
654 that have the same base name and only differ in their running
655 number (e.g. 'VTS_01_1.VOB', 'VTS_01_2.VOB', 'VTS_01_3.VOB' etc)
656 and treats all of those files as if they were concatenated into a
657 single big file. This option, a single '=', causes mkvmerge not to
658 look for those additional files.
659 The '=' can also be put in front of the next file name. Therefore
661 the following two commands are equivalent:
662 $ mkvmerge -o full.mkv = file1.vob
664 $ mkvmerge -o full.mkv =file1.vob
665 ( file1 file2 )
667 If multiple file names are contained in a pair of parenthesis then
668 those files will be treated as if they were concatenated into a
669 single big file consisting of the content of each of the files one
670 after the other.
671 This can be used for e.g. VOB files coming from a DVD or MPEG
673 transport streams. It cannot be used if each file contains its own
674 set of headers which is usually the case with stand-alone files
675 like AVI or MP4.
676 Putting a file name into parenthesis also prevents mkvmerge(1) from
678 looking for additional files with the same base name as described
679 in option =. Therefore these two command lines are equivalent:
680 $ mkvmerge -o out.mkv = file.mkv
682 $ mkvmerge -o out.mkv '(' file.mkv ')'
683 Several things should be noted:
685 1. There must be spaces both after the opening and before the
687 closing parenthesis.
688 2. Every parameter between parenthesis is interpreted as a file
690 name. Therefore all options applying to this logical file must
691 be listed before the opening parenthesis.
692 3. Some shells treat parenthesis as special characters. Hence you
694 must escape or quote them as shown in the example above.
695 Attachment support (more global options)
697 --attachment-description description
698 Plain text description of the following attachment. Applies to the
699 next --attach-file or --attach-file-once option.
700 --attachment-mime-type MIME type
702 MIME type of the following attachment. Applies to the next
703 --attach-file or --attach-file-once option. A list of officially
704 recognized MIME types can be found e.g. at the IANA homepage[2].
705 The MIME type is mandatory for an attachment.
706 If no MIME type is given a for an attachment, its type will be
708 detected automatically.
709 --attachment-name name
711 Sets the name that will be stored in the output file for this
712 attachment. If this option is not given then the name will be
713 derived from the file name of the attachment as given with the
714 --attach-file or the --attach-file-once option.
715 --attach-file file-name, --attach-file-once file-name
717 Creates a file attachment inside the Matroska(TM) file. The MIME
718 type must have been set before this option can used. The difference
719 between the two forms is that during splitting the files attached
720 with --attach-file are attached to all output files while the ones
721 attached with --attach-file-once are only attached to the first
722 file created. If splitting is not used then both do the same.
723 mkvextract(1) can be used to extract attached files from a
725 Matroska(TM) file.
726 --enable-legacy-font-mime-types
728 Enables the use of legacy MIME types for certain types of font
729 attachments. For example, 'application/x-truetype-font' will be
730 used for TrueType fonts instead of 'fonts/ttf'.
731 This affects both new attachments if its MIME type is detected
733 automatically and existing attachments whose stored MIME types will
734 be remapped to the legacy ones.
735 The affected MIME types are 'font/sfnt', 'font/ttf' and
737 'font/collection' which are all mapped to
738 'application/x-truetype-fonts' and 'font/otf' which is mapped to
739 'application/vnd.ms-opentype'.
740 Options that can be used for each input file
742 -a, --audio-tracks [!]n,m,...
743 Copy the audio tracks n, m etc. The numbers are track IDs which can
744 be obtained with the --identify switch. They're not simply the
745 track numbers (see section track IDs). Default: copy all audio
746 tracks.
747 Instead of track IDs you can also provide ISO 639-2 language codes.
749 This will only work for source files that provide language tags for
750 their tracks.
751 Default: copy all tracks of this kind.
753 If the IDs are prefixed with ! then the meaning is reversed: copy
755 all tracks of this kind but the ones listed after the !.
756 -d, --video-tracks [!]n,m,...
758 Copy the video tracks n, m etc. The numbers are track IDs which can
759 be obtained with the --identify switch. They're not simply the
760 track numbers (see section track IDs). Default: copy all video
761 tracks.
762 Instead of track IDs you can also provide ISO 639-2 language codes.
764 This will only work for source files that provide language tags for
765 their tracks.
766 If the IDs are prefixed with ! then the meaning is reversed: copy
768 all tracks of this kind but the ones listed after the !.
769 -s, --subtitle-tracks [!]n,m,...
771 Copy the subtitle tracks n, m etc. The numbers are track IDs which
772 can be obtained with the --identify switch. They're not simply the
773 track numbers (see section track IDs). Default: copy all subtitle
774 tracks.
775 Instead of track IDs you can also provide ISO 639-2 language codes.
777 This will only work for source files that provide language tags for
778 their tracks.
779 If the IDs are prefixed with ! then the meaning is reversed: copy
781 all tracks of this kind but the ones listed after the !.
782 -b, --button-tracks [!]n,m,...
784 Copy the button tracks n, m etc. The numbers are track IDs which
785 can be obtained with the --identify switch. They're not simply the
786 track numbers (see section track IDs). Default: copy all button
787 tracks.
788 Instead of track IDs you can also provide ISO 639-2 language codes.
790 This will only work for source files that provide language tags for
791 their tracks.
792 If the IDs are prefixed with ! then the meaning is reversed: copy
794 all tracks of this kind but the ones listed after the !.
795 --track-tags [!]n,m,...
797 Copy the tags for tracks n, m etc. The numbers are track IDs which
798 can be obtained with the --identify switch (see section track IDs).
799 They're not simply the track numbers. Default: copy tags for all
800 tracks.
801 If the IDs are prefixed with ! then the meaning is reversed: copy
803 everything but the IDs listed after the !.
804 -m, --attachments [!]n[:all|first],m[:all|first],...
806 Copy the attachments with the IDs n, m etc to all or only the first
807 output file. Each ID can be followed by either ':all' (which is the
808 default if neither is entered) or ':first'. If splitting is active
809 then those attachments whose IDs are specified with ':all' are
810 copied to all of the resulting output files while the others are
811 only copied into the first output file. If splitting is not active
812 then both variants have the same effect.
813 The default is to copy all attachments to all output files.
815 If the IDs are prefixed with ! then the meaning is reversed: copy
817 everything but the IDs listed after the !.
818 -A, --no-audio
820 Don't copy any audio track from this file.
821 -D, --no-video
823 Don't copy any video track from this file.
824 -S, --no-subtitles
826 Don't copy any subtitle track from this file.
827 -B, --no-buttons
829 Don't copy any button track from this file.
830 -T, --no-track-tags
832 Don't copy any track specific tags from this file.
833 --no-chapters
835 Don't copy chapters from this file.
836 -M, --no-attachments
838 Don't copy attachments from this file.
839 --no-global-tags
841 Don't copy global tags from this file.
842 -y, --sync TID:d[,o[/p]]
844 Adjust the timestamps of the track with the id TID by d ms. The
845 track IDs are the same as the ones given with --identify (see
846 section track IDs).
847 o/p: adjust the timestamps by o/p to fix linear drifts. p defaults
849 to 1 if omitted. Both o and p can be floating point numbers.
850 Defaults: no manual sync correction (which is the same as d = 0 and
852 o/p = 1.0).
853 This option can be used multiple times for an input file applying
855 to several tracks by selecting different track IDs each time.
856 --cues TID:none|iframes|all
858 Controls for which tracks cue (index) entries are created for the
859 given track (see section track IDs). 'none' inhibits the creation
860 of cue entries. For 'iframes' only blocks with no backward or
861 forward references ( = I frames in video tracks) are put into the
862 cue sheet. 'all' causes mkvmerge(1) to create cue entries for all
863 blocks which will make the file very big.
864 The default is 'iframes' for video and subtitle tracks and 'none'
866 for audio tracks. See also option --no-cues which inhibits the
867 creation of cue entries regardless of the --cues options used.
868 This option can be used multiple times for an input file applying
870 to several tracks by selecting different track IDs each time.
871 --default-track-flag TID[:bool]
873 Sets the "default track" flag for the given track (see section
874 track IDs) if the optional argument bool is set to 1 or if it isn't
875 present. The flag will be set if the source container doesn't
876 provide that information and the user doesn't specify it via this
877 option.
878 If the user does not explicitly select a track during playback, the
880 player should select one of the tracks that has its "default track"
881 flag set, taking user preferences such as their preferred language
882 into account.
883 This option can be used multiple times for an input file applying
885 to several tracks by selecting different track IDs each time.
886 --track-enabled-flag TID[:bool]
888 Sets the "track enabled" flag for the given track (see section
889 track IDs) to the given value bool (0 or 1; defaults to 1 if not
890 specified). Tracks are enabled by default if no option is specified
891 for them and the source container doesn't provide this information
892 either.
893 Only tracks whose "track enabled" flag is set should be considered
895 for playback.
896 This option can be used multiple times for an input file applying
898 to several tracks by selecting different track IDs each time.
899 --forced-display-flag TID[:bool]
901 Sets the "forced display" flag for the given track (see section
902 track IDs) if the optional argument bool is set to 1 or if it isn't
903 present. Use this for tracks containing onscreen text or
904 foreign-language dialogue.
905 This option can be used multiple times for an input file applying
907 to several tracks by selecting different track IDs each time.
908 --hearing-impaired-flag TID[:bool]
910 Sets the "hearing impaired" flag for the given track (see section
911 track IDs) if the optional argument bool is set to 1 or if it isn't
912 present. This flag can be set if the track is suitable for users
913 with hearing impairments.
914 This option can be used multiple times for an input file applying
916 to several tracks by selecting different track IDs each time.
917 --visual-impaired-flag TID[:bool]
919 Sets the "visual impaired" flag for the given track (see section
920 track IDs) if the optional argument bool is set to 1 or if it isn't
921 present. This flag can be set if the track is suitable for users
922 with visual impairments.
923 This option can be used multiple times for an input file applying
925 to several tracks by selecting different track IDs each time.
926 --text-descriptions-flag TID[:bool]
928 Sets the "text descriptions" flag for the given track (see section
929 track IDs) if the optional argument bool is set to 1 or if it isn't
930 present. This flag can be set if the track contains textual
931 descriptions of video content suitable for playback via a
932 text-to-speech system for a visually-impaired user.
933 This option can be used multiple times for an input file applying
935 to several tracks by selecting different track IDs each time.
936 --original-flag TID[:bool]
938 Sets the "original language" flag for the given track (see section
939 track IDs) if the optional argument bool is set to 1 or if it isn't
940 present. This flag can be set if the track is in the content's
941 original language (not a translation).
942 This option can be used multiple times for an input file applying
944 to several tracks by selecting different track IDs each time.
945 --commentary-flag TID[:bool]
947 Sets the "commentary" flag for the given track (see section track
948 IDs) if the optional argument bool is set to 1 or if it isn't
949 present. This flag can be set if the track contains commentary.
950 This option can be used multiple times for an input file applying
952 to several tracks by selecting different track IDs each time.
953 --blockadd TID:level
955 Keep only the BlockAdditions up to the level level for the given
956 track. The default is to keep all levels. This option only affects
957 certain kinds of codecs like WAVPACK4.
958 --track-name TID:name
960 Sets the track name for the given track (see section track IDs) to
961 name.
962 --language TID:language
964 Sets the language for the given track (see section track IDs). Both
965 ISO 639-2 language codes and ISO 639-1 country codes are allowed.
966 The country codes will be converted to language codes
967 automatically. All languages including their ISO 639-2 codes can be
968 listed with the --list-languages option.
969 This option can be used multiple times for an input file applying
971 to several tracks by selecting different track IDs each time.
972 -t, --tags TID:file-name
974 Read tags for the track with the number TID from the file
975 file-name. See the section about tags below for details.
976 --aac-is-sbr TID[:0|1]
978 Tells mkvmerge(1) that the track with the ID TID is SBR AAC (also
979 known as HE-AAC or AAC+). This options is needed if a) the source
980 file is an AAC file (not for a Matroska(TM) file) and b) the AAC
981 file contains SBR AAC data. The reason for this switch is that it
982 is technically impossible to automatically tell normal AAC data
983 from SBR AAC data without decoding a complete AAC frame. As there
984 are several patent issues with AAC decoders mkvmerge(1) will never
985 contain this decoding stage. So for SBR AAC files this switch is
986 mandatory. The resulting file might not play back correctly or even
987 not at all if the switch was omitted.
988 If the source file is a Matroska(TM) file then the CodecID should
990 be enough to detect SBR AAC. However, if the CodecID is wrong then
991 this switch can be used to correct that.
992 If mkvmerge wrongfully detects that an AAC file is SBR then you can
994 add ':0' to the track ID.
995 --audio-emphasis TID:n|symbolic-name
997 Sets the emphasis for the audio track with the track ID TID. The
998 mode can either be a number n (certain values between 0 and 16) or
999 a symbolic name. All valid numbers & symbolic names can be listed
1000 with the --list-audio-emphasis option.
1001 --reduce-to-core TID
1003 Some audio codecs have a lossy core and optional extensions that
1004 implement lossless decoding. This option tells mkvmerge(1) to only
1005 copy the core but not the extensions. By default mkvmerge(1) copies
1006 both the core and the extensions.
1007 Currently only DTS tracks are affected by this option. TrueHD
1009 tracks that contain an embedded AC-3 core are instead presented as
1010 two separate tracks for which the user can select which track to
1011 copy. For DTS such a scheme would not work as the HD extensions
1012 cannot be decoded by themselves – unlike the TrueHD data.
1013 --remove-dialog-normalization-gain TID
1015 Some audio codecs contain header fields that tell the decoder or
1016 player to apply a (usually negative) gain for dialog normalization.
1017 This option tells mkvmerge(1) to remove or minimize that gain by
1018 modifying the corresponding header fields.
1019 Currently only AC-3, DTS and TrueHD tracks are affected by this
1021 option.
1022 --timestamps TID:file-name
1024 Read the timestamps to be used for the specific track ID from
1025 file-name. These timestamps forcefully override the timestamps that
1026 mkvmerge(1) normally calculates. Read the section about external
1027 timestamp files.
1028 --default-duration TID:x
1030 Forces the default duration of a given track to the specified
1031 value. Also modifies the track's timestamps to match the default
1032 duration. The argument x must be postfixed with 's', 'ms', 'us',
1033 'ns', 'fps', 'p' or 'i' to specify the default duration in seconds,
1034 milliseconds, microseconds, nanoseconds, 'frames per second',
1035 'progressive frames per second' or 'interlaced frames per second'
1036 respectively. The number x itself can be a floating point number or
1037 a fraction.
1038 If the default duration is not forced then mkvmerge will try to
1040 derive the track's default duration from the container and/or the
1041 encoded bitstream for certain track types, e.g. AVC/H.264 or
1042 MPEG-2.
1043 This option can also be used to change the FPS of video tracks
1045 without having to use an external timestamp file.
1046 --fix-bitstream-timing-information TID[:0|1]
1048 Normally mkvmerge(1) does not change the timing information
1049 (frame/field rate) stored in the video bitstream. With this option
1050 that information is adjusted to match the container timing
1051 information. The container timing information can come from various
1052 sources: from the command line (see option --default-duration), the
1053 source container or derived from the bitstream.
1054 Note
1056 This has only been implemented for AVC/H.264 video tracks so
1057 far.
1058 --compression TID:n
1060 Selects the compression method to be used for the track. Note that
1061 the player also has to support this method. Valid values are
1062 'none', 'zlib' and 'mpeg4_p2'/'mpeg4p2'.
1063 The compression method 'mpeg4_p2'/'mpeg4p2' is a special
1065 compression method called 'header removal' that is only available
1066 for MPEG4 part 2 video tracks.
1067 The default for some subtitle types is 'zlib' compression. This
1069 compression method is also the one that most if not all playback
1070 applications support. Support for other compression methods other
1071 than 'none' is not assured.
1072 Options that only apply to video tracks
1074 -f, --fourcc TID:FourCC
1075 Forces the FourCC to the specified value. Works only for video
1076 tracks in the 'MS compatibility mode'.
1077 --display-dimensions TID:widthxheight
1079 Matroska(TM) files contain two values that set the display
1080 properties that a player should scale the image on playback to:
1081 display width and display height. These values can be set with this
1082 option, e.g. '1:640x480'.
1083 Another way to specify the values is to use the --aspect-ratio or
1085 the --aspect-ratio-factor option (see below). These options are
1086 mutually exclusive.
1087 --aspect-ratio TID:ratio|width/height
1089 Matroska(TM) files contain two values that set the display
1090 properties that a player should scale the image on playback to:
1091 display width and display height. With this option mkvmerge(1) will
1092 automatically calculate the display width and display height based
1093 on the image's original width and height and the aspect ratio given
1094 with this option. The ratio can be given either as a floating point
1095 number ratio or as a fraction 'width/height', e.g. '16/9'.
1096 Another way to specify the values is to use the
1098 --aspect-ratio-factor or --display-dimensions options (see above
1099 and below). These options are mutually exclusive.
1100 --aspect-ratio-factor TID:factor|n/d
1102 Another way to set the aspect ratio is to specify a factor. The
1103 original aspect ratio is first multiplied with this factor and used
1104 as the target aspect ratio afterwards.
1105 Another way to specify the values is to use the --aspect-ratio or
1107 --display-dimensions options (see above). These options are
1108 mutually exclusive.
1109 --cropping TID:left,top,right,bottom
1111 Sets the pixel cropping parameters of a video track to the given
1112 values.
1113 --color-matrix-coefficients TID:n
1115 Sets the matrix coefficients of the video used to derive luma and
1116 chroma values from red, green and blue color primaries. The
1117 parameter n is an integer rangeing from 0 and 10.
1118 Valid values and their meaning are:
1120 0: GBR, 1: BT709, 2: unspecified, 3: reserved, 4: FCC, 5: BT470BG,
1122 6: SMPTE 170M, 7: SMPTE 240M, 8: YCOCG, 9: BT2020 non-constant
1123 luminance, 10: BT2020 constant luminance
1124 --color-bits-per-channel TID:n
1126 Sets the number of coded bits for a color channel. A value of 0
1127 indicates that the number of bits is unspecified.
1128 --chroma-subsample TID:hori,vert
1130 The amount of pixels to remove in the Cr and Cb channels for every
1131 pixel not removed horizontally/vertically.
1132 Example: For video with 4:2:0 chroma subsampling, the parameter
1134 should be set to TID:1,1.
1135 --cb-subsample TID:hori,vert
1137 The amount of pixels to remove in the Cb channel for every pixel
1138 not removed horizontally/vertically. This is additive with
1139 --chroma-subsample.
1140 Example: For video with 4:2:1 chroma subsampling, the parameter
1142 --chroma-subsample should be set to TID:1,0 and Cb-subsample should
1143 be set to TID:1,0.
1144 --chroma-siting TID:hori,vert
1146 Sets how chroma is sited horizontally/vertically (0: unspecified,
1147 1: top collocated, 2: half).
1148 --color-range TID:n
1150 Sets the clipping of the color ranges (0: unspecified, 1: broadcast
1151 range, 2: full range (no clipping), 3: defined by
1152 MatrixCoefficients/TransferCharacteristics).
1153 --color-transfer-characteristics TID:n
1155 The transfer characteristics of the video.
1156 Valid values and their meaning are:
1158 0: reserved, 1: ITU-R BT.709, 2: unspecified, 3: reserved, 4: gamma
1160 2.2 curve, 5: gamma 2.8 curve, 6: SMPTE 170M, 7: SMPTE 240M, 8:
1161 linear, 9: log, 10: log sqrt, 11: IEC 61966-2-4, 12: ITU-R BT.1361
1162 extended color gamut, 13: IEC 61966-2-1, 14: ITU-R BT.2020 10 bit,
1163 15: ITU-R BT.2020 12 bit, 16: SMPTE ST 2084, 17: SMPTE ST 428-1;
1164 18: ARIB STD-B67 (HLG)
1165 --color-primaries TID:n
1167 Sets the color primaries of the video.
1168 Valid values and their meaning are:
1170 0: reserved, 1: ITU-R BT.709, 2: unspecified, 3: reserved, 4: ITU-R
1172 BT.470M, 5: ITU-R BT.470BG, 6: SMPTE 170M, 7: SMPTE 240M, 8: FILM,
1173 9: ITU-R BT.2020, 10: SMPTE ST 428-1, 22: JEDEC P22 phosphors
1174 --max-content-light TID:n
1176 Sets the maximum brightness of a single pixel (Maximum Content
1177 Light Level) in candelas per square meter (cd/m²). The value of n
1178 should be a non-negtive integer.
1179 --max-frame-light TID:n
1181 Sets the maximum brightness of a single full frame (Maximum
1182 Frame-Average Light Level) in candelas per square meter (cd/m²).
1183 The value of n should be a non-negtive integer.
1184 --chromaticity-coordinates
1186 TID:red-x,red-y,green-x,green-y,blue-x,blue-y
1187 Sets the red/green/blue chromaticity coordinates as defined by CIE
1188 1931.
1189 --white-color-coordinates TID:x,y
1191 Sets the white color chromaticity coordinates as defined by CIE
1192 1931.
1193 --max-luminance TID:float
1195 Sets the maximum luminance in candelas per square meter (cd/m²).
1196 The value should be less than 9999.99.
1197 --min-luminance TID:float
1199 Sets the minimum luminance in candelas per square meter (cd/m²).
1200 The value should be less than 999.9999.
1201 --projection-type TID:method
1203 Sets the video projection method used. Valid values are 0
1204 (rectangular projection), 1 (equirectangular projection), 2
1205 (cubemap projection) and 3 (mesh projection).
1206 --projection-private TID:data
1208 Sets private data that only applies to a specific projection. Data
1209 must be given as hex numbers with or without the "0x" prefix, with
1210 or without spaces.
1211 --projection-pose-yaw TID:float
1213 Specifies a yaw rotation to the projection.
1214 --projection-pose-pitch TID:float
1216 Specifies a pitch rotation to the projection.
1217 --projection-pose-roll TID:float
1219 Specifies a roll rotation to the projection.
1220 --field-order TID:n
1222 Sets the field order for the video track with the track ID TID. The
1223 order must be one of the following numbers:
1224 0: progressive; 1: interlaced with top field displayed first and
1226 top field stored first; 2: undetermined field order; 6: interlaced
1227 with bottom field displayed first and bottom field stored first; 9:
1228 interlaced with bottom field displayed first and top field stored
1229 first; 14: interlaced with top field displayed first and bottom
1230 field stored first
1231 --stereo-mode TID:n|symbolic-name
1233 Sets the stereo mode for the video track with the track ID TID. The
1234 mode can either be a number n between 0 and 14 or a symbolic name.
1235 All valid numbers & names can be listed with the
1236 --list-stereo-modes option.
1237 Options that only apply to text subtitle tracks
1239 --sub-charset TID:character-set
1240 Sets the character set for the conversion to UTF-8 for UTF-8
1241 subtitles for the given track ID. If not specified the charset will
1242 be derived from the current locale settings. Note that a charset is
1243 not needed for subtitles read from Matroska(TM) files or from Kate
1244 streams, as these are always stored in UTF-8. See the section about
1245 text files and character sets for an explanation how mkvmerge(1)
1246 converts between character sets.
1247 This option can be used multiple times for an input file applying
1249 to several tracks by selecting different track IDs each time.
1250 Other options
1252 -i, --identify file-name
1253 Will let mkvmerge(1) probe the single file and report its type, the
1254 tracks contained in the file and their track IDs. If this option is
1255 used then the only other option allowed is the filename.
1256 The output format used for the result can be changed with the
1258 option --identification-format.
1259 -J file-name
1261 This is a convenient alias for "--identification-format json
1262 --identify file-name".
1263 -F, --identification-format format
1265 Determines the output format used by the --identify option. The
1266 following formats are supported: text (the default if this option
1267 isn't used) and json.
1268 1. The text format is short and human-readable. It consists of one
1270 line per item found (container, tracks, attachments etc.).
1271 This format is not meant to be parsed. The output will be
1273 translated into the language mkvmerge(1) uses (see also
1274 --ui-language).
1275 2. The json format outputs a machine-readable JSON representation.
1277 This format follows the JSON schema described in the following
1278 file:
1279 mkvmerge-identification-output-schema-v17.json[3]
1281 All versions of the JSON schema are available both online and
1283 in the released source code archives.
1284 --probe-range-percentage percentage
1286 File types such as MPEG program and transport streams (.vob, .m2ts)
1287 require parsing a certain amount of data in order to detect all
1288 tracks contained in the file. This amount is 0.3% of the source
1289 file's size or 10 MB, whichever is higher.
1290 If tracks are known to be present but not found then the percentage
1292 to probe can be changed with this option. The minimum of 10 MB is
1293 built-in and cannot be changed.
1294 --list-audio-emphasis
1296 Lists all valid numbers & their corresponding symbolic names for
1297 the --audio-emphasis option.
1298 --list-languages
1300 Lists all languages and their ISO 639-2 code which can be used with
1301 the --language option.
1302 --list-stereo-modes
1304 Lists all valid numbers & their corresponding symbolic names for
1305 the --stereo-mode option.
1306 -l, --list-types
1308 Lists supported input file types.
1309 --priority priority
1311 Sets the process priority that mkvmerge(1) runs with. Valid values
1312 are 'lowest', 'lower', 'normal', 'higher' and 'highest'. If nothing
1313 is given then 'normal' is used. On Unix like systems mkvmerge(1)
1314 will use the nice(2) function. Therefore only the super user can
1315 use 'higher' and 'highest'. On Windows all values are useable for
1316 every user.
1317 Selecting 'lowest' also causes mkvmerge(1) to select idle I/O
1319 priority in addition to the lowest possible process priority.
1320 --command-line-charset character-set
1322 Sets the character set to convert strings given on the command line
1323 from. It defaults to the character set given by system's current
1324 locale. This settings applies to arguments of the following
1325 options: --title, --track-name and --attachment-description.
1326 --output-charset character-set
1328 Sets the character set to which strings are converted that are to
1329 be output. It defaults to the character set given by system's
1330 current locale.
1331 -r, --redirect-output file-name
1333 Writes all messages to the file file-name instead of to the
1334 console. While this can be done easily with output redirection
1335 there are cases in which this option is needed: when the terminal
1336 reinterprets the output before writing it to a file. The character
1337 set set with --output-charset is honored.
1338 --flush-on-close
1340 Tells the program to flush all data cached in memory to storage
1341 when closing files opened for writing. This can be used to prevent
1342 data loss on power outages or to circumvent certain problems in the
1343 operating system or drivers. The downside is that multiplexing will
1344 take longer as mkvmerge will wait until all data has been written
1345 to the storage before exiting. See issues #2469 and #2480 on the
1346 MKVToolNix bug tracker for in-depth discussions on the pros and
1347 cons.
1348 --ui-language code
1350 Forces the translations for the language code to be used (e.g.
1351 'de_DE' for the German translations). Entering 'list' as the code
1352 will cause the program to output a list of available translations.
1353 --abort-on-warnings
1355 Tells the program to abort after the first warning is emitted. The
1356 program's exit code will be 1.
1357 --deterministic seed
1359 Enables the creation of byte-identical files if the same version of
1360 mkvmerge(1) is used with the same source files, the same set of
1361 options and the same seed. Note that the "date" segment information
1362 field is not written in this mode.
1363 The seed can be an arbitrary string and does not have to be a
1365 number.
1366 The result of byte-identical files is only guaranteed under the
1368 following conditions:
1369 1. The same version of mkvmerge(1) built with the same versions of
1371 libEBML and libMatroska is used.
1372 2. The source files used are byte-identical.
1374 3. The same command line options are used in the same order (with
1376 the notable exception of --output ...).
1377 Using other versions of mkvmerge(1) or other command-line options
1379 may result in the same byte-identical file but is not guaranteed to
1380 do so.
1381 --debug topic
1383 Turn on debugging for a specific feature. This option is only
1384 useful for developers.
1385 --engage feature
1387 Turn on experimental features. A list of available features can be
1388 requested with mkvmerge --engage list. These features are not meant
1389 to be used in normal situations.
1390 --gui-mode
1392 Turns on GUI mode. In this mode specially-formatted lines may be
1393 output that can tell a controlling GUI what's happening. These
1394 messages follow the format '#GUI#message'. The message may be
1395 followed by key/value pairs as in
1396 '#GUI#message#key1=value1#key2=value2...'. Neither the messages nor
1397 the keys are ever translated and always output in English.
1398 @options-file.json
1400 Reads additional command line arguments from the file options-file.
1401 See the section about option files for further information.
1402 --capabilities
1404 Lists information about optional features that have been compiled
1405 in and exit. The first line output will be the version information.
1406 All following lines contain exactly one word whose presence
1407 indicates that the feature has been compiled in. These features
1408 are:
1409 • 'FLAC' -- reading raw FLAC files and handling FLAC tracks in
1411 other containers, e.g. Ogg(TM) or Matroska(TM).
1412 -h, --help
1414 Show usage information and exit.
1415 -V, --version
1417 Show version information and exit.
1418
1420 For each file the user can select which tracks mkvmerge(1) should take.
1421 They are all put into the file specified with -o. A list of known (and
1422 supported) source formats can be obtained with the -l option.
1423 Important
1425 The order of command line options is important. Please read the
1426 section "Option order" if you're new to the program.
1427
1429 The order in which options are entered is important for some options.
1430 Options fall into two categories:
1431 1. Options that affect the whole program and are not tied to any input
1433 file. These include but are not limited to --command-line-charset,
1434 --output or --title. These can appear anywhere on the command line.
1435 2. Options that affect a single input file or a single track in an
1437 input file. These options all apply to the following input file on
1438 the command line. All options applying to the same input (or to
1439 tracks from the same input file) file can be written in any order
1440 as long as they all appear before that input file's name. Examples
1441 for options applying to an input file are --no-chapters or
1442 --chapter-charset. Examples for options applying to a single track
1443 are --default-duration or --language.
1444 The options are processed from left to right. If an option appears
1446 multiple times within the same scope then the last occurrence will be
1447 used. Therefore the title will be set to "Something else" in the
1448 following example:
1449 $ mkvmerge -o output.mkv --title 'This and that' input.avi --title 'Something else'
1451 The following example shows that using the --language option twice is
1453 OK because they're used in different scopes. Even though they apply to
1454 the same track ID they apply to different input files and therefore
1455 have different scopes:
1456 $ mkvmerge -o output.mkv --language 0:fre français.ogg --language 0:deu deutsch.ogg
1458
1460 Let's assume you have a file called MyMovie.avi and the audio track in
1461 a separate file, e.g. 'MyMovie.wav'. First you want to encode the audio
1462 to OggVorbis(TM):
1463 $ oggenc -q4 -oMyMovie.ogg MyMovie.wav
1465 After a couple of minutes you can join video and audio:
1467 $ mkvmerge -o MyMovie-with-sound.mkv MyMovie.avi MyMovie.ogg
1469 If your AVI already contains an audio track then it will be copied as
1471 well (if mkvmerge(1) supports the audio format). To avoid that simply
1472 do
1473 $ mkvmerge -o MyMovie-with-sound.mkv -A MyMovie.avi MyMovie.ogg
1475 After some minutes of consideration you rip another audio track, e.g.
1477 the director's comments or another language to 'MyMovie-add-audio.wav'.
1478 Encode it again and join it up with the other file:
1479 $ oggenc -q4 -oMyMovie-add-audio.ogg MyMovie-add-audio.wav
1481 $ mkvmerge -o MM-complete.mkv MyMovie-with-sound.mkv MyMovie-add-audio.ogg
1482 The same result can be achieved with
1484 $ mkvmerge -o MM-complete.mkv -A MyMovie.avi MyMovie.ogg MyMovie-add-audio.ogg
1486 Now fire up mplayer(TM) and enjoy. If you have multiple audio tracks
1488 (or even video tracks) then you can tell mplayer(TM) which track to
1489 play with the '-vid' and '-aid' options. These are 0-based and do not
1490 distinguish between video and audio.
1491 If you need an audio track synchronized you can do that easily. First
1493 find out which track ID the Vorbis track has with
1494 $ mkvmerge --identify outofsync.ogg
1496 Now you can use that ID in the following command line:
1498 $ mkvmerge -o goodsync.mkv -A source.avi -y 12345:200 outofsync.ogg
1500 This would add 200ms of silence at the beginning of the audio track
1502 with the ID 12345 taken from 'outofsync.ogg'.
1503 Some movies start synced correctly but slowly drift out of sync. For
1505 these kind of movies you can specify a delay factor that is applied to
1506 all timestamps -- no data is added or removed. So if you make that
1507 factor too big or too small you'll get bad results. An example is that
1508 an episode I transcoded was 0.2 seconds out of sync at the end of the
1509 movie which was 77340 frames long. At 29.97fps 0.2 seconds correspond
1510 to approx. 6 frames. So I did
1511 $ mkvmerge -o goodsync.mkv -y 23456:0,77346/77340 outofsync.mkv
1513 The result was fine.
1515 The sync options can also be used for subtitles in the same manner.
1517 For text subtitles you can either use some Windows software (like
1519 SubRipper(TM)) or the subrip(TM) package found in transcode(1)'s
1520 sources in the 'contrib/subrip' directory. The general process is:
1521 1. extract a raw subtitle stream from the source:
1523 $ tccat -i /path/to/copied/dvd/ -T 1 -L | tcextract -x ps1 -t vob -a 0x20 | subtitle2pgm -o mymovie
1525 2. convert the resulting PGM images to text with gocr:
1527 $ pgm2txt mymovie
1529 3. spell-check the resulting text files:
1531 $ ispell -d american *txt
1533 4. convert the text files to a SRT file:
1535 $ srttool -s -w -i mymovie.srtx -o mymovie.srt
1537 The resulting file can be used as another input file for mkvmerge(1):
1539 $ mkvmerge -o mymovie.mkv mymovie.avi mymovie.srt
1541 If you want to specify the language for a given track then this is
1543 easily done. First find out the ISO 639-2 code for your language.
1544 mkvmerge(1) can list all of those codes for you:
1545 $ mkvmerge --list-languages
1547 Search the list for the languages you need. Let's assume you have put
1549 two audio tracks into a Matroska(TM) file and want to set their
1550 language codes and that their track IDs are 2 and 3. This can be done
1551 with
1552 $ mkvmerge -o with-lang-codes.mkv --language 2:ger --language 3:dut without-lang-codes.mkv
1554 As you can see you can use the --language switch multiple times.
1556 Maybe you'd also like to have the player use the Dutch language as the
1558 default language. You also have extra subtitles, e.g. in English and
1559 French, and want to have the player display the French ones by default.
1560 This can be done with
1561 $ mkvmerge -o with-lang-codes.mkv --language 2:ger --language 3:dut --default-track-flag 3 without-lang-codes.mkv --language 0:eng english.srt --default-track-flag 0 --language 0:fre french.srt
1563 If you do not see the language or default track flags that you've
1565 specified in mkvinfo(1)'s output then please read the section about
1566 default values.
1567 Turn off the compression for an input file.
1569 $ mkvmerge -o no-compression.mkv --compression -1:none MyMovie.avi --compression -1:none mymovie.srt
1571
1573 Regular track IDs
1574 Some of the options for mkvmerge(1) need a track ID to specify which
1575 track they should be applied to. Those track IDs are printed by the
1576 readers when demuxing the current input file, or if mkvmerge(1) is
1577 called with the --identify option. An example for such output:
1578 $ mkvmerge -i v.mkv
1580 File 'v.mkv': container: Matroska(TM)
1581 Track ID 0: video (V_MS/VFW/FOURCC, DIV3)
1582 Track ID 1: audio (A_MPEG/L3)
1583 Do not confuse the track IDs that are assigned to the tracks that are
1585 placed in the output MKV file with the track IDs of the input files.
1586 Only the input file track IDs are used for options needing these
1587 values.
1588 Also note that each input file has its own set of track IDs. Therefore
1590 the track IDs for file 'file1.ext' as reported by 'mkvmerge --identify'
1591 do not change no matter how many other input files are there or in
1592 which position 'file1.ext' is used.
1593 Track IDs are assigned like this:
1595 • AVI files: The video track has the ID 0. The audio tracks get IDs
1597 in ascending order starting at 1.
1598 • AAC, AC-3, MP3, SRT and WAV files: The one 'track' in that file
1600 gets the ID 0.
1601 • Most other files: The track IDs are assigned in order the tracks
1603 are found in the file starting at 0.
1604 The options that use the track IDs are the ones whose description
1606 contains 'TID'. The following options use track IDs as well:
1607 --audio-tracks, --video-tracks, --subtitle-tracks, --button-tracks and
1608 --track-tags.
1609 Special track IDs
1611 There are several IDs that have special meaning and do not occur in the
1612 identification output.
1613 The special track ID '-1' is a wild card and applies the given switch
1615 to all tracks that are read from an input file.
1616 The special track ID '-2' refers to the chapters in a source file.
1618 Currently only the --sync option uses this special ID. As an
1619 alternative to --sync -2:... the option --chapter-sync ... can be
1620 used.
1621
1623 Note
1624 This section applies to all programs in MKVToolNix even if it only
1625 mentions mkvmerge(1).
1626 Introduction
1628 All text in a Matroska(TM) file is encoded in UTF-8. This means that
1629 mkvmerge(1) has to convert every text file it reads as well as every
1630 text given on the command line from one character set into UTF-8. In
1631 return this also means that mkvmerge(1)'s output has to be converted
1632 back to that character set from UTF-8, e.g. if a non-English
1633 translation is used with --ui-language or for text originating from a
1634 Matroska(TM) file.
1635 mkvmerge(1) does this conversion automatically based on the presence of
1637 a byte order marker (short: BOM) or the system's current locale. How
1638 the character set is inferred from the locale depends on the operating
1639 system that mkvmerge(1) is run on.
1640 Byte order markers (BOM)
1642 Text files that start with a BOM are already encoded in one
1643 representation of UTF. mkvmerge(1) supports the following five modes:
1644 UTF-8, UTF-16 Little and Big Endian, UTF-32 Little and Big Endian. Text
1645 files with a BOM are automatically converted to UTF-8. Any of the
1646 parameters that would otherwise set the character set for such a file
1647 (e.g. --sub-charset) is silently ignored.
1648 Linux and Unix-like systems including macOS
1650 On Unix-like systems mkvmerge(1) uses the setlocale(3) system call
1651 which in turn uses the environment variables LANG, LC_ALL and LC_CYPE.
1652 The resulting character set is often one of UTF-8 or the ISO-8859-*
1653 family and is used for all text file operations and for encoding
1654 strings on the command line and for output to the console.
1655 Windows
1657 On Windows the default character set used for converting text files is
1658 determined by a call to the GetACP() system call.
1659 Reading the command line is done with the GetCommandLineW() function
1661 which already returns a Unicode string. Therefore the option
1662 --command-line-charset is ignored on Windows.
1663 Output to the console consists of three scenarios:
1665 1. If the output is redirected with the option --redirect-output then
1667 the default charset is UTF-8. This can be changed with
1668 --output-charset.
1669 2. If the output is redirected with cmd.exe itself, e.g. with mkvinfo
1671 file.mkv > info.txt, then the charset is always UTF-8 and cannot be
1672 changed.
1673 3. Otherwise (when writing directly to the console) the Windows
1675 function WriteConsoleW() is used and the option --output-charset is
1676 ignored. The console should be able to output all Unicode
1677 characters for which the corresponding language support is
1678 installed (e.g. Chinese characters might not be displayed on
1679 English Windows versions).
1680 Command line options
1682 The following options exist that allow specifying the character sets:
1683 • --sub-charset for text subtitle files and for text subtitle tracks
1685 stored in container formats for which the character set cannot be
1686 determined unambiguously (e.g. Ogg files),
1687 • --chapter-charset for chapter text files and for chapters and file
1689 titles stored in container formats for which the character set
1690 cannot be determined unambiguously (e.g. Ogg files for chapter
1691 information, track and file titles etc; MP4 files for chapter
1692 information),
1693 • --command-line-charset for all strings on the command line,
1695 • --output-charset for all strings written to the console or to a
1697 file if the output has been redirected with the --redirect-output
1698 option. On non-Windows systems the default for the output charset
1699 is the system's current charset. On Windows it defaults to UTF-8
1700 both for redirecting with --redirect-output and with cmd.exe
1701 itself, e.g. mkvinfo file.mkv > info.txt.
1702
1704 An option file is a file mkvmerge(1) can read additional command line
1705 arguments from. This can be used in order to circumvent certain
1706 limitations of the shell or the operating system when executing
1707 external programs like a limited command line length.
1708 An option file contains JSON-formatted data. Its content must be a
1710 valid JSON array consisting solely of JSON strings. The file's encoding
1711 must be UTF-8. The file should not start with a byte order marker
1712 (BOM), but if one exists, it will be skipped.
1713 The rules for escaping special characters inside JSON are the ones in
1715 the official JSON specification, RFC 7159[4].
1716 The option file's name itself must be specified as a command line
1718 argument prefixed with a '@' character.
1719 The command line 'mkvmerge -o "my file.mkv" -A "a movie.avi" sound.ogg'
1721 could be converted into the following JSON option file called e.g.
1722 'options.json':
1723 [
1725 "-o",
1726 "c:\\Matroska\\my file.mkv",
1727 "--title",
1728 "#65",
1729 "-A",
1730 "a movie.avi",
1731 "sound.ogg"
1732 ]
1733 The corresponding command would then be 'mkvmerge @options.json'.
1735
1737 Matroska(TM) supports file linking which simply says that a specific
1738 file is the predecessor or successor of the current file. To be
1739 precise, it's not really the files that are linked but the Matroska(TM)
1740 segments. As most files will probably only contain one Matroska(TM)
1741 segment the following explanations use the term 'file linking' although
1742 'segment linking' would be more appropriate.
1743 Each segment is identified by a unique 128 bit wide segment UID. This
1745 UID is automatically generated by mkvmerge(1). The linking is done
1746 primarily via putting the segment UIDs (short: SID) of the
1747 previous/next file into the segment header information. mkvinfo(1)
1748 prints these SIDs if it finds them.
1749 If a file is split into several smaller ones and linking is used then
1751 the timestamps will not start at 0 again but will continue where the
1752 last file has left off. This way the absolute time is kept even if the
1753 previous files are not available (e.g. when streaming). If no linking
1754 is used then the timestamps should start at 0 for each file. By default
1755 mkvmerge(1) does not use file linking. If you want that you can turn it
1756 on with the --link option. This option is only useful if splitting is
1757 activated as well.
1758 Regardless of whether splitting is active or not the user can tell
1760 mkvmerge(1) to link the produced files to specific SIDs. This is
1761 achieved with the options --link-to-previous and --link-to-next. These
1762 options accept a segment SID in the format that mkvinfo(1) outputs: 16
1763 hexadecimal numbers between 0x00 and 0xff prefixed with '0x' each, e.g.
1764 '0x41 0xda 0x73 0x66 0xd9 0xcf 0xb2 0x1e 0xae 0x78 0xeb 0xb4 0x5e 0xca
1765 0xb3 0x93'. Alternatively a shorter form can be used: 16 hexadecimal
1766 numbers between 0x00 and 0xff without the '0x' prefixes and without the
1767 spaces, e.g. '41da7366d9cfb21eae78ebb45ecab393'.
1768 If splitting is used then the first file is linked to the SID given
1770 with --link-to-previous and the last file is linked to the SID given
1771 with --link-to-next. If splitting is not used then the one output file
1772 will be linked to both of the two SIDs.
1773
1775 The Matroska(TM) specification states that some elements have a default
1776 value. Usually an element is not written to the file if its value is
1777 equal to its default value in order to save space. The elements that
1778 the user might miss in mkvinfo(1)'s output are the language and the
1779 default track flag elements. The default value for the language is
1780 English ('eng'), and the default value for the default track flag is
1781 true. Therefore if you used --language 0:eng for a track then it will
1782 not show up in mkvinfo(1)'s output.
1783
1785 Maybe you also want to keep some photos along with your Matroska(TM)
1786 file, or you're using SSA subtitles and need a special TrueType(TM)
1787 font that's really rare. In these cases you can attach those files to
1788 the Matroska(TM) file. They will not be just appended to the file but
1789 embedded in it. A player can then show those files (the 'photos' case)
1790 or use them to render the subtitles (the 'TrueType(TM) fonts' case).
1791 Here's an example how to attach a photo and a TrueType(TM) font to the
1793 output file:
1794 $ mkvmerge -o output.mkv -A video.avi sound.ogg \
1796 --attachment-description "Me and the band behind the stage in a small get-together" \
1797 --attachment-mime-type image/jpeg \
1798 --attach-file me_and_the_band.jpg \
1799 --attachment-description "The real rare and unbelievably good looking font" \
1800 --attachment-mime-type application/octet-stream \
1801 --attach-file really_cool_font.ttf
1802 If a Matroska(TM) containing attachments file is used as an input file
1804 then mkvmerge(1) will copy the attachments into the new file. The
1805 selection which attachments are copied and which are not can be changed
1806 with the options --attachments and --no-attachments.
1807
1809 The Matroska(TM) chapter system is more powerful than the old known
1810 system used by OGM files. The full specifications can be found at the
1811 Matroska(TM) website[1].
1812 mkvmerge(1) supports two kinds of chapter files as its input. The first
1814 format, called 'simple chapter format', is the same format that the OGM
1815 tools expect. The second format is a XML based chapter format which
1816 supports all of Matroska(TM)'s chapter functionality.
1817 Apart from dedicated chapter files mkvmerge(1) can also read chapters
1819 from other file formats (e.g. MP4, Ogg, Blu-rays or DVDs).
1820 The simple chapter format
1822 This format consists of pairs of lines that start with 'CHAPTERxx=' and
1823 'CHAPTERxxNAME=' respectively. The first one contains the start
1824 timestamp while the second one contains the title. Here's an example:
1825 CHAPTER01=00:00:00.000
1827 CHAPTER01NAME=Intro
1828 CHAPTER02=00:02:30.000
1829 CHAPTER02NAME=Baby prepares to rock
1830 CHAPTER03=00:02:42.300
1831 CHAPTER03NAME=Baby rocks the house
1832 mkvmerge(1) will transform every pair or lines into one Matroska(TM)
1834 ChapterAtom. It does not set any ChapterTrackNumber which means that
1835 all chapters apply to all tracks in the file.
1836 As this is a text file character set conversion may need to be done.
1838 See the section about text files and character sets for an explanation
1839 how mkvmerge(1) converts between character sets.
1840 The XML based chapter format
1842 The XML based chapter format looks like this example:
1843 <?xml version="1.0" encoding="ISO-8859-1"?>
1845 <!DOCTYPE Chapters SYSTEM "matroskachapters.dtd">
1846 <Chapters>
1847 <EditionEntry>
1848 <ChapterAtom>
1849 <ChapterTimeStart>00:00:30.000</ChapterTimeStart>
1850 <ChapterTimeEnd>00:01:20.000</ChapterTimeEnd>
1851 <ChapterDisplay>
1852 <ChapterString>A short chapter</ChapterString>
1853 <ChapterLanguage>eng</ChapterLanguage>
1854 </ChapterDisplay>
1855 <ChapterAtom>
1856 <ChapterTimeStart>00:00:46.000</ChapterTimeStart>
1857 <ChapterTimeEnd>00:01:10.000</ChapterTimeEnd>
1858 <ChapterDisplay>
1859 <ChapterString>A part of that short chapter</ChapterString>
1860 <ChapterLanguage>eng</ChapterLanguage>
1861 </ChapterDisplay>
1862 </ChapterAtom>
1863 </ChapterAtom>
1864 </EditionEntry>
1865 </Chapters>
1866 With this format three things are possible that are not possible with
1868 the simple chapter format:
1869 1. The timestamp for the end of the chapter can be set,
1871 2. chapters can be nested,
1873 3. the language and country can be set.
1875 The mkvtoolnix distribution contains some sample files in the doc
1877 subdirectory which can be used as a basis.
1878 The following lists the supported XML tags, their data types and, where
1880 appropriate, the valid range for their values:
1881 Chapters (master)
1883 EditionEntry (master)
1884 EditionUID (unsigned integer, valid range: 1 <= value)
1885 EditionFlagHidden (unsigned integer, valid range: 0 <= value <= 1)
1886 EditionFlagDefault (unsigned integer, valid range: 0 <= value <= 1)
1887 EditionFlagOrdered (unsigned integer, valid range: 0 <= value <= 1)
1888 ChapterAtom (master)
1889 ChapterAtom (master)
1890 ChapterUID (unsigned integer, valid range: 1 <= value)
1891 ChapterTimeStart (unsigned integer)
1892 ChapterTimeEnd (unsigned integer)
1893 ChapterFlagHidden (unsigned integer, valid range: 0 <= value <= 1)
1894 ChapterFlagEnabled (unsigned integer, valid range: 0 <= value <= 1)
1895 ChapterSegmentUID (binary, valid range: 1 <= length in bytes)
1896 ChapterSegmentEditionUID (unsigned integer, valid range: 1 <= value)
1897 ChapterPhysicalEquiv (unsigned integer)
1898 ChapterTrack (master)
1899 ChapterTrackNumber (unsigned integer, valid range: 1 <= value)
1900 ChapterDisplay (master)
1901 ChapterString (UTF-8 string)
1902 ChapterLanguage (UTF-8 string)
1903 ChapterCountry (UTF-8 string)
1904 ChapterProcess (master)
1905 ChapterProcessCodecID (unsigned integer)
1906 ChapterProcessPrivate (binary)
1907 ChapterProcessCommand (master)
1908 ChapterProcessTime (unsigned integer)
1909 ChapterProcessData (binary)
1910 Reading chapters from Blu-rays
1912 mkvmerge(1) can read chapters from unencrypted Blu-rays. For that you
1913 can use the path to one of the MPLS play lists with the --chapters
1914 parameter.
1915 Example: --chapters /srv/blurays/BigBuckBunny/BDMV/PLAYLIST/00001.mpls
1917 Reading chapters from DVDs
1919 When MKVToolNix is compiled with the libdvdread(TM) library,
1920 mkvmerge(1) can read chapters from DVDs. For that you can use the path
1921 to one of the folders or files on the DVD with the --chapters
1922 parameter. As DVDs can contain more than one title and each title has
1923 its own set of chapters, you can append a colon and the desired title
1924 number to the end of the file name argument. The title number defaults
1925 to 1.
1926 Example: --chapters /srv/dvds/BigBuckBunny/VIDEO_TS:2
1928 General notes
1930 When splitting files mkvmerge(1) will correctly adjust the chapters as
1931 well. This means that each file only includes the chapter entries that
1932 apply to it, and that the timestamps will be offset to match the new
1933 timestamps of each output file.
1934 mkvmerge(1) is able to copy chapters from Matroska(TM) source files
1936 unless this is explicitly disabled with the --no-chapters option. The
1937 chapters from all sources (Matroska(TM) files, Ogg files, MP4 files,
1938 chapter text files) are usually not merged but end up in separate
1939 ChapterEditions. Only if chapters are read from several Matroska(TM) or
1940 XML files that share the same edition UIDs will chapters be merged into
1941 a single ChapterEdition. If such a merge is desired in other situations
1942 as well then the user has to extract the chapters from all sources with
1943 mkvextract(1) first, merge the XML files manually and mux them
1944 afterwards.
1945
1947 Introduction
1948 Matroska(TM)'s tag system is similar to that of other containers: a set
1949 of KEY=VALUE pairs. However, in Matroska(TM) these tags can also be
1950 nested, and both the KEY and the VALUE are elements of their own. The
1951 example file example-tags-2.xml shows how to use this system.
1952 Scope of the tags
1954 Matroska(TM) tags do not automatically apply to the complete file. They
1955 can, but they also may apply to different parts of the file: to one or
1956 more tracks, to one or more chapters, or even to a combination of both.
1957 The Matroska(TM) specification[5] gives more details about this fact.
1958 One important fact is that tags are linked to tracks or chapters with
1960 the Targets Matroska(TM) tag element, and that the UIDs used for this
1961 linking are not the track IDs mkvmerge(1) uses everywhere. Instead the
1962 numbers used are the UIDs which mkvmerge(1) calculates automatically
1963 (if the track is taken from a file format other than Matroska(TM)) or
1964 which are copied from the source file if the track's source file is a
1965 Matroska(TM) file. Therefore it is difficult to know which UIDs to use
1966 in the tag file before the file is handed over to mkvmerge(1).
1967 mkvmerge(1) knows two options with which you can add tags to
1969 Matroska(TM) files: The --global-tags and the --tags options. The
1970 difference is that the former option, --global-tags, will make the tags
1971 apply to the complete file by removing any of those Targets elements
1972 mentioned above. The latter option, --tags, automatically inserts the
1973 UID that mkvmerge(1) generates for the tag specified with the TID part
1974 of the --tags option.
1975 Example
1977 Let's say that you want to add tags to a video track read from an AVI.
1978 mkvmerge --identify file.avi tells you that the video track's ID (do
1979 not mix this ID with the UID!) is 0. So you create your tag file, leave
1980 out all Targets elements and call mkvmerge(1):
1981 $ mkvmerge -o file.mkv --tags 0:tags.xml file.avi
1983 Tag file format
1985 mkvmerge(1) supports a XML based tag file format. The format is very
1986 closely modeled after the Matroska(TM) specification[5]. Both the
1987 binary and the source distributions of MKVToolNix come with a sample
1988 file called example-tags-2.xml which simply lists all known tags and
1989 which can be used as a basis for real life tag files.
1990 The basics are:
1992 • The outermost element must be <Tags>.
1994 • One logical tag is contained inside one pair of <Tag> XML tags.
1996 • White spaces directly before and after tag contents are ignored.
1998 Data types
2000 The new Matroska(TM) tagging system only knows two data types, a UTF-8
2001 string and a binary type. The first is used for the tag's name and the
2002 <String> element while the binary type is used for the <Binary>
2003 element.
2004 As binary data itself would not fit into a XML file mkvmerge(1)
2006 supports two other methods of storing binary data. If the contents of a
2007 XML tag starts with '@' then the following text is treated as a file
2008 name. The corresponding file's content is copied into the Matroska(TM)
2009 element.
2010 Otherwise the data is expected to be Base64 encoded. This is an
2012 encoding that transforms binary data into a limited set of ASCII
2013 characters and is used e.g. in email programs. mkvextract(1) will
2014 output Base64 encoded data for binary elements.
2015 The deprecated tagging system knows some more data types which can be
2017 found in the official Matroska(TM) tag specs. As mkvmerge(1) does not
2018 support this system anymore these types aren't described here.
2019 Known tags for the XML file format
2021 The following lists the supported XML tags, their data types and, where
2022 appropriate, the valid range for their values:
2023 Tags (master)
2025 Tag (master)
2026 Targets (master)
2027 TargetTypeValue (unsigned integer)
2028 TargetType (UTF-8 string)
2029 TrackUID (unsigned integer)
2030 EditionUID (unsigned integer)
2031 ChapterUID (unsigned integer)
2032 AttachmentUID (unsigned integer)
2033 Simple (master)
2034 Simple (master)
2035 Name (UTF-8 string)
2036 TagLanguage (UTF-8 string)
2037 DefaultLanguage (unsigned integer)
2038 String (UTF-8 string)
2039 Binary (binary)
2040
2042 With a segment info XML file it is possible to set certain values in
2043 the "segment information" header field of a Matroska(TM) file. All of
2044 these values cannot be set via other command line options.
2045 Other "segment information" header fields can be set via command line
2047 options but not via the XML file. This includes e.g. the --title and
2048 the --timestamp-scale options.
2049 There are other elements that can be set neither via command line
2051 options nor via the XML files. These include the following elements:
2052 DateUTC (also known as the "muxing date"), MuxingApp, WritingApp and
2053 Duration. They're always set by mkvmerge(1) itself.
2054 The following lists the supported XML tags, their data types and, where
2056 appropriate, the valid range for their values:
2057 Info (master)
2059 SegmentUID (binary, valid range: length in bytes == 16)
2060 SegmentFilename (UTF-8 string)
2061 PreviousSegmentUID (binary, valid range: length in bytes == 16)
2062 PreviousSegmentFilename (UTF-8 string)
2063 NextSegmentUID (binary, valid range: length in bytes == 16)
2064 NextSegmentFilename (UTF-8 string)
2065 SegmentFamily (binary, valid range: length in bytes == 16)
2066 ChapterTranslate (master)
2067 ChapterTranslateEditionUID (unsigned integer)
2068 ChapterTranslateCodec (unsigned integer)
2069 ChapterTranslateID (binary)
2070
2072 The Matroska(TM) file layout is quite flexible. mkvmerge(1) will
2073 render a file in a predefined way. The resulting file looks like this:
2074 [EBML head] [segment {meta seek #1} [segment information] [track
2076 information] {attachments} {chapters} [cluster 1] {cluster 2} ...
2077 {cluster n} {cues} {meta seek #2} {tags}]
2078 The elements in curly braces are optional and depend on the contents
2080 and options used. A couple of notes:
2081 • meta seek #1 includes only a small number of level 1 elements, and
2083 only if they actually exist: attachments, chapters, cues, tags,
2084 meta seek #2. Older versions of mkvmerge(1) used to put the
2085 clusters into this meta seek element as well. Therefore some
2086 imprecise guessing was necessary to reserve enough space. It often
2087 failed. Now only the clusters are stored in meta seek #2, and meta
2088 seek #1 refers to the meta seek element #2.
2089 • Attachment, chapter and tag elements are only present if they were
2091 added.
2092 The shortest possible Matroska(TM) file would look like this:
2094 [EBML head] [segment [segment information] [track information] [cluster
2096 1]]
2097 This might be the case for audio-only files.
2099
2101 mkvmerge(1) allows the user to chose the timestamps for a specific
2102 track himself. This can be used in order to create files with variable
2103 frame rate video or include gaps in audio. A frame in this case is the
2104 unit that mkvmerge(1) creates separately per Matroska(TM) block. For
2105 video this is exactly one frame, for audio this is one packet of the
2106 specific audio type. E.g. for AC-3 this would be a packet containing
2107 1536 samples.
2108 Timestamp files that are used when tracks are appended to each other
2110 must only be specified for the first part in a chain of tracks. For
2111 example if you append two files, v1.avi and v2.avi, and want to use
2112 timestamps then your command line must look something like this:
2113 $ mkvmerge ... --timestamps 0:my_timestamps.txt v1.avi +v2.avi
2115 There are four formats that are recognized by mkvmerge(1). The first
2117 line always contains the version number. Empty lines, lines containing
2118 only whitespace and lines beginning with '#' are ignored.
2119 Timestamp file format v1
2121 This format starts with the version line. The second line declares the
2122 default number of frames per second. All following lines contain three
2123 numbers separated by commas: the start frame (0 is the first frame),
2124 the end frame and the number of frames in this range. The FPS is a
2125 floating point number with the dot '.' as the decimal point. The ranges
2126 can contain gaps for which the default FPS is used. An example:
2127 # timestamp format v1
2129 assume 27.930
2130 800,1000,25
2131 1500,1700,30
2132 Timestamp file format v2
2134 In this format each line contains a timestamp for the corresponding
2135 frame. This timestamp must be given in millisecond precision. It can be
2136 a floating point number, but it doesn't have to be. You have to give at
2137 least as many timestamp lines as there are frames in the track. The
2138 timestamps in this file must be sorted. Example for 25fps:
2139 # timestamp format v2
2141 0
2142 40
2143 80
2144 Timestamp file format v3
2146 In this format each line contains a duration in seconds followed by an
2147 optional number of frames per second. Both can be floating point
2148 numbers. If the number of frames per second is not present the default
2149 one is used. For audio you should let the codec calculate the frame
2150 timestamps itself. For that you should be using 0.0 as the number of
2151 frames per second. You can also create gaps in the stream by using the
2152 'gap' keyword followed by the duration of the gap. Example for an audio
2153 file:
2154 # timestamp format v3
2156 assume 0.0
2157 25.325
2158 7.530,38.236
2159 gap, 10.050
2160 2.000,38.236
2161 Timestamp file format v4
2163 This format is identical to the v2 format. The only difference is that
2164 the timestamps do not have to be sorted. This format should almost
2165 never be used.
2166
2168 mkvmerge(1) exits with one of three exit codes:
2169 • 0 -- This exit code means that muxing has completed successfully.
2171 • 1 -- In this case mkvmerge(1) has output at least one warning, but
2173 muxing did continue. A warning is prefixed with the text
2174 'Warning:'. Depending on the issues involved the resulting file
2175 might be ok or not. The user is urged to check both the warning and
2176 the resulting file.
2177 • 2 -- This exit code is used after an error occurred. mkvmerge(1)
2179 aborts right after outputting the error message. Error messages
2180 range from wrong command line arguments over read/write errors to
2181 broken files.
2182
2184 mkvmerge(1) uses the default variables that determine the system's
2185 locale (e.g. LANG and the LC_* family). Additional variables:
2186 MKVMERGE_DEBUG, MKVTOOLNIX_DEBUG and its short form MTX_DEBUG
2188 The content is treated as if it had been passed via the --debug
2189 option.
2190 MKVMERGE_ENGAGE, MKVTOOLNIX_ENGAGE and its short form MTX_ENGAGE
2192 The content is treated as if it had been passed via the --engage
2193 option.
2194
2196 mkvinfo(1), mkvextract(1), mkvpropedit(1), mkvtoolnix-gui(1)
2197
2199 The latest version can always be found at the MKVToolNix homepage[6].
2200
2202 Moritz Bunkus <moritz@bunkus.org>
2203 Developer
2204
2206 1. the Matroska(TM) website
2207 https://www.matroska.org/
2208 2. the IANA homepage
2210 https://www.iana.org/assignments/media-types/
2211 3. mkvmerge-identification-output-schema-v17.json
2213 https://mkvtoolnix.download/doc/mkvmerge-identification-output-schema-v17.json
2214 4. RFC 7159
2216 https://tools.ietf.org/html/rfc7159
2217 5. Matroska(TM) specification
2219 https://www.matroska.org/technical/specs/index.html
2220 6. the MKVToolNix homepage
2222 https://mkvtoolnix.download/
2223MKVToolNix 73.0.0 2023-01-02 MKVMERGE(1)