similar to: ogg-dev Digest, Vol 89, Issue 1

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

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

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

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

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:

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

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

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

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

"ogg.k.ogg.k@googlemail.com" <ogg.k.ogg.k@googlemail.com> wrote: ... > > * don't bother with non-UTF8 > > Yes, I was going to leave it as is while keeping the header field there, > just in case. I do know, however, that people in eastern countries tend > to dislike utf-8 for the size it takes for their language, as it's been, er... > /optimized/ for the

uans <engineering at wwrn.net> wrote: > I was looking at the wiki's sites and I came across some to the effect > of OggOCM. Is this already implemented in Ogg. How can I get some more > information on how to access it. I don't believe anyone has yet implemented it. Regards, Martin -- Martin J Leese E-mail: martin.leese stanfordalumni.org Web:

Adam Rosi-Kessel <adam at rosi-kessel.org> wrote: > I finally got something like an explanation from the Mediamonkey > developers. Here is their explanation as to why MM corrupted my files: > > > the problem was caused by the fact that Vorbis library uses alloca() > > function on several places, which allocates memory on stack. We > > changed it to alloc() and

On 10/19/07, Sampo Syreeni <decoy@iki.fi> wrote: > On 2007-10-19, Martin Leese wrote: > > OggPCM Draft3 > > Draft 3 is obviously a joke. Draft 2 is what most of the people agreed > upon the last time around, with the channel maps left unfinished. Draft > 1 was abandoned by most people in favour of draft 2. So what is "OggPCM"? I started this thread

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)

"Silvia Pfeiffer" <silviapfeiffer1 at gmail.com> wrote: ... > Also, it would be good if we can keep > our magic numbers to the first 8 bytes. So Kate and Yuv4mpeg both need to be trimmed. ... >>> char[9]: '\x80kate\0\0\0\0' | kate >>> char[9]: 'YUV4MPEG2' | yuv4mpeg Regards, Martin -- Martin J Leese E-mail: martin.leese

"Benjamin M. Schwartz" wrote: > On 06/04/2012 10:50 AM, Oleksij Rempel wrote: ... >> XMP fits to our needs, but it >> looks like there is still no ready documentation about muxing XML to ogg. > > Well then you've already solved the problem. Just store the XMP in a > VorbisComment field named "XMP" (or whatever name you like). This suggestion falls

Sampo Syreeni <decoy at iki.fi> wrote: ... > [I]n > well-designed and matched protocol environments, if you expect to see > some array of differing protocols, you will also see an easy way of > discerning those protocols from each other. Before engaging in any sort > of decoding endeavor. > > File names, resource fork types or IFF/RIFF block types do not seem to > be

Oleksij Rempel <bug-track at fisher-privat.net> wrote: > Ok, > you are right, using existing technology will save time :) What has not yet been discussed is what you are streaming *to*. That is to say, what software is going to receive the metadata, and what will it do with it. This is important because VorbisComments can contain pretty much anything you want. Suggestions for field

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