Dolby Vision now possible through MP4 Mux.

[ArArdin]

Nice. Went flawless after clearing some path-related issues. Really feel like a blundering novice here.

Thanks a bunch for your quick response

[ArArdin]

A few questions regarding the options after the first "4" (DoVi Profile 7 Input (MKV/BDMV)) if you don't mind, RESET_9999.

It is possible for P7 mp4 to be STDL (IIRC the old Yusesope tool could do so), where BL and EL+RPU be interleaved in one hevc track. Is there a particular reason to why there's no option to output such STDL mp4?
Another thing is, I've recently learned that chapters can be muxed in mp4. Can you tell me how this is done in case I have a - let's say chapters.txt file - or do I have to add the chapters in mkv first?

[RESET_9999]

A few questions regarding the options after the first "4" (DoVi Profile 7 Input (MKV/BDMV)) if you don't mind, RESET_9999.

It is possible for P7 mp4 to be STDL (IIRC the old Yusesope tool could do so), where BL and EL+RPU be interleaved in one hevc track. Is there a particular reason to why there's no option to output such STDL mp4?
Another thing is, I've recently learned that chapters can be muxed in mp4. Can you tell me how this is done in case I have a - let's say chapters.txt file - or do I have to add the chapters in mkv first?

the ST-DL P7 workflow is hidden a bit but it's there in workflow 4-1-2. It's only for BDMV or DT-DL input though.

I guess I could let workflow 5 to mux the ST P7 video untouched(right now it convert to p8)

[DjObama]

Hi,
I have LG B8, your spreadsheet doesn't list support for the B series, however every MEL title has worked so far. I'm getting confused about the FEL titles. So far none has worked for me after converting to ts or m2ts, some dont play some stutter for a bit and stop playing. However with the last movie I decided to follow the 4-3 workflow and created a DT-DL mp4 which plays fine.
My question is: Is it possible that my tv just doesn't play the second (1080p fel) video stream and I see only the BL+RPU on the screen? Or does DT-DL playing in DV mean everything works fine? How can I verify this as an total amateur?

[Gatorman]

if you use the dovi_scripts, it's not too complicated.

automated: workflow 8-6-2
manual (with staxrip or in cli x265.exe):
1. workflow 7-1 in manual mode.
2. edit the avs script: remove the text overlay and uncomment convertbits(10)
3. convert the rpu to p8.
4. encode the avs file just like any HDR video file(with the rpu or inject it after the encode).

Sorry for my ignorance. The first section is was created with the 7-1 Manual option. Is the second section edited correctly for encoding with StaxRip?

Code: Select all

LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\DoViBaker_x64.dll") 
LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\avs_libplacebo.dll") 
LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\dgdecnv_242\DGDecodeNV.dll") 
bl = DGSource("I:\Working\Dolby-Vision-Tools\Movie_BL.dgi") 
el = DGSource("I:\Working\Dolby-Vision-Tools\Movie_EL.dgi") 
SetFilterMTMode("DoViBaker",2)  
DoViBaker(bl, el, rpu= "I:\Working\Dolby-Vision-Tools\Movie_RPU_FEL.bin") 
# libplacebo_Tonemap(src_csp=1, dst_csp=0, dynamic_peak_detection=true, tone_mapping_function=0, tone_mapping_mode=1) 
# ConvertToYUV420(matrix="709") 
# SetFilterMTMode("DoViBaker",2) and Prefetch(8) must be removed to use libplacebo 
ConvertToYUV420(matrix="2020") 
# ConvertBits(10) 
# Crop(0, 280, -0, -280) 
# Spline36Resize(1920, 1080) 
Prefetch(8)

Code: Select all

LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\DoViBaker_x64.dll") 
LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\avs_libplacebo.dll") 
LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\dgdecnv_242\DGDecodeNV.dll") 
bl = DGSource("I:\Working\Dolby-Vision-Tools\Movie_BL.dgi") 
el = DGSource("I:\Working\Dolby-Vision-Tools\Movie_EL.dgi") 
DoViBaker(bl, el, rpu= "I:\Working\Dolby-Vision-Tools\Movie_RPU_FEL.bin") 
ConvertToYUV420(matrix="2020")

[RESET_9999]

