jcdr428 wrote: ↑
Tue Mar 31, 2020 6:04 pm
means there is no backward compatibility. SDR is 1, 1, 1, HDR10 is 9, 16, 9.
Primary Dolby Vision PID Carrying a non-SDR and non-HDR Compliant BL substream
The value of stream_type shall be set to 0x06 (indicating PES packets containing private data).
I think what you think (in fact I had written despite
color_description_present_flag = 0 and chroma_location_info_present = 0)
But then I analyze the LG demo (I think LG has all the hardware and software certified by Dolby) and I see this:
stream_type shouldn't be 0x06? (I don't think it's because of the presence of HEVC_timing_and_HRD_descriptor in place of 0x0504444F5649)
jcdr428 wrote: ↑
Tue Mar 31, 2020 8:26 pm
The way FEL is triggered in the RPU of profile 7 and of profile 4/6 seems to be different. So it is not as simple as copying the EL/RPU from the second track to the first.
Edit: if anyone is interested in parsing RPU information https://patentimages.storage.googleapis ... 9132A1.pdf
About 20 days ago I posted the comparison between two RPU headers (HERE
). Out of curiosity, I analyzed an RPU of the LG demo (BL+EL+RPU, dvhe.04.06) and the header is identical to that of the MEL stream (from a UHD-BD).
I didn't go beyond the header because that document is a nightmare.
I don't think current RPUs are implemented as described in the patent.
A simple example, considering the final sequence 0b10000000 (0x80) as rbsp_trailing_bits(), the previous 4 bytes should represent the CRC value (calculated on the entire rpu_data () excluding rpu_data_crc32).
The calculated CRC32 value never corresponds to that present in the RPU.
As for the FEL layer, in the case of profile 4, a device must control and must flag, in case of profile 7 the device can control and can flag. However, the variables to be checked are the same.
The fact that on LG televisions a BL+EL+RPU file goes jerky (unlike a simple BL+RPU) could be due precisely to the presence of the FEL layer which saturates the decoder buffer.
My dvhe.04 files are High Tier 5.1 (both BL and FEL/MEL because they come from a UHD-BD)
From the official Dolby documentation:
Code: Select all
In certain cases, the Dolby Vision specification imposes tighter constraints on the maximum tier bit rate and
the maximum decoded picture buffer size, as compared to the HEVC Main10 Level 5.1 specification.
See sections Dolby Vision levels and Limitation on decoder buffer size.
shawnc22 wrote: ↑
Tue Mar 31, 2020 3:38 pm
When playing back the DV4 file, the renderer actually lists the codec as dvhe.04.06, but nothing for the DV6 file.
I'm sorry guys but the latest version of Exoplayer (2.10) does not support profile 6. There is an article about it on the developer blog (HERE
) and checking the code (HERE
) it shows the same thing!