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

Hi, I am new to the Opus community. I intend to optimize Opus encoder/decoder for MIPS and commit the changes to the Opus repository for it be included in Android. Can somebody point me how to go about it? A pointer to a previous mail thread with a similar discussion might help. Thanks and Regards, Rhishikesh Agashe -------------- next part -------------- An HTML attachment was scrubbed...

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 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

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

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

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, 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.

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

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

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

1. If you're building in CCS, I hope you have created new projects and imported the source and header files. 2. Then right click on project you want to build -> Build Properties -> Under C600 Compiler, click on Basic Options -> Change Optimization level On Fri, Sep 6, 2013 at 12:30 AM, <opus-request at xiph.org> wrote: > Send opus mailing list submissions to >

Hi Ralph, I have pushed patches to enable radix 3 and radix 5. Github: https://github.com/projectNe10/Ne10/releases/tag/v1.2.0 Best Regards, Phil Wang > Date: Thu, 11 Dec 2014 10:46:50 -0800 > From: Ralph Giles <giles at thaumas.net> > Subject: Re: [opus] [ARM][FFT][NEON] Integrate Ne10 into Opus? > To: opus at xiph.org > Message-ID: <5489E69A.5000305 at thaumas.net>

hi,All, I want to know whether Opus has AEC features like Speex? Thanks 2012/10/17 <opus-request at xiph.org> > Send opus mailing list submissions to > opus at xiph.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xiph.org/mailman/listinfo/opus > or, via email, send a message with subject or body 'help' to

<div id="contentDescription" style="line-height:1.5;text-align:justify;text-justify:inter-ideograph"> <div>Thanks to your reply.</div><div><br></div><div>So part of the wiki is out of date? Beside Opus-tools, I also concern about the spec, optimization and future work in wiki. Could you tell me about if they are out

Hi Ralph, I am using Http Progressive download technique to download the opus audio in chunks. So I am not sure if the Opusfile seek API will work in this case. Please correct me if I am wrong. Is there anyway to get or calculate the byte offset corresponding to the PCM time position? Then I can ask the server to serve the file from that byte onwards. Regards, Deepak. On Tue, Nov 8, 2016 at

陈伟旭 wrote: > So part of the wiki is out of date? Beside Opus-tools, I also concern > about the spec, optimization and future work in wiki. Could you tell me > about if they are out of date? > On 08/28/2019 00:08, Ralph Giles <mailto:giles at thaumas.net> wrote: For the Spec section: There is a Matroska mapping, and it has been implemented in Firefox and FFmpeg (and Chrome

Dear Christian van Bijleveld, You can use any of the below DSPs of Texas Instruments 1. TMS320C674x - This supports floating point implementation of opus 2. TMS320C66x - This supports both floating and fixed point implementations 3. TMS320C64x - This supports only fixed point implementation Regards, Mahantesh On Mon, May 13, 2013 at 10:12 PM, <opus-request at xiph.org> wrote: >

This is only available for apps that target API level 19 and up. On 18 and lower, the futimens() function won't be available via libc.so. You will need to target API 19 (KitKat) in order to actually use it. If I do an "nm -D prebuilts/ndk/9/platforms/android-19/arch-arm/usr/lib/libc.so", I can see futimens() is present. On the others, it is definitely missing. Steve On Mon, Nov

The format you're describing here actually has *more* overhead than Ogg, not less. It's also unseakable, not robust errors, and without support for metadata. I'm not sure why you would want that. It's not like you're forced to include much data in the Ogg metadata (which seems to be the source of all the overhead you're seeing). Jean-Marc On 05/12/2016 11:51 AM, Amit

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