mike admin wrote: ↑Thu Oct 01, 2020 9:13 pm
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
MKVToolNix (v49 and higher) is supposedly capable of generating MKV files keeping the Dolby Vision data previously created by MakeMKV.
However, you indicate that if a MKV file with Dolby Vision is passed through MKVToolNix, it will no longer have Dolby Vision because you indicate that this new MKV file from MKVToolNix must be passed again through MakeMKV.
Is this correct?
So MKVToolNix is not working quite right completely?
I don't fully understand it since MKVToolNix really does preserve that data, since otherwise the video track would have a much smaller size.
So the real problem is that MKVToolNix doesn't keep this data well identified, or something like that?
mike admin wrote: ↑Mon Oct 05, 2020 9:07 pm
Rumourd wrote: ↑Sat Oct 03, 2020 5:31 am
What if you used 1.15.1 and later? Will it work then?
Yes.
1.15.0 - DV discarded
1.15.1 - DV bitstream preserved when opening BD disc. Discarded if source is MKV file. A bug - DV bitstream is (slightly and reversibly) corrupted. No MKV DV metadata.
1.15.2 - DV bitstream preserved when opening BD disc. Discarded if source is MKV file. No bitstream corruption bug. Full MKV DV metadata.
1.15.3 - DV bitstream preserved when opening all sources. DV metadata ignored in source container, full MKV DV metadata always reconstructed from bitstream. Corrupted bitstream produced by 1.15.1 is recognized and repaired.
DV bitstreams with invalid codec IDs (V_QUICKTIME and V_MS_FOURCC/DVHE) produced by mkvtoolnix and ffmpeg are properly recognized.
And in this other message, I see that you again indicate something similar to my suspicions.
Thank you very much for all your time and your fantastic work.
Regards!