I’ve released mkvtoolnix v7.1.0. It fixes a few minor issues. Probably the most important fix is that the new statistics tags introduced with v7.0.0 aren’t written to WebM files anymore as the WebM specs currently don’t allow tags.
For packagers: nothing has changed since v7.0.0.
Here’s the full ChangeLog since release 7.0.0:
- 2014-07-27 Moritz Bunkus <firstname.lastname@example.org>
- Released v7.1.0.
- all: bug fix: Fixed file seeking code for »seek relative to end of file« case. Fixes #1035.
- mmg: bug fix: Selecting the root of the chapter editor tree will disable the language/country inputs properly as changing those fields doesn’t make sense for the root.
- 2014-07-26 Moritz Bunkus <email@example.com>
- all: bug fix: if MKVToolNix on Windows is residing in a directory containing non-ASCII characters then translations weren’t found. This has only been fixed for cases where those non-ASCII characters are part of the system’s active code page.
- 2014-07-10 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge: bug fix: track statistics tags are not written for WebM files anymore as the WebM specification doesn’t allow tags.
- 2014-07-01 Moritz Bunkus <email@example.com>
- 2014-06-18 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge: enhancement: SSA/ASS: in addition to semicolons comments can now start with exclamation marks, too.
- 2014-06-11 Moritz Bunkus <email@example.com>
- mkvextract: bug fix: Fixed a crash when opening damaged/invalid Matroska files in all extraction modes. Fixes #1027.
I’ve released mkvtoolnix v7.0.0. It’s a release that includes a couple of minor enhancements to mmg and mkvmerge and the usual bug fixes (nothing major – though some more cases of overly long file detection times have been fixed).
The most prominent change is that mkvmkerge will now write certain track-specific statistics (such as bit rate) as tags. See the ChangeLog for more details. Accompanying this change is that mkvmerge’s verbose identification mode will now include the track’s tags as well in order to make retrieving that information easier for other programs.
For packagers: this build requires Boost’s Date/Time library.
Here’s the full ChangeLog since release 6.9.1:
- 2014-06-09 Moritz Bunkus <firstname.lastname@example.org>
- Released v7.0.0.
- 2014-05-26 Moritz Bunkus <email@example.com>
- mkvmerge: enhancement: In addition to the track statistics tags»BPS«, »DURATION«, »NUMBER_OF_BYTES« and »NUMBER_OF_FRAMES«mkvmerge will write two more tags identifying which application wrote the statistics (»_STATISTICS_WRITING_APP«) and when the file in question was written: »_STATISTICS_WRITING_DATE_UTC«.»_STATISTICS_WRITING_APP« will always contain the same string contained in the segment info header element »WritingApp«.»_STATISTICS_WRITING_DATE_UTC« will contain the same timestamp as in the segment info header element »Date«, though»_STATISTICS_WRITING_DATE_UTC« is actually a string representation instead of an integer value. Additionally a tag named »_STATISTICS_TAGS« is written containing the names of the tags that mkvmerge has set automatically. It equals the following currently: »BPS DURATION NUMBER_OF_BYTES NUMBER_OF_FRAMES«.
- build system: Boost’s "date/time" library is now required.
- 2014-05-25 John Peebles <firstname.lastname@example.org>
- mkvmerge: bug fix: If a single subtitle track contains two or more entries at the same timecode then the cue duration and cue relative position elements written were wrong.
- 2014-05-24 Moritz Bunkus <email@example.com>
- mkvinfo: bug fix: fixed wrong progress percentage shown during saving the information to text files. Fixes #1016.
- mkvmerge: new feature: Added a global option for disabling writing the tags with statistics for each track: –disable-track-specific-tags.
- 2014-05-20 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge: new feature: When identifying a Matroska file in verbose identification mode track-specific tags will be output as well. The format is »tag_<tag name in lower case>:<tag value>», e.g. for a tag named »BPS« with the value »224000« the output would be »tag_bps:224000«. Enhancement for #1021.
- mkvmerge: new feature: mkvmerge will write track-specific tags with statistics (»BPS« for the average number of bits per second,»DURATION« for the duration, »NUMBER_OF_BYTES« and»NUMBER_OF_FRAMES« for the track’s size in bytes and its number of frames/packets). Implements #1021.
- 2014-05-18 Moritz Bunkus <email@example.com>
- mkvmerge: bug fix: Changed the file type detection order again. The text subtitle formats are now probed after those binary formats that can be detected quickly and unambiguously. This avoids some mis-detection if e.g. Matroska files as ASS text subtitles if they do contain such a track.
- mmg: enhancement: The chapter editor will only use fast-mode parsing when loading chapters from Matroska files.
- 2014-05-14 Moritz Bunkus <firstname.lastname@example.org>
- all: bug fix: fixed invalid memory access in the cleanup procedures which only occurred if the output was redirected with the »–redirect-output« command line parameter.
- 2014-05-04 Moritz Bunkus <email@example.com>
- mkvmerge: enhancement: The last chapter entry read from MPLS files is removed if it is at most five seconds long. Patch by Andrew Dvorak (see AUTHORS).
- mkvmerge: enhancement: added the attachment UID to the verbose identification output of Matroska files.
- 2014-04-21 Moritz Bunkus <firstname.lastname@example.org>
- mmg: bug fix: Selecting a subtitle track correctly sets the»character set« drop-down box if no character set was set for this track. Fixes #1008.
- mmg: enhancement: the subtitle character set cannot be set anymore for subtitle tracks read from Matroska files as mkvmerge ignores that setting for said container anyway (text subs are always encoded in UTF-8 in Matroska).
- 2014-04-20 Moritz Bunkus <email@example.com>
- mmg: enhancement: mmg will look for the »mkvmerge« executable in the same directory as the »mmg« executable is located it if the location hasn’t been set by the user on all operating systems (before: only on Windows). Improves detection if »mkvmerge« is not in the $PATH.
I’ve released MKVToolNix 6.9.1 mere hours after the release of 6.9.0 due to a severe bug that wasn’t present in 6.8.0. Here’s the combined announcement for both releases.
There were the usual bug fixes all over the place. No major new features, but it was time for a new release.
Here’s the full ChangeLog since release 6.8.0:
- 2014-04-18 Moritz Bunkus <firstname.lastname@example.org>
- Released v6.9.1.
- mkvmerge: bug fix: fixed huge memory usage when probing files (it was reading the whole file into memory for that).
- Released v6.9.0.
- all: new feature: added a Brazilian Portuguese translation of the programs by Thiago Kühn (see AUTHORS).
- mkvpropedit, mmg’s header editor: bug fix: fixed a failed assertion in libEBML when writing the same changes twice to certain files (those for which a seek head with a single entry pointing to the elements modified by mkvpropedit/mmg’s header editor; e.g. x264 creates such files). Fixes #1007.
- 2014-03-22 Moritz Bunkus <email@example.com>
- mkvmerge: bug fix: reading fonts embedded in SSA/ASS files was sometimes truncating the attachments created from them. Fixes #1003.
- mkvmerge: bug fix: fixed display of very large IDs during attachment extraction.
- mkvmerge: enhancement: improved file type detection speed for text subtitle formats.
- 2014-03-10 Moritz Bunkus <firstname.lastname@example.org>
- mkvextract: bug fix: during the extraction of chapters, tags or segment info XML files with the –redirect-output parameter the BOM (byte order mark) was written twice.
- 2014-03-05 Moritz Bunkus <email@example.com>
- 2014-03-04 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge: bug fix: fixed timestamp assignment for AVC/h.264 videos in which recovery point SEIs occur in front of the second field of two interlaced fields.
I’ve released MKVToolNix 6.8.0. There were tons of bug fixes for the Windows builds, especially for the 64bit builds.
The one new feature that is present is support for h.265/HEVC video: but only for reading it from elementary streams or from other Matroska files. My initial plan was to have reading it from MPEG transport streams work as well, but alas, free time is in short supply, and this release is a week overdue already.
The HEVC support has been implemented by Rovi Corp (DivX). I’ve merged their changes, updated them to the current code base and cleaned them up somewhat. Their work is much appreciated.
For package maintainers nothing has changed compared to 6.7.0.
Here’s the full ChangeLog since release 6.7.0:
- 2014-03-02 Moritz Bunkus <email@example.com>
- Released v6.8.0.
- 2014-02-28 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge, mkvextract: new feature: added support for h.265/HEVC by merging the patches from DivX/Rovi Corp. So far HEVC is only supported as elementary streams and read from other Matroska files.
- 2014-02-22 Moritz Bunkus <email@example.com>
- mkvmerge: enhancement: The deprecated ISO 639-1 code "iw" is now recognized for Hebrew.
- 2014-02-15 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge: bug fix: The AC3 packetizer will re-derive the sampling frequency and the number of channels from the bitstream. This way obviously invalid information from the source container like a sampling frequency of 0 Hz will be fixed.
- 2014-02-05 Moritz Bunkus <email@example.com>
- mkvmerge: enhancements: AVI reader: audio chunks with obvious wrong size information (bigger than 10 MB) will be skipped.
- 2014-02-03 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge: bug fix: When reading M2TS files belonging to an MPLS playlist mkvmerge will now only copy packets whose timestamps lie between the »in time« and »out time« restrictions from the playlist’s entry corresponding to that M2TS file. Fixes #985.
- 2014-01-22 Moritz Bunkus <email@example.com>
- all: Windows 64bit: fixed return value checks for opening files. Fixes #972.
- 2014-01-21 Moritz Bunkus <firstname.lastname@example.org>
- all: Windows: when redirecting the program’s output with cmd.exe (e.g. »mkvinfo file.mkv > info.txt«) the programs will no longer write two line feed characters (\r) per carriage return character (\n). Fixes #970.
- all: Windows: the default charset for the files created with»–redirect-output« has been changed from the system’s local charset to UTF-8. Just like before it can be changed with»–output-charset«. See #970.
- all: bug fix: Windows: messages written to the console (cmd.exe) are not re-encoded to the local charset and back to UTF-16 before they’re handed over to ConsoleWriteW(). This fixes outputting Unicode characters to the console that are not part of the local charset. Fixes #971.
- 2014-01-18 Moritz Bunkus <email@example.com>
- extract: bug fix: using names of non-existing files in»attachments«, »chapters«, »cuesheet« or »tags« mode caused mkvextract to crash instead of emitting a proper error message. Fixes #964.
- 2014-01-17 Moritz Bunkus <firstname.lastname@example.org>
- mmg: bug fix: fixed the check for WebM-compatible track types for Opus.
- 2014-01-12 Moritz Bunkus <email@example.com>
- mkvmerge: bug fix: fixed muxing Sorenson v3 (SVQ3) video from QuickTime files.
- 2014-01-11 Moritz Bunkus <firstname.lastname@example.org>
- mkvmerge, mkvextract, mkvpropedit: enhancement: attachments in Matroska files with a missing FileUID element are not ignored anymore even though they violate the specs. mkvmerge generates a new FileUID instead.
- 2014-01-10 Moritz Bunkus <email@example.com>
- mkvmerge: re-built with the 64bit build for Windows with a newer compiler version in order to fix #957. It was due to a bug in gcc: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56742
- mmg: bug fix: mkvmerge’s file identification is written to a temporary file with –redirect-output and from there into mmg instead of directly from mkvmerge. This prevents from character re-coding done by wxWidgets 3.0.0 on Windows. Fixes #959.
- 2014-01-09 Moritz Bunkus <firstname.lastname@example.org>
- installer: enhancement: the architecture (32bit vs 64bit) is mentioned in the interface.
- installer: bug fix: the installation directory for 64bit builds will default to the proper directory (»C:\Program Files« instead of »C:\Program Files (x86)«). Fixes #956.