table of contents
- НАЗВА
- КОРОТКИЙ ОПИС
- ОПИС
- Usage
- Option order
- Examples
- Track IDs
- Text files and character set conversions
- Option files
- ВИОКРЕМЛЕННЯ СПЕЦІАЛЬНИХ СИМВОЛІВ У ТЕКСТІ
- Subtitles
- File linking
- Default values
- ВКЛАДЕННЯ
- РОЗДІЛИ
- ТЕГИ
- The segment info XML files
- Matroska(TM) file layout
- External timecode files
- КОДИ ЗАВЕРШЕННЯ
- Environment variables
- ДИВІТЬСЯ ТАКОЖ
- WWW
- Author
- ПРИМІТКИ
other versions
- wheezy 5.6.0-1
- jessie 7.3.0-1
- testing 9.8.0-dmo1
- unstable 9.8.0-dmo1
- experimental 12.0.0-1
other languages
mkvmerge(1) | Користувацькі команди | mkvmerge(1) |
НАЗВА¶
mkvmerge - Merge multimedia streams into a Matroska(TM) fileКОРОТКИЙ ОПИС¶
mkvmerge
[global options] {-o out} [options1] {file1}
[[options2] {file2}] [@optionsfile]
ОПИС¶
This program takes the input from several media files and joins their streams (all of them or just a selection) into a Matroska(TM) file; see the Matroska(TM) website[1].Global options¶
-v, --verboseIncrease verbosity.
-q, --quiet
Suppress status output.
-o, --output file-name
Write to the file file-name. If
splitting is used then this parameter is treated a bit differently. See the
explanation for the --split option for details.
-w, --webm
Create a WebM compliant file. This is also
turned on if the output file name's extension is "webm". This mode
enforces several restrictions. The only allowed codecs are VP8 video and
Vorbis audio tracks. Neither chapters nor tags are allowed. The DocType header
item is changed to "webm".
--title title
Sets the general title for the output file,
e.g. the movie name.
--default-language language-code
Sets the default language code that will be
used for all tracks unless overwritten with the --language option. The
default language code is 'und' for 'undefined'.
Segment info handling (global options)¶
--segmentinfo filename.xmlRead segment information from a XML file. This
file can contain the segment family UID, segment UID, previous and next
segment UID elements. An example file and a DTD are included in the MKVToolNix
distribution.
See the section about segment info XML files below for details.
--segment-uid SID1,SID2,...
Sets the segment UIDs to use. This is a
comma-separated list of 128bit segment UIDs in the usual UID form: hex numbers
with or without the "0x" prefix, with or without spaces, exactly 32
digits.
Each file created contains one segment, and each segment has one segment UID. If
more segment UIDs are specified than segments are created then the surplus
UIDs are ignored. If fewer UIDs are specified than segments are created then
random UIDs will be created for them.
Chapter and tag handling (global options)¶
--chapter-language language-codeSets the ISO639-2 language code that is
written for each chapter entry. Defaults to 'eng'. See the section about
chapters below for details.
This option can be used both for simple chapter files and for source files that
contain chapters but no information about the chapters' language, e.g. MP4 and
OGM files.
--chapter-charset character-set
Sets the character set that is used for the
conversion to UTF-8 for simple chapter files. See the section about text files
and character sets for an explanation how mkvmerge(1) converts between
character sets.
This switch does also apply to chapters that are copied from certain container
types, e.g. Ogg/OGM and MP4 files. See the section about chapters below for
details.
--cue-chapter-name-format format
•%p is replaced by the current
entry's PERFORMER string,
•%t is replaced by the current
entry's TITLE string,
•%n is replaced by the current
track number and
•%N is replaced by the current
track number padded with a leading zero if it is < 10.
Read chapter information from the file
file-name. See the section about chapters below for details.
--global-tags file-name
Read global tags from the file
file-name. See the section about tags below for details.
General output control (advanced global options)¶
--track-order FID1:TID1,FID2:TID2,...This option changes the order in which the
tracks for an input file are created. The argument is a comma separated list
of pairs IDs. Each pair contains first the file ID ( FID1) which is
simply the number of the file on the command line starting at 0. The second is
a track ID ( TID1) from that file. If some track IDs are omitted then
those tracks are created after the ones given with this option have been
created.
--cluster-length spec
Limit the number of data blocks or the
duration of data in each cluster. The spec parameter can either be a
number n without a unit or a number d postfixed with 'ms'.
If no unit is used then mkvmerge(1) will put at most n data blocks
into each cluster. The maximum number of blocks is 65535.
If the number d is postfixed with 'ms' then mkvmerge(1) puts at
most d milliseconds of data into each cluster. The minimum for d
is '100ms', and the maximum is '32000ms'.
mkvmerge(1) defaults to putting at most 65535 data blocks and 5000ms of
data into a cluster.
Programs trying to find a certain frame can only seek directly to a cluster and
have to read the whole cluster afterwards. Therefore creating larger clusters
may lead to imprecise or slow seeking.
--no-cues
Tells mkvmerge(1) not to create and
write the cue data which can be compared to an index in an AVI. Matroska(TM)
files can be played back without the cue data, but seeking will probably be
imprecise and slower. Use this only if you're really desperate for space or
for testing purposes. See also option --cues which can be specified for
each input file.
--clusters-in-meta-seek
Tells mkvmerge(1) to create a meta seek
element at the end of the file containing all clusters. See also the section
about the Matroska(TM) file layout.
--disable-lacing
Disables lacing for all tracks. This will
increase the file's size, especially if there are many audio tracks. This
option is not intended for everyday use.
--enable-durations
Write durations for all blocks. This will
increase file size and does not offer any additional value for players at the
moment.
--timecode-scale factor
Forces the timecode scale factor to
factor. Valid values are in the range 1000..10000000 or
the special value -1.
Normally mkvmerge(1) will use a value of 1000000 which means that
timecodes and durations will have a precision of 1ms. For files that will not
contain a video track but at least one audio track mkvmerge(1) will
automatically chose a timecode scale factor so that all timecodes and
durations have a precision of one audio sample. This causes bigger overhead
but allows precise seeking and extraction.
If the special value -1 is used then mkvmerge(1) will use sample
precision even if a video track is present.
File splitting, linking, appending and concatenation (more global options)¶
--split specificationSplits the output file after a given size or a
given time. Please note that tracks can only be split right before a key
frame. Due to buffering mkvmerge(1) will split right before the next
key frame after the split point has been reached. Therefore the split point
may be a bit off from what the user has specified.
At the moment mkvmerge(1) supports four different modes.
1.Splitting by size.
Syntax: --split [size:] d[k|m|g]
Examples: --split size:700m or --split 150000000
The parameter d may end with 'k', 'm' or 'g' to indicate that the size is
in KB, MB or GB respectively. Otherwise a size in bytes is assumed. After the
current output file has reached this size limit a new one will be started.
The 'size:' prefix may be omitted for compatibility reasons.
2.Splitting after a duration.
Syntax: --split [duration:] HH:MM:SS.nnnnnnnnn|ds
Examples: --split duration:00:60:00.000 or --split 3600s
The parameter must either have the form HH:MM:SS.nnnnnnnnn for specifying
the duration in up to nano-second precision or be a number d followed
by the letter 's' for the duration in seconds. HH is the number of
hours, MM the number of minutes, SS the number of seconds and
nnnnnnnnn the number of nanoseconds. Both the number of hours and the
number of nanoseconds can be omitted. There can be up to nine digits after the
decimal point. After the duration of the contents in the current output has
reached this limit a new output file will be started.
The 'duration:' prefix may be omitted for compatibility reasons.
3.Splitting after specific timecodes.
Syntax: --split timecodes: A[,B[,C...]]
Example: --split timecodes:00:45:00.000,01:20:00.250,6300s
The parameters A, B, C etc must all have the same format as
the ones used for the duration (see above). The list of timecodes is separated
by commas. After the input stream has reached the current split point's
timecode a new file is created. Then the next split point given in this list
is used.
The 'timecodes:' prefix must not be omitted.
4.Keeping specific parts by specifying
timecode ranges while discarding others.
Syntax: --split parts:
start1-end1[,[+]start2-end2[,[+]
start3-end3...]]
Examples:
1.--split
parts:00:01:20-00:02:45,00:05:50-00:10:30.RE
2.--split
parts:00:01:20-00:02:45,+00:05:50-00:10:30.RE
For this splitting mode the output filename is treated differently than for the
normal operation. It may contain a printf like expression '%d'
including an optional field width, e.g. '%02d'. If it does then the current
file number will be formatted appropriately and inserted at that point in the
filename. If there is no such pattern then a pattern of '-%03d' is assumed
right before the file's extension: '-o output.mkv' would result in
'output-001.mkv' and so on. If there's no extension then '-%03d' will be
appended to the name.
--link
3.--split parts:-00:02:45,00:05:50-.RE
The parts mode tells mkvmerge(1) to keep certain ranges of timecodes
while discarding others. The ranges to keep have to be listed after the parts:
keyword and be separated by commas. A range itself consists of a start and an
end timecode in the same format the other variations of --split accept
(e.g. both 00:01:20 and 80s refer to the same timecode).
If a start timecode is left out then it defaults to the previous range's end
timecode. If there was no previous range then it defaults to the start of the
file (see example 3).
If an end timecode is left out then it defaults to the end of the source files
which basically tells mkvmerge to keep the rest (see example 3).
Normally each range will be written to a new file. This can be changed so that
consecutive ranges are written to the same file. For that the user has to
prefix the start timecode with a +. This tells mvkmerge not to create a new
file and instead append the range to the same file the previous range was
written to. Timecodes will be adjusted so that there will be no gap in the
output file even if there was a gap in the two ranges in the input file.
In example 1 mkvmerge will create two files. The first will contain the content
starting from 00:01:20 until 00:02:45. The second file will contain the
content starting from 00:05:50 until 00:10:30.
In example 2 mkvmerge will create only one file. This file will contain both the
content starting from 00:01:20 until 00:02:45 and the content starting from
00:05:50 until 00:10:30.
In example 3 mkvmerge will create two files. The first will contain the content
from the start of the source files until 00:02:45. The second file will
contain the content starting from 00:05:50 until the end of the source
files.
Link files to one another when splitting the
output file. See the section on file linking below for details.
--link-to-previous segment-UID
Links the first output file to the segment
with the segment UID given by the segment-UID parameter. See the
section on file linking below for details.
--link-to-next segment-UID
Links the last output file to the segment with
the segment UID given by the segment-UID parameter. See the section on
file linking below for details.
--append-mode mode
Determines how timecodes are calculated when
appending files. The parameter mode can have two values: 'file' which
is also the default and 'track'.
When mkvmerge appends a track (called 'track2_1' from now on) from a second file
(called 'file2') to a track (called 'track1_1') from the first file (called
'file1') then it has to offset all timecodes for 'track2_1' by an amount. For
'file' mode this amount is the highest timecode encountered in 'file1' even if
that timecode was from a different track than 'track1_1'. In track mode the
offset is the highest timecode of 'track1_1'.
Unfortunately mkvmerge cannot detect which mode to use reliably. Therefore it
defaults to 'file' mode. 'file' mode usually works better for files that have
been created independently of each other; e.g. when appending AVI or MP4
files. 'track' mode may work better for sources that are essentially just
parts of one big file, e.g. for VOB and EVO files.
Subtitle tracks are always treated as if 'file' mode were active even if 'track'
mode actually is.
--append-to SFID1:STID1:DFID1:DTID1[,...]
This option controls to which track another
track is appended. Each spec contains four IDs: a file ID, a track ID, a
second file ID and a second track ID. The first pair, "source file
ID" and "source track ID", identifies the track that is to be
appended. The second pair, "destination file ID" and
"destination track ID", identifies the track the first one is
appended to.
If this option has been omitted then a standard mapping is used. This standard
mapping appends each track from the current file to a track from the previous
file with the same track ID. This allows for easy appending if a movie has
been split into two parts and both file have the same number of tracks and
track IDs with the command mkvmerge -o output.mkv part1.mkv
+part2.mkv.
+
A single '+' causes the next file to be
appended instead of added. The '+' can also be put in front of the next file
name. Therefore the following two commands are equivalent:
=
$ mkvmerge -o full.mkv file1.mkv + file2.mkv $ mkvmerge -o full.mkv file1.mkv +file2.mkv
Normally mkvmerge(1) looks for files in
the same directory as an input file that have the same base name and only
differ in their running number (e.g. 'VTS_01_1.VOB', 'VTS_01_2.VOB',
'VTS_01_3.VOB' etc) and treats all of those files as if they were concatenated
into a single big file. This option, a single '=', causes mkvmerge not to look
for those additional files.
The '=' can also be put in front of the next file name. Therefore the following
two commands are equivalent:
( file1 file2 )
$ mkvmerge -o full.mkv = file1.mkv $ mkvmerge -o full.mkv =file1.mkv
If multiple file names are contained in a pair
of parenthesis then those files will be treated as if they were concatenated
into a single big file consisting of the content of each of the files one
after the other.
This can be used for e.g. VOB files coming from a DVD or MPEG transport streams.
It cannot be used if each file contains its own set of headers which is
usually the case with stand-alone files like AVI or MP4.
Putting a file name into parenthesis also prevents mkvmerge(1) from
looking for additional files with the same base name as described in option
=. Therefore these two command lines are equivalent:
Several things should be noted:
$ mkvmerge -o out.mkv = file.mkv $ mkvmerge -o out.mkv '(' file.mkv ')'
1.There must be spaces both after the opening
and before the closing parenthesis.
2.Every parameter between parenthesis is
interpreted as a file name. Therefore all options applying to this logical
file must be listed before the opening parenthesis.
3.Some shells treat parenthesis as special
characters. Hence you must escape or quote them as shown in the example
above.
Attachment support (more global options)¶
--attachment-description descriptionPlain text description of the following
attachment. Applies to the next --attach-file or
--attach-file-once option.
--attachment-mime-type MIME type
Sets the name that will be stored in the
output file for this attachment. If this option is not given then the name
will be derived from the file name of the attachment as given with the
--attach-file or the --attach-file-once option.
--attach-file file-name, --attach-file-once
file-name
Creates a file attachment inside the
Matroska(TM) file. The MIME type must have been set before this option can
used. The difference between the two forms is that during splitting the files
attached with --attach-file are attached to all output files while the
ones attached with --attach-file-once are only attached to the first
file created. If splitting is not used then both do the same.
mkvextract(1) can be used to extract attached files from a Matroska(TM)
file.
Options that can be used for each input file¶
-a, --audio-tracks [!]n,m,...Copy the audio tracks n, m etc.
The numbers are track IDs which can be obtained with the --identify
switch. They're not simply the track numbers (see section track IDs). Default:
copy all audio tracks.
If the IDs are prefixed with ! then the meaning is reversed: copy everything but
the IDs listed after the !.
-d, --video-tracks [!]n,m,...
Copy the video tracks n, m etc.
The numbers are track IDs which can be obtained with the --identify
switch. They're not simply the track numbers (see section track IDs). Default:
copy all video tracks.
If the IDs are prefixed with ! then the meaning is reversed: copy everything but
the IDs listed after the !.
-s, --subtitle-tracks [!]n,m,...
Copy the subtitle tracks n, m
etc. The numbers are track IDs which can be obtained with the
--identify switch. They're not simply the track numbers (see section
track IDs). Default: copy all subtitle tracks.
If the IDs are prefixed with ! then the meaning is reversed: copy everything but
the IDs listed after the !.
-b, --button-tracks [!]n,m,...
Copy the button tracks n, m etc.
The numbers are track IDs which can be obtained with the --identify
switch. They're not simply the track numbers (see section track IDs). Default:
copy all button tracks.
If the IDs are prefixed with ! then the meaning is reversed: copy everything but
the IDs listed after the !.
--track-tags [!]n,m,...
Copy the tags for tracks n, m
etc. The numbers are track IDs which can be obtained with the
--identify switch (see section track IDs). They're not simply the track
numbers. Default: copy tags for all tracks.
If the IDs are prefixed with ! then the meaning is reversed: copy everything but
the IDs listed after the !.
-m, --attachments
[!]n[:all|first],m[:all|first],...
Copy the attachments with the IDs n,
m etc to all or only the first output file. Each ID can be followed by
either ':all' (which is the default if neither is entered) or ':first'. If
splitting is active then those attachments whose IDs are specified with ':all'
are copied to all of the resulting output files while the others are only
copied into the first output file. If splitting is not active then both
variants have the same effect.
The default is to copy all attachments to all output files.
If the IDs are prefixed with ! then the meaning is reversed: copy everything but
the IDs listed after the !.
-A, --no-audio
Don't copy any audio track from this
file.
-D, --no-video
Don't copy any video track from this
file.
-S, --no-subtitles
Don't copy any subtitle track from this
file.
-B, --no-buttons
Don't copy any button track from this
file.
-T, --no-track-tags
Don't copy any track specific tags from this
file.
--no-chapters
Don't copy chapters from this file.
-M, --no-attachments
Don't copy attachments from this file.
--no-global-tags
Don't copy global tags from this file.
--chapter-charset character-set
Sets the charset that is used for the
conversion to UTF-8 for chapter information contained in the source file. See
the section about text files and character sets for an explanation how
mkvmerge(1) converts between character sets.
--chapter-language language-code
Sets the ISO639-2 language code that is
written for each chapter entry. This option can be used for source files that
contain chapters but no information about the chapters' languages, e.g. for
MP4 and OGM files.
-y, --sync TID:d[,o[/p]]
Adjust the timecodes of the track with the id
TID by d ms. The track IDs are the same as the ones given with
--identify (see section track IDs).
o/p: adjust the timestamps by o/p to fix linear
drifts. p defaults to 1 if omitted. Both o and p can be
floating point numbers.
Defaults: no manual sync correction (which is the same as d = 0
and o/p = 1.0).
This option can be used multiple times for an input file applying to several
tracks by selecting different track IDs each time.
--cues TID:none|iframes|all
Controls for which tracks cue (index) entries
are created for the given track (see section track IDs). 'none' inhibits the
creation of cue entries. For 'iframes' only blocks with no backward or forward
references ( = I frames in video tracks) are put into the cue sheet. 'all'
causes mkvmerge(1) to create cue entries for all blocks which will make
the file very big.
The default is 'iframes' for video tracks and 'none' for all others. See also
option --no-cues which inhibits the creation of cue entries regardless
of the --cues options used.
This option can be used multiple times for an input file applying to several
tracks by selecting different track IDs each time.
--default-track TID[:bool]
Sets the 'default' flag for the given track
(see section track IDs) if the optional argument bool is not present.
If the user does not explicitly select a track himself then the player should
prefer the track that has his 'default' flag set. Only one track of each kind
(audio, video, subtitles, buttons) can have his 'default' flag set. If the
user wants no track to have the default track flag set then he has to set
bool to 0 for all tracks.
This option can be used multiple times for an input file applying to several
tracks by selecting different track IDs each time.
--forced-track TID[:bool]
Sets the 'forced' flag for the given track
(see section track IDs) if the optional argument bool is not present. A
player must play all tracks for which this flag is set to 1.
This option can be used multiple times for an input file applying to several
tracks by selecting different track IDs each time.
--blockadd TID:level
Keep only the BlockAdditions up to the level
level for the given track. The default is to keep all levels. This
option only affects certain kinds of codecs like WAVPACK4.
--track-name TID:name
Sets the track name for the given track (see
section track IDs) to name.
--language TID:language
Sets the language for the given track (see
section track IDs). Both ISO639-2 language codes and ISO639-1 country codes
are allowed. The country codes will be converted to language codes
automatically. All languages including their ISO639-2 codes can be listed with
the --list-languages option.
This option can be used multiple times for an input file applying to several
tracks by selecting different track IDs each time.
-t, --tags TID:file-name
Read tags for the track with the number
TID from the file file-name. See the section about tags below
for details.
--aac-is-sbr TID[:0|1]
Tells mkvmerge(1) that the track with
the ID TID is SBR AAC (also known as HE-AAC or AAC+). This options is
needed if a) the source file is an AAC file ( not for a Matroska(TM)
file) and b) the AAC file contains SBR AAC data. The reason for this switch is
that it is technically impossible to automatically tell normal AAC data from
SBR AAC data without decoding a complete AAC frame. As there are several
patent issues with AAC decoders mkvmerge(1) will never contain this
decoding stage. So for SBR AAC files this switch is mandatory. The resulting
file might not play back correctly or even not at all if the switch was
omitted.
If the source file is a Matroska(TM) file then the CodecID should be enough to
detect SBR AAC. However, if the CodecID is wrong then this switch can be used
to correct that.
If mkvmerge wrongfully detects that an AAC file is SBR then you can add ':0' to
the track ID.
--timecodes TID:file-name
Read the timecodes to be used for the specific
track ID from file-name. These timecodes forcefully override the
timecodes that mkvmerge(1) normally calculates. Read the section about
external timecode files.
--default-duration TID:x
Forces the default duration of a given track
to the specified value. Also modifies the track's timecodes to match the
default duration. The argument x must be postfixed with 's', 'ms',
'us', 'ns', 'fps', 'p' or 'i' to specify the default duration in seconds,
milliseconds, microseconds, nanoseconds, 'frames per second', 'progressive
frames per second' or 'interlaced frames per second' respectively. The number
x itself can be a floating point number or a fraction.
If the default duration is not forced then mkvmerge will try to derive the
track's default duration from the container and/or the encoded bitstream for
certain track types, e.g. AVC/h.264 or MPEG-2.
This option can also be used to change the FPS of video tracks without having to
use an external timecode file.
--nalu-size-length TID:n
Forces the NALU size length to n bytes.
This parameter is only used if the AVC/h.264 elementary stream packetizer is
used. If left out it defaults to 4 bytes, but there are files that contain
frames or slices that are all smaller than 65536 bytes. For such files you can
use this parameter and decrease the size to 2.
--compression TID:n
Selects the compression method to be used for
the track. Note that the player also has to support this method. Valid values
are 'none', 'zlib', 'lzo'/'lxo1x', 'bz2'/'bzlib' and 'mpeg4_p2'/'mpeg4p2'. The
values 'lzo'/'lxo1x' and 'bz2'/'bzlib' are only available if
mkvmerge(1) has been compiled with support for the liblzo(TM) and
bzlib(TM) compression libraries, respectively.
The compression method 'mpeg4_p2'/'mpeg4p2' is a special compression method
called 'header removal' that is only available for MPEG4 part 2 video tracks.
The default for some subtitle tracks is 'zlib' compression. This compression
method is also the one that most if not all playback applications support.
Support for other compression methods other than 'none' is not assured.
Options that only apply to video tracks¶
-f, --fourcc TID:FourCCForces the FourCC to the specified value.
Works only for video tracks in the 'MS compatibility mode'.
--display-dimensions TID:widthxheight
Another way to set the aspect ratio is to
specify a factor. The original aspect ratio is first multiplied with
this factor and used as the target aspect ratio afterwards.
Another way to specify the values is to use the --aspect-ratio or
--display-dimensions options (see above). These options are mutually
exclusive.
--cropping TID:left,top,right,bottom
Sets the pixel cropping parameters of a video
track to the given values.
--stereo-mode TID:n|keyword
Sets the stereo mode for the video track with
the track ID TID. The mode can either be a number n between
0 and 14 or one of these keywords:
'mono', 'side_by_side_left_first', 'top_bottom_right_first',
'top_bottom_left_first', 'checkerboard_right_first',
'checkerboard_left_first', 'row_interleaved_right_first',
'row_interleaved_left_first', 'column_interleaved_right_first',
'column_interleaved_left_first', 'anaglyph_cyan_red',
'side_by_side_right_first', 'anaglyph_green_magenta',
'both_eyes_laced_left_first', 'both_eyes_laced_right_first'.
Options that only apply to text subtitle tracks¶
--sub-charset TID:character-setSets the character set for the conversion to
UTF-8 for UTF-8 subtitles for the given track ID. If not specified the charset
will be derived from the current locale settings. Note that a charset is not
needed for subtitles read from Matroska(TM) files or from Kate streams, as
these are always stored in UTF-8. See the section about text files and
character sets for an explanation how mkvmerge(1) converts between
character sets.
This option can be used multiple times for an input file applying to several
tracks by selecting different track IDs each time.
Other options¶
-i, --identify file-nameWill let mkvmerge(1) probe the single
file and report its type, the tracks contained in the file and their track
IDs. If this option is used then the only other option allowed is the
filename.
-I, --identify-verbose file-name
Will let mkvmerge(1) probe the single
file and report its type, the tracks contained in the file and their track
IDs. If this option is used then the only other option allowed is the
filename.
This option causes mkvmerge(1) to output additional information about the
container and each track within. The extra information is surronded by square
brackets. It consists of space-saparated key/value pairs where keys and values
are separated by a colon.
Each value is escaped according to the rules described in the section about
escaping special characters in text.
-l, --list-types
Lists supported input file types.
--list-languages
Lists all languages and their ISO639-2 code
which can be used with the --language option.
--priority priority
Sets the process priority that
mkvmerge(1) runs with. Valid values are 'lowest', 'lower', 'normal',
'higher' and 'highest'. If nothing is given then 'normal' is used. On Unix
like systems mkvmerge(1) will use the nice(2) function.
Therefore only the super user can use 'higher' and 'highest'. On Windows all
values are useable for every user.
--command-line-charset character-set
Sets the character set to convert strings
given on the command line from. It defaults to the character set given by
system's current locale. This settings applies to arguments of the following
options: --title, --track-name and
--attachment-description.
--output-charset character-set
Встановлює
вихідний
набір
символів
заданого в
командному
рядку для
конвертації.
Типово
використовується
набір
символів
згідно
поточної
локалі
системи.
-r, --redirect-output file-name
Writes all messages to the file
file-name instead of to the console. While this can be done easily with
output redirection there are cases in which this option is needed: when the
terminal reinterprets the output before writing it to a file. The character
set set with --output-charset is honored.
--ui-language code
Forces the translations for the language
code to be used (e.g. 'de_DE' for the German translations). It is
preferable to use the environment variables LANG, LC_MESSAGES
and LC_ALL though. Entering 'list' as the code will cause
mkvmerge(1) to output a list of available translations.
--debug topic
Turn on debugging for a specific feature. This
option is only useful for developers.
--engage feature
Turn on experimental features. A list of
available features can be requested with mkvmerge --engage list. These
features are not meant to be used in normal situations.
@options-file
Reads additional command line arguments from
the file options-file. See the section about option files for further
information.
--capabilities
Lists information about optional features that
have been compiled in and exit. The first line output will be the version
information. All following lines contain exactly one word whose presence
indicates that the feature has been compiled in. These features are:
-h, --help
•'BZ2' -- the bzlib(TM) compression
library. Affects the available compression methods for the
--compression option.
•'LZO' -- the lzo(TM) compression
library. Affects the available compression methods for the
--compression option.
•'FLAC' -- reading raw FLAC files and
handling FLAC tracks in other containers, e.g. Ogg(TM) or Matroska(TM).
Відображається
інформація
про
використання
додатку і
відбувається
завершення
роботи
додатку.
-V, --version
Відображається
інформація
про версію
додатку і
відбувається
завершення
роботи
додатку.
--check-for-updates
Відбувається
перевірка на
наявність
нової версії
шляхом
завантаження
з URL http://mkvtoolnix-releases.bunkus.org/latest-release.xml.
Буде
відображено
чотири рядка
у key=value стилі: URL,
звідки
отримана
інформація (key
version_check_url), поточна
запущена
версія (key running_version),
остання
випущена
версія (key available_version) і URL
для
завантаження
(key download_url).
Після чого
додаток
завершує
роботу з
кодом
повернення 0,
якщо немає
нової
версії, і з
кодом 2, якщо
виникла
помилка
(наприклад,
коли не було
отримано
інформації
про
оновлення
взагалі).
Дана опція
наявна лише
тоді, коли
додаток
компілювався
з підтримкою
libcurl.
Usage¶
For each file the user can select which tracks mkvmerge(1) should take. They are all put into the file specified with -o. A list of known (and supported) source formats can be obtained with the -l option.Option order¶
The order in which options are entered is important for some options. Options fall into two categories: 1.Options that affect the whole program and
are not tied to any input file. These include but are not limited to
--command-line-charset, --output or --title. These can
appear anywhere on the command line.
2.Options that affect a single input file or
a single track in an input file. These options all apply to the following
input file on the command line. All options applying to the same input (or to
tracks from the same input file) file can be written in any order as long as
they all appear before that input file's name. Examples for options applying
to an input file are --no-chapters or --chapter-charset.
Examples for options applying to a single track are --default-duration
or --language.
The options are processed from left to right. If an option appears multiple
times within the same scope then the last occurence will be used. Therefore
the title will be set to "Something else" in the following example:
$ mkvmerge -o output.mkv --title 'This and that' input.avi --title 'Something else'
$ mkvmerge -o output.mkv --language 0:fre français.ogg --language 0:deu deutsch.ogg
Examples¶
Let's assume you have a file called MyMovie.avi and the audio track in a separate file, e.g. 'MyMovie.wav'. First you want to encode the audio to OggVorbis(TM):$ oggenc -q4 -oMyMovie.ogg MyMovie.wav
$ mkvmerge -o MyMovie-with-sound.mkv MyMovie.avi MyMovie.ogg
$ mkvmerge -o MyMovie-with-sound.mkv -A MyMovie.avi MyMovie.ogg
$ oggenc -q4 -oMyMovie-add-audio.ogg MyMovie-add-audio.wav $ mkvmerge -o MM-complete.mkv MyMovie-with-sound.mkv MyMovie-add-audio.ogg
$ mkvmerge -o MM-complete.mkv -A MyMovie.avi MyMovie.ogg MyMovie-add-audio.ogg
$ mkvmerge --identify outofsync.ogg
$ mkvmerge -o goodsync.mkv -A source.avi -y 12345:200 outofsync.ogg
$ mkvmerge -o goodsync.mkv -y 23456:0,77346/77340 outofsync.mkv
1.extract a raw subtitle stream from the
source:
$ tccat -i /path/to/copied/dvd/ -T 1 -L | tcextract -x ps1 -t vob -a 0x20 | subtitle2pgm -o mymovie
2.convert the resulting PGM images to text
with gocr:
$ pgm2txt mymovie
3.spell-check the resulting text files:
$ ispell -d american *txt
4.convert the text files to a SRT file:
The resulting file can be used as another input file for mkvmerge(1):
$ srttool -s -w -i mymovie.srtx -o mymovie.srt
$ mkvmerge -o mymovie.mkv mymovie.avi mymovie.srt
$ mkvmerge --list-languages
$ mkvmerge -o with-lang-codes.mkv --language 2:ger --language 3:dut without-lang-codes.mkv
$ mkvmerge -o with-lang-codes.mkv --language 2:ger --language 3:dut --default-track 3 without-lang-codes.mkv --language 0:eng english.srt --default-track 0 --language 0:fre french.srt
$ mkvmerge -o no-compression.mkv --compression -1:none MyMovie.avi --compression -1:none mymovie.srt
Track IDs¶
Some of the options for mkvmerge(1) need a track ID to specify which track they should be applied to. Those track IDs are printed by the readers when demuxing the current input file, or if mkvmerge(1) is called with the --identify option. An example for such output:$ mkvmerge -i v.mkv File 'v.mkv': container: Matroska(TM) Track ID 1: video (V_MS/VFW/FOURCC, DIV3) Track ID 2: audio (A_MPEG/L3)
•
AVI files: The video track has the ID 0. The audio tracks get IDs in ascending
order starting at 1.
•
AAC, AC3, MP3, SRT and WAV files: The one 'track' in that file gets the ID
0.
•Most other files: The track IDs are
assigned in order the tracks are found in the file starting at 0.
The special track ID ' -1' is a wild card and applies the given switch to
all tracks that are read from an input file.
The options that use the track IDs are the ones whose description contains
'TID'. The following options use track IDs as well: --audio-tracks,
--video-tracks, --subtitle-tracks, --button-tracks and
--track-tags.
Text files and character set conversions¶
All text in a Matroska(TM) file is encoded in UTF-8. This means that mkvmerge(1) has to convert every text file it reads as well as every text given on the command line from one character set into UTF-8. In return this also means that mkvmerge(1)'s output has to be converted back to that character set from UTF-8, e.g. if a non-English translation is used with --ui-language or for text originating from a Matroska(TM) file.•
--sub-charset for text subtitle files and for text subtitle tracks stored
in container formats for which the character set cannot be determined
unambiguously (e.g. Ogg files),
•
--chapter-charset for chapter text files and for chapters and file titles
stored in container formats for which the character set cannot be determined
unambiguously (e.g. Ogg files for chapter information, track and file titles
etc; MP4 files for chapter information),
•
--command-line-charset for all strings on the command line,
•
--output-charset for all strings written to the console or to a file if
the output has been redirected with the --redirect-output option.
Option files¶
An option file is a file mkvmerge(1) can read additional command line arguments from. This can be used in order to circumvent certain limitations of the shell or the operating system when executing external programs like a limited command line length. There are several rules regarding option files. Lines whose first non-whitespace character is a hash mark ('#') are treated as comments and ignored. White spaces at the start and end of a line will be stripped. Each line must contain exactly one option. A line not containing anything is also ignored. An empty argument is represented by the line '#EMPTY#'. Several chars can be escaped, e.g. if you need to start a non-comment line with '#'. The rules are described in the section about escaping text. Note that backslashes must always be escaped. Hash marks ('#') must be escaped if they should not start a comment. The command line ' mkvmerge -o "my file.mkv" -A "a movie.avi" sound.ogg' could be converted into the following option file:# Write to the file "c:\Matroska\my file.mkv" on Windows. -o c:\\Matroska\\my file.mkv # Set the title to '#65'. --title \h65 # Only take the video from "a movie.avi". -A a movie.avi sound.ogg
ВИОКРЕМЛЕННЯ СПЕЦІАЛЬНИХ СИМВОЛІВ У ТЕКСТІ¶
Є декілька місць, де спеціальні символи у тексті мають або повинні бути виокремлені. Правила для виокремлювання прості: кожен символ, що потребує виокремлення, замінюється на зворотній слеш з деяким символом, що йде після нього. The rules are: ' ' (a space) becomes '\s', '"' (double quotes) becomes '\2', ':' becomes '\c', '#' becomes '\h' and '\' (a single backslash) itself becomes '\\'.Subtitles¶
There are several text and bitmap subtitle formats that can be embedded into Matroska(TM). Text subtitles must be recoded to UTF-8 so that they can be displayed correctly by a player (see the section about text files and character sets for an explanation how mkvmerge(1) converts between character sets). Kate subtitles are already encoded in UTF-8 and do not have to be re-encoded. The following subtitle formats are supported at the moment:•Subtitle Ripper (SRT) files
•Substation Alpha (SSA) / Advanced
Substation Alpha scripts (ASS)
•Universal Subtitle Format (USF)
files
•OggKate streams
•VobSub bitmap subtitle files
•PGS bitmap subtitle files as found on
BluRay discs
File linking¶
Default values¶
The Matroska(TM) specification states that some elements have a default value. Usually an element is not written to the file if its value is equal to its default value in order to save space. The elements that the user might miss in mkvinfo(1)'s output are the language and the default track flag elements. The default value for the language is English ('eng'), and the default value for the default track flag is true. Therefore if you used --language 0:eng for a track then it will not show up in mkvinfo(1)'s output.ВКЛАДЕННЯ¶
Maybe you also want to keep some photos along with your Matroska(TM) file, or you're using SSA subtitles and need a special TrueType(TM) font that's really rare. In these cases you can attach those files to the Matroska(TM) file. They will not be just appended to the file but embedded in it. A player can then show those files (the 'photos' case) or use them to render the subtitles (the 'TrueType(TM) fonts' case). Here's an example how to attach a photo and a TrueType(TM) font to the output file:$ mkvmerge -o output.mkv -A video.avi sound.ogg \ --attachment-description "Me and the band behind the stage in a small get-together" \ --attachment-mime-type image/jpeg \ --attach-file me_and_the_band.jpg \ --attachment-description "The real rare and unbelievably good looking font" \ --attachment-type application/octet-stream \ --attach-file really_cool_font.ttf
РОЗДІЛИ¶
The Matroska(TM) chapter system is more powerful than the old known system used by OGM files. The full specifications can be found at the Matroska(TM) website[1].The simple chapter format¶
This formmat consists of pairs of lines that start with 'CHAPTERxx=' and 'CHAPTERxxNAME=' respectively. The first one contains the start timecode while the second one contains the title. Here's an example:CHAPTER01=00:00:00.000 CHAPTER01NAME=Intro CHAPTER02=00:02:30.000 CHAPTER02NAME=Baby prepares to rock CHAPTER03=00:02:42.300 CHAPTER03NAME=Baby rocks the house
The XML based chapter format¶
The XML based chapter format looks like this example:<?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE Chapters SYSTEM "matroskachapters.dtd"> <Chapters> <EditionEntry> <ChapterAtom> <ChapterTimeStart>00:00:30.000</ChapterTimeStart> <ChapterTimeEnd>00:01:20.000</ChapterTimeEnd> <ChapterDisplay> <ChapterString>A short chapter</ChapterString> <ChapterLanguage>eng</ChapterLanguage> </ChapterDisplay> <ChapterAtom> <ChapterTimeStart>00:00:46.000</ChapterTimeStart> <ChapterTimeEnd>00:01:10.000</ChapterTimeEnd> <ChapterDisplay> <ChapterString>A part of that short chapter</ChapterString> <ChapterLanguage>eng</ChapterLanguage> </ChapterDisplay> </ChapterAtom> </ChapterAtom> </EditionEntry> </Chapters>
1.The timestamp for the end of the chapter
can be set,
2.chapters can be nested,
3.the language and country can be set.
The mkvtoolnix distribution contains some sample files in the doc subdirectory
which can be used as a basis.
The following lists the supported XML tags, their data types and, where
appropriate, the valid range for their values:
Chapters (master) EditionEntry (master) EditionUID (unsigned integer, valid range: 1 <= value) EditionFlagHidden (unsigned integer, valid range: 0 <= value <= 1) EditionFlagDefault (unsigned integer, valid range: 0 <= value <= 1) EditionFlagOrdered (unsigned integer, valid range: 0 <= value <= 1) ChapterAtom (master) ChapterAtom (master) ChapterUID (unsigned integer, valid range: 1 <= value) ChapterTimeStart (unsigned integer) ChapterTimeEnd (unsigned integer) ChapterFlagHidden (unsigned integer, valid range: 0 <= value <= 1) ChapterFlagEnabled (unsigned integer, valid range: 0 <= value <= 1) ChapterSegmentUID (binary, valid range: 1 <= length in bytes) ChapterSegmentEditionUID (unsigned integer, valid range: 1 <= value) ChapterPhysicalEquiv (unsigned integer) ChapterTrack (master) ChapterTrackNumber (unsigned integer, valid range: 1 <= value) ChapterDisplay (master) ChapterString (UTF-8 string) ChapterLanguage (UTF-8 string) ChapterCountry (UTF-8 string) ChapterProcess (master) ChapterProcessCodecID (unsigned integer) ChapterProcessPrivate (binary) ChapterProcessCommand (master) ChapterProcessTime (unsigned integer) ChapterProcessData (binary)
General notes¶
When splitting files mkvmerge(1) will correctly adjust the chapters as well. This means that each file only includes the chapter entries that apply to it, and that the timecodes will be offset to match the new timecodes of each output file.ТЕГИ¶
Introduction¶
Scope of the tags¶
Example¶
Let's say that you want to add tags to a video track read from an AVI. mkvmerge --identify file.avi tells you that the video track's ID (do not mix this ID with the UID!) is 0. So you create your tag file, leave out all Targets elements and call mkvmerge(1):$ mkvmerge -o file.mkv --tags 0:tags.xml file.avi
Tag file format¶
•The outermost element must be
<Tags>.
•One logical tag is contained inside one
pair of <Tag> XML tags.
•White spaces directly before and after
tag contents are ignored.
Data types¶
The new Matroska(TM) tagging system only knows two data types, a UTF-8 string and a binary type. The first is used for the tag's name and the <String> element while the binary type is used for the <Binary> element. As binary data itself would not fit into a XML file mkvmerge(1) supports two other methods of storing binary data. If the contents of a XML tag starts with '@' then the following text is treated as a file name. The corresponding file's content is copied into the Matroska(TM) element. Otherwise the data is expected to be Base64 encoded. This is an encoding that transforms binary data into a limited set of ASCII characters and is used e.g. in email programs. mkvextract(1) will output Base64 encoded data for binary elements. The deprecated tagging system knows some more data types which can be found in the official Matroska(TM) tag specs. As mkvmerge(1) does not support this system anymore these types aren't described here.Known tags for the XML file format¶
The following lists the supported XML tags, their data types and, where appropriate, the valid range for their values:Tags (master) Tag (master) Targets (master) TargetTypeValue (unsigned integer) TargetType (UTF-8 string) TrackUID (unsigned integer) EditionUID (unsigned integer) ChapterUID (unsigned integer) AttachmentUID (unsigned integer) Simple (master) Simple (master) Name (UTF-8 string) TagLanguage (UTF-8 string) DefaultLanguage (unsigned integer) String (UTF-8 string) Binary (binary)
The segment info XML files¶
With a segment info XML file it is possible to set certain values in the "segment information" header field of a Matroska file. All of these values cannot be set via other command line options. Other "segment information" header fields can be set via command line options but not via the XML file. This includes e.g. the --title and the --timecode-scale options. There are other elements that can be set neither via command line options nor via the XML files. These include the following elements: DateUTC (also known as the "muxing date"), MuxingApp, WritingApp and Duration. They're always set by mkvmerge(1) itself. The following lists the supported XML tags, their data types and, where appropriate, the valid range for their values:Info (master) SegmentUID (binary, valid range: length in bytes == 16) SegmentFilename (UTF-8 string) PreviousSegmentUID (binary, valid range: length in bytes == 16) PreviousSegmentFilename (UTF-8 string) NextSegmentUID (binary, valid range: length in bytes == 16) NextSegmentFilename (UTF-8 string) SegmentFamily (binary, valid range: length in bytes == 16) ChapterTranslate (master) ChapterTranslateEditionUID (unsigned integer) ChapterTranslateCodec (unsigned integer) ChapterTranslateID (binary)
Matroska(TM) file layout¶
The Matroska(TM) file layout is quite flexible. mkvmerge(1) will render a file in a predefined way. The resulting file looks like this: [EBML head] [segment {meta seek #1} [segment information] [track information] {attachments} {chapters} [cluster 1] {cluster 2} ... {cluster n} {cues} {meta seek #2} {tags}] The elements in curly braces are optional and depend on the contents and options used. A couple of notes:•meta seek #1 includes only a small
number of level 1 elements, and only if they actually exist: attachments,
chapters, cues, tags, meta seek #2. Older versions of mkvmerge(1) used
to put the clusters into this meta seek element as well. Therefore some
imprecise guessing was necessary to reserve enough space. It often failed. Now
only the clusters are stored in meta seek #2, and meta seek #1 refers to the
meta seek element #2.
•Attachment, chapter and tag elements
are only present if they were added.
The shortest possible Matroska file would look like this:
[EBML head] [segment [segment information] [track information] [cluster 1]]
This might be the case for audio-only files.
External timecode files¶
$ mkvmerge ... --timecodes 0:my_timecodes.txt v1.avi +v2.avi
Timecode file format v1¶
This format starts with the version line. The second line declares the default number of frames per second. All following lines contain three numbers separated by commas: the start frame ( 0 is the first frame), the end frame and the number of frames in this range. The FPS is a floating point number with the dot '.' as the decimal point. The ranges can contain gaps for which the default FPS is used. An example:# timecode format v1 assume 27.930 800,1000,25 1500,1700,30
Timecode file format v2¶
In this format each line contains a timecode for the corresponding frame. This timecode must be given in millisecond precision. It can be a floating point number, but it doesn't have to be. You have to give at least as many timecode lines as there are frames in the track. The timecodes in this file must be sorted. Example for 25fps:# timecode format v2 0 40 80
Timecode file format v3¶
In this format each line contains a duration in seconds followed by an optional number of frames per second. Both can be floating point numbers. If the number of frames per second is not present the default one is used. For audio you should let the codec calculate the frame timecodes itself. For that you should be using 0.0 as the number of frames per second. You can also create gaps in the stream by using the 'gap' keyword followed by the duration of the gap. Example for an audio file:# timecode format v3 assume 0.0 25.325 7.530,38.236 gap, 10.050 2.000,38.236
Timecode file format v4¶
This format is identical to the v2 format. The only difference is that the timecodes do not have to be sorted. This format should almost never be used.КОДИ ЗАВЕРШЕННЯ¶
•
0 -- This exit codes means that muxing has completed successfully.
•
1 -- In this case mkvmerge(1) has output at least one warning, but
muxing did continue. A warning is prefixed with the text 'Warning:'. Depending
on the issues involved the resulting file might be ok or not. The user is
urged to check both the warning and the resulting file.
•
2 -- This exit code is used after an error occurred. mkvmerge(1)
aborts right after outputting the error message. Error messages range from
wrong command line arguments over read/write errors to broken files.
Environment variables¶
The content is treated as if it had been
passed via the --debug option.
MKVTOOLNIX_ENGAGE and its short form MTX_ENGAGE
The content is treated as if it had been
passed via the --engage option.
MKVTOOLNIX_OPTIONS and its short form MTX_OPTIONS
The content is split on white space. The
resulting partial strings are treated as if it had been passed as command line
options. If you need to pass special characters (e.g. spaces) then you have to
escape them (see the section about escaping special characters in text).
ДИВІТЬСЯ ТАКОЖ¶
WWW¶
Остання версія завжди може бути знайдена на веб-сторінці the MKVToolNix homepage[4].Author¶
Moritz Bunkus <moritz@bunkus.org>Розробник
ПРИМІТКИ¶
- 1.
- the Matroska(TM) website
- 2.
- the IANA homepage
- 3.
- the Matroska(TM) specification
- 4.
- the MKVToolNix homepage
2012-05-27 | MKVToolNix 5.6.0 |