Displaying 20 results from an estimated 2000 matches similar to: "[PATCH] Support for Ambisonics"
2018 Mar 19
3
[PATCH] Support for Ambisonics
Hi Drew,
I think the libopusenc patch is better, but there's still a few issues left:
1) The static MAX_PACKET_BUFFER_SIZE value is still problematic because
if you link libopusenc with a new version of libopus that supports
higher order projection or just more projection channels for order 3,
then you will overflow the buffer. I think what you'd want is a
_ope_opus_header_get_size() call
2018 Mar 26
3
[PATCH] Support for Ambisonics
Apologies! That patch will not work correctly with Opus 1.2. Will send an
updated patch shortly!!
On Mon, Mar 26, 2018 at 11:56 AM Drew Allen <bitllama at google.com> wrote:
> Hello all!
>
> I've attached an updated patch for opusfile, based on formatting
> suggestions I got for the opus and libopusenc patches.
>
> Cheers!
> Drew
>
> On Thu, Mar 22, 2018 at
2018 Mar 20
2
[PATCH] Support for Ambisonics
Just to confirm, I would use opeint_* for all the
OpusGenericEncoder-related functions?
On Tue, Mar 20, 2018 at 8:38 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> 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
2018 Mar 22
2
[PATCH] Support for Ambisonics
Thanks! 2 down, 2 to go. :D :D :D
On Wed, Mar 21, 2018 at 11:19 PM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> Thanks, the libopus and the libopusenc patches are now merged.
>
> Cheers,
>
> Jean-Marc
>
> On 03/20/2018 12:36 PM, Drew Allen wrote:
> > Attached is an updated patch based on Jean-Marc and Mark's comments. :)
> >
> >
2018 Mar 20
2
[PATCH] Support for Ambisonics
Attached is an updated patch based on Jean-Marc and Mark's comments. :)
Cheers,
Drew
On Tue, Mar 20, 2018 at 9:20 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> On 03/20/2018 11:51 AM, Drew Allen wrote:
> > Just to confirm, I would use opeint_* for all the
> > OpusGenericEncoder-related functions?
>
> Correct. Or you can also use oge_ if you like. Just
2018 Mar 20
2
[PATCH] Support for Ambisonics
Hi Drew,
Some comments on the libopusenc patch:
+ 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.
+ if (_oge_use_projection(h->channel_mapping))
+ {
+ len=27+(h->channels*(h->nb_streams+h->nb_coupled)*2);
+ }
+ else
+ {
+
2018 Jul 30
2
Fwd: [PATCH] Support for Ambisonics
Friendly ping for the opus-tools patch...
---------- Forwarded message ---------
From: Drew Allen <bitllama at google.com>
Date: Mon, Mar 19, 2018 at 2:53 PM
Subject: Re: [PATCH] Support for Ambisonics
To: opus at xiph.org <opus at xiph.org>
On Mon, Mar 19, 2018 at 11:52 AM Drew Allen <bitllama at google.com> wrote:
> Hello all,
>
> Sorry for the delay (got really
2018 Sep 16
1
[PATCH] Support for Ambisonics
Since the opusenc and opusinfo changes were independent I split them
up and landed the opusinfo changes (with updated mapping family
numbers).
- Mark
On Thu, Sep 6, 2018 at 4:22 AM, Mark Harris <mark.hsj at gmail.com> wrote:
> Hi Drew,
>
> Sorry for the delay.
>
> FYI the patch that you attached is not your latest version. This
> thread that you replied to is an older
2019 Dec 18
2
opusenc for ambisonics?
I compiled the latest (git master) of opus, libopusenc, opusfile and
opus-tools:
$ opusenc --version
opusenc opus-tools 0.2-8-g4976421 (using libopus 1.3.1-4-gad8fe90d)
I tried to encode a 3rd order Ambisonics wav file with the standard
Ambix (ACN-SN3D) format; opusinfo is reporting :
Streams: 16, Coupled: 0
Channel Mapping Family: 255 Map: [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10,
11, 12, 13, 14,
2019 Dec 18
2
opusenc for ambisonics?
Hi Andrew,
I suspect that the configure option should be enable-ambisonics (instead
of enable_ambisonics), but for each of opus, libopusenc, opusfile and
opus-tools git repos (on master branch), when I try "./configure
--enable-ambisonics", I get this error message:
configure: WARNING: unrecognized options: --enable-ambisonics
Thanks for your help.
Marc
Le 19-12-18 à 11 h 52, Andrew
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 08
2
[PATCH] Move demixing matrix defines
Hello Jean-Marc et all,
I've attached an updated patch which I feel addresses all 3 cases.
PTAL, Thanks!
Cheers,
Drew
On Wed, Mar 7, 2018 at 8:39 PM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> Make sure the modified libraries work in all of these three cases:
> 1) libopus 1.2.1
> 2) libopus master (or 1.3-beta) with --enable-ambisonics
> 3) libopus master (or
2019 Dec 19
1
opusenc for ambisonics?
Unfortunately, ambisonics aren't exposed in opusenc yet, thus the trouble.
They're an API-only feature, but it's a good time to discuss what such a
command-line interface would look like, notably: how to specify multiple
streams & stream order, select the mapping family, coupled channels, and
how to specify the matrix (for family 3). Likewise, there's no multistream
support at
2018 Mar 07
1
[PATCH] Support for Ambisonics and Projection API.
Excellent, thanks Tim for writing back so quickly!
Cheers,
Drew
On Tue, Mar 6, 2018 at 6:25 PM, Timothy B. Terriberry <tterribe at xiph.org>
wrote:
> Drew Allen wrote:
>
>> Please feel free to ask any questions or give any feedback you might
>> have. :)
>>
>
> A few comments from a quick glance through the opusfile patch:
>
> You unconditionally
2018 Mar 07
2
[PATCH] Move demixing matrix defines
Move demixing matrix defines to opus_define to better determine
availability of Projection API.
Allows libopusenc, opusfile and opus-tools to much more easily determine
availability of Projection API.
Cheers,
Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/opus/attachments/20180307/110f7aaf/attachment.html>
2018 Mar 19
0
[PATCH] Support for Ambisonics
On Mon, Mar 19, 2018 at 11:52 AM Drew Allen <bitllama at google.com> wrote:
> Hello all,
>
> Sorry for the delay (got really sick last week).
>
> Attached are updated patches for libopus, libopusenc, opusfile and
> opus-tools.
>
> Note that the patches for libopusenc, opusfile and opus-tools are
> dependent on the patch for libopus.
>
> Please let me know if
2017 May 18
4
Strange behavior with OGG packets?
Hello all,
I'm currently in the process of implementing a mixing matrix into the
header of OPUS files for the proposed channel mapping 3 seen here:
https://tools.ietf.org/html/draft-ietf-codec-ambisonics-03#section-3.2
My implementation simply replaces writing the stream mapping char array
with the Q15 col-wise matrix vals described in the above document.
I'm able to write/read matrices
2018 Mar 19
0
[PATCH] Support for Ambisonics
Hi Jean-Marc,
I've modified my patches for libopus and libopusenc based on your
suggestions.
Cheers,
Drew
On Mon, Mar 19, 2018 at 2:05 PM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> Hi Drew,
>
> I think the libopusenc patch is better, but there's still a few issues
> left:
> 1) The static MAX_PACKET_BUFFER_SIZE value is still problematic because
> if you
2018 Mar 26
0
[PATCH] Support for Ambisonics
Hello all!
I've attached an updated patch for opusfile, based on formatting
suggestions I got for the opus and libopusenc patches.
Cheers!
Drew
On Thu, Mar 22, 2018 at 9:19 AM Drew Allen <bitllama at google.com> wrote:
> Thanks! 2 down, 2 to go. :D :D :D
>
> On Wed, Mar 21, 2018 at 11:19 PM Jean-Marc Valin <jmvalin at jmvalin.ca>
> wrote:
>
>> Thanks, the
2018 Jul 07
0
[PATCH] Support for Ambisonics
Minor thing missed: Adding the files to the VS project file.
(Sorry for the direct reply, Drew, Gmail's interface always trips me up on
mailing lists.)
On Fri, Jul 6, 2018 at 6:06 PM Joshua Bowman <silverbacknet at gmail.com>
wrote:
> Minor thing missed: Adding the files to the VS project file.
>
> (Sorry for the direct reply, Drew, Gmail's interface always trips me up