Dolby Vision now possible through MP4 Mux.

Please post here for issues related to UHD discs
Post Reply
Maxoumax6
Posts: 7
Joined: Sun Mar 29, 2020 9:03 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Maxoumax6 »

Does the profil change the DV's "quality"?
mrhollywood
Posts: 16
Joined: Thu May 02, 2019 7:01 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by mrhollywood »

The NEO U22-XJ is now officially out. Anyone gonna pick one up and test it's DV functionality?
http://shop.minix.us/neo-u22-xj
Angryunibrow
Posts: 104
Joined: Wed Nov 06, 2019 11:26 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Angryunibrow »

mrhollywood wrote: Wed Apr 01, 2020 6:07 pm The NEO U22-XJ is now officially out. Anyone gonna pick one up and test it's DV functionality?
http://shop.minix.us/neo-u22-xj
Patiently waiting to see what this supports also, but I'm not expecting anything above what we have now with the shield.
Although if this can produce accurate DV color as apposed to the shield that might be worth it.
MastaG
Posts: 98
Joined: Thu Aug 08, 2019 11:40 am

Re: Dolby Vision now possible through MP4 Mux.

Post by MastaG »

shawnc22 wrote: Wed Apr 01, 2020 3:18 pm
MastaG wrote: Wed Apr 01, 2020 8:10 am So if I understand correctly we still didn't get single track video with full EL layer (profiel 04 or 06) to work on LG C# without stuttering?
Correct, that is my understanding as well from the latest tests we have done.
Strange as my mode 1 "BL+EL+RPU" merge of Gemini Man (FEL HFR) did trigger DV and played smoothly on my C8 when I was using an older rev of TsMuxer.
See my post: https://www.makemkv.com/forum/viewtopic ... 295#p86295

The older rev of TsMuxer was showing profile 08.09.
That makes me wonder whether the TV was actually processing the full enhancement layer or perhaps it was only using the metadata (due to the profile saying 08).

Who kbnows :P

Anyways I've recompiled TsMuxer with the last two changes of jcdr248's PR: https://github.com/justdan96/tsMuxer/pull/269
And I tried to create a dual track TS file of Gemini Man, but that only triggers HDR10 on my C8.

Code: Select all

$ mediainfo Gemini\ Man\ 2019_DL.ts 
General
ID                                       : 1 (0x1)
Complete name                            : Gemini Man 2019_DL.ts
Format                                   : MPEG-TS
File size                                : 75.4 GiB
Duration                                 : 1 h 57 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 92.2 Mb/s
Maximum Overall bit rate                 : 35.5 Mb/s

Video #1
ID                                       : 4113 (0x1011)
Menu ID                                  : 1 (0x1)
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : SMPTE ST 2086, HDR10 compatible
Codec ID                                 : 36
Duration                                 : 1 h 57 min
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : Display P3
Mastering display luminance              : min: 0.0010 cd/m2, max: 1000 cd/m2
Maximum Content Light Level              : 5180 cd/m2
Maximum Frame-Average Light Level        : 1577 cd/m2

Video #2
ID                                       : 4117 (0x1015)
Menu ID                                  : 1 (0x1)
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : Dolby Vision, Version 1.0, dvhe.07.09, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID                                 : 6
Duration                                 : 1 h 57 min
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : Display P3
Mastering display luminance              : min: 0.0010 cd/m2, max: 1000 cd/m2

Audio #1
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : AC-3 MLP FBA 16-ch
Format/Info                              : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name                          : Dolby TrueHD with Dolby Atmos
Muxing mode                              : Stream extension
Codec ID                                 : 131
Duration                                 : 1 h 57 min
Bit rate mode                            : Variable
Bit rate                                 : 640 kb/s
Maximum bit rate                         : 7 944 kb/s
Channel(s)                               : 8 channels
Channel layout                           : L R C LFE Ls Rs Lb Rb
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Stream size                              : 536 MiB (1%)
Language                                 : English
Service kind                             : Complete Main
Number of dynamic objects                : 11
Bed channel count                        : 1 channel
Bed channel configuration                : LFE

