Dolby Vision now possible through MP4 Mux.

[RESET_9999]

Good 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

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 93

set hdr10plus_parser_path=%~dp0tools\hdr10plus_parser.exe ====> set hdr10plus_parser_path=%~dp0tools\hdr10plus_tool.exe

[dom61]

Good 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

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 93

set hdr10plus_parser_path=%~dp0tools\hdr10plus_parser.exe ====> set hdr10plus_parser_path=%~dp0tools\hdr10plus_tool.exe

Thank you for the confirmation
I went ahead in the procedure and when I am processing the file "DV.xml", it is prompted to enter a value of enter a value of CANVAS_WIDTH
How to do this?
Thank you very much

[RESET_9999]

Thank you for the confirmation
I went ahead in the procedure and when I am processing the file "DV.xml", it is prompted to enter a value of enter a value of CANVAS_WIDTH

mediainfo is used to read and set the input resolution. So your path to mediainfo might not be right??

[quietvoid]

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).

That's not really how the workflow works.
The grading is done in CM v4.0 and the L2 metadata is generated automatically by software.
So the trim passes are still done only once.

Anyways, there has to be more experimenting on how CM v4.0 and L8 behave.
I don't agree that it should be removed.

[RESET_9999]

That's not really how the workflow works.

yes 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.
Just take the Spears and Munsill clip and generate DV in resolve, the automatic trims are a LOT darker than the original as shown here https://drive.google.com/file/d/1_PkGF9 ... share_link

Anyways, there has to be more experimenting on how CM v4.0 and L8 behave.
I don't agree that it should be removed.

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.

[quietvoid]

yes 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.

I'm only clarifying your statement that the trim passes are done two times (L8 + L2), because it's not true.

If you even did a little research, you would've found that L2 is always autogenerated.
So the trim passes are what creates the L8, not the L2. At least in a CM v4.0 workflow.

For CM v2.9, of course the trims are done once and they result in the L2.

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.

That's not at all the same situation. It would only be comparing different algorithms.

[RESET_9999]

If you even did a little research, you would've found that L2 is always autogenerated.

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....
My point is that the trims are edited manually after the analysis. They are NOT just the result of an algorithm.

I'm only clarifying your statement that the trim passes are done two times (L8 + L2), because it's not true.

The metadata in L2 and L8 works quite differently as you know, so i disagree with you here.
If they do L2 and L8 trims they must go through each of them but then we learned that the studios can be very lazy so who knows how much work they really put in the trims.

That's not at all the same situation. It would only be comparing different algorithms.

huh? please do some tests and then come at me again

[dom61]

Thank you for the confirmation
I went ahead in the procedure and when I am processing the file "DV.xml", it is prompted to enter a value of enter a value of CANVAS_WIDTH

mediainfo is used to read and set the input resolution. So your path to mediainfo might not be right??

I solved it by downloading the correct version

After 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

[RESET_9999]

After 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

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.
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.

[dom61]

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.
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.

I finally managed to import DV metadata, ask for confirmation if the procedure is correct.
I performed the procedure only for Dolby Vision, launched DoVi_Scripts 1>1 Drag & Drop MKV file and DV.xml file




And only the ".hevc" file is generated. , then I enter the file in MKVToolNix to create the mkv file which has these characteristics.
The "RPU.bin" file is not generated as in the videotutorial

[RESET_9999]

And only the ".hevc" file is generated. , then I enter the file in MKVToolNix to create the mkv file which has these characteristics.
The "RPU.bin" file is not generated as in the videotutorial

yes by default no rpu is exported.. you must edit line 35 set keep_rpu=NO

Also, you must have turned off the muxing(line 21) because the script is supposed to mux to MKV.

[dom61]

yes by default no rpu is exported.. you must edit line 35 set keep_rpu=NO

Also, you must have turned off the muxing(line 21) because the script is supposed to mux to MKV.

OK line 39 has been changed, but line 21 is active.

[sultanmehmet]

Can somebody confirm if I can just copy the 'raw' m2ts file to my HDD?

No, you'll get "fake" DV if you do that. You must remux to TS/M2TS or BDMV with the nightly tsmuxer.

It sounds like you're using the very old tsmuxer. I use this version (had issues with the latest ones)...
https://github.com/justdan96/tsMuxer/re ... 2-02-15-09

Thanks man, that did the trick! I don't know how I didn't download that version as I thought I just went on google a couple of days ago and downloaded the lastest one. But it worked and I got my x700 in the mail today and tested it out. It played in hdr10 at first but I noticed that DV was turned off in the settings, so after I turned it on it worked like a charm! Its funny how even though this x700 feels like a cheap piece of plastic it plays back DV so effortlessly.

[caelar900]

Finally got the script working and started converting most of my duplicate p5 files to p8 only to realize about 60 odd films in that p8 has the red push issue on shield -_- Looks like Apple TV with infuse doesn't work quite right either from some of the test patterns I was looking at. Oh well guess I'll be sticking with P5 for plex files and x800 for all my p7's.

[Draco1544]

@RESET_9999 Hi, where I can fine the DoVi_mp4_DVH1.exe required by your script for mp4 workflow ?