Dolby Vision now possible through MP4 Mux.

[HotFudge]

In the script 3-1 it works properly, I just tested it.
If you do the xml in resolve , you have to edit L5 when you inject in 1-1 because otherwise, the dovi_tool cannot know which side is 281 or 280 but the analysis itself in resolve is correct.

I updated to you 1.9.8.6 scipts and yes you are right your scripts work properly.

Resolve still gives top 280 bottom 281 (when I input top 281 bottom 1880 in the blanking section) so i guess i just edit the L5 for resolve xml's

Cheers

[johnjon94]

In instances when the DV video track is letterboxed, but the HDR track is cropped - how should the RPU be adjusted?

For instance -
Jack Ryan Season 4 Amazon -
DV: 3840x2610, HDR: 3840x1600

[RESET_9999]

always match L5 to the BL you're injecting
No letterbox = 0

[speeddemon]

Has anyone figured out why CM_Analyze gets so slow sometimes?

[Gatorman]

btw, I got a response from Dolby about the Cm_analyze.exe slow performance:

Our Professional Tools make use of Apple’s ProRes decoding library and we have identified performance bugs, including lack of GPU accelerated decoding on Windows and Linux, and a severe performance hit when running on some AMD chips, including their high-performance scalable EPYC chips.

Unfortunately, we are dependent on Apple updating their ProRes libraries to get this fixed.
Until we get an update from Apple, the only recommendation we can offer is to use JPEG2000 which has full GPU decoding support.

I'm sorry I can't give you any better news.
Let me know if there's anything else we can support with.

Thanks,

Michael

[deadchip12]

Recently I have encountered more freezing on my x700 than ever before. Looks like a problem between my 4TB external HDD and the bluray player. A lot of the times folders inside the hdd won't show up at all and turning off the player then will make it freeze (black screen - unable to reboot until I unplug and replug the power adapter). Playing a video (regardless of whether it is in 4k or 1080p, HDR or SDR) and exiting it midway will make the player freeze as well. Very frustrating. Any ideas why?

[Amaury]

I everyone,

I downloaded DDVT TOOL but I’m having a hard time understanding how DV works. I hope someone can help me understand better.

For exemple I have a HDR remux and I would like to inject a DV layer from another source (same number of frames, but the DV source is cropped), do I have to add the base layer and the rpu or just the rpu ? Is there a specific order ?

If I understand correctly DV is based on frame number, if I want to convert a movie from 23,976 to 24 fps do I have to edit something ?

Thanks,

Amaury

[skull88]

Amaury,

That's another tool with its own dedicated thread over at doom9, so I recommend visit there: https://forum.doom9.org/showthread.php?t=183479
As for DoVi_Scripts, which is mostly discussed here, you should read all of the information first in the readme on github and try it first, then ask any remaining questions.

[speeddemon]

Now the problem is that most of the CMv4.0 movies only have a 100nits L8 trim pass which is obviously not used in DV playback but they do have proper L2 trims that are ignored on cmv4.0 devices (shield/firestick/appletv/internal tv ). So you get inferior quality on those devices unless you remove the CMV4.0 block.

@RESET is this still true?

[RESET_9999]

yes, I always remove cmv4.0 when it doesnt have L8 but has proper L2 trims.
The bluray Wierd Science Is a good example. It's two times brighter in cmv4.0 because the very strong L2 trims are not used.

[speeddemon]

yes, I always remove cmv4.0 when it doesnt have L8 but has proper L2 trims.
The bluray Wierd Science Is a good example. It's two times brighter in cmv4.0 because the very strong L2 trims are not used.

Would you consider maintaining a list on your DoVi Google Sheet of all these rules you follow? I'm up for writing the first draft for you if you want some help.

[RESET_9999]

Well this is where it gets strange, I think only two times i've seen a cmv4.0 with active L8

[deadchip12]

