similar to: Fwd: HW requirements?

Hi all, I would like to implement an opus encoder on a TI CC2650 MCU (128 kB Flash). I did not find any information about the hardware requirements of opus, but I found that someone already had trouble with the flash size with the 512 kB ATMEL AT32UC3B0512. (http://lists.xiph.org/pipermail/opus/2016-August/ 003611.html) Do you think I should start implementing or rather find an other

On 7/23/13, Silvia Pfeiffer <silviapfeiffer1 at gmail.com> wrote: > On 23 Jul 2013 15:17, "Martin Leese" <martin.leese at stanfordalumni.org> > wrote: ... >> Information about Metadata >> has been collected together in the Xiph Wiki >> at: >> https://wiki.xiph.org/Metadata > > That page is a bit outdated. It has CMML in it which we

On 10/25/18, Rodger Combs wrote: > >> On Oct 25, 2018, at 12:47, Martin Leese <martin.leese at stanfordalumni.org> >> wrote: ... >> An alternative approach is to only define >> popular layouts. For more obscure layouts, >> such as 2.1 and Mid/Side, assume that the >> person doing the encoding knew what they >> put in, and so knows what will come

---------- Forwarded message ---------- From: Martin Leese <martin.leese at stanfordalumni.org> Date: Mon, 20 Dec 2010 21:42:04 -0700 Subject: To: flac-dev at xiph.org Erik de Castro Lopo wrote: > Can someone please remove this moron > spammer [Gourav Tewatia] from this list. And also delete their four posts from the archive (otherwise the SPAM links will be picked up by search

On 9/26/07, Josh Coalson <xflac@yahoo.com> wrote: > --- Martin Leese <martin.leese@stanfordalumni.org> wrote: ... > > Where can I find more detail on what is a > > "non-audio" RIFF chunk? > > it is any riff chunk that is not "fmt " or "data" > > > Ambisonic ".amb" files are WAVE-EX files with > > a

Erik de Castro Lopo <mle+xiph@mega-nerd.com> wrote: > Martin Leese wrote: > > So what is "OggPCM"? I started this thread > > because I was puzzled why someone was > > changing a draft instead of the document > > itself. > > The original OggPCM was started by a person who really didn't > lnow what they were doing and wouldn't listen to

I have been tidying up bits of the Wiki. This one is not clear cut, so I decided to seek advice. Also, I wasn't sure where to post this question, so defaulted to ogg-dev. Should Speex and CMML be removed from the Wiki Sidebar at: https://wiki.xiph.org/MediaWiki:Sidebar ? Many thanks, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web:

On 10/21/07, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote: > On 10/21/07, Martin Leese <martin.leese@stanfordalumni.org> wrote: > > Either "OggPCM" or "OggPCM Draft2" needs > > to be deleted. It really doesn't matter which, > > but I would suggest that "OggPCM" takes the > > big sleep. Just give time for me (or Sempo)

On August 9, 2013, Silvia Pfeiffer wrote: > On Thu, Jul 25, 2013 at 6:36 AM, Martin Leese wrote: ... >> Should Speex and CMML be removed from >> the Wiki Sidebar > Don't remove Speex - it's still very much in use. > > We probably want to add Daala to the list of video codecs: > https://wiki.xiph.org/Daala > > We probably want to remove CCML from the

On Wed, Jul 22, 2009 at 7:24 PM, Martin Leese<martin.leese at stanfordalumni.org> wrote: > Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > >> Martin Leese wrote: >>> Anyway, calling alloc()s with no corresponding >>> free()s is a memory leak. Not good code. >> >> The alloca() function allocates space on the stack and >> that

Brendan Bolles wrote: > Hey everyone, according to Wikipedia's 4-year-old information, there is no > standard for putting metadata into an Ogg file. True. > That metadata must be > included in the codec. More generally, in a stream in the Ogg file. Codecs are streams, but so are things like Ogg Skeleton. Information about Metadata has been collected together in the Xiph Wiki

On Sat, Nov 29, 2008 at 2:20 PM, Josh Coalson <xflac at yahoo.com> wrote: > --- Martin Leese <martin.leese at stanfordalumni.org> wrote: >> Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: >> ... >> > Whats more, the sndfile-convert program can also convert >> > from FLAC to the following file formats that support 63 bit >> > file

Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > Martin Leese wrote: >> Anyway, calling alloc()s with no corresponding >> free()s is a memory leak. Not good code. > > The alloca() function allocates space on the stack and > that allocation is automatically freed when the function > that did the allocation returns. > > The Linux man page is quite

Bastiaan Timmer wrote: ... > In a > previous message I mentioned writing some more convenience functions, but on > closer inspection they would either be inefficient or very difficult > to implement. Could you briefly list these, in case somebody else wants to have a go. Many thanks, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web:

" Ivo Emanuel Gon?alves " <justivo at gmail.com> wrote: ... > To be fair, only the Vorbis users requested albumart. FLAC users > should in theory be able to use the tag too if they want, but this > wouldn't be something we'd see in other codecs like Speex and Theora. This is a minor point, but FLAC users can already do this using METADATA_BLOCK_PICTURE (which

Ralph Giles <giles at thaumas.net> wrote: > On 5 March 2012 01:51, Silvia Pfeiffer <silvia at silvia-pfeiffer.de> wrote: >> I've started the following wiki page: >> https://wiki.xiph.org/Chapter_Extension > > Not webvtt-style '-->' timestamp separators? :) ... > We should also trim leading and trailing whitespace. Silvia Pfeiffer <silvia at

Ulrich Windl wrote: > Hi! > > Recently I made some recordings (44.1kH/24bit WAV), and after > post-processing (normalization, noide reduction) I saved them as flac (still > 44.1kHz/24bit). > I noticed that ogg123 can decode these, but it will output 24 bit only. > Specifically there's no option to transform the output to 16bit. > When trying to pipe the 24bit WAV output

> On Oct 25, 2018, at 12:47, Martin Leese <martin.leese at stanfordalumni.org> wrote: > > Rodger Combs wrote: > >> I've run into some issues using Opus with source files in channel layouts >> other than the default 8. For instance, 2.1 isn't supported, so I have to >> either downconvert to 2.0 or upconvert to 5.1 (which usually involves adding >>

Shayne Wissler <wissler at gmail.com> wrote: > On Tue, Oct 6, 2009 at 1:57 PM, Martin Leese > <martin.leese at stanfordalumni.org> wrote: ... >> For Ogg Vorbis and Ogg FLAC, see: >> http://wiki.xiph.org/index.php/MIMETypesCodecs#Codecs_Parameter > > Isn't this meta information used in e.g. email and HTML? I don't think > it will help vet a standalone

Am I supposed to take an "INFORMATIVE" document as standard? How can one know the output channel order if there is no standard way to map it on creation? Being undefined, it's up to the decoders to decide the channel order, leading to incompatibility among implementations. On Wed, Nov 10, 2010 at 03:49, Martin Leese <martin.leese at stanfordalumni.org > wrote: > Ricardo