similar to: ReplayGain support for Vorbis"

Hello all, I'm glad to announce to you that Vorbis now has full ReplayGain support. If you're not familiar with ReplayGain, take a look at www.replaygain.org. The main features are: a) all songs play back with equal loudness b) removes the need for normalization c) allows for clipping prevention Using it is very simple. Get a compatible decoder (ogg123, XMMS and WinAmp all support it

Hi all, I have implemented ReplayGain support for Vorbis. If you are not familiar with it, it is basically a method of making sure all your files have equal loudness, remove the need for normalization and prevent clipping during playback. The process is totally lossless, and supporting it requires minimal work. More info about the exact workings can be found on www.replaygain.org (recommended

Hi all, I started testing the RC1 encoder at ftp://sjeng.sourceforge.net/pub/sjeng/oggdrop.exe (based on branch_monty_20010708) On the songs I have tested so far (not much :) I did not hear any stereo issues, but there are some very noticeable problems with the produced files. Songs without much high-end will suddenly have one when encoded. (you'd expect it the other way around) It

And thats only a player. What about an (Open Source) encoder? Nah, I'll stick with OGG for the time being. Regards, Mark -- Mark de Bokx Internet Service Engineer ICT Communication and Media Services PlanetMediaGroup the Netherlands "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty not safety." --Benjamin Franklin

Hi all, ome people asked if it was possible to make an even higher quality mode by incorporating some of the changes from the first tuned version into the 350kbps mode. I did so and made a new version with this new mode. It gives bitrates from roughly 300-350kbps. That's a lot, but it also gets very hard to find something it artifacts on :) Should be sufficient for archival quality. In

I would very much like a lowpass option because for FM radio broadcasting I don't want to encode frequencies above 15khz. I'm waiting for this option before switching to ogg from mp3(lame). Ross. > -----Original Message----- > From: owner-vorbis@xiph.org [mailto:owner-vorbis@xiph.org]On Behalf Of > Gian-Carlo Pascutto > Sent: Tuesday, 4 September 2001 01:46 > To:

Hi! I am very pleased with the progress that Ogg is making, expecially after I read the latest comparision tests on http://ff123.net/128test/instruct.html that put OGG on top aside with MPC. BUT the APPLAUD.WAV test case ( http://lame.sourceforge.net/download/samples/applaud.wav ) still produces **VERY** easily audible high-frequency artifacts when encoded with OGG RC3 up to q4.9 (!!!). Things

After doing an informal (128k) listening test, I have concluded that I prefer Beta4 over RC2. The 16kHz low-pass on the RC2 encoder makes it sound like FM radio. Both encoders SEEM to have a couple of dB bump at 10kHz. JT --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

As far as I can see, transcoding could be usefull for people who do not primarly care about quality but about filesizes. One could assume that such a user would have a collection of mp3's at 128kbps or higher bitrates, and uses an encoder like BladeEnc or Xing. He wants to take uses of ogg's supposed quality and transcode his 128-or-higher files into 96 or 112kbps oggs to save diskspace.

In case you missed it, RC2 is on slashdot.org too: http://slashdot.org/article.pl?sid=01/08/13/1811241 BTW Gian-Carlo Pascutto wrote on /. that RC3 should appear very soon (in a week or so)? Also, it looks like Wall Street Journal article is not available on-line (at least to non-registered persons). If someone is registered or have a paper edition, please post this article somewhere so that we

---------- > Van: ORK <korsmo@solungen.hm.no> > Aan: vorbis@xiph.org > Onderwerp: [vorbis] OggEnc help file > Datum: maandag 3 september 2001 18:21 > > Somebody asked how to use OggEnc a while ago. > > OggEnc v0.8 (libvorbis rc2) > (c) 2001 Michael Smith <msmith@labyrinth.net.au) > > Usage: oggenc [options] input.wav [...] LOL! --- >8 ---- List

When using the abx utility that is in LAME's misc dir, trying it on an ogg (with ogg123) gives the following output: Standard Open Source Bug detected, try murksaround ... (ogg123 is decoding to stdout) IIRC this also happened with older mpg123's but no longer with the latest release. Latest ogg123 from CVS still gives it though. Someone stole code but forgot to check for fixes? :)

As a developer for a company that uses OGG's Vorbis & Speex codecs, it would be nice if there were small, cute, professional-looking "powered by" icons we could use on our website for these codecs. Do these exist? -david <p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a

Found this on usenet: August 13, 2001 E-Business Inventors Release Free Alternative To MP3 Music, but Cost Is High By MEI FONG Staff Reporter of THE WALL STREET JOURNAL SOMERVILLE, Mass. -- Christopher Montgomery wants to be the Linus Torvalds of music, the creator of a piece of free software that has the sweeping impact of Mr. Torvalds's Linux operating system. He soon may begin finding

Hello -- I desperately want to start using Ogg compression on music I release on the internet, but I am encountering a fair amount of artifacts. I noticed some in beta4 and was hoping they would disappear with RC1. However, I've been playing with RC2 and I've still been banging my head into a number of problems. A majority of the music I make has long drones with a fair amount of spectral

Hey When playing an http ogg stream served by icecast, ogg123 (vorbis-tools-1.0.1) seems to detect replaygain metadata because it displays it in a nice way, but does ogg123 actually alter the playback volume according to the replaygain variables? I can notice no effect. I did some googling on this but didn't find much help. I discovered a vgplay patch for vorbis-tools 1.0.1 but after

When a locale is in effect that does not use the point as the decimal mark (e.g., sv_SE or de_DE, which use a comma) and a ReplayGain tag is read for --apply-replaygain-which-is-not-lossless, the gain value was misinterpreted (e.g., "-2.29" truncated to "-2"). This is fixed by resetting the locale to "C" temporarily, based on Josh Coalson's fix of the dual case

Declaring variables in the middle of a block isn't supported by older (pre-C99?) compilers, and gcc 2.95 is one of them. --- a/src/plugin_common/replaygain.c +++ b/src/plugin_common/replaygain.c @@ -28,10 +28,11 @@ void FLAC_plugin__replaygain_get_from_fi double *track_peak, FLAC__bool *track_peak_set,

This new ReplayGain feature is cool, but made all my .mp3 and .mod files sound so loud, so I wrote a Winamp DSP plugin that: - If a file is playing that is not known, a ReplayGain value will be calculated while playing. - If a file is known, the ReplayGain value is applied. What that means is that my .mp3 files now sound as loud as my .oggs. I hacked this thing together very quick, so

My replaygain player side backend code is up at savannah: https://savannah.nongnu.org/projects/vgplay/ Pull it from CVS for the time being, as the file area isn't up and working just yet. It applies album and track gain values as scale factors to float pcm and includes an arbitary value preamp, a couple of limiting strategies. There's also helper function to pull the replaygain