similar to: Version 1.1.1-beta is out

Hi everyone, After much waiting, Opus 1.1.1 is finally here. The main changes are: - x86 SSE, SSE2 and SSE4.1 optimizations contributed by Cisco, - MIPS optimizations contributed by Imagination Technologies, - ARM Neon optimizations contributed by Linaro and ARM, - many architecture-independent optimizations, - memory footprint reductions, and - several minor bug fixes. The quality of the

I just tried decoding with v1.1: ./opus_demo -d 48000 2 opus_encoded_crash.opus out.pcm and I see no issue (including with valgrind). Does the same command-line create problems for you? What compile flags did you use? fixed-point or float, any assembly, ...? Could be assembly here, or even a compiler bug wouldn't be unheard of. Cheers, Jean-Marc On 20/04/15 07:27 AM, Suresh Thiriveedi

Still can't reproduce. What OS and compiler version? Jean-Marc On 21/04/15 02:48 AM, Suresh Thiriveedi wrote: > Hi, > > There is no change in the compiler flags. I'm using as it is from the > original code. No change in the Makefile and I believe it is using the > floating point only by default. > > We are using 8k samples and mono so the commands is as follows.

This is observed on a live call between webRTC browser client and another legacy client. Our server is there in between and transcoding from opus to another codec and this is observed while decoding the opus. Anyway, I'll try to capture/dump the packets in the server before feeding to the opus_decode and share with you. But this will not have the first 8 bytes (length+enc range) to directly

Hi Looks like 1.1 version is sensitive to the system architecture/compiler/kernel version. Below is my observation in various linux system I have. As you mentioned, you are not observed the crash in your system, can you please share your system details. And also please comment on the below table/observations. *Machine IP* *optimization flags* *RHEL version* *kernel version* *gcc version*

Hi, We are able to reproduce the issue with the 1.1 opus_demo (sample file). We captured the frames in our server just before the opus_decode and fed the file to opus_demo (1.1) and it is crashing. Same file is tested with 1.1.1 and it is fine. So this is in line with our server testing observation and I think here we can conclude that the 1.1 library is crashing while handling a specific mode

On 26/11/15 16:40, Jean-Marc Valin wrote: > Please report any issue you find in this release. Using the new SS4.1 code I see a 30% performance increase in my 7 years old AMD laptop. I compile with this: ./configure --disable-static --enable-intrinsics \ --enable-float-approx "make test" runs fine. Great. When I try to do the same on a server running Ubuntu

Hi Jean-Marc, Could you please update if you got a chance to look into. As I mentioned, I don't see the same issue in 1.1.1, but I don't see any difference in 1.1.1 other than optimization based on the architecture. This optimization could have fixed some stack overflow issue in some specific cases? Thanks Suresh On 13 April 2015 at 12:39, Suresh Thiriveedi <sthiriveedi at

To be decodable by opus_demo, you'll have to add the 8-byte "header". Just put in the length of the packet followed by "0" for the encoder range (0 means "not present"). That being said, from previous experience, the most likely cause of the crash is a bug in your software causing a corruption in Opus. So it's safe to assume that if you can't reproduce

Did the patch 5 split / AVX fix work get merged at all, I didn't see any more mails about it? Thanks! On Tue, 14 Jan 2020 at 21:34, Marcus Asteborg <xnorpx at outlook.com> wrote: > Awesome thanks! Good comments. > > Please apply patch 1-4 and I prepare another iteration on patch 5 for you > too look at. > > //Marcus > ------------------------------ > *From:*

Please provide the input file that produces this with opus_demo. On 16/04/15 03:24 AM, Suresh Thiriveedi wrote: > Hi Jean-Marc, > > Could you please update if you got a chance to look into. As I > mentioned, I don't see the same issue in 1.1.1, but I don't see any > difference in 1.1.1 other than optimization based on the architecture. > This optimization could have

Hi, There is no change in the compiler flags. I'm using as it is from the original code. No change in the Makefile and I believe it is using the floating point only by default. We are using 8k samples and mono so the commands is as follows. [root at MEDIA opus-1.1]# ./opus_demo -d 8000 1 opus_encoded_crash.opus opus_encoded_crash.pcm *And segmentation is as below..*. ............ Calling

Hi Jean-Marc, Thanks for your response. Please find the details as below. *Backtrace we got for this crash:* #0 0x0000000000800c54 in opus_decode_frame (st=0x38906b8f99d09c5, data=0xf0aa10b4ef1008ae <Address 0xf0aa10b4ef1008ae out of bounds>, len=-188613428, pcm=0x6e80016085efd57, frame_size=44037315, decode_fec=58716895) at src/opus_decoder.c:384 #1 0x00000000008009c0 in

Red Hat Enterprise Linux Server release 6.4 (Santiago) gcc version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) We see the issue in all our Intel based Linux servers. Thanks Suresh On 21 April 2015 at 12:41, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > Still can't reproduce. What OS and compiler version? > > Jean-Marc > > On 21/04/15 02:48 AM, Suresh Thiriveedi

Hi Dean, It should work for 24kec, 34kc and 74kc cores. Thanks and Regards, Rhishi -----Original Message----- From: opus-bounces at xiph.org [mailto:opus-bounces at xiph.org] On Behalf Of Dean Blackketter Sent: Monday, June 23, 2014 02:37 To: Jean-Marc Valin Cc: opus at xiph.org Subject: Re: [opus] MIPS optimizations Great, will do and report back. On Jun 22, 2014, at 9:13 AM, Jean-Marc

Hi, I'm curious to know when would be the 1.1.1 stable version available. In 1.1, we are facing crash when opus library is trying to decode the CELT-only, full band and 20 ms. So we tried with 1.1.1 beta and it looks to be fine. Is there any open issue regarding this in 1.1 version? Thanks Suresh -------------- next part -------------- An HTML attachment was scrubbed... URL:

I suggest you try it. I do know that it requires the dsp extensions, but it may work on a 24k. Just change the -march=74kc and see if it works. Jean-Marc On 22/06/14 11:26 AM, Dean Blackketter wrote: > Thanks for this. > > There?s not much documentation there. > > It appears that these optimizations are for MIPS 74K only and don?t apply to 24K-based builds, correct? > >

Hi all, With some downtime it's time for some CMake fixes. Most critically is the SSE fixes to avoid crashes that is described in 154 and 132 in github. Patch 5 should address this and also adding APPROX-FLOAT option. Hopefully this can give some gains for those of us running on Windows servers.j I went through the pull request and picked out a few that will ease up integration for

Hi All, Regarding cycle measurements for ARM/NEON, ARM no longer provide cycle accurate simulators. The method we use is to to make measurements on hardware via the PMU unit on the core itself. Note that if your running under Linux you may be 'allowed' to access the PMU directly but can access via it system calls. Typically you will need to make a series of measurements and average them.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Jesus, Thanks for the report. As far as I can tell, what's happening is that when intrinsics are enabled, we compile all tests with -msse4.1, even when it's only run-time detected. In most cases, that doesn't cause any issue, but sometimes the compiler will take the C code and generate an SSEx instruction on its own. I think this is