Audio #2
ID                                       : 4353 (0x1101)
Menu ID                                  : 1 (0x1)
Format                                   : E-AC-3
Format/Info                              : Enhanced AC-3
Commercial name                          : Dolby Digital Plus
Codec ID                                 : 135
Duration                                 : 1 h 57 min
Bit rate mode                            : Constant
Bit rate                                 : 448 kb/s
Channel(s)                               : 6 channels
Channel layout                           : L R C LFE Ls Rs
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Stream size                              : 375 MiB (0%)
Language                                 : English
Service kind                             : Complete Main
Still hoping to find a way to enjoy the full enhancement layer on the C8 while retaining the TrueHD audio (for storage/collection purposes only, I know the C8 wont play HD-audio due to the lack of e-ARC).
Angryunibrow
Posts: 104
Joined: Wed Nov 06, 2019 11:26 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Angryunibrow »

MastaG wrote: Wed Apr 01, 2020 6:50 pm
shawnc22 wrote: Wed Apr 01, 2020 3:18 pm
MastaG wrote: Wed Apr 01, 2020 8:10 am So if I understand correctly we still didn't get single track video with full EL layer (profiel 04 or 06) to work on LG C# without stuttering?
Correct, that is my understanding as well from the latest tests we have done.
Strange as my mode 1 "BL+EL+RPU" merge of Gemini Man (FEL HFR) did trigger DV and played smoothly on my C8 when I was using an older rev of TsMuxer.
See my post: https://www.makemkv.com/forum/viewtopic ... 295#p86295

The older rev of TsMuxer was showing profile 08.09.
That makes me wonder whether the TV was actually processing the full enhancement layer or perhaps it was only using the metadata (due to the profile saying 08).

Who kbnows :P

Anyways I've recompiled TsMuxer with the last two changes of jcdr248's PR: https://github.com/justdan96/tsMuxer/pull/269
And I tried to create a dual track TS file of Gemini Man, but that only triggers HDR10 on my C8.

Code: Select all

$ mediainfo Gemini\ Man\ 2019_DL.ts 
General
ID                                       : 1 (0x1)
Complete name                            : Gemini Man 2019_DL.ts
Format                                   : MPEG-TS
File size                                : 75.4 GiB
Duration                                 : 1 h 57 min
Overall bit rate mode                    : Variable
Overall bit rate                         : 92.2 Mb/s
Maximum Overall bit rate                 : 35.5 Mb/s

Video #1
ID                                       : 4113 (0x1011)
Menu ID                                  : 1 (0x1)
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : SMPTE ST 2086, HDR10 compatible
Codec ID                                 : 36
Duration                                 : 1 h 57 min
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : Display P3
Mastering display luminance              : min: 0.0010 cd/m2, max: 1000 cd/m2
Maximum Content Light Level              : 5180 cd/m2
Maximum Frame-Average Light Level        : 1577 cd/m2

