Unfortunately an error appears and the plot is not createdRESET_9999 wrote: ↑Tue Jun 20, 2023 2:03 pmTo plot DV (graph screenshot), the workflow is 6-2-4.
For just a quick info summary about the RPU metadata in any file: 2-3
to check the metadata of any frame, input an RPU in: 2-3 or 2-2
looks like your file doesn't have DV or you're using an old dovi_tool(not scripts) version.TheEqualizer wrote: ↑Tue Jun 20, 2023 2:46 pmUnfortunately an error appears and the plot is not created
6-2-4
https://ibb.co/zHTqKMN
Is this the latest version?RESET_9999 wrote: ↑Tue Jun 20, 2023 2:58 pm
looks like your file doesn't have DV or you're using an old dovi_tool(not scripts) version.
Yes, it already works, I replaced dovi-tools in the tool package, tell me, and a more recent version of the package can be obtained by a link in private messages, since I realized that you no longer publish to the publicRESET_9999 wrote: ↑Tue Jun 20, 2023 3:17 pmyes but if your tool pack had the old dovi_tool, it means many other tools are missing or outdated... the latest version of the scripts will not work properly.
DUNE HD REAL VISION shows DT DL with full blu ray 4k dolby vision and ST DL with bdremux mkv 7 profile dolby vision is it true dolvy visiob or not ?RESET_9999 wrote: ↑Tue Jun 20, 2023 2:03 pmTo plot DV (graph screenshot), the workflow is 6-2-4.TheEqualizer wrote: ↑Tue Jun 20, 2023 1:40 pmGood afternoon, tell me what sequence of script points you need to use to analyze the finished mkv file, you need to get a screenshot similar to what is created automatically when converting HDR10+ to DV, is it possible? I can't find a similar scenario, thank you
For just a quick info summary about the RPU metadata in any file: 2-3
to check the metadata of any frame, input an RPU in: 2-3 or 2-2
It's true DV but without FEL support meaning only the dynamic metadata in the RPU is used.
IMO, the L2 trims can only be done/edited by the colorist/director so for our Resolve generated RPU, I recommend removing or overwriting the automatic trims otherwise they can make bright content very dark and dark content brighter which might not be the intended look.
The x700 does not ignore L1, at least not in TV-LED.Wouldn't it cause a problem on x700 with C1, since x700 ignores L1 metadata and uses only L2?
First, grade the HDR image on your Dolby Vision Certified Mastering Monitor to look as
you want it to. Dolby recommends starting by setting the look of the HDR image, to set
the overall intention for the grade.
2 When using various grading controls in the Color page to grade HDR images, you may
find it useful to enable the HDR Mode of the node you’re working on by right-clicking
that node in the Node Editor and choosing HDR mode from the contextual menu. This
setting adapts that node’s controls to work within an expanded HDR range. Practically
speaking, this makes controls that operate by letting you make adjustments at different
tonal ranges, such as Custom Curves, Soft Clip, etcetera, work more easily with wide-
latitude signals.
3 When you’re happy with the HDR grade, click the Analysis button in the Dolby Vision
palette. This analyzes every pixel of every frame of the current shot, and performs and
stores a statistical analysis that is sent to the CMU to guide its automatic conversion of
the HDR signal to an SDR signal.
4 If you’re not happy with the automatic conversion, use the Lift/Gamma/Gain/Chroma
Weight/Chroma Gain controls in the Dolby Vision palette to manually “trim” the result to
the best possible Rec. 709 approximation of the HDR grade you created in step 1. This
stores what Dolby refers to as “artistic guidance” metadata.
5 If you obtain a good result, then move on to the next shot and continue work. If you
cannot obtain a good result, and worry that you may have gone too far with your HDR
grade to derive an acceptable SDR downconvert, you can always trim the HDR grade a
bit, and then re-trim the SDR grade to try and achieve a better downconversion. Dolby
recommends that if you make significant changes to the HDR master, particularly if you
modify the blacks or the peak highlights, you should re-analyze the scene. However, if
you only make small changes, then reanalyzing is not strictly required
As you can see, the general idea promoted by Dolby is that a colorist will focus on grading the
HDR picture relative to the 1000, 2000, 4000, or higher nit display that is being used, and will
then rely on the colorist to use the Dolby Vision controls to “trim” this into a 100 nit SDR
version with artistic guidance. This “artistic guidance” metadata is saved as part of the mastered
media, and it’s used to more intelligently scale the HDR highlights to fit within any given HDR
display’s peak highlights, to handle how to downconvert the image for SDR displays, and also
how to respond when a television’s ABL circuit kicks in. In all of these cases, the colorist’s
artistic intent is used to guide all dynamic adjustments to the content.
Thank you for the deep explanation. So in your script, I should change "Choose if you want to remove the 600 and 1000nits L2 trim pass" to "YES", right?RESET_9999 wrote: ↑Thu Jun 22, 2023 7:19 pmIMO, the L2 trims can only be done/edited by the colorist/director so for our Resolve generated RPU, I recommend removing or overwriting the automatic trims otherwise they can make bright content very dark and dark content brighter which might not be the intended look.
see: https://www.youtube.com/watch?v=ZoseTlZ1JG4
You’re right, I’ve mixed it up with "L1 low contrast and L2 offset 0.75" problem.The x700 does not ignore L1, at least not in TV-LED.
https://drive.google.com/file/d/1gctmX1 ... drive_link
If you have access to the Dolby Metafier, yes. If you don't, you can set the script to just overwrite all the trims. This is how the script is set by default.
The L1 problem with the x800m2/x700 seem to be with low nits contents (under 1000nits). It's almost like the player knows the content is within the TV capabilities and decides to ignore L1 while the other devices(shield c2 internal,firestick) just apply the L1 metadata regardless of the content brightness.You’re right, I’ve mixed it up with "L1 low contrast
That is actually a much bigger problem. I did more tests about it and it turns out, any value over 2048 for trim offset has no effect in TV-LED mode on X700 x800m2 and Shield and most likely all the true TV-LED devicesL2 offset 0.75" problem
Good afternoon, I want to clarify once and for all for myself, in cases where dv has fewer frames than hdr, for exampleRESET_9999 wrote: ↑Sun Jul 25, 2021 9:48 pmfirst, you have to find the frame difference between the two videos. Personally, I use MPC-BE and find the same frame for both videos, press ''control-g'' and calculate the frame number difference. You can navigate frame by frame with ''control left/right arrow'' when the video is paused.
then the framecount of both rpu and hdr10 video must match. so you calculate how many frames you have to remove or add at the end of the rpu. (include the frame you added or removed from the start of the rpu) ... just math at this point.
EDIT: it is no more needed to calculate the framecount since the latest update. You only need to calculate the frame difference so the rpu is in sync with the bluray remux.