search for: agash

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 Grade) scores for Opus Encoder using PQEvalAudio Tool Hi, I checked the ODG (Objective Difference Grade) scores for a few reference vectors using the PQEvalAudio Tool an...

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

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.

...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... URL: http://lists.xiph.org/pipermail/opus/attachments/20130911/d4ba4856/attachment.htm

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

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 to PEAQ and - as a result - now I am not using it anymore. With best regards, Christian Ho...

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

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 embedded systems, high > stack usage is discouraged. > > How are we planning to take care of that? > > > > One idea i...