yeah i should have mentioned that the link would be online for only 1 week.
I PMed you a new link.
yeah i should have mentioned that the link would be online for only 1 week.
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?RESET_9999 wrote: ↑Tue Mar 07, 2023 6:53 pmyes it's the latest stable version but a new beta 1.7.6.1 coming up later today.
-- HDR10plus_tool and Dovi_tool must be updated to the latest version (hdr10plus to DV was totally wrong with the old dovi_tool)
I suggest you re-do any HDR10plus to DV conversion you did with the old dovi_tool
see: https://slow.pics/c/G6OH6k9p
-- HDR10plus plotter no longer requires python
-- new workflow that can batch remove CMV4.0 metadata block (2-1-6):
most of the CMV4.0 movies only have a L8 100nits trims and L2 has no effect on CMV4.0 device(shield,firestick,tv internal)
pattern to see what I'm talking about:
CMV4.0 original: https://drive.google.com/file/d/1lR1u9H ... share_link
cmv4.0 removed: https://drive.google.com/file/d/1ZqS9Ml ... share_link
-- bugfix: (2-1-5) batch edit L5 failed after the first file for mkv input
-- Code cleanup
First, most of the movies are done in CMV4.0 but exported in CMV2.9.jayper wrote: ↑Tue Mar 07, 2023 9:54 pmThanks 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?
yeah, in the next script version I'll keep the original name "hdr10plus_tool.exe" but for the current 1.7.6, you have to rename it "hdr10plus_parser.exe" or you can change the tool path name at line 93dom61 wrote: ↑Tue Mar 07, 2023 10:25 pmGood evening.
I apologize using the link Read Me https://github.com/quietvoid/hdr10plus_tool
I can download "hdr10plus_tool.exe" and not "hdr10plus_parser.exe"
Should I rename the file?
Thank you
Thank you for the confirmationRESET_9999 wrote: ↑Tue Mar 07, 2023 10:41 pmyeah, in the next script version I'll keep the original name "hdr10plus_tool.exe" but for the current 1.7.6, you have to rename it "hdr10plus_parser.exe" or you can change the tool path name at line 93dom61 wrote: ↑Tue Mar 07, 2023 10:25 pmGood evening.
I apologize using the link Read Me https://github.com/quietvoid/hdr10plus_tool
I can download "hdr10plus_tool.exe" and not "hdr10plus_parser.exe"
Should I rename the file?
Thank you
set hdr10plus_parser_path=%~dp0tools\hdr10plus_parser.exe ====> set hdr10plus_parser_path=%~dp0tools\hdr10plus_tool.exe
mediainfo is used to read and set the input resolution. So your path to mediainfo might not be right??
That's not really how the workflow works.RESET_9999 wrote: ↑Tue Mar 07, 2023 10:39 pmI 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).
yes it is how it works... Each trims are edited manually after the analysis to make sure the desired look is preserved.That's not really how the workflow works.
As I told you in PM, take the spears and munsil, generate cmv4.0 metadata and compare on cmv2.9 and 4.0 devices. I'm sure you will agree.Anyways, there has to be more experimenting on how CM v4.0 and L8 behave.
I don't agree that it should be removed.
I'm only clarifying your statement that the trim passes are done two times (L8 + L2), because it's not true.RESET_9999 wrote: ↑Wed Mar 08, 2023 3:06 amyes it is how it works... Each trims are edited manually after the analysis to make sure the desired look is preserved.
Dolby vision is not just an algorithm.
That's not at all the same situation. It would only be comparing different algorithms.RESET_9999 wrote: ↑Wed Mar 08, 2023 3:06 amAs I told you in PM, take the spears and munsil, generate cmv4.0 metadata and compare on cmv2.9 and 4.0 devices. I'm sure you will agree.
LOL I know very well that the dv analysis generates L2/L8 automatically, I literally asked you by pm how to overwrite them in my script because they have a too strong effect....
The metadata in L2 and L8 works quite differently as you know, so i disagree with you here.I'm only clarifying your statement that the trim passes are done two times (L8 + L2), because it's not true.
huh? please do some tests and then come at me againThat's not at all the same situation. It would only be comparing different algorithms.
I solved it by downloading the correct versionRESET_9999 wrote: ↑Tue Mar 07, 2023 11:06 pmmediainfo is used to read and set the input resolution. So your path to mediainfo might not be right??
No, you can only create single layer files. In order to create a P7 dual-layer file, you must have/create an enhancement layer (EL) which is currently not possible.dom61 wrote: ↑Wed Mar 08, 2023 6:54 amAfter processing a movie with DaVinci, I performed the export of Dolby Vision metadata (DV.xml), following the tutorial on Youtube as reference.
I ask if it is possible to inject only Dolby Vision metadata (DV.xml)
to get Mediainfo similar to this.
Thank you very much
I finally managed to import DV metadata, ask for confirmation if the procedure is correct.RESET_9999 wrote: ↑Wed Mar 08, 2023 11:59 amNo, you can only create single layer files. In order to create a P7 dual-layer file, you must have/create an enhancement layer (EL) which is currently not possible.
It might be possible to make a blank EL in the future though but i believe the BL has to be encoded a certain way also.
yes by default no rpu is exported.. you must edit line 35 set keep_rpu=NO