mkvextract — extract tracks from Matroska™ files into other files
This program extracts specific parts from a Matroska™ file to other useful formats. The first argument, mode, tells
mkvextract(1) what to extract. Currently supported is the extraction of tracks, tags, attachments, chapters, CUE sheets and timecodes. The second argument is the name of the source file. It must be a
Matroska™ file. All following arguments are options and extraction specifications; both of which depend on the selected mode.
The following options are available in all modes and only described once in this section.
--command-line-charset character-setSets the character set to convert strings given on the command line from. It defaults to the character set given by system's current locale.
--output-charset character-setSets the character set to which strings are converted that are to be output. It defaults to the character set given by system's current locale.
-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 mkvextract(1) to
output a list of available translations.
-v, --verboseBe verbose and show all the important Matroska™ elements as they're read.
-h, --helpShow usage information and exit.
-V, --versionShow version information and exit.
@options-file
Reads additional command line arguments from the file options-file. 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. There is no meta character escaping.
The command line 'mkvextract tracks source.mkv --raw 1:destination.raw' could be converted into the following option file:
# Extract a track from source.mkv
tracks
source.mkv
# Output the track as raw data.
--raw
1:destination.raw
Syntax: mkvextract tracks source-filename [options] TID1:dest-filename1 [TID2:dest-filename2 ...]
The following command line options are available for each track in the 'tracks' extraction mode. They have to appear
in front of the track specification (see below) they should be applied to.
-c character-setSets the character set to convert the next text subtitle track to. Only valid if the next track ID targets a text subtitle track. It defaults to UTF-8.
--blockadd levelKeep only the BlockAdditions up to this level. The default is to keep all levels. This option only affects certain kinds of codecs like WAVPACK4.
--cuesheet
Causes mkvextract(1) to extract a CUE sheet from the chapter information and tag data for the following track into a
file whose name is the track's output name with '.cue' appended to it.
--raw
Extracts the raw data into a file without any container data around it. Unlike the --fullraw flag this flag does not cause the contents of the
CodecPrivate element to be written to the file. This mode works with all CodecIDs, even
the ones that mkvextract(1) doesn't support otherwise, but the resulting files might not be usable.
--fullraw
Extracts the raw data into a file without any container data around it. The contents of the CodecPrivate
element will be written to the file first if the track contains such a header element. This mode works with all
CodecIDs, even the ones that mkvextract(1) doesn't support otherwise, but the resulting files might not be
usable.
--no-oggOnly valid for FLAC tracks. Normally FLAC tracks are embedded in an Ogg transport stream. With this switch they are extracted to raw FLAC files instead.
TID:outname
Causes extraction of the track with the ID TID into the file
outname if such a track exists in the source file. This option can be
given multiple times. The track IDs are the same as the ones output by
mkvmerge(1)'s --identify option.
Each output name should be used only once. The exception are RealAudio and RealVideo tracks. If you use the same name for different tracks then those tracks will be saved in the same file. Example:
$ mkvextract tracks input.mkv 1:output-two-tracks.rm 2:output-two-tracks.rm
Syntax: mkvextract tags source-filename [options]
The extracted tags are written to the console unless the output is redirected (see the section about output redirection for details).
Syntax: mkvextract attachments source-filename [options] AID1:outname1 [AID2:outname2 ...]
Causes extraction of the attachment with the ID AID into the file outname if such an
attachment exists in the source file. If the outname is left empty then the name of the attachment inside the
source Matroska™ file is used instead. This option can be given multiple times. The attachment IDs are the same as the ones output
by mkvmerge(1)'s --identify option.
Syntax: mkvextract chapters source-filename [options]
-s, --simpleExports the chapter information in the simple format used in the OGM tools (CHAPTER01=..., CHAPTER01NAME=...). In this mode some information has to be discarded. Default is to output the chapters in XML format.
The extracted chapters are written to the console unless the output is redirected (see the section about output redirection for details).
Syntax: mkvextract cuesheet source-filename [options]
The extracted cue sheet is written to the console unless the output is redirected (see the section about output redirection for details).
Syntax: mkvextract timecodes_v2 source-filename [options]
The extracted timecodes are written to the console unless the output is redirected (see the section about output redirection for details).
Several extraction modes cause mkvextract(1) to write the extracted data to the console. There are generally two ways of writing this data into a file: one provided by the shell and one provided by mkvextract(1) itself.
The shell's builtin redirection mechanism is used by appending '> output-filename.ext' to the command
line. Example:
$ mkvextract tags source.mkv > tags.xml
mkvextract(1)'s own redirection is invoked with the --redirect-output option. Example:
$ mkvextract tags source.mkv --redirect-output tags.xml
On Windows you should probably use the --redirect-output option because
cmd.exe sometimes interpretes special characters before they're written into the output file resulting in broken
output.
The decision about the output format is based on the track type, not on the extension used for the output file name. The following track types are supported at the moment:
H.264 / AVC video tracks are written to H.264 elementary streams which can be processed further with e.g. MP4Box™ from the GPAC™ package.
Fixed FPS video tracks with this CodecID are written to AVI files.
RealVideo™ tracks are written to RealMedia™ files.
These will be extracted to raw MP3 and AC3 files.
Raw PCM data will be written to a WAV file.
All AAC files will be written into an AAC file with ADTS headers before each packet. The ADTS headers will not contain the deprecated emphasis field.
Vorbis audio will be written into an OggVorbis™ file.
RealAudio™ tracks are written to RealMedia™ files.
TrueAudio™ tracks are written to TTA files. Please note that due to Matroska™'s limited
timecode precision the extracted file's header will be different regarding two fields: data_length (the total
number of samples in the file) and the CRC.
Simple text subtitles will be written as SRT files.
SSA and ASS text subtitles will be written as SSA/ASS files respectively.
Kate™ streams will be written within an Ogg™ container.
Tags are converted to a XML format. This format is the same that mkvmerge(1) supports for reading tags.
Attachments are written to they output file as they are. No conversion whatsoever is done.
Chapters are converted to a XML format. This format is the same that mkvmerge(1) supports for reading chapters. Alternatively a stripped-down version can be output in the simple OGM style format.
Timecodes are first sorted and then output as a timecode v2 format compliant file ready to be fed to mkvmerge(1). The extraction to other formats (v1, v3 and v4) is not supported.
mkvextract(1) exits with one of three exit codes:
0 -- This exit codes means that extraction has completed successfully.
1 -- In this case mkvextract(1) has output at least one warning, but extraction did continue. A warning is
prefixed with the text 'Warning:'. Depending on the issues involved the resulting files might be ok or not. The
user is urged to check both the warning and the resulting files.
2 -- This exit code is used after an error occured. mkvextract(1) aborts right after outputting the error message.
Error messages range from wrong command line arguments over read/write errors to broken files.