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

[Kuler087]

The Average-Joe calibrated TV is meaningless. Nobody sees SDR at 100 nits, calibrated or uncalibrated.
sigh! ok, if you say so, but please stop, this is nonsense...
and BTW you can do the same SDR to HDR in Resolve, and the luminance reading and colors will be identical to my script.

[wyup]

In Resolve you can do many things. Excuse me, this is not nonsense, this is very relevant.
Mixed SDR and HDR sources are only meant in a HDR project when they are color managed, graded and they have similar average brightness.

It is ages since tvs have more than 100 nits. Evidently, movies in SDR are not meant to be watched at 100 nits and they don't need to be graded at 100 nits, because people watch them brighter. Your LG G5 tv shows SDR with so much brighness by default. You adjust it to taste and watches OK.

If you mix SDR mapped at around 100 nits with HDR masters with different brightness you can't assess picture quality gain because you're not watching them at the same average brightness and this makes evaluation confusing. Most movies will be brighter but that doesn't atomatically make them better. They're just brighter.

[Kuler087]

Saying that a TV calibrated to a target brightness (100–120 nits) can go brighter than that target is nonsense, yes. Clearly, you have no idea how SDR is graded, how it's calibrated, and how it's best viewed.
I do not care how you prefer watching SDR, and this is my last reply about this. Move on and stop following my YouTube comparisons and script if you're not happy. Or maybe go complain to the calibrators and colorists about how they've been calibrating and grading SDR incorrectly all these years, lol...

[wyup]

I don't appreciate your arrogance and disparaging attitude to what I say. You don't read any of my arguments, only say 'nonsense' and don't reason at all. I didn't mention any number of target brightness in particular
Saying that a TV calibrated to a target brightness (100–120 nits) can go brighter than that target is nonsense, yes. Clearly, you have no idea how SDR is graded, how it's calibrated, and how it's best viewed.

All tvs today show SDR by default higher than 100 nits. That's a fact. It's perfectly viewable and tv are tweaked to look good at maximum brrightness. Your top of the line G5 has 471 nits 100% window in SDR.
I don't think it will perform bad at all at 150 nits or higher instead.

For the n-th time, SDR is a relative brightness system, and in principle it's made to look good at whatever brightness you choose. Yes, Resolve and colorspace conversion functions map SDR to 100 nits into a HDR container, because they need to set a point, and 100 nits was kind of the standard for SDR, but it doesn't apply anymore with todays tvs and how people watch tv. It's pointless to watch SDR at 100 nits if you want or need more brightness. Doesn't matter how it was graded. It's made to look good at more brightness.

When you place SDR in a HDR container and watch on a HDR tv you almost always see SDR dimmer than HDR and that isn't representative of the dynamic range of SDR because for the tv you are making a HDR file with the dynamic range of the HDR video, MaxDML in practice for Samsung TVs, which is usually 1,000 nits. So you're placing 100 nits into 1/10 of the reserved curve of the tv, so SDR looks dim. Even if the tv takes MaxCLL, if it is 800 nits, you're using 1/8 of the range for SDR. To me, what it counts though for comparison is average brightness, which'd be MaxFALL avg. Ideally both SDR and HDR should present similar average brightness prior to comparison, and that would consist of transposing the SDR to a similar level. Yeah, that's tough, but I'm making my point. How are you going to compare 100 nit SDR to a 4,000 nit HDR version? You can't evaluate dynamic range between both. More average nits don't necessarily means higher dynamic range, only brighter.

I don't say your clips are nonsense as you say to me, and your scripts and channel are indeed good work. But I'm trying to make a point with a fair reasoning. And things are not black or white, no pun intended.

Sources:

BT.1886, the EOTF for SDR blu-rays:
https://www.wikiwand.com/en/articles/ITU-R_BT.1886
https://www.itu.int/rec/R-REC-BT.1886/en

