Displaying 6 results from an estimated 6 matches for "opus_copy_channel_out".
2017 Oct 04
3
[PATCH] Support for Channel Mapping 253.
...om the previous version?
2) Someone on this list might know better than I do on that one, but for
the new _ctl_va_list() calls, I believe the convention is for va_start()
and va_end() to appear in the caller rather than in in the va_list()
function itself.
3) I'm not sure I understand why the opus_copy_channel_out*() functions
had to be moved.
4) OpusPEncoder: I'd prefer a more explicit name: OpusProjectionEncoder
5) Do you need to expose the "generic" opus_projection_encode() and
opus_projection_encode_float() in the API?
6) In mapping_matrix_multiply_float(), for the !FIXED_POINT case you&...
2017 Oct 10
0
[PATCH] Support for Channel Mapping 253.
...ne, but for
the new _ctl_va_list() calls, I believe the convention is for va_start()
and va_end() to appear in the caller rather than in in the va_list()
function itself.
*My understanding is that it's impossible to pass ellipsis to another
function.*
3) I'm not sure I understand why the opus_copy_channel_out*() functions
had to be moved.
*Not sure how that happened. Reverted.*
4) OpusPEncoder: I'd prefer a more explicit name: OpusProjectionEncoder
*Done.*
5) Do you need to expose the "generic" opus_projection_encode() and
opus_projection_encode_float() in the API?
*I'm confused...
2017 Oct 10
2
[PATCH] Support for Channel Mapping 253.
...his list might know better than I do on that one, but for
> the new _ctl_va_list() calls, I believe the convention is for va_start()
> and va_end() to appear in the caller rather than in in the va_list()
> function itself.
>
> 3) I'm not sure I understand why the opus_copy_channel_out*() functions
> had to be moved.
>
> 4) OpusPEncoder: I'd prefer a more explicit name: OpusProjectionEncoder
>
> 5) Do you need to expose the "generic" opus_projection_encode() and
> opus_projection_encode_float() in the API?
>
> 6) In map...
2017 Sep 19
3
[PATCH] Support for Channel Mapping 253.
Hello all,
Attached is an up-to-date patch for supporting channel mapping 253. Please
advise and Thank you for your time.
Cheers,
Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/opus/attachments/20170919/055d9034/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name:
2017 Oct 10
0
[PATCH] Support for Channel Mapping 253.
...do on that one, but
> for
> > the new _ctl_va_list() calls, I believe the convention is for
> va_start()
> > and va_end() to appear in the caller rather than in in the va_list()
> > function itself.
> >
> > 3) I'm not sure I understand why the opus_copy_channel_out*()
> functions
> > had to be moved.
> >
> > 4) OpusPEncoder: I'd prefer a more explicit name:
> OpusProjectionEncoder
> >
> > 5) Do you need to expose the "generic" opus_projection_encode() and
> > opus_projection_encode_float(...
2017 Oct 11
2
[PATCH] Support for Channel Mapping 253.
...> the new _ctl_va_list() calls, I believe the convention is for
> va_start()
> > and va_end() to appear in the caller rather than in in the
> va_list()
> > function itself.
> >
> > 3) I'm not sure I understand why the opus_copy_channel_out*()
> functions
> > had to be moved.
> >
> > 4) OpusPEncoder: I'd prefer a more explicit name:
> OpusProjectionEncoder
> >
> > 5) Do you need to expose the "generic"
> opus_projection_encode() and
>...