Dolby Vision now possible through MP4 Mux.

MastaG · Post by **MastaG** » Thu Apr 02, 2020 3:16 pm

deadchip12 wrote: Thu Apr 02, 2020 3:04 pm
MastaG wrote: Thu Apr 02, 2020 1:38 pm
deadchip12 wrote: Thu Apr 02, 2020 11:52 am

I followed the exact same steps in your post but Gemini Man still stutters every 2 seconds on my oled C9. The file is stored in an external hdd connected to the tv via usb and played using the tv internal media player.
Well the "boken/bugged" version of TsMuxer (when not all DV contributions were committed) created a .ts file that says:
Code: Select all
Dolby Vision, Version 1.0, dvhe.08.09, BL+EL+RPU / SMPTE ST 2086, HDR10 compatible
The hevc file of Gemini Man was indeed created with yusesope's 0.0.3 tool (mode 1 BL+EL+RPU).

However after reading all the posts here, it seems with profile 08 I'm telling the LG decoder to just ignore the EL layer and only read RPU (as if the hevc file was generated using mode 2 BL+RPU).
Like mp4muxer says:
Code: Select all
 --dv-profile <arg>                 = Sets the Dolby Vision profile. This option is MANDATORY for 
                                      DoVi elementary stream: Valid profile values are:
                                      4 - dvhe.04, BL codec: HEVC10; EL codec: HEVC10; BL compatibility: SDR/HDR.   
                                      5 - dvhe.05, BL codec: HEVC10; EL codec: N/A;    BL compatibility: None.      
                                      7 - dvhe.07, BL codec: HEVC10; EL codec: HEVC10; BL compatibility: Blue-ray HDR10. 
                                      8 - dvhe.08, BL codec: HEVC10; EL codec: N/A;    BL compatibility: SDR/HDR.   
                                      9 - dvav.09, BL codec: AVC;    EL codec: N/A;    BL compatibility: SDR/HDR
Only 04 and 07 should present an EL layer.. 07 is probably dual-track since it's for meant for BluRay.
So with profile 08 set in my .ts file the LG decoder probably doesn't stutter since it's ignoring the FEL layer.

I think the decoder is simply not powerful enough to process BL+EL+RPU for such high bitrate movies with a full enhanced layer, especially not a 60fps movie like Gemini Man.
So I guess I should go for mode 2 / profile 05 then.

@jcdr428
Could you add another commit to your PR to change the profile 06 back to 04?
I’m not sure I understand everything you mentioned but you got the file played on the c8 without stutter right? I used the same programs from the links you posted and followed the steps but then the file stutters on the c9. What can explain this?

Well I meant to say that the FEL movies such as Gemini Man were playing smooth on my C8 because I was using an older revision of TsMuxer.

This version would incorrectly set profile 08 in the .ts file.

I've edited my last post with all the DV profiles.
And as you can see, profile 08 doesn't mention an EL layer.

So with profile 08 the LG player will treat the video track as BL+RPU. (Like when using mode 2 when using yusecope's tool).
Thus it ignores the EL layer altogether, making it play smooth.

So you'll see DV but it's only processing the RPU metadata, not the full EL layer.

I think the SoC is not powerful enough to process BL+EL+RPU (profile 04/06) when using a full enhancement layer (FEL) at such high bitrates.

So you might as well use BL+RPU (mode 2) instead as it gives the same result as using profile 08 (telling the player there is no EL).

EDIT:

Even without the full enhancement layer you can clearly see the difference between DV and HDR10.

In this movie DV adds some nice shading.

And at 60fps it's really beautiful to watch, even though it's a bad movie overall.

Angryunibrow · Post by **Angryunibrow** » Thu Apr 02, 2020 3:41 pm

@jcdr428
Could you add another commit to your PR to change the profile 06 back to 04?

I think this would be best also, we should be using profile 4 not 6.

yusesope · Post by **yusesope** » Fri Apr 03, 2020 9:18 am

shawnc22 wrote: Thu Apr 02, 2020 12:01 pm Any reason you can think of to explain why it still looks like it’s working (DV still triggered) despite the apparent lack of support for profile 6? Also kind of interesting to see profile 7 mentioned in the code even though its not supported.

I think the application starts a "tunneled video playback" session (more information HERE). What happens next depends on how nVidia implemented the hardware decoder. Most likely the EL layer is discarded and only the BL layer is processed together with the RPU metadata.

As for profile 7, it is considered to define codecsPrefix = "dvhe" but in the "MediaCodecVideoRenderer" class (HERE) only the profiles mentioned in the article seem to be taken into consideration (the various profiles are defined HERE)

MastaG wrote: Thu Apr 02, 2020 1:38 pm 07 is probably dual-track since it's for meant for BluRay.

I agree with everything you wrote. I have a doubt about the previous statement.
Why don't you try creating a profile 7 file using my tool (-mode 1) and mp4muxer?
Does your LG TV play it?

jcdr428 · Post by **jcdr428** » Fri Apr 03, 2020 9:43 am

@Angryunibrow @shawnc22 could you please:
- Mux FEL Blu-ray BL and EL to single layer with yusesope tool, then to profile 4 with Dolby mp4muxer,
- Change in dvcC atom dv_profile from 4 to 6, and dv_bl_signal_compatibility_id from 2 to 1
(i.e. change '64 76 63 43 01 00 08 37 20' to '64 76 63 43 01 00 0C 37 10' with an Hex editor)

and try it on TV ?

@yusesope ExoPlayer being open-source, profile 6 can be pushed easily.

MastaG · Post by **MastaG** » Fri Apr 03, 2020 11:32 am

yusesope wrote: Fri Apr 03, 2020 9:18 am
MastaG wrote: Thu Apr 02, 2020 1:38 pm 07 is probably dual-track since it's for meant for BluRay.
I agree with everything you wrote. I have a doubt about the previous statement.
Why don't you try creating a profile 7 file using my tool (-mode 1) and mp4muxer?
Does your LG TV play it?

I've just tried it:

www.makemkv.com

MakeMKV support forum