Its definition doesn't mention 100-nits, just from V=0 to V=1. Only for a EOTF-CRT matching it sets 0.1 or 0.01 for black level and 100 nits for white. But it's for a alternative CRT approximation. We no longer live in the CRT age.

[xooyoozoo]

My TV definitely does not like cmv2.9 4000 nit MDL and starts tonemapping out of the gate (based on your tv-led response test files (https://docs.google.com/spreadsheets/d/15i0a84uiBtWiHZ5CXZZ7wygLFXwYOd84/edit?gid=1289366200#gid=1289366200)). My TV starts tonemapping at ~1950 nits otherwise with cmv4 RPUs. I've started analyzing my collection to see which are 4k MDL cmv2.9 to see which to prioritize for generating cmv4.

Couple random questions:


If an RPU has no L2-1000 or L2-600 trims but has an L2-100, is that L2-100 still getting used for tonemapping purposes by a bright TV?
Is there any benefit to replacing L2 trims in generated cmv4 with the original L2 trims from cmv2.9?

[Kuler087]

1. If the RPU MDL is higher than your TV target, yes, the 100-nits trim should not be used. So in your case, it doesn't use the 100-600nits trims when the RPU MDL is 1000nits. You can confirm with these: https://drive.google.com/drive/u/1/folders/1J-jBAHSgHlixq9Lkjc_p98JnvY8naE0X
2. No, and you should never mix metadata from different versions of the analysis algo

[SamuriHL]

Can you describe in a bit of detail the output blanking in Resolve for titles that have multiple aspect ratios? Nolan films with IMAX scenes embedded within them is a great example. In your video you set the output blanking for the main aspect ratio but then it looks like you set it per scene for the IMAX shots? Not 100% sure how that works. Any hints would be appreciated. Thanks!

[Kuler087]

Resolve blanking has two main options:

1- Timeline blanking

2- Per-clip (shot) blanking

You first set the timeline blanking to match the main aspect ratio of your project. Then, for any shots that have a different aspect ratio, you need to override the timeline blanking by applying per-clip blanking.

You don’t have to adjust each IMAX shot one by one. You can select a group (or even all) of the IMAX shots and use your mouse wheel to copy the grade (which includes the blanking) to all selected shots.

As shown in the video, for this grade/blanking copy-paste method using the mouse wheel to work, you must be outside of the blanking page. If you're inside the blanking edit page, you won’t be able to copy or paste the data.

[SamuriHL]

Thanks for that. I have a couple I'll try it on maybe this weekend and see how that goes. Really loving the results so far of this process, though!

[Eikichi]

Hi all,

I've been using dovi_scripts for a while now and I have a question.
I use it mainly because I have an LG OLED that only supports Dolby Vision via MP4 files.

To fix this, I use dovi_script gui.
I put one of my Dolby Vision MKVs in it, select MP4 output, and simply click on dovi_muxer, and that's it.
I end up with a working Dolby Vision MP4 that actually launches Dolby Vision mode once I play it on my TV.

But it seems surprisingly too easy to me, so I'd like to know if this is really the right method to do it?
Is the MP4 file I get really a Dolby Vision file, or does it trigger the mode on my TV but it's not "real" Dolby Vision?

Thanks to anyone who takes time to explain this to me. :thanks:

[Kuler087]

But it seems surprisingly too easy to me, so I'd like to know if this is really the right method to do it?
Is the MP4 file I get really a Dolby Vision file, or does it trigger the mode on my TV but it's not "real" Dolby Vision?


Yes, it's real Dolby Vision. MP4 is just a container. It has better compatibility with internal TV players, but it doesn't affect the Dolby Vision metadata itself.

[dkangel]

hello
i have a question, some p7 FEL remux have black bars but L5 are 0/0/0/0
is it normal ? do i to correct it ?
thank you

[Kuler087]

yes some releases have incorrect L5. You can correct it if you want.

[dkangel]

thank you
it seems that some releases have also incorrect L5 276/277 instead of 277/277
my plans are to buy an am6b and i've learn by you that this player is sensible to L5 :)

[Kuler087]

yep, I see that often.

[ralberti]

Hi all,

I have the latest DoVi Scripts (3.0.7) I followd the installation instructions and installed also the needed additional tools. I did not change anything in the settings of the script file. I am trying to perform a conversion from P7 to P8 (option 4-1) but the result is a file in HDR10 format instead of DV P8. I am not sure if I am doing something wrong. Can you help me to figure out what may be the problem. This is the Log Information given by the script:

===============
- INPUT INFO -
===============

L5 Left offset: 0
L5 Right offset: 0
L5 Top offset: 276
L5 Bottom offset: 277
Enhancement Layer: FEL
L2 trims: 100 nits
DoVi source min_pq: 50 nits
DoVi source max_pq: 4000 nits
HDR10 BL input MDL: min: 0.0050 cd/m2, max: 4000 cd/m2
HDR10 BL MDP: Display P3
Resolution: 3840 x 1604 @ 23.976

WARNING. WARNING. WARNING.
Profile 7 with Full Enhancement Layer (FEL) detected...
The output could be wrong if FEL expand the brightness...
SEE: https://docs.google.com/spreadsheets/d/15i0a84uiBtWiHZ5CXZZ7wygLFXwYOd84/edit?gid=828864432#gid=828864432

Presione una tecla para continuar . . .
tsMuxeR version git-7f8667d. github.com/justdan96/tsMuxer
B-pyramid level 1 detected. Shift DTS to 2 frames
0.0% complete
Decoding AC3 stream (track 2): Bitrate: 224Kbps Sample Rate: 48KHz Channels: 2
Decoding TRUE-HD stream (track 3): TRUE-HD. Peak bitrate: 3189Kbps Sample Rate: 48KHz Channels: 8
Decoding PGS stream (track 4): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 5): Resolution: 1920:1080 Frame rate: 23.976
0.8% complete
Decoding PGS stream (track 6): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 7): Resolution: 1920:1080 Frame rate: 23.976
44.1% complete
TRUE-HD stream (track 3): bad frame detected at position00:49:32,943. Resync stream.
Decoding TRUE-HD stream (track 3): TRUE-HD. Peak bitrate: 3507Kbps Sample Rate: 48KHz Channels: 8
96.8% complete
TRUE-HD stream (track 3): bad frame detected at position01:49:21,432. Resync stream.
Decoding TRUE-HD stream (track 3): TRUE-HD. Peak bitrate: 3879Kbps Sample Rate: 48KHz Channels: 8
100.0% complete
Processed 167628 video frames
100.0% complete
Flushing write buffer
Demux complete.
Demuxing time: 10 min 14 sec
converting and injecting RPU...
Rewriting file with interleaved EL NALUs..

