similar to: base64 ALBUMART vorbiscomment

"Santiago Jimeno" wrote: > Flac files, as us knows, follows the Vorbis Tags system included in block 4 > Recently Vorbis has established the possibility to include picture files by > means of 2 Tags: COVERARTMIME AND COVERART. > To work therewith is quite easy. No. this in incorrect. The VorbisComment "COVERART" was only ever unofficial, and has been deprecated

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

I have been tidying up the VorbisComment page in the XiphWiki. The problem with it was that it was a mixture of proposals and discussion of those proposals. This made it difficult for implementers to see what to implement. The problem section is: http://wiki.xiph.org/index.php/VorbisComment#New_ENCODER_field_name_proposal This is a mess, and all I could do was add attributions to the

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

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

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

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

"Kurosawa, Taku" wrote: > Hi Martijn, > > Sorry for the late reply again, > The application we are preparing this time is not exactly similar to > Replaygain. > > Replaygain as we understand is something which normalize the loudness at > content provider side, but our application takes different approach. It is > designed to normalize the loudness at player

Hi, I have posted this three times to the flac-dev, vorbis-dev, and ogg-dev mailing lists. I wanted to see what code there was currently to support Ambisonics. So I downloaded the code from the xiph download page for libogg-1.1.3, libvorbis-1.1.2, vorbis-tools-1.1.1 and flac-1.1.4, but wasn't able to find anything. If it exists then I missed it, so could somebody please point me to it.

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 > empty channels, which prevents the playback device from upconverting to the > native layout). > To address this,

"Gabriel I." wrote: > Greetings, > > I apologize if I posted this in the wrong list, I wasn't sure where to post > it, but seeing as the tags are called "vorbis comments" I thought vorbis, > rather than ogg-dev, would be the right choice. (actually, I'm not even a > developer anyway) Hi Gabriel, I doubt whether the Xiph community would promote a

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

Not sure if this belongs here or in flac-dev. I am subscribed to both, so flop it over if fits better over there. Looking at the Changelog for FLAC 1.2.1 (17-Sep-2007), it says: "With the new --keep-foreign-metadata in flac, non-audio RIFF and AIFF chunks can be stored in FLAC files and recreated when decoding." Where can I find more detail on what is a

Shayne Wissler <wissler at gmail.com> wrote: > I have a program that is given a random file and needs to determine > whether it is Vorbis or FLAC. For Vorbis, there are various places > where I can infer that I have a bad stream. But for FLAC, when I call > either FLAC__stream_decoder_process_until_end_of_metadata or > FLAC__stream_decoder_process_single, it searches the

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:

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

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: