Displaying 3 results from an estimated 3 matches for "opus_demixing_matrix_size_max".
2018 Mar 07
1
[PATCH] Support for Ambisonics and Projection API.
...the #include around this #define. This will also allow us to not
have to explicitly enable ambisonics. :)
>
> The addition of fields to the OpusHead struct is a breaking ABI change
> (specifically, all callers of opus_head_parse() would need to be rebuilt
> from source).
>
> Is OPUS_DEMIXING_MATRIX_SIZE_MAX future-proof? I seem to recall much
> larger matrices being allowed according to the spec. You'll note that
> OPUS_CHANNEL_COUNT_MAX is 255, even though opusfile currently only supports
> mappings with up to 8 channels (see the private OP_NCHANNELS_MAX used
> internally, for compari...
2018 Mar 06
3
[PATCH] Support for Ambisonics and Projection API.
Hello all,
Attached are patches for libopusenc, opusfile and opus-tools in order to
provide support for Ambisonics and the Projection API for encoding/decoding
channel mapping 253 and 254.
Please feel free to ask any questions or give any feedback you might have.
:)
Cheers,
Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2018 Mar 07
0
[PATCH] Support for Ambisonics and Projection API.
...rc/internal.h for the hacks
I've had to do to detect other libopus API additions (hopefully we can
avoid things like that here).
The addition of fields to the OpusHead struct is a breaking ABI change
(specifically, all callers of opus_head_parse() would need to be rebuilt
from source).
Is OPUS_DEMIXING_MATRIX_SIZE_MAX future-proof? I seem to recall much
larger matrices being allowed according to the spec. You'll note that
OPUS_CHANNEL_COUNT_MAX is 255, even though opusfile currently only
supports mappings with up to 8 channels (see the private
OP_NCHANNELS_MAX used internally, for comparison). The idea w...