similar to: Global stack on Cortex-M4

Dear all, Sorry for this simple and maybe stupid question, I'm working in the implementation of opus for ARMv7e microcontroller using a library CMSIS/DSP used to calculate the CFFT and MDCT based on the DCT-IV. my question is: In the implementation of Celt you have used a fixed length CFFT equal to 1920, I want to know if there is some issues which can appear if a change that configuration

Hi all ! If someone could give me a hint on how to proceed with the following i'd be very happy: I have a test setup on an nrf52832 (Cortex M4) in which I receive audio from a PDM microphone (64 sample frame) and pass it directly to an I2S device i.e. from ISR to ISR. With uncompressed audio this works just fine. Now I try to insert OPUS1.3 in the path but cannot make it work. The

---------- Forwarded message --------- From: Peter Svensson <petersvenss85 at gmail.com> Date: tis 19 feb. 2019 kl 20:43 Subject: Re: [opus] Custom mode To: Emily Bowman Hi Emily ! Thank you for responding. I think my problem is not (yet) with OPUS itself. Encoding at complexity 0 takes 1.6ms ( 4.342ms at complexity 10 !) and decoding takes 1.9ms. 3.5ms, out of my 4.096ms budget, is

Dear all In the paper section describes how CELT and SILK had implemented a look/up head delay of (2.5ms), (5ms) respectively , could you explain me> 1) those values are fixed. 1) how you guarantee those values independent of the architecture's performance. Thanks so much On Tue, Apr 18, 2017 at 10:05 AM, Diego Alejandro Parra Guzman < daparrag at correo.udistrital.edu.co>

Dear all. According with my question. CELT CFFT size configuration I'm not completely sure about how the kiss_fft works for sizes which are not power of two, as occur in the case of celt which calculate the mdct using a fft sizes of 480, 240, 120, and 60, I guess that internally the input data is padded with zeros in order to compute efficiently the mdct using the Cooley and Tukey

Dear all I'm working on the implementation of the MDCT for the processor ARM-Cortex-M4 I'm trying to replicate the behavior of the MDCT for several overlapped values however I realized that current implementation of the MDCT is very close to the theory only in case in which we have and overlap exactly equal to N/2 where N is the size of the input vector as is shown in the examples for

Thanks for the response. If we add the support would you accept the patch? Seems like a pretty straightforward flag since it maps directly to NumericLiteralParser::NumericLiteralParser within LiteralSupport.cpp. I understand the maintenance concern with flags that affect multiple points in code though. Still trying to get the bottom of why we're crashing with double floating point literal.

Hello, lately, I have been thinking about how to resolve the problem with that the program size increases enormously when including <iostream> when compiling with libstdc++. In this library, in <iostream> there is a static object __ioinit initialized like so: ... // For construction of filebuffers for cout, cin, cerr, clog et. al. static ios_base::Init __ioinit; ... This

Dear all, Currently I'm working in and optimization of opus for an arm-architecture *"armv7e-m"* I've involved in the general opus documentation as well in the architecture, however opus Is so big and difficult to discover specific optimization points, I want to know if you could give me a general view about of the principal points that I have to consider in order to optimize

* Published in IEEE Xplore * Google Scholar H5-Index = 22 ------------------------------ ---- Doctoral Symposium of CISTI'2023 ------------------------------ ------------ CISTI'2023 - 18th Iberian Conference on Information Systems and Technologies 20 - 23 of June 2023, University of Aveiro, Aveiro, Portugal http://cisti.eu/

Dear LLVM developers, Hello, I'm trying to find a way of cross-compiling my c code against Baremetal Cortex-M device (so target triple will be arm-none-eabi) only using LLVM/Clang, and not using anything from GNU (ld or libc). I'm doing this to know which one of LLVM/clang and GCC produces smaller flash image size because saving flash is a big deal in our projects. 1) When I just follow

Hi Diego, Really, the only way to know what to optimize is to run a profiler. Optimizing without profiling is a waste of time and is often harmful. Cheers, Jean-Marc On 18/04/17 04:12 AM, Diego Alejandro Parra Guzman wrote: > Dear all, > > Currently I'm working in and optimization of opus for an > arm-architecture *"armv7e-m"* I've involved in the general >

Dear all: I want to formulate couple of questions about SILK codec: 1. I've seen the documentation to the SILK codec that is part of the OPUS exactly the paper with title "The opus codec voice coding with opus, and the "RFC 6716 specification of opus" . Well, I detected that in both is defined a High-Pass filter as part of SILK; however in the paper you put the following

Hi All, Clang lacks support for the -fsingle-precision-constant flag. Are there specific reasons for this or is it just waiting to be implemented? This flag is especially important in the embedded world. From http://processors.wiki.ti.com/index.php/Floating_Point_Optimization#float_vs._double_vs._long_double : *Once all of your data is defined as float, there are still cases where you may

CRAN (and crantastic) updates this week New packages ------------ * disclapmix (0.1) Maintainer: Mikkel Meyer Andersen Author(s): Mikkel Meyer Andersen and Poul Svante Eriksen License: GPL-2 http://crantastic.org/packages/disclapmix disclapmix makes inference in a mixture of Discrete Laplace distributions using the EM algorithm. * EstSimPDMP (1.1) Maintainer: Unknown Author(s):