Pass over HDR10+ and Dolby Vision information?

[Nico8583]

Thanks ! I did some tests, for someone who is searching to try it :
With an UHD BD (replace playlist number and paths, video track index if needed) :

ffmpeg.exe -playlist 123 -i bluray:"D:\PathToTheUHDBDFolder" -map 0:v:1 -c:v copy -vbsf hevc_mp4toannexb -f hevc - | dovi_tool -m 2 extract-rpu - -o RPU.bin

With a MKV from MakeMKV (single track dual layer) :

ffmpeg.exe -i "D:\Movie.mkv" -c:v copy -vbsf hevc_mp4toannexb -f hevc - | dovi_tool -m 2 extract-rpu - -o RPU.bin

With a MKV from mkvtoolnix (double track) (replace video track index if needed) :

ffmpeg.exe -i "D:\Movie.mkv" -map 0:v:1 -c:v copy -vbsf hevc_mp4toannexb -f hevc - | dovi_tool -m 2 extract-rpu - -o RPU.bin

RPU is bit to bit identical for all outputs

[Nico8583]

Another question : is it possible to convert profile 7 dual track (BL + EL) to profile 8.1 with one command ? Or I need to extract BL track + extract RPU from EL track then inject to BL track and remux BL track to MKV ?
And if I do that, does the BL track will keep HDR10+ metadata if include ? Thanks.

[quietvoid]

Originally Posted by Nico8583

Another question : is it possible to convert profile 7 dual track (BL + EL) to profile 8.1 with one command ?

Use the convert command: https://github.com/quietvoid/dovi_tool#convert
The examples do exactly what you're looking for.
You need a single video file first, though.

Otherwise, just extract the RPU and inject it back in the BL, yes.

Originally Posted by Nico8583

And if I do that, does the BL track will keep HDR10+ metadata if include ? Thanks.

Yes.

[Nico8583]

Ok so the convert command can do that from a MakeMKV file. Or do you know another software than MakeMKV or yusesope just to combine BL+EL+RPU into a single track ? Thanks.

[quietvoid]

Originally Posted by Nico8583

Or do you know another software than MakeMKV or yusesope just to combine BL+EL+RPU into a single track ? Thanks.

Not that I'm aware of.

[Yomiko]

I can think of two approaches but I don't know which one should be preferred.

1) Encode as HDR10, then inject-rpu with dovi_tool
2) Encode with x265 Dolby Vision options

[Nico8583]

Thanks quietvoid and inject RPU can work only with raw stream ? Is it possible to inject RPU to a stream inside a MKV ? Thanks

[quietvoid]

Originally Posted by Nico8583

Thanks quietvoid and inject RPU can work only with raw stream ? Is it possible to inject RPU to a stream inside a MKV ? Thanks

Only raw stream currently.
In the future I hope it might be possible to make it possible to pipe from any container.

The output is always going to be the raw HEVC, though.

[mattl0]

Originally Posted by quietvoid

Only raw stream currently.
In the future I hope it might be possible to make it possible to pipe from any container.

The output is always going to be the raw HEVC, though.

That is enough That would save a lot of time .

Question 1 with profile 8.1 example : Since injecting rpu into a BL HEVC is longer than simply use the convert command , are they both the same? I did some test and the rpu after each case have the same weight. But are they Injected the same way in the final hevc output?

Question 2 for profile 7 (can be applied to mel too): i saw that it is possible to have a BL and an EL file without rpu. Just need to mux both BL and EL.

With this approch, do you think it would be beneficial to mux the BL with the el, and then inject rpu generated from a json.

So we would have a p7 fel with an new rpu rpu.

A command to completly extract the rpu (so remove rpu to get one hevc file BL+el without rpu /. or two hevc BL + ( El minus the rpu)), would be noce if you ever feel like it, have the time and find it useful. The idea can be wrong too.

[mattl0]

Last one sorry,

I have a lg c1. It can read profile 8.1 Dolby vision for int player or plex. But how can I know that the rpu is really processed by the tv? Maybe you have a hint for this . Thank you @quietvoid .