=================
- MUXING TO MKV -
=================

mkvmerge v91.0 ('Signs') 64-bit
'D:\DoviScripts 3.0.7\videofile_P8.hevc': Using the demultiplexer for the format 'HEVC/H.265'.
'D:\DoviScripts 3.0.7\videofile.mkv': Using the demultiplexer for the format 'Matroska'.
'D:\DoviScripts 3.0.7\videofile_P8.hevc' track 0: Using the output module for the format 'HEVC/H.265 (unframed)'.
'D:\DoviScripts 3.0.7\videofile.mkv' track 1: Using the output module for the format 'AC-3'.
'D:\DoviScripts 3.0.7\videofile.mkv' track 2: Using the output module for the format 'text subtitles'.
'D:\DoviScripts 3.0.7\videofile.mkv' track 3: Using the output module for the format 'TrueHD'.
'D:\DoviScripts 3.0.7\videofile.mkv' track 4: Using the output module for the format 'HDMV PGS'.
'D:\DoviScripts 3.0.7\videofile.mkv' track 5: Using the output module for the format 'HDMV PGS'.
'D:\DoviScripts 3.0.7\videofile.mkv' track 6: Using the output module for the format 'HDMV PGS'.
The file 'D:\DoviScripts 3.0.7\videofile_DV.mkv' has been opened for writing.
'D:\DoviScripts 3.0.7\videofile_P8.hevc' track 0: Extracted the aspect ratio information from the video bitstream and set the display dimensions to 3840/1604.
The cue entries (the index) are being written...
Multiplexing took 14 minutes 12 seconds.
Deleting TEMP folder...


