Log in

View Full Version : DolbyVision encode error: ": Dolby Vision requires VBV settings to enable HRD"


blublub
29th January 2020, 12:51
Hi

can anyone help me how to solve this error:

: Dolby Vision requires VBV settings to enable HRD.

Command line:
--colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --crf 16 --fps 24000/1001 --min-keyint 24 --keyint 240 --frames 5742 --sar 1:1 --profile main10 --output-depth 10 --level-idc=51 --high-tier --no-sao --ctu=32 --rd=4 --psy-rdoq=2 --frame-threads=2 --me=3 --subme=2 --qcomp=0.8 --bframes=6 --ref=5 --psy-rd=2 --hdr-opt --hrd-concat --hrd --colormatrix=bt2020nc --chromaloc=2 --transfer=smpte2084 --aq-mode=1 --deblock=-1:-1 --rc-lookahead=23 --dolby-vision-profile=8.1

thx

benwaggoner
29th January 2020, 16:55
You need to set --vbv-bufsize and --vbv-maxrate to the appropriate values. I don't know what those would be for your scenario. It's not clear what you're doing here; high tier plus 10 second GOP isn't supported by anything I can think.

blublub
29th January 2020, 20:27
You need to set --vbv-bufsize and --vbv-maxrate to the appropriate values. I don't know what those would be for your scenario. It's not clear what you're doing here; high tier plus 10 second GOP isn't supported by anything I can think.

Hi

Where did I specify "10 second GOP" ? I cant see it

benwaggoner
29th January 2020, 20:34
Hi

Where did I specify "10 second GOP" ? I cant see it

--keyint 240 --min-keyint 24 --fps 24000/1001 give you a 1-10 sec GOP.

blublub
29th January 2020, 20:50
--keyint 240 --min-keyint 24 --fps 24000/1001 give you a 1-10 sec GOP.Mhh that is Auto-set by Ripbot.
The encode actually started after adding the vbv setting. Maybe it'll work and I get a x265 mkv with Dolby Vision and Hdr10 fallback

benwaggoner
29th January 2020, 23:32
Mhh that is Auto-set by Ripbot.
The encode actually started after adding the vbv setting. Maybe it'll work and I get a x265 mkv with Dolby Vision and Hdr10 fallback
What are you playing it back on, though? Not much will support High Tier Level 5.1.

blublub
30th January 2020, 08:45
What are you playing it back on, though? Not much will support High Tier Level 5.1.HTPC. So far it could handle it.

benwaggoner
31st January 2020, 01:32
HTPC. So far it could handle it.
Using GPU decode?

Blue_MiSfit
31st January 2020, 03:35
What HTPC can actually do the Dolby Vision part of this? AFAIK Dolby Vision output (Profile 5 or 8.1) from PC isn't possible yet. I could be wrong tho :)

You sure you're not just seeing the HDR10 base layer from the Profile 8.1 stream?

blublub
31st January 2020, 08:05
What HTPC can actually do the Dolby Vision part of this? AFAIK Dolby Vision output (Profile 5 or 8.1) from PC isn't possible yet. I could be wrong tho :)

You sure you're not just seeing the HDR10 base layer from the Profile 8.1 stream?Hi

It probably would play it.
The main thing I noticed yesterday is that mkv container doesn't work with DV, so it's not going to work anyway and I just encode HDR 10 or 10+ as it seems, whatever the fallback option is.
Looks like I gotta redo those titles once it becomes a workable option

RanmaCanada
31st January 2020, 17:10
The problem is that yes, mkv doesn't support Dolby Vision, but also that the only way for consumers to play it back outside of the UHD, AFAIK is the old, discontinued Oppo UHD Player. You could rip the disc and play it back via network, but it had to be an exact image of the disc. As for muxing into a .TS or an mp4, there are issues there as well.

"Single track DV plays fine on LG TVs and Apple TV 4K, but UHD discs are dual track and can ONLY be played on the discontinued Oppo player. It’s EXTREMELY unlikely there will ever be a software solution to play dual track DV, so the big open question is can someone get ahold of software to change dual-track to single track. So far no luck. Also the DV layer needs to be embedded using special software and hardware which is locked down and not available to the public." <--lifted from reddit

There is currently also no software players that support Dolby Vision on PC. Yes you can play games that are in Dolby Vision, but that's because it's baked into the game with all the coding. Let's also not forget that Windows still can't do basic HDR properly. Even Kodi just recently got Dolby Vision working on Netflix, but not with anything else.

Blue_MiSfit
31st January 2020, 18:54
Dolby Vision MP4 files play just fine via USB on LG TVs (2016+ OLED) - that's how I do all my test encodes :)

RanmaCanada
1st February 2020, 02:59
Dolby Vision MP4 files play just fine via USB on LG TVs (2016+ OLED) - that's how I do all my test encodes :)

Yes but it will only play on a select few devices. My TCL 6 series will not play such files, even though the TV 100% supports Dolby Vision.

Basically your Dolby Encodes are the equivalent of making mini-disc copies of your stuff. The moment your TV dies, or a new firmware update breaks the feature, your encodes will stop working as they aren't standard.

It sucks as Dolby Vision is far superior to HDR.

blublub
1st February 2020, 18:49
Yep. And most titles ra Dolby Vision anyway. Just like a handful have HDR10+

Blue_MiSfit
1st February 2020, 23:38
To get playback on other devices (Apple TV, Chromecast, Android TV, Amazon Fire TV, etc) you generally have to segment the content into fragmented mp4 / cmaf and use an HLS playlist or DASH manifest to serve it up from a web server using the native player of the device.

Dolby Vision is widely supported these days, but generally only via DASH / HLS in the native players / a native app on these devices.