@Andrew-Stevenson

Thank you so much (!) for providing an example of your source and the MediaInfo readout. Doing so has put your inquiry in a whole new light, one that may lead you to a resolution, by suggesting more appropriate shooting and render formats.

• Your source footage is DolbyVision(r) HLG. This presents a couple of problems for Vegas Pro, one being a licensure / compatibility issue, the other being the need to choose a render format more suited to your HLG source.
• Vegas does not support DolbyVision due to licensing restrictions. The Dynamic Metadata track, therefore, cannot be imported, and one is faced with constantly changing color information that is unmitigated in the software. The parent company has hinted that this is probably not going to be resolved any time soon. At this time, I know of no free video converters that decode DolbyVision to conventional formats.
• 

@mark-y That's probably only important for a conversion to a another dynamic metdadata t HDR format like HDR10+?

Dolby Vision decode is useful for tone mapping to a SDR monitor for color grading while the entire workflow remains HDR from source to color space to encode. You can see when it encodes and it drops the tone mapping.

Dolby Vision HDR is usefull in a HDR-TV or other HDR monitor, that is capable to decode Dolby Vision HDR. But not in an SDR monitor - since Dolby Vision is one of the HDR formats availabel. And in an HDR monitor that supports Dolby Vision HDR, the metadata are read to adjust every take of the video. But the metadata are generated during editing - typically in tools like Resolve if someone has invested in an individual Dolby Vision HDR licens.

And in this example video, it is the autmatic of the small iphone that reduces the aperature, since the motive becomes brighter due to the sun caused by the camera move.

By the way, you see also in Resolve the blocking, what was really a discussion point in this request.

@Wolfgang S. Yes the blocking is really there, Windows players can sometimes create artifacts that aren't actually there when they use the microsoft HEVC decoder for 10bit HDR and wondered if the player was actually correct or was Vegas + player both incorrectly decoding.

Editing HLG is not as easy as it could be, many people aren't actually interested in HDR, they want the most information possible from their camera to create highest quality SDR version. Advice here is to not use HDR, but the tone mapping + scopes makes it very easy for working with an output of 100nits or 1000.

Hard to find out which editors use Dolby Vision decode, Chat GPT lists 5, but I don't trust it, although Dolby Vision decode would be useful for iphone owners if there's a huge cost both in license fee and man hours to implement it isn't likely to ever happen and unfortunately due to priorities nor should it.

The blocking in the original footage is found both in the preview of Vegas and Resolve - we are not talking about Windows player.

And HLG was never designed as acquisition format for HDR. It should be a delivery format only.
The only advantage is, that the gamma curve is compatible with the gamma curve of SDR, but the gamut is not.

Enough people use HDR today, Netflix is full of HDR productions. But the advice is to shoot in log and grade to HDR10. If one shoots in HLG, then hard cuts should take place only - and not transformation.

Decoding of HLG is not an issue at all. Vegas is able to do so.

 

I'll look forward to your thread!

I need to do some more experimentation with the CinemaP3 app on the iPhone to see what codec is uses under various conditions. I have some footage that is DolbyVision and others that are not. I have found that it is easy to disturb the settings the app uses so some of the footage I captured was in 50fps and some in 24fps or 30fps and there are differences in the MediaInfo of the clips. I will be trying to identify what is the discerning part of the settings that makes the difference between a blocky or non-blocky sky.

Andrew, I haven't looked closely at the blockiness, but I will when I post and maybe make an opinion. It may or may not be secondary to your decoding and delivery parameters; also note that I am unable to address any issues that may have cropped up in Vegas Pro 21 or 22, noting that some are being reported.

The CinemaP3 app on your phone "may" mean a transform for P3 monitors; it will be helpful if you will tell me your monitor make and model number, so we can be sure the output transform matches your monitor's color gamut, as well as conforming to your source and compatible output format.