Start time: 11:08:33,80
End time: 11:53:19,54
Time taken: 0:52:46

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?


Kind Regards

[Kuler087]

set the display dimensions to 3840/1604
TRUE-HD stream (track 3): bad frame detected at position00:49:32,943. Resync stream.


looks like there are issues with your input. This workflow is meant for untouched P7 remux

[Black Ops]

Off topic question but thought i might aswell ask an expet. In your opinion what is the best way to convert a 4k hdr video to SDR? which algorithm is "good enough". Most 4k releases are HDR but some people dont have good HDR tv and SDR looks better. Of course if the rip has dolby vision you can extract the SDR 100 nit grade and you are good to go. But in cases where there is only a hdr10 stream, its not possible to do so

[Kuler087]

For those without original DV metadata. I generate a 100nits trim in Resolve with the balanced tuning and a slight raise in gamma and gain(bit too dark otherwise).
If it's too much work, then use libplacebo (8-2-2)

https://i.ibb.co/H1RpkVG/chrome-wx-RIk-DO2-VD.gif

[Gatorman3385]

For those without original DV metadata. I generate a 100nits trim in Resolve with the balanced tuning and a slight raise in gamma and gain(bit too dark otherwise).
If it's too much work, then use libplacebo (8-2-2)

Is a Dolby Vision Trim license required to use the trim controls? That option in not enabled for me. I'm using the paid version of Resolve Studio.

https://imgur.com/ygXjE6M.png

[Kuler087]

yes Trims Control requires a license.
check your pm

[Gatorman3385]

Are these trim adjustment suggested for DV to SDR when there is original DV metadata?

[Kuler087]

No, only when you generate from scratch. I don’t think you can edit original or imported metadata in Resolve.

The original imported metadata contains all the trim adjustments made during the color grading process by the colorist, so the artistic intent is preserved 100%.

[wyup]

Hi, what's the difference between these workflows when converting from DV HDR to SDR, apart from x265 and PRORES codecs?
Is Dolby CM_Offline DV Trim Pass delivery an advantage? Doesn't 8-2-2 account for trims?

8-2-2 X265: HDR to SDR (DVP7/DVP8/DVP5/HDR10/HLG)
8-2-4 PRORES: DV to SDR (Dolby CM_Offline DV Trim Pass delivery)

I tried 8-2-4 but had to stop the script because it was using huge amounts of storage in ProRes 422 HQ, 700 Mbps or so. Can I change the output codec and bitrate for 8-2-4?

[Kuler087]

8-2-2 uses libplacebo for SDR tone mapping and completely ignores the Dolby Vision trims.

