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

[ReciprocalUniverse]

Originally Posted by TDS

here's another:- choose to play it in 4320p !!!

https://www.youtube.com/watch?v=vIN9Q1Slk0w

This one streamed in 8K SDR, no HDR.

[TDS]

Originally Posted by TDS

That clip was only available (to download & play) in 2160p/4K @ 60fps, you need at least 4320p/8K @ whatever fps !!!

Did it actually display @ 8K ??

Yes, it streamed in 7680 x 4320 @ 60fps AV1 smpte2084/bt2020
...but not Dolby Vision.

120 fps is just the camera frame rate it was shot at, slowed to 60 in post. YouTube doesn't stream higher than 60, at least not at 8K. And there's no tv that supports native 8K 120 playback either.

I don't know about downloading from YouTube, never tried, just streaming.

It would be nice if someone posted some "proper" demo's (not YouTube), the first time I ever saw the Dolby Vision icon was when I downloaded a DV demo that was a .ts.....seeing that icon for the first time put a huge smile on my face.

I use Internet Download Manager to download off YouTube.

[ReciprocalUniverse]

Originally Posted by TDS

It would be nice if someone posted some "proper" demo's (not YouTube), the first time I ever saw the Dolby Vision icon was when I downloaded a DV demo that was a .ts.....seeing that icon for the first time put a huge smile on my face.

I use Internet Download Manager to download off YouTube.

So if IDM is giving you the native file uploaded to YouTube, it may very well contain compliant DV metadata, but what YouTube streams does not.

That was a conversation I had with my pal, he objects to all these YT videos claimed to be DV, but if they really are DV and it's YT that's not streaming DV, shouldn't YT have an obligation to disclose since they are re-encoding them? Afterall, the uploader would not be the one misrepresenting the file.

[TDS]

Originally Posted by ReciprocalUniverse

So if IDM is giving you the native file uploaded to YouTube, it may very well contain compliant DV metadata, but what YouTube streams does not.

That was a conversation I had with my pal, he objects to all these YT videos claimed to be DV, but if they really are DV and it's YT that's not streaming DV, shouldn't YT have an obligation to disclose since they are re-encoding them? Afterall, the uploader would not be the one misrepresenting the file.

I'm not sure if it gives you that access...

Not being someone that uploads ANYTHING to YT, from what I've heard, YT WILL change anything that doesn't follow the "rules".

So I agree with your buddy, just because it says it is, doesn't mean a thing

I mean you might be able to download something that's close to what you want, and re-process it...

For example, I download quite a few train videos from Norway, etc, and re-process them to play a LOT faster, and with no ads

I know that you can play YT @ 2x, but you still get the ad's and occasionally buffering in high res.

[Vymrr]

I tried running your test files but somehow my ugoos am6b+ (running coreelec) is playing them as SDR and HDR content only? I have no issues playing normal DV movies as DV, only your files.

Originally Posted by Kuler087

You can with Resolve and the custom edid I gave you.



All the TVs made after 2019 should support it. You can try the cmv4.0 test files here: https://drive.google.com/drive/u/1/f...rk-Ifx6vRYDEfs

[Kuler087]

Originally Posted by Vymrr

I tried running your test files but somehow my ugoos am6b+ (running coreelec) is playing them as SDR and HDR content only? I have no issues playing normal DV movies as DV, only your files.

works fine on mine

[wyup]

In 8-2-2 (Encode DV to SDR), it would be nice to preview/compare different analyse tunings: balanced, more/most highlights, less/least-highlights and legacy, to choose the best looking SDR for the user.

In 3-1 (DoVi MAKER from HDR10, Dolby Algorythm), something similar would be desired aswell to estimate how DV is going to behave when doing the interpolation for the tv capability. I.e: If my DV-enabled tv has 400 nits of brightness for HDR and the content is graded at 1,000 nits, depending on the chosen analyse tuning, the final image interpolated from the 100-nit mandatory trim would be different.

Also, is it possible to choose how many DV trims to generate? Ie: 100, 400, 600, 1000.
And finally, it would be nice to choose desired trim encoding for HDR10. Ie: convert a native HDR10 4,000 movie to a 1,000, 600 or 400 one, to get better tonemapping than a non-enabled DV tv does.

Thanks for the good work.

[Kuler087]

In 8-2-2 (Encode DV to SDR), it would be nice to preview/compare different analyse tunings: balanced, more/most highlights, less/least-highlights and legacy, to choose the best looking SDR for the user.

In 3-1 (DoVi MAKER from HDR10, Dolby Algorythm), something similar would be desired aswell to estimate how DV is going to behave when doing the interpolation for the tv capability. I.e: If my DV-enabled tv has 400 nits of brightness for HDR and the content is graded at 1,000 nits, depending on the chosen analyse tuning, the final image interpolated from the 100-nit mandatory trim would be different.

I guess you meant 8-2-4 because 8-2-2 use libplacebo for the SDR tonemapping.