Video #2
ID                                       : 4117 (0x1015)
Menu ID                                  : 1 (0x1)
Format                                   : HEVC
Format/Info                              : High Efficiency Video Coding
Format profile                           : Main 10@L5.1@High
HDR format                               : Dolby Vision, Version 1.0, dvhe.07.09, EL+RPU / SMPTE ST 2086, HDR10 compatible
Codec ID                                 : 6
Duration                                 : 1 h 57 min
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate                               : 59.940 (60000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0 (Type 2)
Bit depth                                : 10 bits
Color range                              : Limited
Color primaries                          : BT.2020
Transfer characteristics                 : PQ
Matrix coefficients                      : BT.2020 non-constant
Mastering display color primaries        : Display P3
Mastering display luminance              : min: 0.0010 cd/m2, max: 1000 cd/m2

Audio #1
ID                                       : 4352 (0x1100)
Menu ID                                  : 1 (0x1)
Format                                   : AC-3 MLP FBA 16-ch
Format/Info                              : Audio Coding 3 + Meridian Lossless Packing FBA with 16-channel presentation
Commercial name                          : Dolby TrueHD with Dolby Atmos
Muxing mode                              : Stream extension
Codec ID                                 : 131
Duration                                 : 1 h 57 min
Bit rate mode                            : Variable
Bit rate                                 : 640 kb/s
Maximum bit rate                         : 7 944 kb/s
Channel(s)                               : 8 channels
Channel layout                           : L R C LFE Ls Rs Lb Rb
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Stream size                              : 536 MiB (1%)
Language                                 : English
Service kind                             : Complete Main
Number of dynamic objects                : 11
Bed channel count                        : 1 channel
Bed channel configuration                : LFE

Audio #2
ID                                       : 4353 (0x1101)
Menu ID                                  : 1 (0x1)
Format                                   : E-AC-3
Format/Info                              : Enhanced AC-3
Commercial name                          : Dolby Digital Plus
Codec ID                                 : 135
Duration                                 : 1 h 57 min
Bit rate mode                            : Constant
Bit rate                                 : 448 kb/s
Channel(s)                               : 6 channels
Channel layout                           : L R C LFE Ls Rs
Sampling rate                            : 48.0 kHz
Frame rate                               : 31.250 FPS (1536 SPF)
Compression mode                         : Lossy
Stream size                              : 375 MiB (0%)
Language                                 : English
Service kind                             : Complete Main
Still hoping to find a way to enjoy the full enhancement layer on the C8 while retaining the TrueHD audio (for storage/collection purposes only, I know the C8 wont play HD-audio due to the lack of e-ARC).
Not possible ATM - see response below.
jcdr428 wrote: Tue Mar 31, 2020 10:01 pm
Angryunibrow wrote: Tue Mar 31, 2020 9:22 pm I made the comment that tsmuxer was assigning profile 7.05, while mp4muxer was profile 7.06 - I do not know if that matters.
@Angryunibrow it should be 7.06... I'll fix it. However the level is only related to pixel rate, marking 7.05 does not make any difference if your SoC can play 7.06 pixel rates. The most obvious reason why the TS plays on Blu-ray players only is the HDMV (Blu-ray) descriptors. Standard ETSI descriptors might allow DV but would remove compatibility with PGS, ac3/eac3 and ac3/TrueHD.
mrhollywood
Posts: 16
Joined: Thu May 02, 2019 7:01 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by mrhollywood »

Angryunibrow wrote: Wed Apr 01, 2020 6:16 pm
mrhollywood wrote: Wed Apr 01, 2020 6:07 pm The NEO U22-XJ is now officially out. Anyone gonna pick one up and test it's DV functionality?
http://shop.minix.us/neo-u22-xj
Patiently waiting to see what this supports also, but I'm not expecting anything above what we have now with the shield.
Although if this can produce accurate DV color as apposed to the shield that might be worth it.
The devs specified it supports dual layer, and it's not capable of playing HD from Netflix or any other streaming service so the only thing it can play is rips. I would assume if they're gonna pay for the license they'd implement it right. I'm gonna order one when I get my trumpbux so I'll test it and post results here.
Angryunibrow
Posts: 104
Joined: Wed Nov 06, 2019 11:26 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Angryunibrow »

mrhollywood wrote: Wed Apr 01, 2020 7:42 pm
Angryunibrow wrote: Wed Apr 01, 2020 6:16 pm
mrhollywood wrote: Wed Apr 01, 2020 6:07 pm The NEO U22-XJ is now officially out. Anyone gonna pick one up and test it's DV functionality?
http://shop.minix.us/neo-u22-xj
Patiently waiting to see what this supports also, but I'm not expecting anything above what we have now with the shield.
Although if this can produce accurate DV color as apposed to the shield that might be worth it.
The devs specified it supports dual layer, and it's not capable of playing HD from Netflix or any other streaming service so the only thing it can play is rips. I would assume if they're gonna pay for the license they'd implement it right. I'm gonna order one when I get my trumpbux so I'll test it and post results here.
Do you have a link to them saying that (not that I do not believe you) I would like to see what the exchange was when that was mentioned.

IF, and its a big IF this does support Profile 7, I would think we would need decrypted BDMV folder playback support. Then we do not have to worry about trying to mux these files into something that is not fully supported and losing ATMOS and everything else.

We will see I guess.
shawnc22
Posts: 637
Joined: Tue Jan 21, 2020 7:40 am

Re: Dolby Vision now possible through MP4 Mux.

Post by shawnc22 »

Angryunibrow wrote: Wed Apr 01, 2020 9:20 pm Do you have a link to them saying that (not that I do not believe you) I would like to see what the exchange was when that was mentioned.

IF, and its a big IF this does support Profile 7, I would think we would need decrypted BDMV folder playback support. Then we do not have to worry about trying to mux these files into something that is not fully supported and losing ATMOS and everything else.

We will see I guess.
It was probably from this vague post here: https://theminixforum.com/index.php?thr ... post-17736

The question I have is whether this dolby license fee is an encompassing license that allows for decoding of all profiles and then it's up to the hardware to be capable of dealing with the individual profiles, or is the licence fee broken down by individual profile support. If it's the latter, the skeptic in me finds it hard to believe that any company would pay the profile 7 dolby license fee for a streaming-only device just to satisfy the niche situation we have here. Normal consumers are not going to encounter profile 7 outside of playing it from their physical uhd disks, hence why it's only mostly blu-ray players that have the capability to do so at the moment (LG C# TVs are certainly an exception).
Grencola
Posts: 343
Joined: Sun Jan 27, 2019 5:19 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by Grencola »

shawnc22 wrote: Wed Apr 01, 2020 9:43 pm It was probably from this vague post here: https://theminixforum.com/index.php?thr ... post-17736

The question I have is whether this dolby license fee is an encompassing license that allows for decoding of all profiles and then it's up to the hardware to be capable of dealing with the individual profiles, or is the licence fee broken down by individual profile support. If it's the latter, the skeptic in me finds it hard to believe that any company would pay the profile 7 dolby license fee for a streaming-only device just to satisfy the niche situation we have here. Normal consumers are not going to encounter profile 7 outside of playing it from their physical uhd disks, hence why it's only mostly blu-ray players that have the capability to do so at the moment (LG C# TVs are certainly an exception).
like I mentioned in my follow up post on that link, it either has to do profile 7 or it's pure marketing BS. otherwise I really just don't get it. profile 4 or 5 support will do nothing for consumers as it's a non-certified device so it won't even do Full HD in streaming apps, let alone 4k or dolby vision lol. so either marketing is trying to sell it on the sham that the SoC can physically do dv and android 9 os has a force dv setting that fakes it for everything in the gui, or they will actually support profile 7 so consumers can play their backups. They claim they have a paid dolby license, but would Dolby really grant a license to a non-certified device on good faith that minix customers would only watch legit backups and not commit piracy?
DaMacFunkin
Posts: 314
Joined: Tue Oct 30, 2018 4:17 pm

Re: Dolby Vision now possible through MP4 Mux.

Post by DaMacFunkin »

Nvidia devs said that Dolby will not licence full profile for set top boxes as they see the only Avenue for that is piracy.
yusesope
Posts: 221
Joined: Sun Jul 28, 2019 3:34 am

Re: Dolby Vision now possible through MP4 Mux.

Post by yusesope »

jcdr428 wrote: Tue Mar 31, 2020 6:04 pm ...
means there is no backward compatibility. SDR is 1, 1, 1, HDR10 is 9, 16, 9.
....
Primary Dolby Vision PID Carrying a non-SDR and non-HDR Compliant BL substream
The value of stream_type shall be set to 0x06 (indicating PES packets containing private data).
I think what you think (in fact I had written despite color_description_present_flag = 0 and chroma_location_info_present = 0)
But then I analyze the LG demo (I think LG has all the hardware and software certified by Dolby) and I see this:
Image
stream_type shouldn't be 0x06? (I don't think it's because of the presence of HEVC_timing_and_HRD_descriptor in place of 0x0504444F5649)



jcdr428 wrote: Tue Mar 31, 2020 8:26 pm The way FEL is triggered in the RPU of profile 7 and of profile 4/6 seems to be different. So it is not as simple as copying the EL/RPU from the second track to the first.
...
Edit: if anyone is interested in parsing RPU information https://patentimages.storage.googleapis ... 9132A1.pdf
About 20 days ago I posted the comparison between two RPU headers (HERE). Out of curiosity, I analyzed an RPU of the LG demo (BL+EL+RPU, dvhe.04.06) and the header is identical to that of the MEL stream (from a UHD-BD).

I didn't go beyond the header because that document is a nightmare.
I don't think current RPUs are implemented as described in the patent.
A simple example, considering the final sequence 0b10000000 (0x80) as rbsp_trailing_bits(), the previous 4 bytes should represent the CRC value (calculated on the entire rpu_data () excluding rpu_data_crc32).
The calculated CRC32 value never corresponds to that present in the RPU.

As for the FEL layer, in the case of profile 4, a device must control and must flag, in case of profile 7 the device can control and can flag. However, the variables to be checked are the same.

The fact that on LG televisions a BL+EL+RPU file goes jerky (unlike a simple BL+RPU) could be due precisely to the presence of the FEL layer which saturates the decoder buffer.
My dvhe.04 files are High Tier 5.1 (both BL and FEL/MEL because they come from a UHD-BD)
From the official Dolby documentation:

Code: Select all

In certain cases, the Dolby Vision specification imposes tighter constraints on the maximum tier bit rate and
the maximum decoded picture buffer size, as compared to the HEVC Main10 Level 5.1 specification.
See sections Dolby Vision levels and Limitation on decoder buffer size.


shawnc22 wrote: Tue Mar 31, 2020 3:38 pm When playing back the DV4 file, the renderer actually lists the codec as dvhe.04.06, but nothing for the DV6 file.
Thanks @shawnc22.
I'm sorry guys but the latest version of Exoplayer (2.10) does not support profile 6. There is an article about it on the developer blog (HERE) and checking the code (HERE) it shows the same thing!
deadchip12
Posts: 385
Joined: Thu May 02, 2019 2:49 am

Re: Dolby Vision now possible through MP4 Mux.

Post by deadchip12 »

MastaG wrote: Wed Apr 01, 2020 6:50 pm
Strange as my mode 1 "BL+EL+RPU" merge of Gemini Man (FEL HFR) did trigger DV and played smoothly on my C8 when I was using an older rev of TsMuxer.
See my post: https://www.makemkv.com/forum/viewtopic ... 295#p86295
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.
shawnc22
Posts: 637
Joined: Tue Jan 21, 2020 7:40 am

Re: Dolby Vision now possible through MP4 Mux.

Post by shawnc22 »

yusesope wrote: Thu Apr 02, 2020 10:26 am
shawnc22 wrote: Tue Mar 31, 2020 3:38 pm When playing back the DV4 file, the renderer actually lists the codec as dvhe.04.06, but nothing for the DV6 file.
Thanks @shawnc22.
I'm sorry guys but the latest version of Exoplayer (2.10) does not support profile 6. There is an article about it on the developer blog (HERE) and checking the code (HERE) it shows the same thing!
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.

Bit of a side note on exoplayer lately, I’ve noticed that even though the option is turned on in the settings, content frame rate matching does not seem to be working and everything is still being played at 60hz. Reverting back to the old player solves the issue and all my DV remuxes still seem to work (at least as far as triggering DV goes) like they do with the exoplayer.
Last edited by shawnc22 on Thu Apr 02, 2020 4:32 pm, edited 1 time in total.
MastaG
Posts: 98
Joined: Thu Aug 08, 2019 11:40 am

Re: Dolby Vision now possible through MP4 Mux.

Post by MastaG »

deadchip12 wrote: Thu Apr 02, 2020 11:52 am
MastaG wrote: Wed Apr 01, 2020 6:50 pm
Strange as my mode 1 "BL+EL+RPU" merge of Gemini Man (FEL HFR) did trigger DV and played smoothly on my C8 when I was using an older rev of TsMuxer.
See my post: https://www.makemkv.com/forum/viewtopic ... 295#p86295
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?
deadchip12
Posts: 385
Joined: Thu May 02, 2019 2:49 am

Re: Dolby Vision now possible through MP4 Mux.

Post by deadchip12 »

MastaG wrote: Thu Apr 02, 2020 1:38 pm
deadchip12 wrote: Thu Apr 02, 2020 11:52 am
MastaG wrote: Wed Apr 01, 2020 6:50 pm
Strange as my mode 1 "BL+EL+RPU" merge of Gemini Man (FEL HFR) did trigger DV and played smoothly on my C8 when I was using an older rev of TsMuxer.
See my post: https://www.makemkv.com/forum/viewtopic ... 295#p86295
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?
Post Reply