similar to: Replay Gain in Vorbis

Dat Head <dathead2 at gmail.com> wrote: > can somebody explain replaygain a bit - is it kinda like normalization > but w/o modifying > the files (just giving software a number to use to obtain the level > boost needed?) Try http://www.replaygain.org/ although the pages haven't been updated since 2001. (In the past I have e-mailed updates to the maintainer, but got no

"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

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

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

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

" 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

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:

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

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

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

"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

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

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 <silvia at silvia-pfeiffer.de> wrote: > On Wed, Jul 24, 2013 at 3:59 AM, Martin Leese >> ... >>>> Information about Metadata >>>> has been collected together in the Xiph Wiki >>>> at: >>>> https://wiki.xiph.org/Metadata >> Page updated. See what you think. > > M3F is also not used anywhere

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

"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

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,

On Sun, Apr 13, 2008 at 02:10:51AM -0500, Charles Velasquez wrote: > If that is the case, why is there a warning in the foobar2000 > converter dialogue box stating that "applying ReplayGain adjustment > during conversion will irreversibly alter data in encoded file, > unlike ReplayGain scan after encode"? ReplayGain, as the name implies, works by calculating a scaling-factor