[DoVi_Scripts] Multi-Function Scripts for Dolby Vision processing and a lot more...

[Kuler087]

There is no trim at all for this movie and the cmv4.0 metadata is only for the first two frames (older MA WEB-DLs have this weird authoring).
So yes, I generate cmv4.0 DV with original scene cuts when the original is only cmv2.9 without trims. I even did a trim for this movie.

[Kontrarian]

Yeah, I saw the P5 to P8 RPU on your Google drive (I think it's from iTunes).
When I plotted it I got L1 and L2 but no L3.
When I plotted the Movies Anywhere RPU I get the L3 but it just has MIN going straight across at 2048, MAX at 1641, and AVG at 1016.
So I figured it's probably best to use your "The Prestige (2006)_BD_Resolve.bin" but was wondering what's the deal with that L3 plot?

[Kuler087]

it doesnt matter, its only for the first two frames.

[Kontrarian]

Woah, I feel like an idiot... I didn't even pay attention to the X axis at all and just assumed it was the entire films timeline.

Which one of your files do you recommend we use, The Prestige (2006)_BD_Resolve.bin or The.Prestige.2006.BD-US.Generated.OSC.bin?

https://slow.pics/c/1ChKbXgp

[coopzr]

@Kuler087

6-2 measure brightness with cropping produces a prores video much faster than 8-2-2.

Is the 6-2 prores video sufficient to generate the DV metadata in Resolve or would using the proper 8-2-2 video produce more accurate DV metadata in Resolve?

EDIT:
I was mistaken, they take the same time. I could have sworn 6-2 produced a prores faster previously...

[Kuler087]

6-2 does process prores faster but it doesn't index the frames and use qscale 8(more compression).
It should still be fine for Resolve.

[Kuler087]

Originally Posted by Kontrarian

Which one of your files do you recommend we use, The Prestige (2006)_BD_Resolve.bin or The.Prestige.2006.BD-US.Generated.OSC.bin?

https://slow.pics/c/1ChKbXgp

The one I did trims:

The.Prestige.2006 BD Generated OSC T3 (MANUAL TRIMS)

[lauguru]

@Kuler087 Salut!


Can XML (DaVinci) be converted to RPU or BIN? If so, could it be added?

[Kuler087]

yes, of course. Run it in workflow 1 or plot it in 6-3

[lauguru]

Originally Posted by Kuler087

yes, of course. Run it in workflow 1 or plot it in 6-3

ok thanks

[dapope]

Hi @Kuler087 (thanks again for all your hard work!) or anyone else in the know.

Just wanted to check that I'm correctly understanding how the 1000 nits vs 4000 nits mdl stuff and L2 trims works.

Last night I watched The Nice Guys 2016 (which you analysed here: https://www.youtube.com/watch?v=wlix5YFMLI8&t=15s). I watched on my LG CX internal player after using your tool to convert to P8. The movie is MEL so no concerns about FEL expand brightness.

Highlights in the movie looked great however I thought that the overall look was a little dim. The movie is one of those that has a 4000 mdl but barely goes over 1000 nits, and in such cases you recommend changing the MDL to 1000 nits when creating a new DV grade from the algorithm. But am I correct in thinking that since the film has L2 trims and I wasn't creating a new DV grade, that the film was tonemapped appropriately and appeared as intended?

Thanks again!

[Kuler087]

Well, this movie was mastered with the old cmv2.9 algo, which has a slight black crush, especially with 4000/10000 MDL, and the trim in this movie doesn't add much(mostly static), so it might look better with the cmv4.0 balanced tuning @ 1000nits MDL indeed.

[dapope]

Originally Posted by Kuler087

Well, this movie was mastered with the old cmv2.9 algo, which has a slight black crush, especially with 4000/10000 MDL, and the trim in this movie doesn't add much(mostly static), so it might look better with the cmv4.0 balanced tuning @ 1000nits MDL indeed.

Thank you for your response!
To get a "not perfect, but good enough" solution, is there a quick way to simply edit the DV metadata to change the mdl to 1000 nits, or does such a change require remaking the DV from scratch? I had a poke around your program but couldn't find if it was an option.

[Kuler087]

Workflow 1/Q can edit source_pq, but this would make metadata inaccurate because Dolby calculates them differently based on the MDL.

I generated cmv4.0 1000 MDL for this movie here.

[Kontrarian]

@Kuler087

I see your signature has been updated to now show: LG OLED G5 77''

How are you liking it so far?
Care to share your impressions (pros and cons)?

[Kuler087]

Haven't received it yet; the tracking says it should arrive on Tuesday.
It will be a massive upgrade for sure (800nits C2 to 2500nits G5). The expanded brightness through some of the FEL movies is going to have a huge impact now, can't wait!

[Kontrarian]

@Kuler087, todays the BIG DAY!!!

[Kuler087]

YEAH!
Uniformity is already ten times better than on my C2... I just wish I didn’t have to work this week. More intensive testing will have to wait until the weekend.

[SamuriHL]

That's a good sign though. Are you planning on calibrating it?

[Kuler087]

Yep, for sure. I’ll give it a couple of weeks to break in and let a few firmware updates roll out before calibrating.