similar to: opus on TI55x

Hi Amit, issues I'm facing now are int overflow and memory management. I'm working on it. I'm working on the tms320c5515 evm board. Best regards, Giovanni. On 5 January 2016 at 18:40, Amit Ashara <ashara.amit at gmail.com> wrote: > Hello Giovanni, > > I am running both Opus Encoder and Decoder on a TI Cortex M4 core without > any issues. What is the specific issue

Hi, I'm trying to make OPUS run on TI55, at the moment on the evm 5515 board. I'm compiling with FIXED_POINT, DISABLE_FLOAT_API, TI_C5X_ASM, CONFIG_TI_C55X. I'm actually interested only in the CELT part, so I'm also using OPUS_APPLICATION_RESTRICTED_LOWDELAY. It compiles but I'm still having few problems. I was wondering if anyone succeeded in making it run on this device, or

Hello All When sending the Opus Packet in RTP Payload, the compressed frame is the output of the encoder? Also the config value as given in the RFC6716, 16...19 | CELT-only | NB | 2.5, 5, 10, 20 ms 16 corresponds to 2.5 ms 17 corresponds to 5 ms 18 corresponds to 10 ms 19 corresponds to 20 ms Is this correct representation of the data? Also in the RFC3551 the payload

Hello Jean-Marc, As an example, I am using the output of opus encoder to store the file as the following format and read back the same during decode process, without having much overhead. (Thought it would be useful to put a picture rather than running text) [image: Inline image 2] Regards Amit On Thu, May 12, 2016 at 10:47 AM, Amit Ashara <ashara.amit at gmail.com> wrote: > Hello

On 05/12/2016 10:35 AM, Amit Ashara wrote: > For HMI panels, except for the capture pattern and a single page segment > entry, other fields are not important, and which results in almost 7% > overhead for a 20ms raw frame encoded with Opus. I'm not sure how you get a 7% overhead. In most uses I've seen, the overhead is more around 1%. > At the same time the > file

The overhead of Ogg (in file size) is pretty small and it's efficient enough for most applications (and uses far less CPU than the codec anyway). If anything, you might want to look at optimizing the existing Ogg implementation (e.g. like Tremor did in the context of Vorbis). Of course, you're always free to design a new container, but I doubt it's worth it and it's a lot of work

Hello Ralph, > Likewise opus_encode() takes 16 bit samples, so you need to extend each > sample from an 8 bit source before encoding. Two questions 1. In opusenc.c which API does the extending the 8-bit to 16-bit? 2. If that is the case then how will 24 bit PCM sample work? Regards Amit On Thu, Jan 7, 2016 at 12:21 PM, Ralph Giles <giles at thaumas.net> wrote: > On 07/01/16

>>> Amit Ashara <ashara.amit at gmail.com> schrieb am 11.05.2016 um 19:32 in Nachricht <CAEyg9sjvTWMBMMCJ8HQcYmbv1BtNt54CgpqWaGNm02MWrKcxaQ at mail.gmail.com>: > Hello Jean-Marc, > > So for the moment we can assume that this method is also OK to use? > > On Embedded Systems, both SRAM and Flash can be a restricting factor > besides the compute time. To

>>> Amit Ashara <ashara.amit at gmail.com> schrieb am 12.05.2016 um 17:47 in Nachricht <CAEyg9sgjbsxQY-=VnhQrKiGeTcFSRr1wxOPUhNyCQF8Piuahow at mail.gmail.com>: > Hello Jean-Marc, > > Assuming that a 48KHz, 20ms 8-bit linear PCM data which is 960 bytes is > compressed to 64 bytes (for assumption). The with the Oggs header (4 byte) Actually what I don't

Hello Mark, The resulting 8 bit file has a lot of squelching noise compared to the 16 bit output from OPUS decoder. During encode I am using popi16fmtBuffer[ui32Loop] = (opus_int16)pcRdBuf[ui32Loop]; And during decode since the data is in the lower 8 bit I use pc8bitSamples[ui32Loop] = ((unsigned short)pcop16OutBuf[ui32Loop] ^ 0x80); Regards Amit On Sat, Jan 9, 2016 at 2:39 PM, Amit Ashara

On 05/11/2016 12:35 PM, Amit Ashara wrote: > I ran the opusenc.exe on a wave file and checked the OpusTag section. My > concern is on Total Segment Size being >> than the actual data being > put. Is this just an example of implementation or does a size of 764 > BYTES kept as a place holder for putting more data? Yes, opusenc does reserve some space in the header so that tags can

Hello Daniele It would be worthwhile to attach an external serial flash or USB thumb drive, if the intent is store data. This allows for far more flexibility in storage Regards Amit On Fri, Aug 26, 2016 at 11:02 AM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > On 26/08/16 11:40 AM, Daniele Barzotti wrote: > > You're right! I forgot to say that I need only the encoder

Amit Ashara wrote: > 1. Since the stream I am working with is a mono channel, what should be > the advised page_segments to use. I am using an embedded system so > keeping the flash and SRAM usage are vital for the development. The number of channels has no impact on this at all. > 2. In the OpusTag the is the libopus a mandatory field? Yes.

Hello Tim, Jean-Marc Thanks for the clarification. Let me study the sample OPUS file and see if my understanding is now clarified. Regards Amit On Mon, May 9, 2016 at 2:02 PM, Timothy B. Terriberry <tterribe at xiph.org> wrote: > Amit Ashara wrote: > >> I am referring to the following file >> >> >>

Hello everyone. I would like to use the opus codec in the following scenario: the PCM audio signal, coming from bluetooth module is captured by STM32F446 MCU and then decoded by opus codec. However, I don't know where to start to build the opuslib for ARM Cortex-M4. Could someone provide any hints or give any brief guide on this? WBR, Aleksandr -------------- next part -------------- An

Hi Amit, I'm not sure what you're trying to ask, but the reserved space in the header is an optional thing. Encoders are free to do it, but are not required to do so. Jean-Marc On 05/11/2016 01:32 PM, Amit Ashara wrote: > Hello Jean-Marc, > > So for the moment we can assume that this method is also OK to use? > > On Embedded Systems, both SRAM and Flash can be a

On 10/05/16 02:37 PM, Amit Ashara wrote: > Is there a format document on the OpusTag structure? Search always shows > up Vorbis but not Opus. The basic format is shared with Vorbis, but the 'magic signature' is different ('OpusTags' instead of '0x05vorbis') and vorbis puts a 0x01 value in an extra byte after the last tag. The OpusTag packet layout is described in

Hello Tim I am referring to the following file https://en.wikipedia.org/wiki/File:Sample_of_%22Another_Day_in_Paradise%22.ogg I opened the file in a HEX editor. I do not see the string OpusHead in the packet. It starts with Oggs. Also checking the occurrence of Oggs, I see that the first packet has BOS, the next all (except last) have 00 (which is not defined in the RFC as continuation) and

Hi all, I would like a makefile or makefile option which excludes the encode source code from the Opus build. The reason I want this is that I am developing an embedded application which requires decoding Opus but not encoding. A decode-only build should be much smaller than a full Opus build, which is an important consideration for resource-limited platforms. As someone pointed out on

Hi, I am new to Opus, I want to decode a RTP packet which has opus payload. Following can describe my intention: I have RTP-packet----------> rtp_header+ opus_payload(20ms/960/48000/1channel) I have now opus_palyload after removing the rtp_header, what I want, a simple code using the opus_decoder which can give me the 20 msec opus paylaod consists of 960 samples. Can anybody put a simple