similar to: One question about 0.8.1 version usage

My program always crashes using 0.8.1... But 0.7.0 works well... I built 0.8.1 wrong? Steven -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20100818/d4f57dea/attachment-0002.htm

Hi , I visited celt website. I saw the comparison between AAC-LD with celt. But how about the HE-AAC? If the scenario is that we limit the bandwidth to 50kbps, will music encoded by HE-AAC v2 be better than CELT? What's HE-AAC v2's delay? Thank you very much. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Timothy, Because I don't see any memory overflow, remains only any memory corruption and for sure it happens inside the library. Has anyone managed to run this library on embedded systems such as STM32, NXP IMXRT1060? By using opus_demo code (decoding part)? Pls advise, Kind Regards, Leonid Shigris RT Engineer Email: LeonidS at riscogroup.com -----Original Message----- From: opus

Many people have run opus on small embedded devices. It may be the case that your VLA support isn't providing enough stack. You may want to try using the pseudostack mode which will instead put that memory on the heap and give you better control over making sure you have enough available. On Tue, Jun 4, 2024 at 10:28?AM Leonid Shigris <LeonidS at riscogroup.com> wrote: > > Hi

Hello, I am interested in implementing opus decoder in my project. My OS: FreeRTOS MCU: NXP IMXRT1060 IAR 8.32 I integrated the library opus and successfully compiled (at least didn?t receive compile warning or errors). What a right way to take opus file and decode to wav file? I see, there a few examples, but I don?t know what example will be suitable for me? Pls advise, Kind Regards,

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 am getting hard to find, what is the encoding parameters that is used for coding in the Bitconformance vectors testvectorx.dec. pls send or ref some link about this. i found decoding parameters -d 48000 2 testvectorx.bit testx.out similarly i need to know for encoder. thanks in advance. Regards, sugumar -------------- next part -------------- An HTML

Hi, To be able to validate CMake changes in the Github mirror I propose we add github actions to the repo and start building with CMake. https://github.com/features/actions [https://github.githubassets.com/images/modules/site/social-cards/actions.png]<https://github.com/features/actions> Features • GitHub Actions · GitHub<https://github.com/features/actions> GitHub is where people

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.

#define CELT_GET_BITSTREAM_VERSION 2000 Is there a reason this stayed the same or did someone just forget to change it? -torg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20100716/d45c084e/attachment-0002.htm

Hi, Opus team I'm Huang Hao and trouble you again. When I used the OpusRepacketizer as Jean-Marc mentioned, I got a result (maybe problem I'm not sure) that perplexes me, please give me some comments. The result be described as below: First(all init which are needed I have done), I used opus_encode() to get the encoded data successfully. The encoder control parameters are set: VBR=0,

Hello, I integrated the latest library 1.5.2 into my system. To compile the library have to allow VLA in IAR. Running FreeRTOS on MCU NXP IMXRT1060. I encoding the file using opus_demo.exe. And for decoding I took the part of opus_demo.c and implemented on my MCU. I experience a system crash from time to time by running the decoding. I don?t see any memory overflow not in heap, not thread

Dear all, I am new to OPUS and I am trying to do an evaluation of OPUS. I have tried the examples at the following link: http://www.opus-codec.org/examples/ [image: Inline images 1] Regarding these 3 audio samples, I have not dicovered the description over frame size and complexity level. Can you please tell me what is the frame size and complexity used in these audio sample when you perform

If you encode with int iByteSizeEncoded = opus_encode(m_enc, m_ShortsInput, (1920/sizeof(short)), m_EncodedBytes, (960*6)); ... the byte size is 120. I thought that an odd value like 359 has to be a fault on my side. I thought it would be a multiple of something. So 359 is really correct??? Thank you for clearing this up. Am 06.10.2013 16:50, schrieb Jean-Marc Valin: > Why

Hi everyone, Just to let you know that CELT 0.8.1 is out. It's mostly a bugfix release. The bit-stream is compatible with 0.8.0 with the only exception that CELT no longer supports weird frame sizes that have prime factors above 5. This shouldn't really affect anyone. For those of you unaware of the current effort to standardize an audio codec at the IETF, we have recently created a

Hello everyone, I just wanted to see if anyone else is using PLC on the C55x and having success? I am seeing some issues and was curious if I was doing anything wrong/stupid or maybe I have found a bug? I am using: - the CELT library from OPUS 0.9.5 ( I checked the git repo and no check ins have comments about PLC, I assume it hasn't been updated) - FRAME_SIZE: 240 - PACKET_SIZE:

Why should it return 360 in the first place??? On 10/06/2013 06:33 AM, Hermann Weber wrote: > Why does opus_encode return 359, and not 360, please? > > This is my code: > > int iShortsRead = fread(m_RawBytes, sizeof(short), > (5760/sizeof(short)), fin); > for(int i=0;i<iShortsRead;i++) > { > opus_int32 s; >

Hello, I want to use the CELT codec in an embedded solution. For the embedded solution, the processor speed is of great importance. In the documentation (the presentation of Dr. Jean-Marc Valin, Gregory Maxwell and Dr. Timothy B. Terriberry) the CELT LC (low complexity) mode is mentionned. The LC mode should use half the memory recources and half the MIPS. My question is how to tell the CELT

Hi Bert, Ok, to your initial point, the key nuance is that if 'x' is a vector, you can leave the 'degree' argument unnamed, however, if 'x' is a matrix, you cannot. That aspect of the behavior does not seem to change if poly() is called stand alone or, as suggested in ?poly, within a formula to be parsed. Working on tracing through the code using debug(), the error is