Dolby Vision support #341
Comments
|
Latest updates from Dolby: https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-streams-within-the-http-live-streaming-format-v2.0.pdf Both specs introduce changes in Dolby Vision signaling in m3u8 and mpd compare to previous version. |
This is needed for Dolby Vision as Dolby Vision uses NAL unit type 62 to carry private information. Issue #341. Change-Id: Ib3f06d8f36ef3d89c33162dd74c012a0c3a805e5
|
Updated profiles-levels specification: https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-profiles-levels_v1.3.1.pdf |
|
@kqyang Any update on this ticket? Can we expect DV/HDR+ support in Shaka Packager in the next release? Thanks. |
|
@jigneshdhruv No. We'll update this issue if there are any updates. |
- Add relevant FOURCCs for Dolby Vision. - Parse DOVIDecoderConfigurationRecord (dvcC, dvvC) to generate Dolby Vision codec string. - Propagate Dolby Vision configs (dvcC, dvvC, hvcE) from Demuxer to Muxer. - Add a Dolby Vision end to end test. Support for backward compatibility signaling in DASH and HLS will be added in a later CL. Issue #341 Change-Id: If1385df5f48e04b59cb7661130bea48e26b453bf
Issue #341. Change-Id: I9665ba032b1e069500d866281cb8569ce59876f9
Issue #341 Change-Id: I530b0768341e352f6ee0a1326540cd5712f01638
|
Dolby Vision is already supported. Move the work on Dolby Vision backward compatible profile to #690. |
Added Dolby Vision backward compatible signalling, i.e. for Dolby Vision profile 8, both base codec without Dolby Vision and HDR codec with Dolby Vision are signalled. This is achieved by using a new MuxerListener implementation MultiCodecMuxerListener, which wraps multiple child MuxerListeners and is able to delegate to the child MuxerListeners based on the codecs in the stream. Closes #341. Change-Id: I1967bb1ed503087cdd011c364e5fb5647d516ca4
Dolby Vision Profiles: https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-profiles-levels-v1-2-92-171021.pdf
Our priority is to add support for profile 5 (which is an HEVC Main10 single stream) first, which is the only required and pushed by Dolby right now as far as I know.
Look at Dolby's spec at https://www.dolby.com/us/en/technologies/dolby-vision/dolby-vision-bitstreams-within-the-iso-base-media-file-format.pdf, it seems trivial to add support for Dolby Vision Profile 5. What we need is to add support for Dolby Vision sample entries and Dolby Vision Configuration box. Everything else should be transparent.
The text was updated successfully, but these errors were encountered: