similar to: Opus 1.3-rc released

Tim, Would you mind giving me a more specific example of the sort of document that you think this should look like? I'd like to write up something that is somewhat final. On Mon, May 2, 2016 at 9:30 PM, Michael Graczyk <mgraczyk at google.com> wrote: > On Fri, Apr 29, 2016 at 4:32 PM, Timothy B. Terriberry > <tterribe at xiph.org> wrote: > > As a general point,

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

Hello Tim and others, Thanks for your help explaining this process on IRC. I wrote out a first draft in the RFC xml format. I have attached the xml (labeled as xml.txt so it will appear inline) and the rendered txt files. Please let me know where I can make improvements. I will upload this draft to the IETF datatracker and send it out to codec@ after addressing your comments. -------------- next

I threw a rough draft of an alternative format incorporating the comments received so far in this discussion on the wiki: http://wiki.xiph.org/index.php/OggPCM#Format Oliver, This seems to me like it would support the ambisonic requirements you mention, though it doesn't (and I imagine won't) describe the mic locations. Somebody who actually uses that info could probably define extra

Hi Opus list. I subscribed because your discussion on the IETF draft ("Ambisonics in an Ogg Opus Container") was mentioned on the sursound list. I tried Opus for ambisonics more than a year ago. It does works with uncoupled channels (I had to patch the encoder). I don't know what else could be done to optimize support for ambisonics, as I'm not a codec expert. So I think that

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

Here is the modified patch. I added a flag to configure.ac which is set to 0 to disable ambisonics, and 1 to enable it. Right now the implementation simply creates a surround encoder with N uncoupled streams. Thanks, Michael Graczyk -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Michael, On 04/25/2016 05:32 AM, Michael Graczyk wrote: > Channel Mapping Family 2 > > Allowed numbers of channels: (1 + l)^2 for l = 1...15. > > Explicitly 1, 4, 9, 16, 25, 36, 49, 64, 81, 100, 121, 144, 169, 196, > 225. Ambisonics from first to fifteenth order. Would it make sense to allow an arbitrary number of channels and just "truncate" the list of

Hello, We (Google) have been experimenting with configuration and adjustments to CELT-only Opus that give good results for compressing ambisonic audio signals [1]. Based on our results so far, we would like to use Opus to encode spatial audio. We hope to make it easy/possible to use libopus with other common tools and software modules (ffmpeg/libav in particular). Based on my reading of the

All, Progress has been made on the proposed draft spec for integrating ambisonics into vorbis. We are not yet finished (should be soon), but you can see the progress here: http://docs.google.com/Doc?id=df4dtw69_3626qqq6st The issue we have hit now concerns how/who would implement the encoding and decoding in Vorbis Tools. Because ambisonics uses spherical harmonic components, an ambisonic file

On 19/04/16 12:17 PM, Timothy B. Terriberry wrote: > We should probably start keeping track of the space of invalid TOC > sequences somewhere global so that people don't define conflicting > extensions. I started such a page at https://wiki.xiph.org/OpusExtensions -r -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Hi, I have posted this three times to the flac-dev, vorbis-dev, and ogg-dev mailing lists. I wanted to see what code there was currently to support Ambisonics. So I downloaded the code from the xiph download page for libogg-1.1.3, libvorbis-1.1.2, vorbis-tools-1.1.1 and flac-1.1.4, but wasn't able to find anything. If it exists then I missed it, so could somebody please point me to it.

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,

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

>Yesterday I have finished writing the ambisonic pan filter for oggenc. May I ask what this "pan filter" is? I made some tentative suggestions for coupling Ambisonic B-format in a post "Vorbis Ambisonic coupling" on 4feb07 I gather from the last monthly meeting, that some of you, including Monty, had problems with the phase behaviour of B-format. Would anyone like a

Where can I find the Header file or whatever which specifies the "Mapping" flag. In feb - apr 2007, there was a lot of discussion about Ambisonics and Monty kindly stated that Mapping = 1 ; Denotes and Ambisonic file as opposed to = 0 which is 1 speaker/ 1 channel Has this been written explicitly into the standard? Which standard should I be looking at?

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 you have any additional followup comments or questions. Cheers, Drew -------------- next part -------------- An HTML attachment was

Hi all, My apologies for the confusion ... but I am re-naming this thread again because the proposal doesn't come from Ambisonia. As the founder of Ambisonia I have only been 'mediating' between some members of the ambisonic community ... so it would be wrong to associate the spec with Ambisonia. To clarify. This is what the spec proposes: - that Mapping = 1 means the contents are

It obviously would be nice to have such a mode available, for e.g. DVD audio compression. Apparently, the list doesn''t tell me too much about it. My questions are: 1. What is the current status of the 5.1 channel coupling in Vorbis? 2. If I''ll be interested in participation in its development, what is the recommended reading? -------------- next part -------------- An HTML

On Mon, Apr 25, 2016 at 9:32 AM, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Jean-Marc Valin wrote: >> >> Would it make sense to allow an arbitrary number of channels and just >> "truncate" the list of channels. For example, two-channel ambisonics >> would be W plus X and three-channel would be W, X and Y. The idea is >> that you would get