The analysis tunings are filtering that Dolby applies during the metadata creation so you cannot edit it when the metadata has been exported/delivered. The only way to edit/preview the tuning is within Resolve (or whatever grading software you use) during the grading process.
You can use different tunings in the same timeline and if you hover the metadata, it will tell you the tuning used for this particular shot.

Also, is it possible to choose how many DV trims to generate? Ie: 100, 400, 600, 1000

No, you need a DV license for that.
In a cmv4.0 workflow, even if you don't do any manual trim, the dolby system will auto generate L2 at three targets: 100-600-1000nits
In a cmv2.9 workflow, if you don't do trims, the system will not generate any.

You can remove trims with the metafier though. workflow 2-6

And finally, it would be nice to choose desired trim encoding to HDR10. Ie: convert a native HDR10 4,000 movie to a 1,000, 600 or 400 one, to get better tonemapping than a non-enabled DV tv does.

you can already do that with 8-2-4. You can deliver the 48-100-300-600-1000-2000nits trim even if not present in the metadata. When not present, the desired target is created by extrapolating the existing trims.

[Vymrr]

Originally Posted by Kuler087

works fine on mine

I got it working, turned out DV option in settings was turned off when I played your files.. What are the most obvious clips that would show my TV supports CM4? Maybe it's my eyes, but I kind of found it hard to differentiate for the real content clips. For the test files, are all of them CM4.0 ? I can see differences in brightness for the L8 clips at various nits.

[Kuler087]

When cmv4.0 works, you will see brightness changes when the metadata changes.


Example:

[ReciprocalUniverse]

Kuler, few questions here:

1.) When or why would P5.0 be preferred over P8.1? I understand it's proprietary, differs because of PQ with shaping and IPT-PQ-C2 matrix. Is it better generally or else when or why would it be recommended?

2.) With Resolve Studio, are you monitoring HDR with one of the Decklink cards or are you monitoring with the Windows GPU? The reason I ask is because of the quantity of variations of encoded files in your Drive library. With each change of DV metadata are you having to encode a file to see the result of the change? And yes, they all do play for me on my Hisense U8.

3.) Before you encode HEVC or export an intermediate from Resolve with IPT-PQ-C2, are you able to live monitor this color matrix?

[Kuler087]

1- 10bit DV P5 is more efficient than HDR10/P8 when it comes from a 12bit master.




2- Yes, I monitor HDR with my decklink card. I don't think the HDR preview in Resolve is accurate (too dark). Most of the rpu test file in my GD are generated with dovi_tool. You can generate any p8.1 rpu with a json config, and then I use my script DEE (8-2-6) to encode the profile 5 version.
For example, this is the json config I used for my latest FEL vs BL test file. BTW, if this test file doesn't convince one to get a proper FEL P7 player, nothing will.
https://justpaste.it/3p8rw
D:\DoVi_Scripts\tools\dovi_tool.exe generate -j D:\config.json -o D:\P8_generated.bin



3- No, DV tunneling requires the very expensive decklink card but DV tunneling is pretty much useless. You can see the DV mapping for any target on your HDR mastering monitor and make all the adjustments to the trims. DV is graded in HDR and tunneling is mostly for previewing the final product on a consumer TV. You should never make any change to your trim or grade based on what you see on a consumer TV, always make change according to what you see on your mastering monitor.
trims / master preview example: https://slow.pics/c/cTDiL8Mn

[Vymrr]

Originally Posted by Kuler087

When cmv4.0 works, you will see brightness changes when the metadata changes.


Example:

Yes I got that when the L8 slope number changes. Thanks!

[Hellboy.]

Kuler087 I using workflow (4-3) with (TS version), (set MUX=NO) and (set encode_DDP=NO).
The problem is the audio get extracted and converted and i don't need that. How can i stop the audio from extracting and converting.
I try with a movie with "TrueHD Atmos 7.1" and the audio was converted to .wav and .ec3.
Thanks.

Edit: I check the audio and the audio extracted and converted was not the first, was the last one. A FLAC 2.0 commentary track.

[Kuler087]

Because FLAC is not supported in tsmuxer, the script encodes it to pcm.
I added an exception when MUX=NO, try this: https://drive.google.com/file/d/128g...usp=drive_link

[Hellboy.]

Thanks, that worked.

[Vymrr]

I saw on the excel sheet some movies that have a L5 edits text file. Is that supposed to be injected into the movie file? If so what workflow is it?

[Kuler087]

The L5 text files are active area config .json for when you do a dynamic aspect ratio P8 hybrid with metadata from WEB.
you can use them in workflow 1 if you rename the inputs the same and skip the 2nd input.

EG:
D:\movie.mkv
D:\movie.json (L5 config)

[Gatorman3385]

Is it a bad idea to import the CM4.0 levels from a resolve-generated XML into a MEL CM2.9 RPU from the original disc? Should CM4.0 levels only be imported from videos mastered with it?

[Kuler087]

cmv4.0 and 2.9 metadata must come from the same dv analysis, so yes it's a bad idea.