(Note: simply copied from www.matroska.org.)
Matroska aims to become THE Standard of Multimedia Container Formats. It was derived from a project called MCF, but differentiates from it significantly because it is based on EBML (Extensible Binary Meta Language), a binary derivative of XML. EBML enables the Matroska Development Team to gain significant advantages in terms of future format extensibility, without breaking file support in old parsers.
If you need any more info please head over to Matroska's homepage.
mkvmerge and mkvmerge GUI (or just mmg) are two programs created by Moritz Bunkus. They're part of the mkvtoolnix package. mkvmerge can read a lot of different multimedia files and put their contents into Matroska files. Unfortunately this is a command line program, and not everyone is comfortable working on the command line. This is where mkvmerge GUI comes into play. It is a GUI that provides the user with an intuitive but powerful interface to mkvmerge.
Both programs are available for both Windows and GNU/Linux and other Unix derivatives. The program is licensed under the GPL, so the source code is available to anyone interested.
You can always find the latest version of mkvtoolnix on Moritz Bunkus' website. Windows users will have to download the runtime DLLs as well as the mkvtoolnix binaries. Linux/Unix users will probably download the sources and compile mkvtoolnix themselves.
This guide only focusses on the GUI part of these tools. All command line options are explained in detail in mkvmerge's man page/HTML page.
(Note: This section does not cover compilation and
installation. mkvmerge's own documentation and the
README
files that are included in the mkvtoolnix
package.)
The only thing that mmg needs to know is the location of the mkvmerge binary. Under normal circumstances it will be found automatically. But if not then you can select the binary to use on the Settings tab. |
Use this button to select the path to the mkvmerge program. |
mkvmerge strictly differentiates between files and tracks. An input file usually contains one or more tracks. mkvmerge needs at least one input file and the file name of the Matroska file it should create before it can do any work. Starting with this minimal set of options the user can add more input files, select advanced options for each track, apply some more global options etc.
The typical basic steps are:
When mmg starts up it shows the first and probably most important tab: the input tab. Here you see four different elements. The topmost input box lists all input files. Directly under this box are options that apply to the currently selected input file. The two buttons to the right of the upper list box can be used to add files to the list box with the + button and to remove the selected entry with the - button. |
Use these buttons to add and remove files. |
|
Once the user selects an input file in the upper list box the second list box will contains all tracks that can be read from this file. Each track is ENabled by default and will be muxed into the resulting file. However, you can change that by simply clicking on the check box right in front of the track's name in the second list box. For each of these tracks the user can select track specific options with the input boxes and check boxes below the track listing. These options will be described in the following sections. |
Three enabled tracks and one disabled track. The fourth track will not be copied into the output file. |
Once the user has added and selected an input file he can set
options that apply to this specific file. At the moment only two such
options have been implemented: No chapters
and No
attachments
. These options tell mkvmerge not to copy any
chapters / attachments from the current source file.
More information about chapters can be found in the section about the chapter editor in this document and in mkvmerge's own documentation.
Depending on the type of the currently selected track (audio, video, subtitles) and even depending on the contents of the track only a subset of all the track specific options are available. The options are:
|
|
Matroska files can also contain other files, called attachments. This works basically just like with your favourite email program. The idea is to provide additional information about the file. Some examples could be cover photos for a CD rip, additional background information in text form about the movie or even some compressed fonts for the subtitles. Every attachment needs two things: the file name (obviously) and the MIME type that should be associated with the file. The usage is very easy and similar to adding files on the input tab. On the second tab of the GUI, the attachment tab, you can add a file with the + button and remove the selected attachment with the - button. Once an attachment has been selected the other controls on this tab will be available. You do have to select a MIME type for each attachment, but the description is optional - although it is a good idea to always provide a description. This makes it easier for others to identify what you've attached to this Matroska file. The last option, |
|
The third tab, Global, is packed full of options that apply to the complete file and not just to one or more tracks.
File/segment title
|
|
|
Automatic splitting and file linkingThe
Matroska supports file linking which simply says that a specific file is the predecessor or successor of the current file. To be precise, it's not really the files that are linked but the Matroska segments. As most files will probably only contain one Matroska segment I simply say 'file linking' although 'segment linking' would be more appropriate. Each segment is identified by a unique 128 bit wide segment UID. This UID is automatically generated by mkvmerge. The linking is done primarily via putting the segment UIDs of the previous/next file into the segment header information. mkvinfo prints these UIDs if it finds them. If a file is split into several smaller ones and linking is
used then the time codes will not start at 0 again but will
continue where the last file has left off. This way the
absolute time is kept even if the previous files are not
available (e.g. when streaming). If no linking is used then
the time codes should start at 0 for each file. By default
mkvmerge uses file linking. If you don't want that you
can turn it off by enabling this Manual file/segment linkingRegardless of whether splitting is active or not the user can tell
mkvmerge to link the produced files to specific
UIDs. This is done by entering a valid segment UID into the
two input boxes, If splitting is used then the first file is linked to the UID
given in the |
|