edit-headersĪll following file names will be opened in the header editor.Īdditionally the header editor will be selected on startup instead of the multiplexer tool.
edit-chaptersĪll following file names will be opened in the chapter editor.Īdditionally the chapter editor will be selected on startup instead of the multiplexer tool. infoĪll following file names will be opened in the info tool.Īdditionally the info tool will be selected on startup instead of the multiplexer tool. mergeĪll following file names will be added as source files to the current multiplex job.
Note that if an instance of the application is already running when the application is started a second time, all file names given on the command line are handled by the already-running instance. The default mode is adding files for multiplexing. The current mode can be changed with -merge, -info, -edit-chapters or -edit-headers. Any other file name is added as a source file for multiplexing, opened in the info tool, the chapter editor or in the header editor depending on the current mode. mtxcfg causes the GUI to load the those configuration files in the appropriate tool. Listing configuration file names with the extension. source files, track options etc) can be saved and restored.
It also implements mkvinfo(1)'s and mkvpropedit(1)'s functionality and will evolve to cover mkvextract(1) as well. Mkvtoolnix-gui(1) is a Qt(TM) based GUI for mkvmerge(1). Mkvtoolnix-gui | | ] | ] | ]] Description If you would like to see a donation link for the application here, please include one in the AppStream data.A GUI for mkvmerge(1) including a chapter and a header editor Synopsis Please open a pull request on if you have changed it and would like to see this page updated accordingly. Thanks for shipping AppStream metainfo inside your AppImage. Pro Tips for further enhancing the MKVToolNix AppImage Great! Here are some ideas on how to make it even better. Thanks for distributing MKVToolNix in the AppImage format for all common Linux distributions. If you would like to have the executable bit set automatically, and would like to see MKVToolNix and other AppImages integrated into the system (menus, icons, file type associations, etc.), then you may want to check the optional appimaged daemon. Using this tool, MKVToolNix can be updated by downloading only the portions of the AppImage that have actually changed since the last version. The MKVToolNix AppImage also can be updated using AppImageUpdate. If you would like to update to a new version, simply download the new MKVToolNix AppImage. This is entirely optional and currently needs to be configured by the user. If you want to restrict what MKVToolNix can do on your system, you can run the AppImage in a sandbox like Firejail. Then double-click the AppImage in the file manager to open it. Use at your own risk!ĭownload the MKVToolNix AppImage and make it executable using your file manager or by entering the following commands in a terminal: Follow these instructions only if you trust the developer of the software. This is a Linux security feature.īehold! AppImages are usually not verified by others. However, they need to be marked as executable before they can be run. Unlike other applications, AppImages do not need to be installed before they can be used. Running MKVToolNix on Linux without installation Most AppImages run on recent versions of Arch Linux, CentOS, Debian, Fedora, openSUSE, Red Hat, Ubuntu, and other common desktop distributions. No system libraries or system preferences are altered. Download an application, make it executable, and run! No need to install. Awesome!ĪppImages are single-file applications that run on most Linux distributions. MKVToolNix is available as an AppImage which means "one app = one file", which you can download and run on your Linux system while you don't need a package manager and nothing gets changed in your system. MKVToolNix Website MKVToolNix Bugtracker MKVToolNix FAQ MKVToolNix Help Help translating MKVToolNix MKVToolNix is a set of tools to create, alter and inspect Matroska files
0 kommentar(er)
