Hi,
I investigated Dolby Reference Player and found something that may be relevant to KSPlayer.
Dolby Reference Player ships with GStreamer 1.22 and several Dolby-specific plugins, including:
- dlbac3dec
- dlbtruehddec
- dlbac3parse
- dlbtruehdparse
- dlboar (Dolby Object Audio Renderer)
- dlbaudiodecbin
From my inspection, these plugins appear capable of decoding:
- Dolby Digital Plus (E-AC3)
- Dolby Digital Plus JOC (Atmos)
- Dolby TrueHD
- Dolby TrueHD Atmos
and rendering Atmos object metadata through Dolby OAR into layouts such as:
- 5.1.2
- 5.1.4
- 7.1.2
- 7.1.4
- 7.1.6
- 9.1.2
- 9.1.4
- 9.1.6
This suggests a potentially different approach from using AVPlayer.
Instead of controlling Dolby Reference Player itself, KSPlayer could investigate whether licensed users who own Dolby Reference Player could optionally use the Dolby GStreamer plugins already installed on their system.
Possible architecture:
KSPlayer:
- MKV demuxing
- Video rendering
- Subtitles
- Seeking
- Playback synchronization
- UI
Audio path:
appsrc
-> dlbac3parse / dlbtruehdparse
-> dlbac3dec / dlbtruehddec
-> dlboar
-> appsink
KSPlayer would then receive decoded PCM from appsink and keep full control over playback synchronization.
You can check it out and trial free here : https://professionalsupport.dolby.com/s/dolby-reference-player?language=en_US it's not too expensive so I think it can be a good compromise
Hi,
I investigated Dolby Reference Player and found something that may be relevant to KSPlayer.
Dolby Reference Player ships with GStreamer 1.22 and several Dolby-specific plugins, including:
From my inspection, these plugins appear capable of decoding:
and rendering Atmos object metadata through Dolby OAR into layouts such as:
This suggests a potentially different approach from using AVPlayer.
Instead of controlling Dolby Reference Player itself, KSPlayer could investigate whether licensed users who own Dolby Reference Player could optionally use the Dolby GStreamer plugins already installed on their system.
Possible architecture:
KSPlayer:
Audio path:
appsrc
-> dlbac3parse / dlbtruehdparse
-> dlbac3dec / dlbtruehddec
-> dlboar
-> appsink
KSPlayer would then receive decoded PCM from appsink and keep full control over playback synchronization.
You can check it out and trial free here : https://professionalsupport.dolby.com/s/dolby-reference-player?language=en_US it's not too expensive so I think it can be a good compromise