similar to: Performance comparison between Opus Custom and Standard modes

Hello everyone, I have been having trouble utilizing the PLC function (I think). In older versions (0.7.1) a pointer to NULL did the trick, but with code from the tip of the GIT repository, this method causes the codec to crash on the C55x fixed point platform. I have not determined where the crash occurs. I have also attempted to pass in an array of zero's and this creates an echoey, reverby

Hi, I just released Opus 1.3-beta. This is a beta release towards the upcoming Opus 1.3. Changes include: - The spec fixes in RFC 8251 are now enabled by default - Improvements to the VAD and speech/music classification using an RNN - Improvements to stereo speech coding at low bitrate - Added support for ambisonics projection using mapping 3 (disabled by default) - Fixes to the CELT PLC

Dear Opus Experts, I am interested to know if there is variation in the processing time for each packet. In this application I am mostly interest in the CELT mode, and I need to understand whether the CPU complexity is different depending on which signal I feed the system. Thanks in advance for your attention, Best regards, Dr. Rafael Paiva -------------- next part -------------- An HTML

Hi all, for numerous reasons I am now trying to build Opus with Windows / Visual C++ Express. So far I have been using Linux/OSX/MinGW only. The normal Opus build works out fine but I wonder how I can enable the Opus-custom-mode with Visual C++ Express. Can anyone help ? Thanks in advance, best Alex -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi I am not sure if this issue has been resolved, but on the latest opus 1.1.4, * I downloaded the tarball, * ran ./configure followed by * make and then * make check Can you please help? Thank you make[3]: Entering directory `/prj/avspw/karthikr/Development/BFamily/Broadcast/SDM845/Opus/opus-1.1.4/doc' doxygen Warning: ignoring unsupported tag

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

Hi All. I have an application where the sample rate of the sender and receiver can vary by a small margin and the latency needs to be maintained within bounds and can't drift significantly and the system has to be able to cope with clock mismatches up to 0.5%. For example, the sender may have a clock rate of 48.1kHz and the receiver may have a clock rate of 47.9kHz. Unfortunately the clock

Using -i should prevent failing if the files don't exist. --- appveyor.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appveyor.yml b/appveyor.yml index c85b0b1..ad9c6c0 100644 --- a/appveyor.yml +++ b/appveyor.yml @@ -17,7 +17,7 @@ build: verbosity: minimal after_build: -- cmd: 7z a opus.zip win32\VS2015\%PLATFORM%\%CONFIGURATION%\opus.lib include\*.h +- cmd: 7z

Xiph.Org is pleased to announce that we've released Opus 1.2. The 1.2 release includes: . Speech quality improvements especially in the 12-20 kbit/s range . Improved VBR encoding for hybrid mode . More aggressive use of wider speech bandwidth, including fullband speech starting at 14 kbit/s . Music quality improvements in the 32-48 kb/s range . Generic and SSE CELT optimizations .

I have a question about PLC used by OPUS. We are using OPUS for streaming music in some application. Due to some network problems, we are running into problems related to clock drifts. This causes jitter buffer underflows at the receiver and hence we need to rebuffer the jitter buffer periodically. We are looking at the root cause of this problem (drift), but that's besides the point.

Looking at the Opus comparison page[1], I can't figure out whether the Opus/AAC/Vorbis/MP3 lines are meant to imply a mono or stereo encoding. Could someone please update the caption to clarify this? The single dot for G.711 is clearly mono, but for stereo music, are the codecs at the top meant to converge near 128 kbps, or 256 kbps? [1] http://opus-codec.org/comparison/

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

Hi I'm having a problem compiling opus-tools-0.1.7. Version opus-tools-0.1.6 seems to compile OK. I've tried with opus-1.0.3 and opus-1.1-beta. The errors are like this:- "undefined reference to `sqrtf'" etc. This OS is Peppermint Three, similar to Ubuntu 12.04. It uses:- gcc --version gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3 Google says it's maybe something to do

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

hi, I am porting opus encoder to a low end device with 32K ram, 256K flash and 32MHz arm M3 mcu. But opus seems consume too much. To make it work , what I can think of 1, Only fixed point supported 2, Only mono voice application supported 3, Set complexity to zero 4, Support only one sample rate, like 16KHz 5, Silk mode only or Celt mode only My question is , before

Hi All, First time poster to this group, please ignore my ignorance? I?m trying to use Opus 1.1 on a 400MHz MIPS 24k CPU (AR9331, specifically, like in the Arduino Yun). I?ve successfully built (I think) opus-1.1 and opus-tools-1.8 and they run, but are dog slow. opus-1.1 does have the ?enable-fixed-point option set, as this chip only has soft-float. My short test file (less than one

FYI, the README file section on building for Windows says to see the README.md files in the cmake or meson subdirectories, but there are no README files in either of those subdirectories. -----Original Message----- From: opus <opus-bounces at xiph.org> On Behalf Of Jean-Marc Valin Sent: Monday, March 4, 2024 12:52 PM To: opus at xiph.org Subject: Re: [opus] Opus 1.5 is out -- now with ML

I'm considering implementing Opus as the codec for an embedded ARM-based battery powered audio system. In the interest of battery life and board footprint I'd like to specify the smallest CPU that can do the job. In some quick testing on Cortex-A8 (a very different core, but at least ISA compatible and hopefully fairly similar to M4 for things like cycle counts and code size) I saw

And it turns out there was a missing meson file in the original release so here's 1.5.1 with the file added: https://downloads.xiph.org/releases/opus/opus-1.5.1.tar.gz Cheers, Jean-Marc On 2024-03-04 11:26, Jean-Marc Valin wrote: > Hi everyone, > > I'm happy to announce that Opus 1.5 has just been released. Opus 1.5 is > the first release to make extended use of ML in

Hi everyone, I'm happy to announce that Opus 1.5 has just been released. Opus 1.5 is the first release to make extended use of ML in the encoder and decoder. You can read all the details in our demo page at: https://opus-codec.org/demo/opus-1.5/ Major changes since 1.4 include: - Significant improvement to packet loss robustness using Deep Redundancy (DRED) - Improved packet loss