Displaying 10 results from an estimated 10 matches for "ope_".
Did you mean:
ope
2018 Mar 20
2
[PATCH] Support for Ambisonics
...018 02:40 AM, Mark Harris wrote:
> > + int _oge_use_projection(int channel_mapping);
> >
> > These functions are part of libopusenc, so I'd expect them to have an
> > ope prefix like the other functions in the libopusenc library.
>
> I'd like to avoid using the ope_ prefix for functions that's aren't in
> the public API. Right now there are other functions with a leading
> underscore, so we'll have to fix them as well (not in this patch of
> course). Maybe an "opeint_" prefix would do the job here (unless anyone
> has a better...
2018 Mar 20
2
[PATCH] Support for Ambisonics
...nt _oge_use_projection(int channel_mapping);
> > >
> > > These functions are part of libopusenc, so I'd expect them to have
> an
> > > ope prefix like the other functions in the libopusenc library.
> >
> > I'd like to avoid using the ope_ prefix for functions that's aren't
> in
> > the public API. Right now there are other functions with a leading
> > underscore, so we'll have to fix them as well (not in this patch of
> > course). Maybe an "opeint_" prefix would do the job here...
2018 Mar 22
2
[PATCH] Support for Ambisonics
...> >
> > > > These functions are part of libopusenc, so I'd expect them
> > to have an
> > > > ope prefix like the other functions in the libopusenc
> library.
> > >
> > > I'd like to avoid using the ope_ prefix for functions that's
> > aren't in
> > > the public API. Right now there are other functions with a
> leading
> > > underscore, so we'll have to fix them as well (not in this
> > patch of
> > > course). May...
2018 Mar 26
3
[PATCH] Support for Ambisonics
...; These functions are part of libopusenc, so I'd expect them
>>> > to have an
>>> > > > ope prefix like the other functions in the libopusenc
>>> library.
>>> > >
>>> > > I'd like to avoid using the ope_ prefix for functions that's
>>> > aren't in
>>> > > the public API. Right now there are other functions with a
>>> leading
>>> > > underscore, so we'll have to fix them as well (not in this
>>> > patc...
2018 Mar 20
2
[PATCH] Support for Ambisonics
...re; the family field in this structure is not actually used
except to compare the value to 253 to determine whether to use the
"ms" or "pr" pointer. It would be simpler to omit the incorrectly-set
family field and just check whether the corresponding pointer is
non-NULL.
-int ope_encoder_deferred_init_with_mapping(OggOpusEnc *enc, int
family, int streams,
+int ope_encoder_deferred_init_with_mapping(OggOpusEnc *enc, int
family, int streams,
int coupled_streams, const unsigned char *mapping) {
int ret;
int i;
- OpusMSEncoder *st;
+ OpusGenericEncoder *st;
if (e...
2018 Mar 20
0
[PATCH] Support for Ambisonics
Hi Mark, Drew,
On 03/20/2018 02:40 AM, Mark Harris wrote:
> + int _oge_use_projection(int channel_mapping);
>
> These functions are part of libopusenc, so I'd expect them to have an
> ope prefix like the other functions in the libopusenc library.
I'd like to avoid using the ope_ prefix for functions that's aren't in
the public API. Right now there are other functions with a leading
underscore, so we'll have to fix them as well (not in this patch of
course). Maybe an "opeint_" prefix would do the job here (unless anyone
has a better idea)?
> +int o...
2018 Mar 20
0
[PATCH] Support for Ambisonics
...rris wrote:
> > + int _oge_use_projection(int channel_mapping);
> >
> > These functions are part of libopusenc, so I'd expect them to have an
> > ope prefix like the other functions in the libopusenc library.
>
> I'd like to avoid using the ope_ prefix for functions that's aren't in
> the public API. Right now there are other functions with a leading
> underscore, so we'll have to fix them as well (not in this patch of
> course). Maybe an "opeint_" prefix would do the job here (unless anyone
>...
2018 Mar 22
0
[PATCH] Support for Ambisonics
...nt channel_mapping);
> > >
> > > These functions are part of libopusenc, so I'd expect them
> to have an
> > > ope prefix like the other functions in the libopusenc library.
> >
> > I'd like to avoid using the ope_ prefix for functions that's
> aren't in
> > the public API. Right now there are other functions with a leading
> > underscore, so we'll have to fix them as well (not in this
> patch of
> > course). Maybe an "opeint_" pref...
2018 Mar 26
0
[PATCH] Support for Ambisonics
...gt; > > These functions are part of libopusenc, so I'd expect them
>> > to have an
>> > > > ope prefix like the other functions in the libopusenc
>> library.
>> > >
>> > > I'd like to avoid using the ope_ prefix for functions that's
>> > aren't in
>> > > the public API. Right now there are other functions with a
>> leading
>> > > underscore, so we'll have to fix them as well (not in this
>> > patch of
>> >...
2018 Jul 07
0
[PATCH] Support for Ambisonics
...;>>> > to have an
>>>>>>> > > > ope prefix like the other functions in the libopusenc
>>>>>>> library.
>>>>>>> > >
>>>>>>> > > I'd like to avoid using the ope_ prefix for functions
>>>>>>> that's
>>>>>>> > aren't in
>>>>>>> > > the public API. Right now there are other functions with
>>>>>>> a leading
>>>>>>> > >...