Muxing Dolby Vision MKV to BD creates an unplayable result

[DreckSoft]

When I try to multiplex a MKV with HDR10 and Dolby Vision to a BD Folder, the result is not playable. The video track is muxed as a DV EL, so the output has no main video track.

If I edit the MPLS (with MPLS2JSON) to make the DV stream the main video stream, it plays fine - even with the wrong main video PID.

I've attached the original and edited playlist.
PLAYLIST.zip

After editing the playlist, I applied the changes to the CLPI with BDEdit. The result plays fine as HDR10.

I think the default should be, to mux a video stream as the main video stream. I think for DV to work on BD you will need two video streams, one HDR10 and one with DV EL metadata. So one stream always must be HDR10.

Suggestion: Mux a video stream as the main video stream (BL) per default. Provide an option to mux as DV EL (which would only make sense if there are two video streams but maybe someone has a use case for that). If there are more than one video stream the user should decide which is BL and which is EL.

[Hellboy00000]

Probably you are using a MKV with DV "Double Layer Single Tracks" and that is not Blu-ray standard so is not going to work. You need "Double Layer Double Tracks". And tsMuxer already have a warning for "Double Layer Single Tracks".

Warning! Dolby Vision Double Layer Single Tracks are not standard for BD disks, the disk will not play in a Blu-ray player.

So if this is the case this is not a bug.

[DreckSoft]

As just stated above, it works perfectly if processed correct.

Yes it is Double Layer Single Tracks but it works fine as normal HDR10 if you do it right. So why create a 100% unplayable result when you can get a correct one just without DV? It makes no sense.

[jcdr428]

Ok, I cancel commit d6d1e0e.
@DreckSoft you have to modify the fix so that it does not break the DV muxing into Blu-ray.

[DreckSoft]

Then I don't know how to patch it.