x265 3.0 Dolby Vision encoding

[kabelbrand]

Did someone manage to get an encode up and running with the new --dolby-vision-rpu option?

This is what the command line looks so far:

ffmpeg -loglevel quiet -i Cosmos_Laundromat_Dolby_Vision_24p_2048x858.mxf -pix_fmt yuv420p10 -f rawvideo - | x265-10b - --input-res 2048x858 --input-depth 10 --input-csp i420 --fps 24/1 --profile main10 --level-idc 5.1 --bitrate 30000 --vbv-maxrate 40000 --vbv-bufsize 40000 --repeat-headers --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --max-cll 1000,400 --dolby-vision-profile 8.1 --dolby-vision-rpu cosmos_laundromat_vdm_hdr_p3d65_pq_20160525_01_2048x858_dovi_4000nit_metadata.xml --output Cosmos_Laundromat_Dolby_Vision_24p_2048x858.265

Is there something wrong with the metadata? I always get this error:

x265 [error]: Invalid Dolby Vision RPU startcode in POC 0

Thanks.

[nevcairiel]

Judging from the error, it wants a binary encoded RPU file, and not a metadata XML.

[kabelbrand]

Originally Posted by nevcairiel

Judging from the error, it wants a binary encoded RPU file, and not a metadata XML.

Thanks, it's plain XML indeed. So how do I get a binary presentation of this? "metafier" does not seem to support it.

Btw. the source assets are linked in the command line.

[Selur]

Would be interested in that too.
Also is there a way to extract the data somehow?

As a side note: does using

--master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --max-cll 1000,400

make sense here?
I thought those were HDR-10 settings and shouldn't be used with Dolby Vision.

Cu Selur

[kabelbrand]

Originally Posted by Selur

I thought those were HDR-10 settings and shouldn't be used with Dolby Vision.

I guess when aiming for Dolby Vision profile 8.1 these should be included to also have HDR10 playback compatibility:
http://x265.org/x265-delivers-dolby-vision-streams/

[Selur]

Ah didn't know that.

[halls]

Hi!

There is any way to extract metadata from an existing file into RPU file?

[benwaggoner]

Originally Posted by kabelbrand

I guess when aiming for Dolby Vision profile 8.1 these should be included to also have HDR10 playback compatibility:
http://x265.org/x265-delivers-dolby-vision-streams/

Yes, you should include the 2086 metadata if you want to use it. A device that can't use the 8.1 DoVi metadata will fall back to HDR-10 static metadata (or HDR10+ dynamic metadata if available and supported)

[djloewen]

Am I correct in understanding that there's currently no way to extract the RPU information from the secondary Dolby Vision HEVC track on a commercially-produced UHD Blu-Ray, and use that data to encode in X.265?

[Blue_MiSfit]

I don't believe there is, at least not publicly available.

Also, it's x265 not X.265

[djloewen]

Got it, thanks .

[nghiabeo20]

Originally Posted by benwaggoner

Yes, you should include the 2086 metadata if you want to use it. A device that can't use the 8.1 DoVi metadata will fall back to HDR-10 static metadata (or HDR10+ dynamic metadata if available and supported)

Does DoVi file encoded with previous version of x265 (specifically 2.5) still has this fallback capability? Thanks!

[benwaggoner]

Originally Posted by nghiabeo20

Does DoVi file encoded with previous version of x265 (specifically 2.5) still has this fallback capability? Thanks!

It should, but I've never tried.

[Balling]

>or HDR10+ dynamic metadata if available and supported

Actually HDR10+ is preferred usually.

[benwaggoner]

Originally Posted by Balling

>or HDR10+ dynamic metadata if available and supported

Actually HDR10+ is preferred usually.

Yeah, anything that supports Profile 8.1 or HDR10+ will use one of those before falling back to using the (pretty lame and vestigial) 2086 static metadata.

I don't know of any devices that have shipped with BOTH DoVi 8.1 and HDR10+, and it would be up to the device to pick which one to use if both are available. I don't know if there would be any practical advantage of one over the other. DoVi Profile 5 can, in theory, provide less banding and somewhat more efficiency due to its non-backwards compatible base layer and YCtCp. I've not tested that myself yet, though. It's be a pain to evaluate without a single display that can use both modes. Probably feasible with a couple of reference displays driven by a ColorFront Transcoder...

[Stacey Spears]

Originally Posted by kabelbrand

Thanks, it's plain XML indeed. So how do I get a binary presentation of this? "metafier" does not seem to support it.

Btw. the source assets are linked in the command line.

Dolby Encoding Engine is available for $500 per year per node and can create a binary RPU from a Dolby Vision XML.

[Blue_MiSfit]

Originally Posted by Stacey Spears

Dolby Encoding Engine is available for $500 per year per node and can create a binary RPU from a Dolby Vision XML.

DEE is a solid tool. I've used this for several projects using Dolby tech.

[quietvoid]

Posting in this thread as it's the oldest.

I made a first release of my tool: https://github.com/quietvoid/dovi_to.../tag/0.1.0-fix
It can be used to create an RPU file from a profile 5, 7 or 8 HEVC encoded file.

Commands:
demux: Demuxes single track dual layer Dolby Vision into Base layer and Enhancement layer files.
extract-rpu: Extracts Dolby Vision RPU from an HEVC encoded file.

More info in the README.
Enjoy.

[ghostshadow]

Hello Quietvoid, thank you for your work
I used it on an El.hevc file containing the RPU and I have this error message
thread 'main' has overflowed its stack

[quietvoid]

It might be related to the memory, buffer allocations..
My stack size on linux was limited to 8MB, and I was using 4MB in the code.
I have lowered it way down, please try again.