8-2-4 can deliver any original Dolby Vision trim pass, but this workflow requires a ProRes input and also outputs to ProRes, so it needs a lot of storage space. It also suffers from the same slow performance bug as CM_analyze (3-1), which is why I’ve never actually used it. Resolve is much faster (https://www.youtube.com/watch?v=lM56zLpKDQ8)and achieves the same quality.

[wyup]

Cool. By curiosity, is the cm-analyze bug still present on latest May 5.6.1 version of Dolby Tools?
As a personal quest, I'd like to compare libplacebo BT.2446A HDR10 to SDR tonemapping to DV automatic 'balanced' own.
I believe BT.2446A woud be more appropiate for this task than libplacebo's default BT.2390.

It apprears that DoVi Scripts libplacebo uses an Avisynth 'wrapper' or 'plugin interface' avs_libplacebo 1.5.2 version from dec 2023 that comes itself from an older Vapoursynth one, while ffmpeg builds will use a more recent snapshot like v7.351.0-21-g686ed7e for now. Being a library in continous development it would make sense to use latest version.
Why doesn't Avisyth release more up to date versions of its libplacebo wrapper?

[Kuler087]

Yes the slow performance bug is still present in the latest version but this version did fix the crash I was getting on Windows 11 PC.

libplacebo has many different tone mapping modes and you can test any of them(and more) with DoVi_Scripts. lines 104-113

:: choose if you want to use dynamic peak detection in 7-2 / 7-1 / 8-2-2 true or false (default= false) true or false, see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set peak_detect=false
:: choose the SDR tone mapping function for 7-2 / 7-1 / 8-2-2 (default = bt2390) choices are: "clip", "st2094-40", "st2094-10", "bt2390", "bt2446a", "spline", "reinhard", "mobius", "hable", "gamma", "linear", "linearlight" see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set tone_mapping_function=bt2390
:: choose the SDR tone mapping mode in 7-2 / 7-1 / 8-2-2 choices are: (default = perceptual") "perceptual", "softclip", "relative", "saturation", "absolute", "desaturate", "darken", "highlight", "linear" see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set gamut_mapping_mode=perceptual
:: This helps block out annoying "sparkling" or "flickering" due to small variations in frame-to-frame brightness for the SDR tone mapping mode in 7-2 / 7-1 / 8-2-2 (default=20.0) see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set smoothing_period=20.0
::Which percentile of the input image brightness histogram to consider as the true peak of the scene for the SDR tone mapping mode in 7-2 / 7-1 / 8-2-2 (default=99.995) see info here: https://github.com/Asd-g/avslibplacebo?tab=readme-ov-file#tone-mapping
set percentile=99.995

vapoursynth vs avisynth version, I don't know, but I don't think anything changed regarding the HDR to SDR tone mapping.

[ralberti]

looks like there are issues with your input. This workflow is meant for untouched P7 remux

Thanks for you answer. The error you are mentioning is in an audio track not in video. But I tried a lot of different files, below another example without apparent error messages. The thing is that if I process the same video file with an older version of the script (version 3.0.0) it works great and the output is an DV P8 file, but with the 3.0.7 version the output is an HDR10 file. That why I asume that it is not a problem with the video file itself and that something is working different in version 3.0.7.


============
- P7 TO P8 -
============

-------------------------------------------------------------------------------------
--Convert any P7 file to profile 8
--Input can be MKV/TS/M2TS/MP4/BDMV/MPLS/RPU
--Tutorial: https://youtu.be/sBUL2gjhqEE?list=PLFGpkrmX_eOL2Dre1ZyIJP2uMtcQYH8ql
-------------------------------------------------------------------------------------

Drag and drop a P7 DV file (BDMV folder/mpls or m2ts/ts/mkv/mp4) and press enter...
"D:\DoviScripts 3.0.7\video DV7.mkv"
WARNING: Output path "D:\DoviScripts 3.0.7" has only 85GB of free space. Processing large file may not work....
Do you want to convert the audio to DDP? (default= n )

--> YES= y
--> NO= n
n

Reading input tracks format/id/language...
Done.
tsMuxeR version git-7f8667d. github.com/justdan96/tsMuxer
HEVC muxing fps is not set. Get fps from stream. Value: 23.976
B-pyramid level 1 detected. Shift DTS to 2 frames
0.3% complete
Flushing write buffer
Demux complete.
Demuxing time: 0 sec
Parsing RPU file...
Exporting serialized RPU list...
Done.


===============
- INPUT INFO -
===============

L5 Left offset: 0
L5 Right offset: 0
L5 Top offset: 0
L5 Bottom offset: 0
Enhancement Layer: MEL
L2 trims:
DoVi source min_pq: 50 nits
DoVi source max_pq: 4000 nits
HDR10 BL input MDL: min: 0.0001 cd/m2, max: 1000 cd/m2
HDR10 BL MDP: BT.2020
Resolution: 3840 x 2160 @ 23.976
Output Path Free Space: 85gb


tsMuxeR version git-7f8667d. github.com/justdan96/tsMuxer
B-pyramid level 1 detected. Shift DTS to 2 frames
0.0% complete
Decoding AC3 stream (track 2): Bitrate: 256Kbps Sample Rate: 48KHz Channels: 5.1
Decoding AC3 stream (track 3): Bitrate: 256Kbps Sample Rate: 48KHz Channels: 5.1
Decoding PGS stream (track 5): Resolution: 1920:1080 Frame rate: 23.976
0.4% complete
Decoding PGS stream (track 4): Resolution: 1920:1080 Frame rate: 23.976
100.0% complete
Processed 238900 video frames
100.0% complete
Flushing write buffer
Demux complete.
Demuxing time: 10 min 15 sec
converting and injecting RPU...
Rewriting file with interleaved EL NALUs..

=================
- MUXING TO MKV -
=================

mkvmerge v91.0 ('Signs') 64-bit
'D:\DoviScripts 3.0.7\video DV7_P8.hevc': Using the demultiplexer for the format 'HEVC/H.265'.
'D:\DoviScripts 3.0.7\video DV7.mkv': Using the demultiplexer for the format 'Matroska'.
'D:\DoviScripts 3.0.7\video DV7_P8.hevc' track 0: Using the output module for the format 'HEVC/H.265 (unframed)'.
'D:\DoviScripts 3.0.7\video DV7.mkv' track 1: Using the output module for the format 'AC-3'.
'D:\DoviScripts 3.0.7\video DV7.mkv' track 2: Using the output module for the format 'AC-3'.
'D:\DoviScripts 3.0.7\video DV7.mkv' track 3: Using the output module for the format 'text subtitles'.
'D:\DoviScripts 3.0.7\video DV7.mkv' track 4: Using the output module for the format 'text subtitles'.
The file 'D:\DoviScripts 3.0.7\video DV7_DV.mkv' has been opened for writing.
'D:\DoviScripts 3.0.7\video DV7_P8.hevc' track 0: Extracted the aspect ratio information from the video bitstream and set the display dimensions to 3840/2160.
The cue entries (the index) are being written...
Multiplexing took 15 minutes 50 seconds.
Deleting TEMP folder...


Start time: 22:42:08,46
End time: 23:30:21,69
Time taken: 0:48:21

The script has been completed. Do you want to quit or go back to main menu (q or m default=q)?


Kind regards,

[Kuler087]

Your log from the other day shows that your video is not an untouched P7 remux. The resolution is cropped, which means the video was re-encoded.
Even if it worked on older versions for whatever reason, the output will still be incorrect.

[ralberti]

Your log from the other day shows that your video is not an untouched P7 remux. The resolution is cropped, which means the video was re-encoded.
Even if it worked on older versions for whatever reason, the output will still be incorrect.

Yes the one I posted the other day was sort of a corrupt file and does also not work correctly on older versions, but the one I posted today is working on older versions producing a correct DV P8.1 profile but with the new script version an HDR10 file.

[Kuler087]

Please, give me a sample so I can reproduce it.

[ralberti]

Please, give me a sample so I can reproduce it.

I think I found it after a lot of time executing step by step both scripts and found that after job.4.1.1 in the demux section they behave different due to the value of the variable %ffmpeg_pipe% (OLD script=YES; NEW script=NO). So the old script goes over the :skip.demux way while the new over the :skippipe way. I change the advanced settings where ffmpeg_pipe is set by default to NO to YES and was able to convert to a DV P8.1 file like with the old script.

I now wonder why it does not work with the ffmpeg_pipe=NO option.

[Kuler087]

Unless you provide a sample, I can’t tell you.
The old FFmpeg pipe demuxing mode is faster than mkvextract, but also riskier. I’ve seen some processed files get broken because of FFmpeg.

[ralberti]

Unless you provide a sample, I can’t tell you.
The old FFmpeg pipe demuxing mode is faster than mkvextract, but also riskier. I’ve seen some processed files get broken because of FFmpeg.

I've send you a PM with a link to a sample file.

Kind regards

[Kuler087]

Your file Enhancement Layer hevc is empty with a frame-by-frame RPU. I'm not sure why ffmpeg piping is still able to process the file, but it doesn't appear to be an original P7 rip.

[Gatorman3385]

Is there a way to add DV metadata at 24fps to a video file at 23.976fps?

[Kuler087]

There is no frame order difference between 23.976 and 24fps. Just sync the metadata as usual.

[Gatorman3385]

I remember a while back the default bitrate for EAE eac3 7.1 was changed to 1028 from 1536. Plex has made changes to EAE to fix choppy for high bitrate audio. I have a version from 2022. Might it be worth trying the latest version? What was the reason for lowering the default bitrate?

[Kuler087]

EC3 1536kbps didn't play well on the Sony X800m2 (and webos kodi IIRC)

[danny2576]

Hello
Can DoVi Profile 5 be converted to Profile 8 ?

Thanks

[Kuler087]

Yes, workflow 8-2-1. (Re-encoding is required).

[danny2576]

Thanks

[Gatorman3385]

When playing the Fel Test St DI P7 CMv4 4000nits test file on my am6b+, I don't see the CMv4.0 messages. It just stays on CMv2.9 messages. This is a TV compatibility issue, correct?

[Kuler087]

You mean the osd?

I have more cmv4.0 test files here:
https://drive.google.com/drive/u/1/folders/1BD0FBOjBnf5gu-sUi5U4BUeyGDQEGJuF

[Gatorman3385]

I wasn't able to add pictures at the time and struggled to find the right words. The OSD displays cmv4.0 correctly. Here's what I see. VLC on PC is first, followed by am6b+. Both are at the 29 sec mark. I'll try the other test files.

https://imgur.com/QTss87i.png

https://imgur.com/GkwZiUj.png

[Kuler087]

This test file is designed specifically for testing FEL. It freezes after the Level 2 test.
To properly test CMv4.0, use the test files I linked in my previous response.

[dkangel]

Hello,
i found a hybrid version of the star wars movies
i have the mesaage that there are consecutive frames
so i'm using scene cut edit and remove scene cut flag
here is what i have
have i to delete scene cut 1 to 15 so it wil be 0 16 40
or delete 1 to 16 so it will be 0 40 ?

0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
40
88
133
313
317
350
534
759
.....


Thank you to help my ignorance

Edit : second question, how do i know if a tv can play cmv4.0 ? or is it the player ?

[Kuler087]

Yes select to remove 15 cuts when asked. This doesn't really matter or affect quality, though. You can leave it like this. These consecutive cuts happen when you duplicate frame 0 to sync the metadata.
Always duplicate frame 1, not frame 0 which is almost always a scene cut frame. Dovi_scripts duplicate frame one by default FYI, so this hybrid was not done with my scripts.

You can check cmv4.0 support with this file. If supported, there will be visible brightness changes when the metadata changes.
https://drive.google.com/file/d/1TzYzbhgEVwfFxaL2ZoRcJxAXc4m9Eqbo/view?usp=drive_link

https://i.ibb.co/m5SqVSQ4/Application-Frame-Host-Akg-TAtriy-Q.gif

[dkangel]

i'm looking for a new tv with dolby vision so that's why i'm asking if the cmv4.0 is player dependant or tv dependant
if it's tv dependant i want to know if the tv is cmv4.0 capable before buying
i can't test your video file until then

and thank you for your explanation about consecutive scene cuts, it's very clear !!!

[Kuler087]

both the player and TV must support it...
All the TVs made after 2019 support cmv4.0