similar to: Need info on optimizing Opus code for a particular core/processor

Hi Ralph, Gentle reminder.. Regards, Rhishi -----Original Message----- From: Rhishikesh Agashe Sent: Friday, September 20, 2013 11:02 To: 'Ralph Giles' Subject: RE: [opus] Need info on optimizing Opus code for a particular core/processor Hi Ralph, Can you let me know how to submit my code for review? What is the procedure? Also, could you create an account for the same let me know

Hi Rhishi, PQevalaudio is very unreliable and buggy. I have compared to PEAQ and - as a result - now I am not using it anymore. With best regards, Christian Hoene Von: opus-bounces at xiph.org [mailto:opus-bounces at xiph.org] Im Auftrag von Rhishikesh Agashe Gesendet: Freitag, 4. Oktober 2013 12:35 An: opus at xiph.org Cc: Rasmi Mishra Betreff: [opus] ODG (Objective Difference

Hi, I checked the ODG (Objective Difference Grade) scores for a few reference vectors using the PQEvalAudio Tool and found that some of them show ODG scores as high as -3.5 If we look at the range as described in the link below, it looks unacceptable. http://www-mmsp.ece.mcgill.ca/documents/Software/Packages/AFsp/PQevalAudio.html Am I missing something or are these scores valid? Thanks and

Hi, While testing the Opus Decoder we came across the following: If the decoder encounters an 'Invalid Payload Length' the decoding of the stream is stopped. Also, when the decoder encounters 'Range coder state mismatch', the decoding of the stream is stopped. I believe that it should reject the erroneous payload and start decoding the next payload for it to work properly in a

Hi, We have observed that the stack usage in Opus Encoder/Decoder is enormous(50-60Kb approx). As we all know, in embedded systems, high stack usage is discouraged. How are we planning to take care of that? One idea is to allocate the required memory on heap and pass it on as an argument to the main Opus API and allocate the internal buffers used by the internal modules on the allocated buffer.

Yeah I see the definition, but unlike USE_ALLOCA and VAR_ARRAYS, it has not been used/set anywhere in the code for allocating buffers! Regards, Rhishi -----Original Message----- From: Jean-Marc Valin [mailto:jmvalin at jmvalin.ca] Sent: Friday, September 20, 2013 12:00 To: Rhishikesh Agashe Cc: opus at xiph.org Subject: Re: [opus] Regarding stack usage in Opus Actually, the code already has

In that case, can you please suggest a reliable tool? Thanks, Rhishi From: Christian Hoene [mailto:christian.hoene at symonics.com] Sent: Friday, October 04, 2013 17:30 To: Rhishikesh Agashe; opus at xiph.org Cc: Rasmi Mishra Subject: AW: [opus] ODG (Objective Difference Grade) scores for Opus Encoder using PQEvalAudio Tool Hi Rhishi, PQevalaudio is very unreliable and buggy. I have compared

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

On 2013-10-04 1:34 PM, Rhishikesh Agashe wrote: > I believe that it should reject the erroneous payload and start decoding > the next payload for it to work properly in a streaming environment. Because the decoder's predictor state converges over multiple packets of data, you cannot just skip to the next payload without introducing decoding errors. We have also tried to make the

Actually, the code already has an option for using the heap rather than the stack, see NONTHREADSAFE_PSEUDOSTACK in the code. As the name implies, it's not thread-safe though. Cheers, Jean-Marc On 20/09/13 01:29 AM, Rhishikesh Agashe wrote: > Hi, > > > > We have observed that the stack usage in Opus Encoder/Decoder is > enormous(50-60Kb approx). As we all know, in

On Fri, May 19, 2017 at 4:32 PM, Daniel Berlin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > i think you'd have to write some idiom recognizer here. The ones we have > won't do it. > > I guess my other question would be how commonly this happens. If it's common > and matters a lot, awesome. > I wouldn't do it just to fix SPEC :P > > (people who

From: http://address-sanitizer.googlecode.com/svn-history/r1624/wiki/Android.wiki > AddressSanitizer is fully supported in AOSP starting with JellyBean release. To run > applications built with ASan you'll need an -eng build of Android. > > To build any part of Android system with ASan, add > LOCAL_ADDRESS_SANITIZER:=true to the appropriate Android.mk. I don't see that

On Wed, Sep 11, 2013 at 9:00 AM, Chris Lattner <clattner at apple.com> wrote: > On Sep 10, 2013, at 4:17 PM, Alex Rosenberg <alexr at leftfield.org> wrote: > > I know it's quick to ask, but when might support for the new Apple A7 > processor appear in tree? > > > > Is the 64-bit architecture the same as ARMv8, or will we have a much > bigger set of

On 25/11/2013 18:27, Stephen Hines wrote: > futimens() is available in Android KitKat. We work extensively with > LLVM and this allowed us to remove our ugly workaround for not having > this functionality. Hi Steve, Is your work on a branch somewhere? James is putting a lot of time into this, and the LLVM community has been making best efforts to help review his patches which can be

Hmmm.... following up on your point I've noticed something strange. futimens is missing from the NDK (r9b; it's not in any headers and the libc.so files are the same all the way back to android-9), which is why I thought it's missing from Android generally. The NDK is by far the easiest way to cross-compile since it provides a standalone cross-compilation toolchain. It is however

Hi, Is there anybody out there that is experienced with run-time code generation on an android device? Is it even possible to achieve this? I compiled both llvm and clang for x64 android tablet and everything seemed fine until i tried to call exposed generated function through my native code: it gave an error that indicating I dont have rights to execute code in this memory block.(I will add the

Hello, I’m currently using the Opus encoder in an embedded device with a small ARM Cortex M4, compressing audio in real time and it works great. My implementation is similar to the application note from Texas instrument “Implementing OPUS Voice Code for TM4C129x Device”. The next step in my application is to add voice activation capability in real-time while compression is in progress. Reading

On Mon, Nov 25, 2013 at 12:36 PM, Alp Toker <alp at nuanti.com> wrote: > > On 25/11/2013 18:27, Stephen Hines wrote: > >> futimens() is available in Android KitKat. We work extensively with LLVM >> and this allowed us to remove our ugly workaround for not having this >> functionality. >> > > Hi Steve, > > Is your work on a branch somewhere? >

On Thu, 27 Jun 2019 at 17:46, Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > For our downstream usage, we've switched entirely to the new pass manager. We made the switch a couple of months ago. All of our testing is being done with the NPM, and we're about to start deleting (downstream) code which was only needed by the legacy pass manager. > > I

FWIW, the flags like -print-after, -printer-after-all don't work well with the new pass manager last time I checked. On Mon, Jul 8, 2019 at 12:20 PM Stephen Hines via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The Android platform build (AOSP) has also switched to the new pass manager recently. We do have a few bugs that we are chasing (hence opt-outs), but it is working