Dolby Vision now possible through MP4 Mux.

[daffie]

So this Se7en framestore release with DoVi cm4.0 is actually better in terms of quality when compared with the HDR10 cm2.9 uhd retail bluray ?

Well, 92% of the movie is under 600nits so pretty much all the TVs will be able to display it without tone mapping.
It shouldn't look much different than HDR10 playback unless you have a very low brightness TV/PJ.

The trim has a positive lift over 0.0025(2100) for the whole movie but it is ignored by all the HDMI devices.

Thanks a lot for your reply!
"Unless you have a very low brightness TV."
I have a LG G1 OLED. That should be fine I guess in terms of brightness?

[RESET_9999]

yes

[darrrkmanxxx]

When 6-4 creates trims plot graph image(s), then yes your input contains trims...
if the graph is a straight line (like the Harry Potter movies), then it has static trims and you can discard the original RPU and use the cmv4.0 generated one.

Thanks for the answer. That clarifies a lot for me.
However when I plot a cmv4.0 there are no L2 trims being created but the L1 Plot list it. Are those produced from L8 now and is it also backwards compatible with cmv2.9 devices?

[fazambuja]

I'm pretty late to the party, but what is your guy's suggestion to a Samsung TV owner with only HDR10plus available?

Is it even worth getting something like a Ugoos AM6B? I'm currently using an Apple TV 3rd gen with Infuse.

I mainly download and occasionally rip some UHD Blu-rays.

[RESET_9999]

Is it even worth getting something like a Ugoos AM6B? I'm currently using an Apple TV 3rd gen with Infuse.

Yes, the ugoos supports DV + FEL(LLDV) on any display (SDR/HDR10).

However when I plot a cmv4.0 there are no L2 trims being created but the L1 Plot list it.

All the original/retail CMV4.0 rpu will have L2.
I just noticed the latest script version has the L2 trims plot disabled by default. So re-enable it at line 185

:: plot cmv4.0 only in 6-4. This disable L2 plot (default = NO)
set cmv4.0.only=NO

[SamuriHL]

Have you had a chance to test Davinci 19.x to see if it's still necessary to decode to prores first? Has their hevc support improved at all? I finally was able to fix my Davinci working with their support and I want to start playing with DV conversions soon. Thanks!

P.S. Apparently when I installed the pre-reqs for DoVi Tools, the version of Python that got installed from the Windows store broke Davinci and it was no longer able to start. Throwing that out there as a warning for anyone else who may run into that issue. I will need to solve the Python version issue before I get too far.

[RESET_9999]

Yes, I tested hevc decoding not a long time ago and it still drops frames.
Try the Spears and Munsil demo clip, it drops frames almost instantly with the mkv container. If you remux it to mp4, the SM clip will work but it is still not 100% reliable.

Have you had a chance to test Davinci 19.x to see if it's still necessary to decode to prores first? Has their hevc support improved at all? I finally was able to fix my Davinci working with their support and I want to start playing with DV conversions soon. Thanks!

[RESET_9999]

PS, to those who generate DV...

I said a couple of times that I selected the mastering display luminance based on the content's actual brightness(measured in 6-2).
I said to use 1000nits MDL if 90%+ of the shots have highlights under 1000nits.

Well, this is not longer the right thing to do because I recently discovered that some players like the Ugoos, Oppo, x700, X800m2 will clip highlights if the content is brighter than the RPU mastering display luminance, regardless of the metadata. So it may not be a good idea after all to use 1000nits MDL even if there are only a few highlights brighter than 1000nits because they will be clipped if your TV is not capable of displaying this brightness.

Interestingly, the Shield, the AppleTV, C2-C1-C9 internal player and Hisense internal player do not have this behavior and will tone map the image correctly without clipping regardless of the MDL (as long as L1 is right). This finally explains the RPU response differences between TV-LED devices that we noticed a long time ago (years ago?).

I did some test files that clearly show what I'm talking about: https://drive.google.com/drive/u/1/fold ... URFcibN6X-
Specifically: ''Dolby Vision 1000nits RPU Harry 2848nits scene P8.mp4''

*** This is about TV-LED. LLDV seems to work properly. Confirmed on oppo, ugoos, C9 C1 C2 Hisense... I no longer have the x700 x800m2 but it is most likely the same as the oppo, they have the same soc

[SamuriHL]

Yes, I tested hevc decoding not a long time ago and it still drops frames.
Try the Spears and Munsil demo clip, it drops frames almost instantly with the mkv container. If you remux it to mp4, the SM clip will work but it is still not 100% reliable.

Have you had a chance to test Davinci 19.x to see if it's still necessary to decode to prores first? Has their hevc support improved at all? I finally was able to fix my Davinci working with their support and I want to start playing with DV conversions soon. Thanks!

Good to know thanks. Prores it is then.

Sent from my SM-S928U1 using Tapatalk

[darrrkmanxxx]

PS, to those who generate DV...

I said a couple of times that I selected the mastering display luminance based on the content's actual brightness(measured in 6-2).
I said to use 1000nits MDL if 90%+ of the shots have highlights under 1000nits.

Well, this is not longer the right thing to do because I recently discovered that some players like the Ugoos, Oppo, x700, X800m2 will clip highlights if the content is brighter than the RPU mastering display luminance, regardless of the metadata. So it may not be a good idea after all to use 1000nits MDL even if there are only a few highlights brighter than 1000nits because they will be clipped if your TV is not capable of displaying this brightness.

So do we have to re-generate to a higher mastering display (based on 6.2 measuremnts) or just edit L6?

[RESET_9999]

So do we have to re-generate to a higher mastering display (based on 6.2 measuremnts) or just edit L6?

If you use a Oppo, X800m2 , x700 or Ugoos and the content has highlights brighter than 1000nits, it should be generated again. L6 is useless.

[darrrkmanxxx]

So do we have to re-generate to a higher mastering display (based on 6.2 measuremnts) or just edit L6?

If you use a Oppo, X800m2 , x700 or Ugoos and the content has highlights brighter than 1000nits, it should be generated again. L6 is useless.

alright thanks for the answer!

[deadchip12]

@RESET_9999

I looked for Alien Romulus web rpu in your google drive folder and only saw Alien.Romulus.2024.UHD.BluRay.2160p.TrueHD.Atmos.7.1.DV.HEVC.REMUX-FraMeSToR Retail P7 FEL (cmv4.0 added).bin. Is this file the equivalent of CMV4.0_L3L8L9_transfered.bin? Do we just inject this directly to the bluray mkv file?

[darrrkmanxxx]

@RESET_9999

I looked for Alien Romulus web rpu in your google drive folder and only saw Alien.Romulus.2024.UHD.BluRay.2160p.TrueHD.Atmos.7.1.DV.HEVC.REMUX-FraMeSToR Retail P7 FEL (cmv4.0 added).bin. Is this file the equivalent of CMV4.0_L3L8L9_transfered.bin? Do we just inject this directly to the bluray mkv file?

can you please share the link with all of the RPUs?

[RESET_9999]

can you please share the link with all of the RPUs?

The link is private...
Instructions on how to access it are in the Resolve Metadata Generation tutorial comments.

I looked for Alien Romulus web rpu in your google drive folder and only saw Alien.Romulus.2024.UHD.BluRay.2160p.TrueHD.Atmos.7.1.DV.HEVC.REMUX-FraMeSToR Retail P7 FEL (cmv4.0 added).bin. Is this file the equivalent of CMV4.0_L3L8L9_transfered.bin? Do we just inject this directly to the bluray mkv file?

yes, I did all the possible movies on my GD.