Important: The order of command line options is important. Please read the section if you're new to the program. Option Description -v, -verbose Increase 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 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, VP9 video and Opus, Vorbis audio tracks.
Feb 15, 2018 - [quote=Guest][size=8]Track Concatenator / 2.4 Build 8 / David Schlachter /Audio / 1.2 MB / 14:30:24 / #Merge tracks #Concatenate. Track Concatenator is an application that helps you join together iTunes tracks. This program allows you to merge tracks from iTunes, chapterize them, and add them to your iTunes music library.
The DocType header item is changed to 'webm'. For chapters and tags only a subset of elements are allowed. Mkvmerge(1) will automatically remove all elements not allowed by the specification. 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 tracks for which no language is set with the option and for which the source container doesn't provide a language. The default language code is ' und' for 'undefined'. Option Description -segmentinfo filename.xml Read 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 below for details.segment-uid SID1,SID2. Sets the segment UIDs to use. This is a comma-separated list of 128-bit segment UIDs in the usual UID form: hex numbers with or without the '0x' prefix, with or without spaces, exactly 32 digits. If SID starts with = then its rest is interpreted as the name of a Matroska file whose segment UID is read and used. 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.
Option Description Sets the ISO639-2 language code that is written for each chapter entry. Defaults to ' eng'. See the section about 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.
The language set with this option is also used when chapters are generated with the. Sets the character set that is used for the conversion to UTF-8 for simple chapter files. See the section about 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.
Adjust the timestamps of the chapters in the following source file by d ms. Alternatively you can use the -sync option with the special track ID -2 (see section ).
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. Mkvmerge(1) can create chapters automatically. The following two modes are currently supported:. ' when-appending' – This mode creates one chapter at the start and one chapter whenever a file is appended. Note: mkvmerge(1) requires a video or an audio track to be present in order to be able to determine when a new file is appended. If one or more video tracks are muxed the first one is used. Otherwise the first audio track is used.
' interval: time-spec' – This mode creates one chapter at fixed intervals given by time-spec. The format is either the form HH:MM:SS.nnnnnnnnn or a number followed by one of the units ' s', ' ms' or ' us'. Example: -generate-chapters interval:45s The names for the new chapters are controlled by the option. The language is set with which must occur before -generate-chapters. This sets the name template for chapter names generated by the option.
If the option is not used then default ' Chapter ' will be used. There are several variables that can be used in the template that are replaced by their actual values when a chapter is generated. The string ' ' will be replaced by the chapter number. The string ' ' will be replaced by the chapter's start timestamp. The strings ' and ' are only filled when generating chapters for appended files.
They will be replaced by the appended file's name wihtout respectively with its extension. Note that only the file's base name and extension are inserted, not its directory or drive components. You can specify a minimum number of places for the chapter number with ' ', e.g. The resulting number will be padded with leading zeroes if the number of places is less than specified. You can control the format used by the start timestamp with. The format defaults to '%H:%M:%S' if none is given.
Valid format codes are:.%h – hours.%H – hours zero-padded to two places.%m – minutes.%M – minutes zero-padded to two places.%s – seconds.%S – seconds zero-padded to two places.%n – nanoseconds with nine places.%n – nanoseconds with up to nine places (e.g. Three places with%3n) -cue-chapter-name-format format mkvmerge(1) supports reading CUE sheets for audio files as the input for chapters. CUE sheets usually contain the entries PERFORMER and TITLE for each index entry. Mkvmerge(1) uses these two strings in order to construct the chapter name. With this option the format used for this name can be set. If this option is not given then mkvmerge(1) defaults to the format '%p -%t' (the performer, followed by a space, a dash, another space and the title). If the format is given then everything except the following meta characters is copied as-is, and the meta characters are replaced like this:.%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.
Note: Note that mkvmerge(1) only makes decisions about splitting at key frame positions. This applies to both the start and the end of each range. So even if an end timestamp is between two key frames mkvmerge(1) will continue outputting the frames up to but excluding the following key frame.
Keeping specific parts by specifying frame/field number ranges while discarding others. Syntax: -split parts-frames: start1- end1,+ start2- end2,+ start3- end3. Examples:.split parts-frames:137-258,548-1211.split parts-frames:733-912,+1592-2730.split parts-frames:-430,2512- The parts-frames mode tells mkvmerge(1) to keep certain ranges of frame/field numbers while discarding others. The ranges to keep have to be listed after the parts-frames: keyword and be separated by commas. A range itself consists of a start and an end frame/field number.
Numbering starts at 1. If a start number is left out then it defaults to the previous range's end number. If there was no previous range then it defaults to the start of the file (see example 3).
If an end number is left out then it defaults to the end of the source files which basically tells mkvmerge(1) 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 number with a +. This tells mkvmerge(1) not to create a new file and instead append the range to the same file the previous range was written to. Timestamps 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.
Note: Note that mkvmerge(1) only makes decisions about splitting at key frame positions. This applies to both the start and the end of each range. So even if an end frame/field number is between two key frames mkvmerge(1) will continue outputting the frames up to but excluding the following key frame. In example 1 mkvmerge(1) will create two files. The first will contain the content starting from the first key frame at or after 137 up to but excluding the first key frame at or after 258. The second file will contain the content starting from 548 until 1211.
In example 2 mkvmerge(1) will create only one file. This file will contain both the content starting from 733 until 912 and the content starting from 1592 until 2730. In example 3 mkvmerge(1) will create two files.
The first will contain the content from the start of the source files until 430. The second file will contain the content starting from 2512 until the end of the source files. This mode considers only the first video track that is output.
If no video track is output no splitting will occur. Note: The numbers given with this argument are interpreted based on the number of Matroska (tm) blocks that are output. A single Matroska (tm) block contains either a full frame (for progressive content) or a single field (for interlaced content). Mkvmerge does not distinguish between those two and simply counts the number of blocks.
For example: If one wanted to split after the 25th full frame with interlaced content one would have to use 50 (two fields per full frame) as the split point. Splitting after specific frames/fields. Syntax: -split frames: A, B, C. Example: -split frames:120,237,891 The parameters A, B, C etc must all be positive integers. Numbering starts at 1. The list of frame/field numbers is separated by commas.
After the input stream has reached the current split point's frame/field number a new file is created. Then the next split point given in this list is used. The ' frames:' prefix must not be omitted. This mode considers only the first video track that is output.
If no video track is output no splitting will occur. Note: The numbers given with this argument are interpreted based on the number of Matroska (tm) blocks that are output. A single Matroska (tm) block contains either a full frame (for progressive content) or a single field (for interlaced content). Mkvmerge does not distinguish between those two and simply counts the number of blocks. For example: If one wanted to split after the 25th full frame with interlaced content one would have to use 50 (two fields per full frame) as the split point. Splitting before specific chapters.
Syntax: -split chapters:all or -split chapters: A, B, C. Example: -split chapters:5,8 The parameters A, B, C etc must all be positive integers. Numbering starts at 1. The list of chapter numbers is separated by commas. Splitting will occur right before the first key frame whose timestamp is equal to or bigger than the start timestamp for the chapters whose numbers are listed. A chapter starting at 0s is never considered for splitting and discarded silently. The keyword all can be used instead of listing all chapter numbers manually.
The ' chapters:' prefix must not be omitted. Note: The Matroska (tm) file format supports arbitrary deeply nested chapter structures called 'edition entries' and 'chapter atoms'. However, this mode only considers the top-most level of chapters across all edition entries. 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. 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 files to one another when splitting the output file. See the section on 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 below for details. If SID starts with = then its rest is interpreted as the name of a Matroska file whose segment UID is read and used.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 below for details. If SID starts with = then its rest is interpreted as the name of a Matroska file whose segment UID is read and used.append-mode mode Determines how timestamps 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 ' track21' from now on) from a second file (called ' file2') to a track (called ' track11') from the first file (called ' file1') then it has to offset all timestamps for ' track21' by an amount. For ' file' mode this amount is the highest timestamp encountered in ' file1' even if that timestamp was from a different track than ' track11'.
In track mode the offset is the highest timestamp of ' track11'. 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 file1 file2 If multiple file names are contained in a pair of square brackets then the second and all following files will be appended to the first file named within the brackets. This is an alternative syntax to using '+' between the file names. 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. 'VTS011.VOB', 'VTS012.VOB', 'VTS013.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: $ 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.
Therefore these two command lines are equivalent: $ mkvmerge -o out.mkv = file.mkv $ mkvmerge -o out.mkv '(' file.mkv ')' Several things should be noted:. There must be spaces both after the opening and before the closing parenthesis. 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. Some shells treat parenthesis as special characters. Hence you must escape or quote them as shown in the example above. Option Description Plain text description of the following attachment.
Applies to the next or -attach-file-once option.attachment-mime-type MIME type MIME type of the following attachment. Applies to the next or option.
A list of officially recognized MIME types can be found e.g. The MIME type is mandatory for an attachment.attachment-name name 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 or the option. 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. Can be used to extract attached files from a Matroska (tm) file. Option Description -a, -audio-tracks !n,m. Copy the audio tracks n, m etc. The numbers are track IDs which can be obtained with the switch.
They're not simply the track numbers (see section ). Default: copy all audio tracks. Instead of track IDs you can also provide ISO 639-2 language codes. This will only work for source files that provide language tags for their tracks. Default: copy all tracks of this kind. If the IDs are prefixed with! Then the meaning is reversed: copy all tracks of this kind but the ones 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 switch. They're not simply the track numbers (see section ).
Default: copy all video tracks. Instead of track IDs you can also provide ISO 639-2 language codes.
This will only work for source files that provide language tags for their tracks. If the IDs are prefixed with!
Then the meaning is reversed: copy all tracks of this kind but the ones 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 switch.
They're not simply the track numbers (see section ). Default: copy all subtitle tracks.
Instead of track IDs you can also provide ISO 639-2 language codes. This will only work for source files that provide language tags for their tracks. If the IDs are prefixed with! Then the meaning is reversed: copy all tracks of this kind but the ones 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 switch.
They're not simply the track numbers (see section ). Default: copy all button tracks. Instead of track IDs you can also provide ISO 639-2 language codes. This will only work for source files that provide language tags for their tracks. If the IDs are prefixed with! Then the meaning is reversed: copy all tracks of this kind but the ones 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 switch (see section ). 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! 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. Don't copy chapters from this file. 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 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 timestamps of the track with the id TID by d ms. The track IDs are the same as the ones given with (see section ).
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. Controls for which tracks cue (index) entries are created for the given track (see section ). ' 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 and subtitle tracks and ' none' for audio tracks. See also option 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 ) 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 ) 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. Sets the track name for the given track (see section ) to name.
Sets the language for the given track (see section ). 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 option. This option can be used multiple times for an input file applying to several tracks by selecting different track IDs each time.
Read tags for the track with the number TID from the file file-name. See the section about 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.reduce-to-core TID Some audio codecs have a lossy core and optional extensions that implement lossless decoding. This option tells mkvmerge(1) to only copy the core but not the extensions. By default mkvmerge(1) copies both the core and the extensions. Currently only DTS tracks are affected by this option. TrueHD tracks that contain an embedded AC-3 core are instead presented as two separate tracks for which the user can select which track to copy. For DTS such a scheme would not work as the HD extensions cannot be decoded by themselves – unlike the TrueHD data.remove-dialog-normalization-gain TID Some audio codecs contain header fields that tell the decoder or player to apply a (usually negative) gain for dialog normalization.
This option tells mkvmerge(1) to remove or minimize that gain by modifying the corresponding header fields. Currently only AC-3, DTS and TrueHD tracks are affected by this option.timestamps TID:file-name Read the timestamps to be used for the specific track ID from file-name. These timestamps forcefully override the timestamps that mkvmerge(1) normally calculates. Read the section about. Forces the default duration of a given track to the specified value.
Also modifies the track's timestamps 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 timestamp file.
Normally mkvmerge(1) does not change the timing information (frame/field rate) stored in the video bitstream. With this option that information is adjusted to match the container timing information. The container timing information can come from various sources: from the command line (see option ), the source container or derived from the bitstream. Note: This has only been implemented for AVC/h.264 video tracks so far.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.
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' and ' mpeg4p2'/' mpeg4p2'. The compression method ' mpeg4p2'/' mpeg4p2' is a special compression method called ' header removal' that is only available for MPEG4 part 2 video tracks. The default for some subtitle types 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.
Option Description -f, -fourcc TID:FourCC Forces the FourCC to the specified value. Works only for video tracks in the ' MS compatibility mode'. Matroska (tm) files contain two values that set the display properties that a player should scale the image on playback to: display width and display height. These values can be set with this option, e.g.
' 1:640x480'. Another way to specify the values is to use the or the option (see below). These options are mutually exclusive. Matroska (tm) files contain two values that set the display properties that a player should scale the image on playback to: display width and display height. With this option mkvmerge(1) will automatically calculate the display width and display height based on the image's original width and height and the aspect ratio given with this option. The ratio can be given either as a floating point number ratio or as a fraction ' width/ height', e.g.
Another way to specify the values is to use the or options (see above and below). These options are mutually exclusive. 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 or 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.colour-matrix TID:n Sets the matrix coefficients of the video used to derive luma and chroma values from red, green and blue color primaries. The parameter n is an integer rangeing from 0 and 10. Valid values and their meaning are: 0: GBR, 1: BT709, 2: unspecified, 3: reserved, 4: FCC, 5: BT470BG, 6: SMPTE 170M, 7: SMPTE 240M, 8: YCOCG, 9: BT2020 non-constant luminance, 10: BT2020 constant luminance -colour-bits-per-channel TID:n Sets the number of coded bits for a colour channel.
A value of 0 indicates that the number of bits is unspecified.chroma-subsample TID:hori,vert The amount of pixels to remove in the Cr and Cb channels for every pixel not removed horizontally/vertically. Example: For video with 4:2:0 chroma subsampling, the parameter should be set to TID: 1, 1.cb-subsample TID:hori,vert The amount of pixels to remove in the Cb channel for every pixel not removed horizontally/vertically. This is additive with -chroma-subsample. Example: For video with 4:2:1 chroma subsampling, the parameter -chroma-subsample should be set to TID: 1, 0 and Cb-subsample should be set to TID: 1, 0.chroma-siting TID:hori,vert Sets how chroma is sited horizontally/vertically ( 0: unspecified, 1: top collocated, 2: half).colour-range TID:n Sets the clipping of the color ranges ( 0: unspecified, 1: broadcast range, 2: full range (no clipping), 3: defined by MatrixCoefficients/TransferCharacteristics).colour-transfer-characteristics TID:n The transfer characteristics of the video.
Valid values and their meaning are: 0: reserved, 1: ITU-R BT.709, 2: unspecified, 3: reserved, 4: gamma 2.2 curve, 5: gamma 2.8 curve, 6: SMPTE 170M, 7: SMPTE 240M, 8: linear, 9: log, 10: log sqrt, 11: IEC 61966-2-4, 12: ITU-R BT.1361 extended colour gamut, 13: IEC 61966-2-1, 14: ITU-R BT.2020 10 bit, 15: ITU-R BT.2020 12 bit, 16: SMPTE ST 2084, 17: SMPTE ST 428-1; 18: ARIB STD-B67 (HLG) -colour-primaries TID:n Sets the colour primaries of the video. Valid values and their meaning are: 0: reserved, 1: ITU-R BT.709, 2: unspecified, 3: reserved, 4: ITU-R BT.470M, 5: ITU-R BT.470BG, 6: SMPTE 170M, 7: SMPTE 240M, 8: FILM, 9: ITU-R BT.2020, 10: SMPTE ST 428-1, 22: JEDEC P22 phosphors -max-content-light TID:n Sets the maximum brightness of a single pixel (Maximum Content Light Level) in candelas per square meter (cd/m²).
The value of n should be a non-negtive integer.max-frame-light TID:n Sets the maximum brightness of a single full frame (Maximum Frame-Average Light Level) in candelas per square meter (cd/m²). The value of n should be a non-negtive integer.chromaticity-coordinates TID:red-x,red-y,green-x,green-y,blue-x,blue-y Sets the red/green/blue chromaticity coordinates as defined by CIE 1931.white-colour-coordinates TID:x,y Sets the white colour chromaticity coordinates as defined by CIE 1931.max-luminance TID:float Sets the maximum luminance in candelas per square meter (cd/m²). The value should be less than 9999.99.min-luminance TID:float Sets the minimum luminance in candelas per square meter (cd/m²). The value should be less than 999.9999.projection-type TID:method Sets the video projection method used. Valid values are 0 (rectangular projection), 1 (equirectangular projection), 2 (cubemap projection) and 3 (mesh projection).projection-private TID:data Sets private data that only applies to a specific projection.
Data must be given as hex numbers with or without the '0x' prefix, with or without spaces.projection-pose-yaw TID:float Specifies a yaw rotation to the projection.projection-pose-pitch TID:float Specifies a pitch rotation to the projection.projection-pose-roll TID:float Specifies a roll rotation to the projection. Sets the field order for the video track with the track ID TID. The order must be one of the following numbers: 0: progressive; 1: interlaced with top field displayed first and top field stored first; 2: undetermined field order; 6: interlaced with bottom field displayed first and bottom field stored first; 9: interlaced with bottom field displayed first and top field stored first; 14: interlaced with top field displayed first and bottom field stored first -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', ' sidebysideleftfirst', ' topbottomrightfirst', ' topbottomleftfirst', ' checkerboardrightfirst', ' checkerboardleftfirst', ' rowinterleavedrightfirst', ' rowinterleavedleftfirst', ' columninterleavedrightfirst', ' columninterleavedleftfirst', ' anaglyphcyanred', ' sidebysiderightfirst', ' anaglyphgreenmagenta', ' botheyeslacedleftfirst', ' botheyeslacedrightfirst'.
Option Description Sets 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 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. Option Description 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. The output format used for the result can be changed with the option. This is a convenient alias for ' -identification-format json -identify file-name'. Determines the output format used by the. The following formats are supported: text (the default if this option isn't used) and json. The text format is short and human-readable.
It consists of one line per item found (container, tracks, attachments etc.). This format is not meant to be parsed. The output will be translated into the language mkvmerge(1) uses (see also ). The json format outputs a machine-readable JSON representation. This format follows the JSON schema described in the following file: All versions of the JSON schema are available both online and in the released source code archives. File types such as MPEG program and transport streams (.vob,.m2ts) require parsing a certain amount of data in order to detect all tracks contained in the file. This amount is 0.3% of the source file's size or 10 MB, whichever is higher.
If tracks are known to be present but not found then the percentage to probe can be changed with this option. The minimum of 10 MB is built-in and cannot be changed.l, -list-types Lists supported input file types. Lists all languages and their ISO639-2 code which can be used with the 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 function. Therefore only the super user can use ' higher' and ' highest'. On Windows all values are useable for every user. Selecting ' lowest' also causes mkvmerge(1) to select idle I/O priority in addition to the lowest possible process priority. 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:,. Sets 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. 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 is honored. Forces the translations for the language code to be used (e.g. ' deDE' for the German translations). Entering ' list' as the code will cause the program to output a list of available translations.
Turn on debugging for a specific feature. This option is only useful for developers. 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. Turns on GUI mode. In this mode specially-formatted lines may be output that can tell a controlling GUI what's happening.
These messages follow the format ' #GUI#message'. The message may be followed by key/value pairs as in ' #GUI#message#key1=value1#key2=value2'. Neither the messages nor the keys are ever translated and always output in English.
@ options-file.json Reads additional command line arguments from the file options-file. See the section about 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:. ' FLAC' - reading raw FLAC files and handling FLAC tracks in other containers, e.g.
Track Concatenator 2.4 Free Download For Mac Free
Ogg (tm) or Matroska (tm).h, -help Show usage information and exit.V, -version Show version information and exit. 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.