similar to: ogg123 + replaygain?

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

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying

Hi, I need to adjust the output volume from ogg123 the same way that mpg123 has the "-f n change scalefactor [32768]" option. I need to do this within ogg123, instead of alternatives that involve pipes, such as piping the output to sox. I do not believe that this is currently possible in ogg123, and I'm looking for some suggestions as to how it can be accomplished by modifying

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

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

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,

I've written an updated xmms vorbis plugin, which is currently available from the vgplay cvs as a file tree and patch: http://savannah.nongnu.org/cvs/?group=vgplay (Once some file area problems are sorted, I'll put the patch there for easier access). It's a patch or Input/vorbis tree for xmms 1.2.8 and includes the following features: - Replaygain is now implemented using

Hi! I have a few questions about the log files icecast produces, plus I have a little issue with replaygain but lets start with the icecast log stuff: If a client (listener) connects to icecast at, say, 12:00, the connection time is stored in the access log about 15-30 minutes later (or on disconnection). Is it possible to get icecast to log client connections immediately with the correct

In this topic on Hydrogen Audio(http://www.hydrogenaud.io/forums/index.php?showtopic=105586) someone asked a question about the sample rates that FLAC supports for ReplayGain. The outcome was that the current documentation of MetaFLAC is outdated since Commit http://git.xiph.org/?p=flac.git;a=commit;h=0554a4aee6966bc5b251364753ef85de72dfab19 because as of 1.3.0 FLAC supports Replaygain with many

I backed up my entire CD collection to Flac (350+) to avoid losing them to scratches, laser burns, etc. Now I'm wondering how RG affects the Wav file produced from Flac decompresion if I used the following command with CDex: -8 -V -T artist="%a" -T album="%b" -T title="%t" -T date="%y" -T tracknumber="%tn" -T genre="%g" --replay-gain

Hi, I've been working on ogg123 to see if i could add a remote interface compatible with the one in mpg123. This remote interface is used mainly by mp3 players which use mpg123 as their backend. The reason i did this was that i have recently encoded some of my cd's in ogg vorbis format but wanted to keep using my favourite player (playmp3list,

I've been tinkering with vgplay (my fp gain function and replaygain support code) as well as looking at FLAC replaygain code, with an eye to combining them into a general gain effect plugin helper, however I noticed that the November 19, 2003 Ogg Traffic talks about postfish, being a sound postprocessor with a noise filter and 'a revolutionary declipping filter', that Monty is

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

have linux install on my laptop, and decide to clean up my music collection, found allot of my music that has replaygain tags, and allot don't. How would I fix the ones that don't have any replaygain tags, ? have flac and flac123 ogg ogg123 vorbistools and vorbisgain..etc, all installed, can play music fine, but when I hit a song, that doesn't have replaygain tags, need to turn down

Hello everyone, I'm new to this flac thing (started about a week ago) but I have read a lot about flac and replaygain. As far as I understand it, replaygain is lossless in the sense that I can tell my player to ignore the settings or I can even use foobar2000 to remove the tags entirely, hence getting back to the original audio. If that is the case, why is there a warning in the foobar2000

>b) According to http://wiki.xiph.org/OggOpus#Comment_Header >there should be no REPLAYGAIN_*** tags in Opus files; Opus uses >R128_TRACK_GAIN tag. If some audio player reads Opus tags then it should >be aware of the difference between ReplayGain and R128. But this doesn't >require REPLAYGAIN_REFERENCE_LOUDNESS tag. > > The Opus replaygain spec is fundamentally broken, so

Hello, ogg123 | ices2 are doing transcoding but ogg123 is staying frozen under certain circumstances here is the stack #0 0x401f25d4 in __pthread_sigsuspend () from /lib/libpthread.so.0 #1 0xbffff94c in ?? () #2 0x401f2398 in __pthread_wait_for_restart_signal () from /lib/libpthread.so.0 #3 0x401eef0b in pthread_cond_wait@GLIBC_2.0 () from /lib/libpthread.so.0 #4 0x0804b0d3 in

Using Linux (Kubuntu) using the application "crip" ripping at -q 10 & using replaygain on for volume control -------------------------------------------- Now that I have 2000 .ogg files... first problem: There is NOT one Portable CD Player on the Market, that can play encoded .ogg files AND read the replaygain tags. via a cd-r second problem: Burning... if I am going to burn a

hi! I've got some problems compiling/linking the vorbis tools. at first I had the same problem as mentioned here: http://www.xiph.org/archives/vorbis-dev/200201/0005.html (make was looking for libogg.la in the wrong path) but creating a symlink to /usr/local/lib/libogg.la in /usr/lib/ helped. :) having solved this, I get a new error: --- gcc -O20 -ffast-math -fsigned-char -o ogg123