Thanks so much! Apologies, but I am not yet well-read on the CMV4.0 vs CMV2.9 discussion. Is there a reason one would prefer one versus the other? I'm guessing it is more future-proof, but at this time most hardware doesn't support it? Is there a downside to keeping it?

First, most of the movies are done in CMV4.0 but exported in CMV2.9.

CMV4.0 is backward compatible with cmv2.9. The trim passes (100-600-1000nits) are done in the level 8 for cmv4.0 and level 2 for cmv2.9.
When a device and the rpu are CMV4.0, the L2 trims are ignored because it will use the L8 trims which is the proper behavior.

Now the problem is that most of the CMv4.0 movies only have a 100nits L8 trim pass which is obviously not used in DV playback but they do have proper L2 trims that are ignored on cmv4.0 devices (shield/firestick/appletv/internal tv ). So you get inferior quality on those devices unless you remove the CMV4.0 block. The test files (made with original metadata from the movie Puss in boots) show exactly the problem and I bet this is the reason why we do not see a lot of CMV4.0 movies because the colorist has to do the trim passes two times (L8 + L2).

In my script, you can use 2-6 to export the trims to a text file and verify the raw data. So if you use a CMV4.0 devices, you might want to inspect your movies for cmv4.0 metadata (mostly amazon DV and movie anywhere web-dl ) .

Damn this is becoming more and more complicated day by day.
Any guidelines for the sony x700? What do I need to inspect a movie for before I can watch it without any image degradation?

[RESET_9999]

x700 doesnt support cmv4.0 so it doesnt matter

[RESET_9999]

ok, I'm starting to understand what's going on with the different RPU responses on players in TV-LED and in LLDV. It seems the x700/x800m2 almost completely ignores L1 and always tone map to the TV edid target.

For example in TV-LED, with this L1 maxpq test file, it goes from L1 100 nits to 10 000nits and the content is 3132nits.
https://drive.google.com/file/d/1gctmX1 ... drive_link

On the Shield, C2 internal apps and ATV, it's totally clipped at 100nits L1 and it gets to proper brightness with higher L1 values.
On the x700/x800, at L1 100nits , it's already tone mapped to the TV edid( no clipping, proper brightness) and the higher L1 values barely have any effect because it doesn't have to.

The x700/x800 approach might be safer in case of bad DV metadata (static DV) and guaranteed to never clip but this approach will be less accurate when the colorist decides to modify L1 (blend or copy metadata) because for example if the colorist decides to copy a couple of shots together at 400nits and some of these shots/pixels are brighter (1000+), the x700/x800 would respond differently and always tone map to the edid while the shield and C2 internal apps, it would get tone mapped brighter. So even in TV-LED the player has an impact on the TV RPU processing.


All of this is easy to see and quite obvious with the maxpq test file I posted but then it gets a bit more confusing with the color clipping pattern. (still talking about TV-LED)Using this 0-4000nits pattern with L1 set to 100nits, now the x800/shield and C2 internal player behave exactly the same and clip RED/GREEN at 1000nits while the AppleTV RGB are clipped evenly at 1000nits.
https://drive.google.com/file/d/1oxQq0R ... drive_link

In other words in TV-LED, I believe the x700/x800 might be safer for bad metadata and works properly when it needs to but sometimes less accurate when the colorist starts playing with L1.
BTW, I started measuring all the player with different RPU and pattern(TV-LED measurements coming up tomorrow): https://docs.google.com/spreadsheets/d/ ... 1222148710
I really don't understand how Dolby could have implemented DV so differently in all those devices, not a single one behaves the same and the all cmv2.9 devices that can't do true TV-LED are totally broken when the TV edid is higher than the RPU mastering display.

Also, the x700 and x800m2 behave quite differently in LLDV. Strangely the x800m2 LLDV reacts more to L1 like the cmv4.0 devices but behaves differently than in TV-LED using the same target edid.
https://slow.pics/c/P5BmU0ms