A little of topic …maybe someone have an answer here…
I also have an android ugoos am6b+. But I have not convinced that it is decoding dolby p7 fel ok for the rgb tunneling. Resolution is always set to 1080p like if there are a certification limit or wtv else. Not sure if forcing it back to 2160p is ok. I have the feeling that the it is rendered in 1080p and then converted to 2160p for some reason . The process seems shady; from command line, I also can force the box to swtich to 10 bit when in tunneling mode , and the tv accept it…i do not know if this is normal, and what it does mean

[quietvoid]

Originally Posted by mattl0

Question 1 with profile 8.1 example : Since injecting rpu into a BL HEVC is longer than simply use the convert command , are they both the same? I did some test and the rpu after each case have the same weight. But are they Injected the same way in the final hevc output?

If you only have a video that is already Dolby Vision, then just use convert.
Injecting is only useful for videos that were already encoded in HDR10, but don't contain Dolby Vision metadata.

Originally Posted by mattl0

Question 2 for profile 7 (can be applied to mel too): i saw that it is possible to have a BL and an EL file without rpu. Just need to mux both BL and EL.

That makes no sense, the EL always contains the RPUs.

There isn't really a use case where editing an existing profile 7 is any useful.

Originally Posted by mattl0

Last one sorry,

I have a lg c1. It can read profile 8.1 Dolby vision for int player or plex. But how can I know that the rpu is really processed by the tv? Maybe you have a hint for this . Thank you @quietvoid .

You can try this file: https://forum.makemkv.com/forum/view...113537#p113537
You might have to convert it to mp4 for the TV player.

[benwaggoner]

Originally Posted by mattl0

Last one sorry,

I have a lg c1. It can read profile 8.1 Dolby vision for int player or plex. But how can I know that the rpu is really processed by the tv? Maybe you have a hint for this . Thank you @quietvoid .

The LG will go into a "Dolby Vision" picture mode playing DoVi content. So just hit your settings button and see what picture mode it is in.

A little of topic …maybe someone have an answer here…
I also have an android ugoos am6b+. But I have not convinced that it is decoding dolby p7 fel ok for the rgb tunneling. Resolution is always set to 1080p like if there are a certification limit or wtv else. Not sure if forcing it back to 2160p is ok. I have the feeling that the it is rendered in 1080p and then converted to 2160p for some reason . The process seems shady; from command line, I also can force the box to swtich to 10 bit when in tunneling mode , and the tv accept it…i do not know if this is normal, and what it does mean

RGB 444 takes 1.5x the bandwidth of YUV 422. Depending on HDMI ports and cable, it's not uncommon for there to be enough bandwidth for YUV 422 but not RGB 444, so switching to RGB forces down resolution or frame rate.

You'll want both output and input to be HDMI 2.0, with at least an 18 Gbps rated HDMI cable.

You can make it work with older HDMI versions, but not at RGB 444 4Kp60.

[PoeBear]

Does the VUI base layer stuff on our custom MEL Profile 8.1 hatchetjobs matter? Per the specs (Dolby Vision Profiles and Levels, V1.3.3), Dolby requires a center-left chromaloc on the video track. But with a UHD Blu-ray/Profile 7 video track, Dolby requires top left chromaloc

Does that mean when playing the DV layer, it's gonna shift all my reds? Or is that something that would only affect if it were an FEL profile 8.1, as it would be expecting a different chroma layout to apply its 12-bit coloring?

[mattl0]

Originally Posted by quietvoid

If you only have a video that is already Dolby Vision, then just use convert.
Injecting is only useful for videos that were already encoded in HDR10, but don't contain Dolby Vision metadata.


That makes no sense, the EL always contains the RPUs.

There isn't really a use case where editing an existing profile 7 is any useful.


You can try this file: https://forum.makemkv.com/forum/view...113537#p113537
You might have to convert it to mp4 for the TV player.

Thanks ! This works perfectly i can see all the changes on the video playback on my c1 with internal app.

[mattl0]

Originally Posted by benwaggoner

