search for: fatfs

...s-Opus or Lite) based on the device requirements/limitations while also > enabling conversion tools to be made available 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 [...]

...e requirements/limitations while > also > > enabling conversion tools to be made available 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 > [...] > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20160513/f2de3d05/attachment.html>

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

...ot; kernels, is in -ac and downloads from the above site are still running at >100/day. The bug report rate from all of this is exceedingly low. The current things outstanding for a 1.0 release are: - There are now two reports of an interaction between ext3 and [v]fat. The symptoms are that fatfs decides to return ENOTDIR when its root directory is read. This is rather bizarre - it may be due to ext3 leaving some unexpected state in a buffer_head, and fatfs is assuming that its buffers are coming in with that state zeroed. If anyone can reproduce this, please send me your .config,...

...gs-Opus or Lite) based on the device requirements/limitations while also > enabling conversion tools to be made available 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, othe...

...ween the two formats (Oggs-Opus or Lite) based on the device requirements/limitations while also enabling conversion tools to be made available 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 result...

...the device > requirements/limitations while also enabling conversion tools to be > made available 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 > <mailto:jmvalin at jmvalin.ca>> wrote: > > On 05/12/2016 10:35 AM, Amit Ashara wrote: > > For HMI panels, except for the cap...