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. |
![]() |
#7841 | Link |
QfG Group Germany
Join Date: Oct 2018
Location: Germany
Posts: 275
|
dv profile 7 is Dual Layer. I need Profile 8.1 Single Layer DV + HDR Support. The newest makeMKV can create this Video Stream from a DV Dual Layer UHD, so i have one Single DV + HDR Videostream.
I search a Tool, that can convert 2 Streams (Video Layer and Dolby Vision Layer) in a Single Layer DV Profile 8.1.
__________________
|
![]() |
![]() |
![]() |
#7842 | Link | |
Registered User
Join Date: Dec 2014
Posts: 240
|
Quote:
Code:
https://www.makemkv.com/forum/viewtopic.php?f=12&t=18602&p=96282#p96282
__________________
AMD Ryzen 9 5950X, 32GB DDR4-3200 CL16, RTX 3060, 2TB NVMe PCIE4.0, NAS with 8x16TB HDD |
|
![]() |
![]() |
![]() |
#7843 | Link | |
Registered Loser
Join Date: Dec 2004
Posts: 119
|
Quote:
If you truly want Profile 8.1, you'll need the RPU extracted as an elementary stream and can use x265.exe to encode it with this guide: http://x265.org/x265-delivers-dolby-vision-streams/ The MakeMKV guide linked above is good if you just want to remux, but depending on your player - TV's tend to like dual-layer DV and players like NVidia Shield want single layer DV. Muxing the video - well, let's just say that Dolby's mp4muxer doesn't like to mux encoded x265 Dolby Vision Profile 8.1 streams - it tends to just hang. I would advise using TSMuxeR until MKVToolnix has native support, assuming they handle other DV profiles when support is added. If you can get mp4muxer to work on encoded DV content, I'm all ears on how you got it to work. |
|
![]() |
![]() |
![]() |
#7844 | Link | |
Registered User
Join Date: Dec 2014
Posts: 240
|
Quote:
With the guide o posted, you can encode pure HDR without cropping, the use encoded hevc to combine with EL+RPU to combine into PROFILE 8.1
__________________
AMD Ryzen 9 5950X, 32GB DDR4-3200 CL16, RTX 3060, 2TB NVMe PCIE4.0, NAS with 8x16TB HDD |
|
![]() |
![]() |
![]() |
#7845 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,175
|
New upload: x265 3.4+27-g5163c32d7
CLI changes since x265 3.4+14-gd419c7152:
Last edited by LigH; 17th November 2020 at 11:27. |
![]() |
![]() |
![]() |
#7846 | Link |
Registered User
Join Date: Jan 2020
Posts: 34
|
Version 3.0
hello, on version 3.0 you have introduced the parameters:
–dolby-vision-profile <integer|float> and –dolby-vision-rpu’ File containing Dolby Vision RPU metadata. Excluding as for: --dhdr10-info You do not provide anything to exploit them. Indeed how to extract the Dolby Vision RPU? So these parameters are not usable. For HDR10 + (--dhdr10-info) a coder had to face a python script to extract the metadata to use the: --dhdr10-info. So what do we do to exploit the: –dolby-vision-rpu thank |
![]() |
![]() |
![]() |
#7847 | Link |
German doom9/Gleitz SuMo
Join Date: Oct 2001
Location: Germany, rural Altmark
Posts: 7,175
|
New upload: x265 3.4+30-g6722fce1f
|
![]() |
![]() |
![]() |
#7848 | Link | |
Moderator
![]() Join Date: Jan 2006
Location: Portland, OR
Posts: 4,955
|
Quote:
Dolby hasn't really invested in making Dolby Vision a hobbyist-friendly format. Although the support in the iPhone 12 Pro might change that some. But even that uses a new profile that's not widely supported by TVs (HLG + metadata), and doesn't have RPU data compatible with typical DoVi content. Making a DoVi Blu-ray from an iPhone DoVi file requires changing every pixel in the video and generating new dynamic metadata. |
|
![]() |
![]() |
![]() |
#7850 | Link | |
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 3,179
|
Quote:
I saw the "Dolby Vision" announcement days ago, but it was rather vague. Is it H.265 10bit UHD HDR HLG 60p with metadata? Does it have the FULL HD 10bit additional layer with info to make the 12bit final result? Or perhaps it's still one layer in 8bit? And most importantly, given that most mobile phones have a ridiculously tiny sensor whose stops are low, does all this even make sense? I mean, I read that it can achieve up to 12 stops, but I think that it's not gonna get even close. SDR in BT709 100 nits is 6 stops, if they manage to get 9 stops out of that it would already be a miracle... |
|
![]() |
![]() |
![]() |
#7852 | Link | |
Registered User
Join Date: Nov 2009
Location: Sammamish, WA
Posts: 66
|
Quote:
Profile 5 and 8 are single layer 10-bit profiles. Profile 7 has the additional full enhancement layer for addition bit-depth. Profile 5 uses ICtCp while Profile 7 and 8 use YCbCr. The reason the iPhone went with Profile 8.3 was so they would not have to tone map for the SDR version. |
|
![]() |
![]() |
![]() |
#7853 | Link | |
Registered User
Join Date: Dec 2008
Posts: 416
|
Quote:
|
|
![]() |
![]() |
![]() |
#7854 | Link | |
Derek Prestegard IRL
![]() Join Date: Nov 2003
Location: Los Angeles
Posts: 5,998
|
Quote:
So, from a backwards compatibility standpoint, you can either use WCG (and thus only be really backwards compatible with SDR WCG displays of which there aren't too many AFAIK) or use standard 709 gamut and thus be only HDR and not WCG which won't take advantage of modern HDR displays that are all WCG. Do I have that wrong? |
|
![]() |
![]() |
![]() |
#7855 | Link | |
Moderator
![]() Join Date: Jan 2006
Location: Portland, OR
Posts: 4,955
|
Quote:
My take on HLG has been "it may work in practice, but it definitely doesn't work in theory!" |
|
![]() |
![]() |
![]() |
#7856 | Link | |
Moderator
![]() Join Date: Jan 2006
Location: Portland, OR
Posts: 4,955
|
Quote:
Profile 8.3 isn't great, but it makes for a substantially better HDR source than anything 709 would be. The 12 Pro Max with its improved optics will probably lead to some interesting student and experimental HDR (and HFR) titles. Biggest question is how clean the HEVC encoding will be. I need to finally order mine. |
|
![]() |
![]() |
![]() |
#7857 | Link | ||
Broadcast Encoder
Join Date: Nov 2013
Location: Royal Borough of Kensington & Chelsea, UK
Posts: 3,179
|
Quote:
Also, if it's not and they're just displaying BT2020 on non BT2020 compatible displays that's a poor choice as well... Quote:
My take is: most users are too "inexpert" to notice... (and with the term "inexpert" I've been very kind) |
||
![]() |
![]() |
![]() |
#7858 | Link | ||
Moderator
![]() Join Date: Jan 2006
Location: Portland, OR
Posts: 4,955
|
Quote:
Quote:
|
||
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|