Hi,
I have LG B8, your spreadsheet doesn't list support for the B series, however every MEL title has worked so far. I'm getting confused about the FEL titles. So far none has worked for me after converting to ts or m2ts, some dont play some stutter for a bit and stop playing. However with the last movie I decided to follow the 4-3 workflow and created a DT-DL mp4 which plays fine.
My question is: Is it possible that my tv just doesn't play the second (1080p fel) video stream and I see only the BL+RPU on the screen? Or does DT-DL playing in DV mean everything works fine? How can I verify this as an total amateur?

Yes, the 2018 LG TVs support FEL but indeed, the support in TS/M2TS containers is not great for the Single track rip (makemkv) and the dual track rip will not work.
So the best option for FEL playback on this TV is the MP4 container and DV is processed properly(BL+EL+RPU) as far as I know.

[RESET_9999]

Sorry for my ignorance. The first section is was created with the 7-1 Manual option. Is the second section edited correctly for encoding with StaxRip?

You have to uncomment ConvertBits(10) from the avs script or add a bit-depth 10bit conversion in staxrip.

Code: Select all

LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\DoViBaker_x64.dll") 
LoadPlugin("I:\Working\Dolby-Vision-Tools\tools\dgdecnv_242\DGDecodeNV.dll") 
bl = DGSource("I:\Working\Dolby-Vision-Tools\Movie_BL.dgi") 
el = DGSource("I:\Working\Dolby-Vision-Tools\Movie_EL.dgi") 
SetFilterMTMode("DoViBaker",2)  
DoViBaker(bl, el, rpu= "I:\Working\Dolby-Vision-Tools\Movie_RPU_FEL.bin") 
ConvertToYUV420(matrix="2020") 
ConvertBits(10) 
Prefetch(8)

[Gatorman]

Since baking in FEL with StaxRip I've been getting validate_metadata errors like these, when adding the converted RPU. Is this normal?

Code: Select all

WARNING: L1=0,0,0 metadata at shot: UniqueID = e822cd1d-e184-4959-bd7f-4fcc0f6754fb @[0-43].

Code: Select all

WARNING: shot: UniqueID = bc0fa9d6-cce2-4d50-b990-9b3f88a48802 @[175549-175794] contains target trim(s) without a 100-nit, Rec.709 trim.

[RESET_9999]

Since baking in FEL with StaxRip I've been getting validate_metadata errors like these, when adding the converted RPU. Is this normal?

Code: Select all

WARNING: L1=0,0,0 metadata at shot: UniqueID = e822cd1d-e184-4959-bd7f-4fcc0f6754fb @[0-43].

Code: Select all

WARNING: shot: UniqueID = bc0fa9d6-cce2-4d50-b990-9b3f88a48802 @[175549-175794] contains target trim(s) without a 100-nit, Rec.709 trim.

This is the same in the original RPU. The p7 to p8 conversion does not touch the dynamic metadata (L1/L2 etc..)
BTW, the warnings in metafier is not really a problem. Errors on the other hand is a problem.


FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness: https://www.youtube.com/watch?v=Hk6ria8_PFo

Code: Select all

WARNING: Positive Level2 lift value at shot: UniqueID = b42d5b72-2b5c-431a-a160-d7204bb67330 @[18280-18325]
WARNING: Positive Level2 lift value at shot: UniqueID = 3cff3948-45b7-4179-9260-51d41aadbdb8 @[18326-18421]
WARNING: Positive Level2 lift value at shot: UniqueID = 64ab0852-6218-435c-ab93-80c821f553c8 @[19192-19290]
WARNING: Positive Level2 lift value at shot: UniqueID = 64ab0852-6218-435c-ab93-80c821f553c8 @[19192-19290]
WARNING: Positive Level2 lift value at shot: UniqueID = 2b8c89f0-82ae-449f-a2e8-f25cbb26ff19 @[19380-19479]
WARNING: Positive Level2 lift value at shot: UniqueID = 40c08837-aa0e-4eb6-a42c-d4b19fa30530 @[19914-19932]
WARNING: Positive Level2 lift value at shot: UniqueID = 40c08837-aa0e-4eb6-a42c-d4b19fa30530 @[19914-19932]
WARNING: Positive Level2 lift value at shot: UniqueID = 43bb1490-66a7-4b78-b6f4-b2f2d9bbb6a6 @[50546-50583]
WARNING: Positive Level2 lift value at shot: UniqueID = 43bb1490-66a7-4b78-b6f4-b2f2d9bbb6a6 @[50546-50583]
WARNING: Positive Level2 lift value at shot: UniqueID = 9819a8e5-d54b-4617-bbf4-555f0da2482b @[201575-201632]
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223036 (offset=284)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223037 (offset=285)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223038 (offset=286)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223039 (offset=287)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223040 (offset=288)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223041 (offset=289)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223042 (offset=290)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223043 (offset=291)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223044 (offset=292)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223045 (offset=293)
WARNING: Positive Level2 lift value at shot: UniqueID = 9f396c99-2bbc-4546-8be6-341c36b6cde9 @[222752-223708] and frame: 223046 (offset=294)
WARNING: 17 Shots contain identical Level1 values
WARNING: 15 Shots contain identical Level2 values

[Gatorman]

FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness: https://www.youtube.com/watch?v=Hk6ria8_PFo

Regarding this film, it looks like the MDL of the BL and RPU is .0050/4000 and the MaxCLL is 997 for both. Does the MDL need to be changed to 1/1000, when baking in the FEL with StaxRip? Perhaps the trims take care of this?

BTW, 6-2 is crashing for me when I try to plot HDR.

[Trees]

Quick question; when generating CMv4.0 content (3-1), how does one determine what Mastering Display to use? I assuming higher isn't necessarily better?

2 options:

1- just use the static metadata from your source HDR10
2- check the brightness first with madvr. If 95% of the movie is under 1000nits, use 1000nits MDL else, 4000.

Option 2 is better because some movies have a static MDL of 4000nits but the actual brightness is under 1000nits.
A 4000nits RPU is a lot darker than a 1000nits one regardless of the content's actual brightness and in my opinion, 4000nits MDL + low nits content is wrong without L2 trim passes because if you look at the generated(or original) trims with a 4000nits analysis, they brighten/compensate a lot for the darkness a 4000 rpu brings.

https://slow.pics/c/uVX5iFOD

So I finally got round to do this. Question, though. The files I want to eventually CMv4.0 analyze are HDR10+. The plots are all coming back as dynamic, even though you instructed me to plot the static data (6-2). Is madVR checking the dynamic HDR10+ portion of the video instead of the HDR10 static metadata portion of the video? Is something going wrong? Or will it automatically check the dynamic metadata if the file is HDR10+?

[RESET_9999]

FYI, in the new Mission Impossible, it looks like the colorist missed the memo about L2 0.025 lift. These shots will most likely result in grey letterbox on devices that ignore L5
And you can clearly see on this video how the trims raise the brightness: https://www.youtube.com/watch?v=Hk6ria8_PFo

Regarding this film, it looks like the MDL of the BL and RPU is .0050/4000 and the MaxCLL is 997 for both. Does the MDL need to be changed to 1/1000, when baking in the FEL with StaxRip?

no

BTW, 6-2 is crashing for me when I try to plot HDR.

In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.

So I finally got round to do this. Question, though. The files I want to eventually CMv4.0 analyze are HDR10+. The plots are all coming back as dynamic, even though you instructed me to plot the static data (6-2). Is madVR checking the dynamic HDR10+ portion of the video instead of the HDR10 static metadata portion of the video? Is something going wrong? Or will it automatically check the dynamic metadata if the file is HDR10+?

6-2 is useful to find out about the content brightness you're about to generate DV. It helps you select a better MDL, that's it.
In 3-1, any dynamic metadata(only the scene cuts matter) regardless of the source is used for the Shot list during the CM analysis.
Shot list source is selected in this order:

1- any external file with the same filename as the input (rpu, json, text)
2- internal RPU (in case of original rpu that has no shot, add ''IGNORERPU'' in the input filename.)
3- internal hdr10plus
4- if no dynamic metadata is found, it uses madvr to generate a shot list which means that if your source doesn't have any dynamic metadata, you can use the generated RPU from your previous 6-2 measurement.

[Gatorman]

In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.

Sorry about that. I've added dovi_tool_no_floor. However, 6-2 still crashes. I'm running LAVFilters 0.78.

[RESET_9999]

In the latest version, I removed the 10nits and 100nits floor so you need to add in your tools folder, the modified version of the dovi_tool linked in the release note.

Sorry about that. I've added dovi_tool_no_floor. However, 6-2 still crashes. I'm running LAVFilters 0.78.

does your input filename contain'')''
I just noticed that input with '')'' doesn't work in 6-2. I introduced this bug when I added profile 5 support in 6-2

[Gatorman]

does your input filename contain'')''
I just noticed that input with '')'' doesn't work in 6-2. I introduced this bug when I added profile 5 support in 6-2

There was a ")" in the path. It works fine now. Thank you.