MKVToolNix v30.1.0 released

Hey,

due to an unfortunate bug in v30.0.0 that caused the GUI’s chapter editor to truncate Matroska/WebM files to a few KB, I have to release v30.1.0 today. This release also implements a workaround for dragging & dropping not working on macOS with Qt 5.12 (due to a bug in Qt).

Nothing has changed for package managers since v29.0.0.

You can download the source code or one of the binaries. The Windows and macOS binaries as well as the Linux AppImage are available already. The other Linux binaries are stil being built and will be available over the course of the next couple of hours.

Here are the NEWS since the previous release:

Bug fixes

  • build system: fixed building on non-UTF-8 locales. Fixes #2474.
  • MKVToolNix GUI: multiplexer: implemented a workaround for drag & drop not working on macOS with Qt 5.12 due to a bug in Qt 5.12. Fixes #2472.
  • MKVToolNix GUI: chapter editor: when opening a Matroska/WebM file that doesn’t contain chapters and later saving chapters back to them, the editor was truncating the file down to a couple of KB in size. This was a regression introduced with the implementation of #2439 in v30.0.0 Fixes #2476.

Have fun :)

4 thoughts on “MKVToolNix v30.1.0 released

  1. José

    Can you add a feature to shut down the computer once the multiplexing Job is done.

    Thanks for the great software!!!!!

    Reply
    1. mosu Post author

      That feature is already present in MKVToolNix GUI (look at the “job output” tool; there’s a button called “When finished…”).

      Reply
  2. dREV

    My apologies for the long post I have a question regarding appending HEVC. I use this version https://forum.doom9.org/showthread.php?p=1860073#post1860073 of the encoder via MeGUI ver 2525 and I cut frames to deal with potential problematic issues on said scene then once ready I append but I keep seeing this thing coming .

    Warning: The track number 0 from the file ‘C:\Users\Public\# 0 Encode\test 78\# Episode 03 DONE\4126, 9132)\02 pre-ready encode (4126, 9132) 1.4.mkv’ can probably not be appended correctly to the track number 0 from the file ‘C:\Users\Public\# 0 Encode\test 78\# Episode 03 DONE\0, 4125)\01 pre-ready encode (0, 4125) 1.4.mkv’: The codec’s private data does not match (lengths: 2199 and 2199). Please make sure that the resulting file plays correctly the whole time. The author of this program will probably not give support for playback issues with the resulting file.
    Warning: The track number 0 from the file ‘C:\Users\Public\# 0 Encode\test 78\# Episode 03 DONE\9133, 9275) #Intro\03 pre-ready encode (9133, 9275) #Intro 1.4.mkv’ can probably not be appended correctly to the track number 0 from the file ‘C:\Users\Public\# 0 Encode\test 78\# Episode 03 DONE\4126, 9132)\02 pre-ready encode (4126, 9132) 1.4.mkv’: The codec’s private data does not match (lengths: 2198 and 2199). Please make sure that the resulting file plays correctly the whole time. The author of this program will probably not give support for playback issues with the resulting file.

    etc. till the end of the frame. Is this due to an issue with mkvmerge or the encoder or both? The settings uses the same setting but this is the first cut.

    Writing library : x265 2.9+15-81373aab81df:[Windows][GCC 8.2.1][64 bit] 12bit
    Encoding settings : cpuid=1111039 / frame-threads=3 / numa-pools=12 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=3 / input-res=960×720 / interlace=0 / total-frames=4126 / level-idc=41 / high-tier=1 / uhd-bd=0 / ref=6 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=23 / keyint=250 / gop-lookahead=0 / bframes=16 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=80 / lookahead-slices=0 / scenecut=40 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / no-rect / no-amp / max-tu-size=32 / tu-inter-depth=4 / tu-intra-depth=4 / limit-tu=0 / rdoq-level=1 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / no-strong-intra-smoothing / max-merge=5 / limit-refs=1 / limit-modes / me=4 / subme=7 / merange=57 / temporal-mvp / weightp / weightb / no-analyze-src-pics / deblock=-1:-1 / no-sao / no-sao-non-deblock / rd=6 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=0.95 / psy-rdoq=5.00 / no-rd-refine / no-lossless / cbqpoffs=6 / crqpoffs=6 / rc=crf / crf=16.0 / qcomp=0.75 / qpstep=4 / stats-write=0 / stats-read=0 / vbv-maxrate=50000 / vbv-bufsize=50000 / vbv-init=0.9 / crf-max=0.0 / crf-min=0.0 / ipratio=1.40 / pbratio=1.30 / aq-mode=3 / aq-strength=0.80 / cutree / zone-count=0 / no-strict-cbr / qg-size=64 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=1 / transfer=1 / colormatrix=1 / chromaloc=0 / display-window=0 / max-cll=0,0 / min-luma=0 / max-luma=4095 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / no-opt-cu-delta-qp / no-aq-motion / no-hdr / no-hdr-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=5 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-mv-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei

    My guess is the mkvmerge reads the portion “total-frames=4126” (tho the frame really only has 4125 frames) and so on with the other files and starts telling me the above. When the part in mediainfo it adjusts this part Bits/(Pixel*Frame) but doesn’t do the same with total frame.

    In the H265 documentation not sure if it’s the correct official one https://x265.readthedocs.io/en/default/cli.html under “–total-frames” it mentions I cannot do anything to this and this is so as the encoer using MeGUI refuses to work.

    Should I be concerned about this? Was this already mentioned before and where can I read it so I can understand. If there’s any work around I would like to know as I do not know if there may be video players that may read the total frame and go out of whack.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *