similar to: Unexpected opus_encode results when doubelling frame size

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

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; s=m_RawBytes[2*i+1]<<8|m_RawBytes[2*i]; s=((s&0xFFFF)^0x8000)-0x8000; m_ShortsInput[i]=s; }

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

Hi all, i try to set up something like a mixer and soundbridge. There are several sender clients which sends opus encoded audiostreams. One basestation is decoding the streams and mixing them all together. After that, the resulting stream is encoded with opus again and send to one or two receiving clients. Opus is set up to encode 10ms packets in stereo with 16bit per sample and 44kHz. So,

Hi All, We are using libopus 1.0.2 lib version currently and observing one crash issue in opus_encode() function some times. ------------------------------------------- (gdb) bt #0 0x00007fcdf7c90ea2 in opus_encode () from /usr/lib64/libopus.so.0 -------------------------------------------- Anybody faced this problem earlier and have any idea whether its solved in the latest version libopus

Hi, We would like to use the OPUS codec @ 16 kHz sampling rate and max 32 kbps. What about implementing an OPUS coder and decoder in an FPGA? Has this been done? Would either coder or decoder more suitable for FPGA implementation? Best regards Fredrik Bonde -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all, i am trying convert pcm (16bit pcm) stereo file to mono pcm file using opus_encode and opus_decode, i am able do this but i have doubt about TOC byte after opus encode. below is how encoder and decoder structures are used to do encode and decode file opus_encoder_create(8000, 2, OPUS_APPLICATION_AUDIO, &err); opus_decoder_create(8000, 1, &err); after opus encode bits looks like

Maybe i found the source of the problem. The basestation is running several threads. One per sending client and one per receiving client. In each thread there is either an opus_encode() or an opus_decode() but there is in total only one OpusEncoder and one OpusDecoder defined which where used in every thread. Now every thread has it own OpusEncoder or OpusDecoder. After 20minutes of audiostreaming

On 10/26/2013 01:11 PM, Wang, Chris wrote: > A simpler question. How does opus_encode() generate packets of 20ms > (SILK-only or Hybrid)? Concatenating two 10ms frames or doing it > straight with just one 20ms frame? Just one 20 ms frame. It always returns a single frame except when it just can't (e.g. 60 ms CELT). > From your explanations below, opus_encode() will concatenate

Thanks Jean-Marc and Benjamin for the answers. One follow-up question. If I use a repacketizer as Jean-Marc suggested by combining two 60ms frames to form a 120ms frame, without extracting individual frames and using a new TOC, I would need to have a "de-packetizer" that does the exact opposite of repacketizer. De-packetizer would need to separate this 120ms frame into two 60ms frames

ly or Hybrid frames for 40 or 60ms packet, respectively. That is based on = concatenating 20ms frames, right? Is 60ms the largest packet opus_encode() can generate? In order to get pac= kets of up to 120 ms by combining multiple frames as described in RFC6716 c= lause 2.1.4 one would need to use the "repacketizer". That is if I want to= have a 120 ms packet, I would need to take

My file is 3 hours long, so decoding takes around 5 minutes on an average computer. That is a bit too long unfortunately... Am 23.12.2011 20:38, schrieb Steve Checkoway: > On Dec 23, 2011, at 10:54, Hermann Weber<hermie.weber at gmx.de> wrote: > >> And how many frames does Speex need to "recover"? >> Or is that not predictable? > No idea. My guess is not

Dear Christian van Bijleveld, You can use any of the below DSPs of Texas Instruments 1. TMS320C674x - This supports floating point implementation of opus 2. TMS320C66x - This supports both floating and fixed point implementations 3. TMS320C64x - This supports only fixed point implementation Regards, Mahantesh On Mon, May 13, 2013 at 10:12 PM, <opus-request at xiph.org> wrote: >

HI, I'm trying to simulate an audio conference where each leg can be with a different bit rate. This needs to encode the source PCM to to different bit rates back to back and store and send respective encoded frames/packet to the respective channel. For this I changed the opus_demo as below. But the output of the second encoded frames is completely garbled. Appreciate if anyone can suggest

Dear Nikos, thanks! But you use Opus only for resampling, not for entirely replacing Speex, don't you? Greetings! Hermie Am 07.05.2013 22:53, schrieb Nikos Chantziaras: > The Opus resampler is actually a bugfixed version of the Speex one. Same > interface/API, but with the bugs removed. It's why I recommended it :-) > Otherwise I would have recommended something entirely

Sorry, it seems I have only replied to Lakhdar, not to the newsgroup. Below is my reply to Lakhdar, and I would like to make it more clear now, using some pseudo values for simplicity: I read bytes 1 to 124 from my encoded spx file. I decode themt and get the values: ---Frame 1---- -293 -8234 2134 17 ---Frame 2---- -9323 -732 189 2329 Both frames are just perfect as I need them. But now when I

Hi everybody I wrote a couple of months ago about implementing the opus codec on a DK52 from Nordic (nrf52832 MCU, Cortex M4). In the meantime I got a bit further and would again like to ask some questions. My settings: I included all the opus files into my project (opus-1.2.1) Defined: FIXED POINT, VAR_ARRAYS, DISABLE FLOAT API, OPUS_BUILD, CELT_MODE_ONLY I am able to allocate enough memory

The libopus encoder's opus_encode() method is documented as "Encodes an Opus frame". Does that mean that it always produces a single Opus frame (i.e. the number of frames in the TOC byte will always be 0)? It's not clear from the documentation, but the fact that it cannot produce a 120ms Opus packet makes me wonder if that was the intention and any multi-frame Opus packets must

Dear Nikos, thank you very much for your advice! I am not a little bit new to C++, and experiments (like using another third party library) always turn out to be days of work for me. That is why I would first like to try Speex's new internal resampling function. I am currently still using the old 1.0.4 version. I have now downloaded the new 1.2rc1 version. Unfortunately it does not want

Hello, I've been trying to understand how to use opus codec for quite some time. There is a thing that doesn't make sense to me. I will try to explain what it is below, In *opus_encode() *function, *opus_int16 pcm* is said to have a size of *frame_size * channels*, where *frame_size* is said to be one of* 20, 240, 480, 960, 1920, and 2880.* Let's say, frame_size is 960, then