What it means, that if you have an MKV file with completely bogus or missing metadata, you can open it with 1.15.3 and produce a correct DV MKV, as long as bitstream is not altered. Even if MKV file is produced by a tool that is unaware of Dolby Vision, as long as bitstream is not corrupted. Most tools keep unknown bitstream data as is.
Also, there is another feature - MakeMKV now recognizes Dolby video codec inside "unsupported" container. With this, one can convert any DV file, from any format to DV MKV. Word of warning - this is rather advanced feature, but you can convert pretty much anything to MKV.
Below are the steps to convert DV MP4 or TS file (or anything else) to DV MKV.
Step 1 - you have to convert a source file into MKV. two commands to do so are:
Code: Select all
ffmpeg -i "$1" -vcodec copy -acodec copy -f matroska "$1_ffmpeg.mkv"
Code: Select all
mkvmerge -o "$1_mmg.mkv" "$1"
1 - HEVC MKV (HEVC video with no DOVI descriptors). Could be played back (without DV) and edited.
2 - crappy MKV - the video codec would be either an MS_FOURCC/dvh? or V_QUICKTIME . No player would play this file and most tools would choke on it.
3 - broken MKV - a variant of (2) with vital metadata destroyed. can really rarely get this with ffmpeg method, the P81 MP4 sample produces this (only when using ffmpeg).
4 - DV MKV , that's what new MakeMKV produces.
MakeMKV now can open all 4, extract the raw bitstream and produce a proper DV MKV file. So most of the time workflow would be:
.mp4 -> mkvmerge -> crappy_mkv -> makemkv -> DV_MKV -> mkvmerge -> HEVC_MKV -> makemkv -> DV_MKV
.ts -> ffmpeg -> crappy_mkv -> ...
It is possible to use mkvmerge for .ts sources and ffmpeg for .mp4 sources, but YMMV.