The LG will go into a "Dolby Vision" picture mode playing DoVi content. So just hit your settings button and see what picture mode it is in.


RGB 444 takes 1.5x the bandwidth of YUV 422. Depending on HDMI ports and cable, it's not uncommon for there to be enough bandwidth for YUV 422 but not RGB 444, so switching to RGB forces down resolution or frame rate.

You'll want both output and input to be HDMI 2.0, with at least an 18 Gbps rated HDMI cable.

You can make it work with older HDMI versions, but not at RGB 444 4Kp60.

[quietvoid]

Originally Posted by PoeBear

Does the VUI base layer stuff on our custom MEL Profile 8.1 hatchetjobs matter? Per the specs (Dolby Vision Profiles and Levels, V1.3.3), Dolby requires a center-left chromaloc on the video track. But with a UHD Blu-ray/Profile 7 video track, Dolby requires top left chromaloc

Does that mean when playing the DV layer, it's gonna shift all my reds? Or is that something that would only affect if it were an FEL profile 8.1, as it would be expecting a different chroma layout to apply its 12-bit coloring?

The specification only mentions that VUI parameters are required for profile 8.1

Dolby Vision bitstreams for all profiles other than profile 7 may use center-left or top-left luma-chroma siting.
A chroma sample location type VUI is mandatory unless center-left siting is used.
If a chroma sample location type VUI is present, it must be accurate

To me this means that if the base layer was not processed further, and uses top-left, then it is fine.
Usually people reencode profile 7 as profile 8.1 with top-left, and it seems to be OK.

For profile 7 with an EL, it is probably to make sure both video streams are aligned, yes.

Supposedly the new default is top-left for anything HDR10.

[PoeBear]

Originally Posted by quietvoid

The specification only mentions that VUI parameters are required for profile 8.1

Yes, this is why I'm asking. The current trick to getting MEL playback in a container is to repackage it as Profile 8.1, but the HDR10 base layer will be out of spec (unless you change it at encoding)

I'm asking will there be playback issues due to the out-of-spec file? If so, will they be with MEL/FEL playback, or just FEL?

FEL testing really seems impossible for that anyway anyway, with nothing being able to play FEL back in container format, so it was more of a technical question to those that know the DV specs

Originally Posted by quietvoid

Usually people reencode profile 7 as profile 8.1 with top-left, and it seems to be OK.

"Seems to be" is what I want to avoid. One can easily miss a small chroma shift and think everything is fine, especially if there's not a known correct image to compare against. If there's a spec, I'd like to adhere to it to avoid future problems. Especially since the Profile 8.1 thing is already a workaround due to a lot of TVs/devices not able to playback DV Profile 7.1

Originally Posted by quietvoid

Supposedly the new default is top-left for anything HDR10

Yes when encoding for HDR10 you would set chromaloc to 2 (top-left), but that would go against Dolby's specs for Profile 8.1, which require for center-left (chromaloc 0), hence my inquiry

[SeeMoreDigital]

Originally Posted by quietvoid

You can try this file: https://forum.makemkv.com/forum/view...113537#p113537

That's a most impressive sample quietvoid

[quietvoid]

Originally Posted by PoeBear

Yes when encoding for HDR10 you would set chromaloc to 2 (top-left), but that would go against Dolby's specs for Profile 8.1, which require for center-left (chromaloc 0), hence my inquiry

I'm confused, my quote says that profile 8.1 can use top-left, and is not required to be center-left.

The conflicting information seems to be coming from the table, where it says that BL signal cross-compatibility ID 1 should be using center-left.
But not far down it says both can be used, for profiles other than 7.

[PoeBear]

Originally Posted by quietvoid

But not far down it says both can be used, for profiles other than 7.

I guess that's where I'm getting confused. Then it says "As of the effective date of this specification, top-left chroma siting is not tested during Dolby Vision SoC or device certification"

Does that mean its device dependent on if it would work or not? Why would they put only center-left in the table, but then say that top-left is okay, but that they say they won't even test for it it? I guess I'm just confused by Dolby's documentation itself...