You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those two came to mind yes, but I was also thinking of making it clear how layouts are supported, in relation to how the Web Audio API does things, and how to handle (e.g.) Opus mapping family 255.
If so I assume that means decoding multistream packets is not supported?
Decoding multi-stream packets is supported, as long as the appropriate description field is set.
I think that this issue is partially about mapping the channels once they are decoded? For example, channel mapping 1 (which is multistream) has standard layouts which allow good mappings to be made for spatial audio, whereas channel mapping 255 is completely arbitrary.
For now, the support is fairly minimal and a bit inconsistent.
The text was updated successfully, but these errors were encountered: