similar to: High noise after encoding/decoding procedure

Thanks a lot for your tips. What I have to done to debug: got the raw wav-file, compressed/decompressed it on my PC and saved OPUS packets as an array. Moved this array to the embedded platform and made sure that the frames decoded from the OPUS packets are the same. However, the high noise level was the same, but it wasn`t caused by OPUS. The problem was with my sound bus between an embedded

Hello everyone. I have a problem with a high level of noise after opus encoding/decoding procedure. If I stream a raw data from the microphone and send it back to the speakers I hear the clear sound (with a small delay). If I encode each frame, decode it and send it back to the speakers I hear a very noisy signal - it is so large, so it is almost impossible to distinguish words in my speech...

On 2016-07-12 9:34 AM, Aleksandr Mikoff wrote: > If I encode each frame, decode it and send it back to the speakers I > hear a very noisy signal - it is so large, so it is almost impossible to > distinguish words in my speech... This effect can be caused by some data type issues: - If you are using opus_encode() and opus_decode(), make sure to use 16-bit signed integer samples in the

Hello Benjamin, The original WAV file I have is linear 8-bit PCM. I want to ensure that original linear formats are kept as is. Later I will add support for ulaw. Regards Amit On Fri, Jan 8, 2016 at 5:34 PM, Benjamin Schwartz < benjamin.m.schwartz at gmail.com> wrote: > Do you really need linear 8-bit PCM or do you want ulaw? Linear 8-bit is > ... pretty rare. > > On Thu,

Hello All, Turned out to be a coding error. The modified buffer was not being allocated to write back to the File System. After correction the mono 8 and 16 bit for 8K-48K works well now. Regards Amit On Mon, Jan 11, 2016 at 11:05 AM, Amit Ashara <ashara.amit at gmail.com> wrote: > Hello Mark, > > The resulting 8 bit file has a lot of squelching noise compared to the 16 > bit

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

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

Hello All I have successfully run the Opus Decoder for 16-bit WAV files. However when doing the same on 8-bit, the decoder produces noise, but on 16 bit data the output is working. Both the 8 and 16 bit files are from the same source and hence except for some loss of quality on 8 bit, they are identical in total play back duration. For both 8 and 16 bit data I have used the following parameters

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

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

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

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) + 1 segment entry (which is the size of the segment itself) + 64 bytes will amount to (4+1)/(4+1+64) = ~7.2%. This when compared with the original Oggs container itself for the same data payload size (26+1)/(26+1+64) = ~29.6%. Even if

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 Jean-Marc, I suspected the answer to be No. 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. At the same time the file processing complexity is way too less considering that CRC's do not not need to be considered (programmer pods ensure that)

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

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

Hello Ulrich, Putting some extra space is the not the reason for this request. It is the overhead of the frame v/s payload size. Basically larger the payload less % the overhead is (and that makes sense). However the complexity of implementing a read file structure where the file pointer has to go back-forth for reading the payload when multiple segments have to be read, CRC32 (something which

On 07/01/16 10:04 AM, Amit Ashara wrote: > opus_decoder_ctl(sOpusDec, OPUS_SET_LSB_DEPTH(ui32BitsPerSample)); OPUS_SET_LSB_DEPTH only affects the encoder. If you check the return value here you should get OPUS_UNIMPLEMENTED. > output_samples = opus_decode(sOpusDec, (const unsigned char > *)&pcRdBuf[0], len, opi16_out, (ui32SizeOfWrBuf/ui8ScaleFactor), 0); I suspect the issue is

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