Page 13 of 113
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 2:27 pm
by jcdr428
@kcxserver
Profile 4: BL+EL+RPU, SDR compatible
Profile 5: BL+RPU, (Unspecified colorspace = IPT)
Profile 6: BL+EL+RPU, HDR10 compatible
Profile 7: track 1 BL non-DV, track 2 EL+RPU HDR10 compatible
Profile 8: BL+RPU, HDR10 or HLG or SDR compatible
For dual layer profiles 4, 6 and 7, the BL (Base Layer) is the SDR or HDR10 HEVC layer, the EL (Enhancement Layer) is the Dolby Vision HEVC layer.
Profile 4 is deprecated for service providers (Netflix, Amazon etc.) only: no point broadcasting dual layers.
IMHO Profile 6 and 8 are being deprecated by Dolby because Dolby do not need/want compatibility with concurrent HDR10 anymore. This does not mean that SoC reading P4 (resp. P5) will not keep on reading P6 (resp. P8).
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 3:11 pm
by cardsdoc
Not sure if this was mentioned or not but if I re-mux an MKV using MKVtoolnix will it retain the DV data from MakeMKV? Thanks.
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 3:50 pm
by shawnc22
kcxserver wrote: ↑Fri Apr 24, 2020 11:41 am
shawnc22 wrote: ↑Thu Apr 23, 2020 3:41 pm
Double
PID = 2x HEVC 10bit tracks with the secondary PID containing (EL+RPU) data.
Single
PID = 1x HEVC 10bit track (BL+EL+RPU -> double layer or BL+RPU -> single layer)
Ok as I said I am not an expert but I read a lot about DV. I have never read or heard of PID. Google also does not tell me what that should be.
I always understood the Dolby Vision white paper as 2x HEVC is dual layer and 1x is single layer. Or do I get the graphic wrong:
PID information can be found here on page 13:
https://www.dolby.com/us/en/technologie ... x-v1.2.pdf.
@jcdr428
Any reason why a simple hex edit of dv descriptors in the TS files doesn't work for changing profiles like it does for MP4s?
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 6:06 pm
by steffenmanden
If you got a github account try and go to
https://github.com/google/ExoPlayer/issues/7267
And write that you find it interesting as well - increased interest might bump the priority!
Just only do it if you already got an account so we dont spam with newly created accounts!
Mike wrote his interest as well
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 6:11 pm
by jcdr428
shawnc22 wrote: ↑Fri Apr 24, 2020 3:50 pm
@jcdr428 Any reason why a simple hex edit of dv descriptors in the TS files doesn't work for changing profiles like it does for MP4s?
The TS DOVI descriptor is different from the MP4 DV atom.
In a MP4, there is only one single DV (dvhe or else) atom. In a TS -which main purpose is broadcasting-, the PMT packets with the descriptors are interleaved at least every 100 ms -with tsMuxer every two images.
Examples of DOVI descriptors:
"B0 04 01 00 08 47" with B0 = DOVI descriptor, 04 = descriptor length, 01 = DV major version, 00 = DV minor version, 08 37 = profile 4 (7-bits), level 8 (6-bits), RPU_present, EL_present, BL_present.
"B0 06 01 00 0E 36 80 8F" with B0 = DOVI descriptor, 06 = descriptor length, 01 = DV major version, 00 = DV minor version, 0E 36 = profile 7 (7-bits), level 6 (6-bits), RPU_present, EL_present, BL_not_present, BL=PID 0x1011 (13-bits), reserved (3-bits)
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 6:19 pm
by Hanto
@jcdr428
Do you know why all ts files made by tsmuxer doesn't work whatever the DV profile when MP4 file works fine ?
Thank you
https://www.makemkv.com/forum/viewtopic ... 160#p88027
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 6:56 pm
by shawnc22
jcdr428 wrote: ↑Fri Apr 24, 2020 6:11 pm
shawnc22 wrote: ↑Fri Apr 24, 2020 3:50 pm
@jcdr428 Any reason why a simple hex edit of dv descriptors in the TS files doesn't work for changing profiles like it does for MP4s?
The TS DOVI descriptor is different from the MP4 DV atom.
In a MP4, there is only one single DV (dvhe or else) atom. In a TS -which main purpose is broadcasting-, the PMT packets with the descriptors are interleaved at least every 100 ms -with tsMuxer every two images.
Examples of DOVI descriptors:
"B0 04 01 00 08 47" with B0 = DOVI descriptor, 04 = descriptor length, 01 = DV major version, 00 = DV minor version, 08 37 = profile 4 (7-bits), level 8 (6-bits), RPU_present, EL_present, BL_present.
"B0 06 01 00 0E 36 80 8F" with B0 = DOVI descriptor, 06 = descriptor length, 01 = DV major version, 00 = DV minor version, 0E 36 = profile 7 (7-bits), level 6 (6-bits), RPU_present, EL_present, BL_not_present, BL=PID 0x1011 (13-bits), reserved (3-bits)
Ah got it, so it's not as simple as changing the DOVI values at the first occurrence (e.g. 0C 37 -> 08 37 to go from dvhe.6.06 -> dvhe.4.06) because the descriptors are also interleaved with the images during the muxing process. I do see all the multiple instances of the descriptor now when doing additional finds. Can I simply then do a replaceall or must I repeat the muxing process?
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 7:00 pm
by jcdr428
Hanto wrote: ↑Fri Apr 24, 2020 6:19 pm
Do you know why all ts files made by tsmuxer doesn't work whatever the DV profile when MP4 file works fine ?
There was a version working on TVs, which removed the HDMV descriptors for .ts files. As already explained, I had to re-introduce the hdmv descriptors due to PGS/ac3+trueHD not working anymore -these are hmdv specific. Now I've pushed a
fix pending merge, where the user can manually deselect hdmv descriptors for .ts.
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 7:06 pm
by Hanto
jcdr428 wrote: ↑Fri Apr 24, 2020 7:00 pm
Hanto wrote: ↑Fri Apr 24, 2020 6:19 pm
Do you know why all ts files made by tsmuxer doesn't work whatever the DV profile when MP4 file works fine ?
There was a version working on TVs, which removed the HDMV descriptors for .ts files. As already explained, I had to re-introduce the hdmv descriptors due to PGS/ac3+trueHD not working anymore -these are hmdv specific. Now I've pushed a
fix pending merge, where the user can manually deselect hdmv descriptors for .ts.
@jcdr428
If I understand, if HDMV descriptors is not selected, ts file will work ?
Because "Generate HDMV compatible TS" is not selected and doesn't work too.
Thank you again
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 8:06 pm
by jcdr428
Hanto wrote: ↑Fri Apr 24, 2020 7:06 pm
If I understand, if HDMV descriptors is not selected, ts file will work ?
Because "Generate HDMV compatible TS" is not selected and doesn't work too.
For the moment the option (from old tsMuxer 2.6.12) only changes the AC3 stream_id.
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 8:20 pm
by cardsdoc
All my discs are ripped as MKVs with Plex server serving to 2019 Shield and several ATV4Ks. All my DV discs are additionally ripped to full folder backup and can be streamed to my Oppo 203 if I want DV. I made a few DV TS files with THD/Atmos as per the excellent work from all contributors here which work fine on the 2019 Shield via Plex and is really cool. But to be honest on my pro calibrated LG C7 OLED the difference between HDR10 with active HDR on and DV is very subtle at best. Additionally I prefer to have the chapter and PGS subtitle support. So for now I'm just going to re-rip from the DV full disk backups to MKVs and if Plex decides to support DV via these MKVs great and it should work without further effort but if not I'm not finding it to be worth the effort of also creating TS DV files for now. But for those that want it I think this progress is great.
Re: Dolby Vision and 1.15.1
Posted: Fri Apr 24, 2020 8:31 pm
by ragico
steffenmanden wrote: ↑Fri Apr 24, 2020 6:06 pm
If you got a github account try and go to
https://github.com/google/ExoPlayer/issues/7267
And write that you find it interesting as well - increased interest might bump the priority!
Just only do it if you already got an account so we dont spam with newly created accounts!
Mike wrote his interest as well
Done
Re: Dolby Vision and 1.15.1
Posted: Sat Apr 25, 2020 2:14 am
by Cruzader1986
cardsdoc wrote: ↑Fri Apr 24, 2020 3:11 pm
Not sure if this was mentioned or not but if I re-mux an MKV using MKVtoolnix will it retain the DV data from MakeMKV? Thanks.
I tried doing this and the resulting file size was bigger by a few mbs. Then I tried using tsmuxer and the resulting .ts was still labeled as dolby vision
Re: Dolby Vision and 1.15.1
Posted: Sat Apr 25, 2020 2:44 am
by Angryunibrow
jcdr428 wrote: ↑Fri Apr 24, 2020 8:06 pm
Hanto wrote: ↑Fri Apr 24, 2020 7:06 pm
If I understand, if HDMV descriptors is not selected, ts file will work ?
Because "Generate HDMV compatible TS" is not selected and doesn't work too.
For the moment the option (from old tsMuxer 2.6.12) only changes the AC3 stream_id.
Will this allow making a profile 7 again with .ac3 audio to play on the LG TVs, they would never work because I think of the HDMV descriptors if I remember you mentioning earlier?
What build will this new fix be in so i can test it out.
Re: Dolby Vision and 1.15.1
Posted: Sat Apr 25, 2020 6:52 am
by DaMacFunkin
cardsdoc wrote: ↑Fri Apr 24, 2020 8:20 pm
All my discs are ripped as MKVs with Plex server serving to 2019 Shield and several ATV4Ks. All my DV discs are additionally ripped to full folder backup and can be streamed to my Oppo 203 if I want DV. I made a few DV TS files with THD/Atmos as per the excellent work from all contributors here which work fine on the 2019 Shield via Plex and is really cool. But to be honest on my pro calibrated LG C7 OLED the difference between HDR10 with active HDR on and DV is very subtle at best. Additionally I prefer to have the chapter and PGS subtitle support. So for now I'm just going to re-rip from the DV full disk backups to MKVs and if Plex decides to support DV via these MKVs great and it should work without further effort but if not I'm not finding it to be worth the effort of also creating TS DV files for now. But for those that want it I think this progress is great.
Hi, are you sure a pro would enable active HDR? From what I read on the calibration forums at abs it doesn’t provide a reference picture as the TV gueses the Tone Map as it goes along. I have a C7 and a C9 calibrated by myself with Calman and I have dynamic tone mapping turned off on both, just saying.