Download-Tools/mkvtoolnix
1
0
Fork 0
mirror of https://gitlab.com/mbunkus/mkvtoolnix.git synced 2025-01-21 01:17:48 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Page: mkvalidator ERR009 read doc type version higher than doc type version
Pages
About track UIDs, track numbers and track IDs Adding files vs. Appending files vs. adding as additional parts All tracks vanished after mkvpropedit, the header or chapter editors Appending & splitting FLAC audio tracks not supported Automation examples Batch muxing with the GUI Characters (e.g. Umlauts) aren't shown correctly Chinese not selectable as language Compiling on Debian 11 Bullseye Crash when adding attachments Creating byte identical files Cropping ignored DLLs not found Dark mode issues on Windows 11 Dark mode issues Debugging GUI startup problems Default and forced flags and default yes no in the GUI Delay not shown in the GUI Detecting track language from filename Dolby Vision support status Elements not showing up in output file Embedded fonts dont work FAQ FTP server Home Improving playback compatibility with players JSON output could not be parsed Language not available in MKVToolNix GUI Languages in Matroska and MKVToolNix Launching the command line programs with the Microsoft Store variant Location of settings, job queue, cache folder Long file & path names MKVToolNix GUI MKVToolNix costs money in stores Meta data fields like bitrate lost Multi display support broken in 67.0.0 Officially supported operating systems and versions Playback does not work VLC cannot seek mkvmerge v5.9.0 Release codenames Removing all files doesn't clear all inputs in the GUI Running the command line programs on macOS SRT subtitle file not recognized SUP and HD DVD subtitles Segment duration vs track duration Splitting imprecise Stretch or shrink audio tracks The job queue, statuses and their actions Track statistics tags Transforming mkvmerge's JSON output Troubleshooting TrueHD and AC 3 UTF 8 invalid sequence Understanding mkvinfo's output Use FIFOs stdin stdout Video does not play explorer locks up Virus in installer What happened to the forum What is mkvtoolnix.exe Wrong frame rate displayed mkvalidator ERR009 read doc type version higher than doc type version mkvalidator ERR201 Invalid CueRelativePosition for profile matroska v2 in CueTrackPositions mkvalidator WRN00C unknown element mkvalidator WRN0C0 First Block for video track in Cluster not a keyframe mkvalidator WRN0D0 void data mkvalidator WRN201 unknown element for read profile mkvextract wrong track mkvinfo mkvmerge track IDs wrong mkvinfo track summary mtxcfg file format and the jobQueue
5 mkvalidator ERR009 read doc type version higher than doc type version
Moritz Bunkus edited this page 2016-02-24 21:30:47 +01:00
Table of Contents

mkvalidator error ERR009 read DocType version higher than DocType version

The problem

When running mkvalidator on a file generated by mkvmerge 5.9.0 or later it issues the following warning:

ERR009: The read DocType version 2 is higher than the Doctype version 4

What does this mean?

The answer

This is a bug in mkvalidator in versions up to and including 0.4.2. It has been fixed in v0.5.0. If you're running an earlier version please upgrade to the latest one.

The in-depth explanation

In Matroska there are two header fields that include information about the Matroska standards/specs version number used. One is the DocTypeVersion and one the DocTypeReadVersion.

The first one, the DocTypeVersion, must be set to the highest version number of the Matroska specs from which the muxer creating the file has used elements from. E.g. if the muxer used SimpleBlock elements then the DocTypeVersion must be at least 2 because the SimpleBlock element was added in Matroska v2.

The other element, DocTypeReadVersion, must be set to the minimum Matroska version that a player must support properly in order to be able to play back the file. This is meant to ensure that players that support older versions can still play files created by newer tools even if elements from newer versions of the specs are used.

Logically it is easy to see that DocTypeVersion must always be the same or higher than DocTypeReadVersion.

Starting with 5.9.0 mkvmerge writes two elements from the v4 specs, CueDuration and CueRelativePosition. Therefore mkvmerge sets DocTypeVersion to 4. However, those elements only provide additional information that is not strictly required for playback, not even for seeking (which they aim to improve). Therefore it leaves DocTypeReadVersion at 2.

And here's where the bug in mkvalidator lay: it compared DocTypeReadVersion < DocTypeVersion instead of the other way around. The error it therefore issued, however, is correct in its wording; only the numbers listed didn't make sense because they're taken directly from the file.

Categories: mkvalidator

MKVToolNix FAQ and bug tracker