Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
7th January 2019, 11:37 | #1 | Link |
Compression mode: Lousy
Join Date: Mar 2009
Location: Hamburg, Germany
Posts: 72
|
x265 3.0 Dolby Vision encoding
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: Code:
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 Code:
x265 [error]: Invalid Dolby Vision RPU startcode in POC 0 Last edited by kabelbrand; 7th January 2019 at 11:41. |
7th January 2019, 12:21 | #2 | Link |
Registered Developer
Join Date: Mar 2010
Location: Hamburg/Germany
Posts: 10,344
|
Judging from the error, it wants a binary encoded RPU file, and not a metadata XML.
__________________
LAV Filters - open source ffmpeg based media splitter and decoders |
7th January 2019, 12:49 | #3 | Link | |
Compression mode: Lousy
Join Date: Mar 2009
Location: Hamburg, Germany
Posts: 72
|
Quote:
Btw. the source assets are linked in the command line. Last edited by kabelbrand; 7th January 2019 at 15:02. Reason: added note about metafier |
|
12th January 2019, 11:41 | #6 | Link |
Registered User
Join Date: Oct 2001
Location: Germany
Posts: 7,259
|
Would be interested in that too.
Also is there a way to extract the data somehow? As a side note: does using Code:
--master-display G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1) --max-cll 1000,400 I thought those were HDR-10 settings and shouldn't be used with Dolby Vision. Cu Selur |
14th January 2019, 10:53 | #7 | Link | |
Compression mode: Lousy
Join Date: Mar 2009
Location: Hamburg, Germany
Posts: 72
|
Quote:
http://x265.org/x265-delivers-dolby-vision-streams/ |
|
15th January 2019, 23:01 | #8 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
|
|
11th November 2020, 17:00 | #17 | Link | |
Moderator
Join Date: Jan 2006
Location: Portland, OR
Posts: 4,750
|
Quote:
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... |
|
21st November 2020, 23:10 | #18 | Link |
Registered User
Join Date: Jan 2019
Location: Canada
Posts: 570
|
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. Last edited by quietvoid; 22nd November 2020 at 02:23. |
5th December 2020, 01:09 | #20 | Link | |
Registered User
Join Date: Nov 2020
Posts: 3
|
Quote:
I have a quick question on cropping. I'd like to crop the encode as well. Looking at these specific lines in vdr_dm_data.rs (https://github.com/quietvoid/dovi_to...a.rs#L309-L310) Am I right to assume that the active area for DV can be altered here by hard coding it into the RPU / EL to get a properly cropped encode with DV? Been experimenting with it a bit and I'm having trouble figuring out how the values can be altered. Can I simply hardcode a custom offset here and if so what would be the correct way to input them? Once again, thank you very much for the script. Works amazingly. And your insight would be most appreciated! |
|
Tags |
dolby vision, dovi, hdr, rpu, x265 |
Thread Tools | Search this Thread |
Display Modes | |
|
|