-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check Dolby Atmos and Dolby Vision in current stream #1266
Comments
Hi! For dolby atmos:Looking at it a little, I see that from Dolby, all their provided MPD (so, for DASH) examples with dolby atmos are actually using what dolby calls JOC, for "Joint Object Coding", which is actually packaged in a Dolby Digital + format (with the ec-3 codec) and is retro-compatible to DD+ decoders. To know that we're here handling Dolby Atmos JOC audio track in a player, they seem to advise the usage of two <SupplementalProperty schemeIdUri="tag:dolby.com,2018:dash:EC3_ExtensionType:2018" value="JOC"/>
<SupplementalProperty schemeIdUri="tag:dolby.com,2018:dash:EC3_ExtensionComplexityIndex:2018" value="16"/> The first one indicating that this is JOC, the second one indicating the " decoding complexity of the enhanced AC-3 extension", "equal to the total number of bed objects, ISF objects and dynamic objects" (presumably pertinent for audio decoding only, in which case we may just ignore it?). So now I'm wondering how the RxPlayer should behave when encountering this, while still allowing for future similar technologies and streaming protocol transparency. I looked at what other players were doing.
I think indicating for spatial audio in audio track-related API could be a good way to signal Dolby atmos to an application for now, but this is not yet developed. You're welcome if you want to do it. Dolby visionWe're used to (and we rely on this in production) it being simply defined as a specific codec, often beginning by the However some examples on the web provided by Dolby seems to put it in a special "scte214:supplementaryCodecs" attribute instead. I don't know why and I hope this isn't frequent. |
Hi, For dolby Atmos, this has been merged and release in the For dolby vision, we saw recently that some DASH packagers, like to announce Dolby vision in a We're working on this here: #1307 |
Now that the work has been merged:
I'm closing this issue now to facilitate our management of them, don't hesitate to re-open it if that's not clear or non functional for you. |
Hi there!
Is there way to check Dolby Atmos and Dolby Vision are playing in current stream?
Thanks!
The text was updated successfully, but these errors were encountered: