search for: ashara

...ing 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 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 byte...

...lso 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 Ashara wrote: > 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) &g...

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

...oubt it's worth it and it's a lot of work (e.g. you want your files to be seekable, right?). The only thing I can assure you of is that we're not going to bring a new "low-complexity" container to the IETF for standardization. Cheers, Jean-Marc On 05/12/2016 07:37 AM, Amit Ashara wrote: > 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 struc...

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

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

...utput 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 <ashara.amit at gmail.com> wrote: > Hello Mark, > > Thanks. Let me try the proposed configuration first to make sure that > linear 8-bit PCM is retrieved. > > Regards > Amit > > On Sat, Jan 9, 2016 at 12:28 PM, Mark Harris <mark.hsj at gmail.com> wrote: >...

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

...easily. I am with you on not creating a new container, but this is a suggestion (microcontrollers benefit a lot with simpler file formats, e.g. lwIP, Tiny FatFs) Regards Amit On Thu, May 12, 2016 at 9:58 AM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > 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...

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? Ye...

...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, Jan 7, 2016 at 8:11 PM, Amit Ashara <ashara.amit at gmail.com> wrote: > >> Hello Ralph, >> >> I was finally able to get it to work for both 8 and 16 bit PCM data. >> However the output of the decoder is always 16 bit PCM and never the >> original 8 bit making the wav file decoded 2x times the or...

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

...(e.g. you want your files to be > seekable, right?). The only thing I can assure you of is that we're not > going to bring a new "low-complexity" container to the IETF for > standardization. > > Cheers, > > Jean-Marc > > On 05/12/2016 07:37 AM, Amit Ashara wrote: > > 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 > > i...

Hello Giovanni, I am running both Opus Encoder and Decoder on a TI Cortex M4 core without any issues. What is the specific issue that you are facing? Can you explain? Regards Amit -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20160105/0bc0bc2c/attachment.htm

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 output from OPUS decoder. > During encode I am using > > popi16fmtBuffer[ui32Loop] = (opus_int16)pcRdBuf[ui32Loop]; > > And during de...

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 restricting factor > besides the compute time. To optimize the utilization of embedded > resources, may I suggest a simplifi...

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 >> >> >> https://en.wikipedia.org/wiki/File:Sample_of_%22Another_Day_in_Paradise%22.ogg >> > > The file you are looking at is an Ogg *Vorbis* file. It's not Opus at all. > > The file at < > https...

...ease the time the CPU shall spend in the encapsulation process rather than encoding/decoding process. The answer may be NO, but the question may still be asked. Regards Amit On Thu, May 12, 2016 at 1:29 AM, Ulrich Windl < Ulrich.Windl at rz.uni-regensburg.de> wrote: > >>> 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? > > > &gt...

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

...e 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. 2. In the OpusTag the is the libopus a mandatory field? Regards Amit On Mon, May 9, 2016 at 2:11 PM, Amit Ashara <ashara.amit at gmail.com> wrote: > 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...