Also, could you share your intended use for this video? Is it for your own viewing, or for sharing on Youtube, Social Media, or direct download?

I did some research on the CinemaP3 app and it has luts for Resolve (which I have). CinemaP3 shoots in a number of modes but the only one that triggers the iPhone to show the 'HDR' icon and display the video in HDR on the phone is:

"Cinematic HLG 2020 (10-bit HDR) which it describes as:

Color Primaries: ITU-R BT.2020

Transfer Function: ITU-R BT.2020: ITU-R BT.2100 (HLG)

YCbCr Matrix: ITU-R BT.2020

Code Points 9-18-9

The information on HDR is here:

https://www.blackburnapps.com/cinemap3/technicalGuide03.php

The video is just for my own viewing in two formats - Rec 709 and HDR for my display. I am also interested in knowing what I need to do to do a version for YouTube that would play in HDR.

The screen is a VESA certified DisplayHDR 600 (model MSI MS321UP.) Displays 95% of P3. Not professional but good enough for me, for now.

I am open to suggestions on what the best settings for the media properties, project properties and render settings should be for Vegas.

@Andrew-Stevenson, for your comparison. Tell me if you can't download. Will delete in 3 days.

https://drive.google.com/drive/folders/1P1fvTHeFsfe8cLR544Sg43Gq3piO-4ik

There were two clips, not sure which one you are referring to. Was the gh5* rendered on Vegas 21 or 22? It had the blocky sky which I think has been resolved as the iPhone. What is interesting is that it didn't have the brightly coloured random pixels issue which arrived in my Vegas 22 render.

The P1020437 clip wouldn't play.

Curious why you couldn't deal with the clip - I deleted, but interesting we were shooting the same day and almost the same time.

So, in the same link there's another HDR render for your reference.
Your footage OK.
Too much subjective conclusions not OK.

Don't ask how it's done, you'd feel thankful here to be guided by tons of protfressors.
I'm an outsider.

@Andrew-Stevenson

1. Thank you for sharing your intended use for the video.
2. Thank you for providing your monitor information. I'm quite a bit envious here, because I'll never be able to afford a full P3 monitor such as yours.
3. Thank you for doing the research on CinemaP3. I'm a little behind the learning curve there, but I will be doing some more reading.
4. With the zipped project I gave you in the Off Topic thread, and a new 10 bit sample render I will make soon, you should be able to decide which of the approaches touched on here are best suited to your purpose.

As for the secondary question, whether Vegas 22 now supports DolbyVision(r) decoding of the dynamic metadata chunk, and having been unsuccessful in finding confirmation of that theory on the Vegas website, I have since found the original sample clip I used in my initial inquiry, in 2021.

• This clip is useful in determining the success in decoding the DolbyVision color information, because of the pronounced shift apparent in the blue-yellow axis when the lighting changes beginning at 1:20. If the DolbyVision metadata chunk is being decoded properly in Vegas, this pronounced color shift will simply not occur or at least be more subtle.
• 
• Anyone can download the original Dolbyvision MOV clip for their own testing here.
• https://drive.google.com/open?id=19oPn5_pfqLbkRsiRCnQzrxpCKF7etdos&usp=drive_fs

If what was said above is factual, and some licensing agreement now exists, such that DolbyVision decoding and Dolby Digital AC3 are now supported in Vegas 22, I will buy it. @VEGASDerek

I am eagerly awaiting some more testing of this notion, and perhaps posting your own results in a separate thread would be better, as the discussion is secondary to the main topic, which seems to have pretty much run its course . . .

;?)

If I dare say @Andrew-Stevenson's clip OK, that's because the data/bit rate still around 30mbps, if less than 20mbps for a dimension of 10bit4k, it encourages me as if I will make gold from the air, not to mention what dooolby...

HDRvsiPhone12

For the kids fun:

https://drive.google.com/drive/folders/1P1fvTHeFsfe8cLR544Sg43Gq3piO-4ik