Dolby Vision now possible through MP4 Mux.

[spl147]

How would i bake the EL into the BL?

This is for FEL titles only correct?

https://github.com/erazortt/DoViBaker

also, the latest version of my script can encode P7 FEL to P8.. Workflow (6-9)

Would baking the FEL layer into the base layer not create a profile 5

[RESET_9999]

Would baking the FEL layer into the base layer not create a profile 5

It creates a new HDR10 base layer with P8 original dv metadata

[spl147]

Would baking the FEL layer into the base layer not create a profile 5

It creates a new HDR10 base layer with P8 original dv metadata

So does it retain hdr10 fallback?

[RESET_9999]

So does it retain hdr10 fallback?

of course, no different than any HDR10 + P8 encode.

[spl147]

of course, no different than any HDR10 + P8 encode.

So then what is gained/lost?

[RESET_9999]

So then what is gained/lost?

You gain extra quality/brightness from the FEL.

[spl147]

So then what is gained/lost?

You gain extra quality/brightness from the FEL.

So then would it be the same if played back as HDR10 or DV

[spl147]

of course, no different than any HDR10 + P8 encode.

What would be the command line to accomplish this?

[RESET_9999]

So then would it be the same if played back as DV

only if you compare it to DV on a device that support FEL.

What would be the command line to accomplish this?

I posted my cli a couple post ago.

[spl147]

So then would it be the same if played back as DV

only if you compare it to DV on a device that support FEL.

What would be the command line to accomplish this?

I posted my cli a couple post ago.

Workflow 6-9 using your scripts?

I was referring to using dovibaker

[RESET_9999]

I was referring to using dovibaker

its a ffmpeg x265 cmd and can be used wit the dovi baker. Just change the variables.

[mattiswise]

How would i bake the EL into the BL?

This is for FEL titles only correct?




Can someone translate this into noob for me please?

[speeddemon]

Aside from the time/effort involved. Is there a downside to doing this and/or anything you miss out on or that could be improved upon further from your tutorial?

The only thing I don't do in the video is the project image scaling. I found out that if you set your project to 1080p with cubic algo, it produces much better metadata that are almost identical to the original.
https://ibb.co/r2tMX6n

Just curious, do you know why this produces better results?
Also, have you considered adding this note to the video description on YouTube? It might help others who follow along, but don't come read this message.

Also, what would it take to analyze for multiple trims or does it already do this? Have you ever attempted this?

Your project set to CMV4.0 will produce L2 trims. My script by default, will remove them as explained recently in this thread.

Why set the project to CMv4.0 instead of CMv2.9 then? Would you not get better results just initially setting to CMv2.9 to avoid the issues you demonstrated here with CMv2.9 when CMv4.0 analysis is used?

[RESET_9999]

Why set the project to CMv4.0 instead of CMv2.9 then? Would you not get better results just initially setting to CMv2.9 to avoid the issues you demonstrated here with CMv2.9 when CMv4.0 analysis is used?

This video doesn't show issues. It just shows the difference between the format.
CMV4.0 is the latest dolby algo and it produces better metadata and Dolby recommends using it even if you're going to deliver in CM v2.9

NOTE It’s currently recommended for all users to choose Dolby Vision v4.0 for analysis
and trimming, as it provides superior results. If you’re required to deliver Dolby Vision v2.9
metadata when mastering for backwards compatibility, DaVinci Resolve can now export
v2.9 metadata from projects using v4.0 workflows.

[spl147]

do we need to download ALL these tools listed in the readme seperately?