View Single Post
Old 8th August 2022, 01:31   #344  |  Link
Balling
Registered User
 
Join Date: Feb 2020
Posts: 541
Quote:
Originally Posted by FranceBB View Post
Dolby stuff have always been a pain to handle and after creating proprietary stuff with audio, now they're fiddling with video too. (T_T)

It took ages for the open source community to decode proprietary audio codecs like DolbyE (and the current ffmpeg implementation is far from ideal and only works with the u8 workaround which made me write several lines of code cross-checking with mediainfo given that ffprobe cannot even recognize DolbyE in an mxf container) and now they're back with DolbyED2 Atmos (currently impossible to decode) and DolbyVision profiles (also currently impossible to decode).
Best case scenario, they're just using the 12bit dual layer profile so that it's H.265 10bit PQ + metadata layer to create the 12bit and we can still watch the content by ignoring the proprietary Dolby Vision metadata layer. Worse case scenario: they're using the Dolby Vision Proprietary colorspace like dvhe0509 and we won't be able to see the content correctly (although there's been a recent attempt with libplacebo in VLC, MPV and Avisynth to tackle it).
Dolby e-destribution v2 Atmos samples welcome on ffmpeg bug tracker.

"they're using the Dolby Vision Proprietary colorspace like dvhe0509 and"

That was implemented in full. PQ 12 bit mapping would be good though.
Balling is offline   Reply With Quote