similar to: celt-dev renamed to opus

Yes, that's a start. Ultimately, though, I'm hoping to reduce the 80ms requirement, and am trying to get a handle on what state in the decoder must converge and what complications I might be up against. I'm also only considering CELT-based encodings if that simplifies things. I know that Opus can do inter-frame energy envelope prediction, but that dependency can be eliminated by

Hi everyone, I've made several posts recently about CELT being "replaced" by the Opus codec ( http://opus-codec.org/ ) and I thought it was time to give an update on what's going on. As many of you know, I've been involved at the IETF on this new Opus codec, which essentially merge (a modified version of) Skype's SILK codec with CELT. This is more than just two codecs

All, Just a heads up that the IETF codec working group has issued a last call on the draft Opus specification. This means we think the draft adequately documents the format, and that we're willing to live with whatever bugs are present in the reference implementation, if they can't be fixed without breaking decodes. In turn, this means we could really use some feedback from implementers.

Hi, folks, I have an old CELT thing that I'm updating to Opus and I'm trying to get individual pieces upgraded.  My first task is upgrading the CELT encoder to Opus. The old CELT thing treated the L and R channels as independent mono streams, encoded them somehow with CELT to form one bitstream, sent one bitstream across, and then unpacked it manually after the decoder. Can I do that

So, once all those things are in place what Andrew says WILL happen? I think plans as important as that deserves an announcement. Roadmap for the project? Future directions for the main committers? Are there patent issues? Date: Mon, 11 Jul 2011 20:45:14 -0400 > From: Gregory Maxwell <gmaxwell at gmail.com> > Subject: Re: [CELT-dev] Mailing list and project shutdown >

I too would like to know the status of the opus IP holders. From what I've seen on the CELT and opus lists, it seems that the CELT part of opus is covered by patents from Xiph and Broadcom, and the SILK part of opus is covered by the rest. All of the IP holders except Qualcomm and Huawei have released their patents to the public as far as opus is concerned, and the general consensus from

I saw the custom API, but nothing explicitly says "CELT-only" just "custom sample rate and frame size". I'll dig further now that you've pointed me in a direction. Thanks, -a On 7/6/15, 6:18 PM, Jean-Marc Valin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I believe what you want is called Opus custom (OPUS_CUSTOM in the > code).

Hi, Since our device can only handle the Celt part of Opus (due to a MIPS limitation), we have two questions: 1. Is it possible to via SDP force the remote party to send a specific mode of the 32 different possible modes or to force the remote side to use CELT only? 2. In the reference implementation of Opus it looks like the only way to force the encoder to use CELT only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I believe what you want is called Opus custom (OPUS_CUSTOM in the code). With that you can compile only the contents of the celt/ directory and use it like the old CELT. Jean-Marc On 07/06/2015 06:48 PM, Andrew Lentvorski wrote: > Is there a configuration or compile flag that lets me disable the > SILK portion of the codec and use CELT

Hi, I've been studying the Opus code and documentation for a while and have seen it mentioned several times that Opus uses pre-skip to allow the codec to converge. What convergence are they referring to? Rate control? Energy envelope prediction after seeking? Is there a discussion of this somewhere? Also, I'm also interested in the seeking behaviour of the decoder. If, say, I want to

Hi everyone, I'd just like to announce CELT 0.11.1 (sorry about failing to announce 0.11). The bit-stream is now is "soft-freeze", which means we won't change it unless we find bugs -- which we did between 0.11 and 0.11.1. The API should also be close to the final API. Compared to 0.10.x there are also small quality improvements, mostly at high bit-rate. I'd also like

Hi , We've downloaded the CELTV0.11.1 source code from celt-codec.org . But having trouble with mathops-test and tandem-test unit test that exercises internal components of CELT codec, please find attached document for each test case failure in details. Also could you please give some inputs on CELT Low complexity code and full version of the code, point me source code to CELT

Sorry about that, let me check the correct version for the intrin0.h include guard. //Marcus ________________________________ From: Ralph Giles <giles at thaumas.net> Sent: Thursday, June 11, 2020 19:31 To: Marcus Asteborg <xnorpx at outlook.com>; opus at xiph.org <opus at xiph.org> Subject: Re: [opus] Misc patches Speaking of needing more complete ci feedback, the intrin0.h

Is there a configuration or compile flag that lets me disable the SILK portion of the codec and use CELT only? I could have sworn that there is something, but I can't seem to find it in the mailing list archives. The application here is that I am attempting to update from the old CELT codec to OPUS. Unfortunately, the CELT codec was running *very* close to the CPU (MIPS32--80MHz) limit

I?m trying to build Opus (git master) for iOS, and it doesn?t build unless I disable the ARM assembly. It looks like the problem is that Apple?s assembler doesn?t support all the assembler directives that the GNU assembler does. I suspect this is a combination of the fact that Apple platforms are Mach-O rather than Elf, and just the fact that Apple?s assembler is extremely divergent from the

Hi Xiph, We are porting the CELT audio codec onto our Blackfin DSP for subsequent software distribution to our customers and would like to ensure we have covered the licensing appropriately. In reviewing the Opus codec info, it looks like there are multiple contributors (Xiph, Qualcomm, Broadcom, Skype, Microsoft, Huawei), however Xiph seems to be the main (and possibly only) IP holder in

On 23/02/15 10:30 AM, Tony wrote: > I __think__ opus-tools' opusenc has code which can be used as a > template/sample for how to create an .Ogg file with Opus content. As > expected, it makes use of libopus and libogg. Sadly that's the best option currently. As you say it's a bit complicated, although oggenc has a lot of extra support for controlling encoder options you

Hi All, Cortex-M4 is a single issue CPU whereas A8 is dual issue so this is the main reason you are seeing a slow-down, use of NEON I would say is secondary, certainly for CELT. We (ESPICO) have done optimisation work on OPUS v1.1 and have ARM implementations about twice the speed of the 'off the shelf' version. Please contact me directly if you want to discuss further. Cliff

hey great job with the celt codec. im very eager to use it. im just wondering how? there is little to no documentation on how to use the celt codec. is there anyway to encode an icecast stream using the celt codec? or is there any software with celt support built in? thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Verified that intrin0.h was available in 1910, by building it locally on VS2017 version 15.0 MSVC++ 14.1 _MSC_VER == 1910 (Visual Studio 2017 version 15.0) https://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B //Marcus ________________________________ From: Marcus Asteborg <xnorpx at outlook.com> Sent: Thursday, June 11, 2020 20:15 To: Ralph Giles <giles at thaumas.net>; opus at