Mp3 Gain works pretty good on my mp3's. But I have about 17 wave songs and would like to have them sound close to the same volume. Would wave gain do this?
Thanks
Full Version: Mp3 Gain and Wave Gain
Yes
--
GCP
--
GCP
I kinda talked about this on another thread, but I'll piggyback on this one because it's newer and I think I can explain my question better.
In MP3 gain, you select the "target normal volume" prior to applying the gain. How come WAV gain has no such option? What "target normal volume" does it use? I want the highest volume possible, so when I use MP3 gain in radio mode, I simply raise the "target normal volume" until there is no clipping on any tracks. Does WAV gain do this?
Hopefully I've explained myself clearly.
In MP3 gain, you select the "target normal volume" prior to applying the gain. How come WAV gain has no such option? What "target normal volume" does it use? I want the highest volume possible, so when I use MP3 gain in radio mode, I simply raise the "target normal volume" until there is no clipping on any tracks. Does WAV gain do this?
Hopefully I've explained myself clearly.
QUOTE
Originally posted by goweropolis
In MP3 gain, you select the "target normal volume" prior to applying the gain. How come WAV gain has no such option? What "target normal volume" does it use? I
In MP3 gain, you select the "target normal volume" prior to applying the gain. How come WAV gain has no such option? What "target normal volume" does it use? I
Was wandering that myself ???
At a guess, 89dB, which is the standard level in every other tool.
--
GCP
--
GCP
Like Garf says, 89dB, like the rest. It uses the standard code.
If you want to maximise the non-clipping volume, Volumax http://www.inf.ufpr.br/~rja00/files/volumax.zip does exactly that on wave files on a track or album basis.
If you want to maximise the non-clipping volume, Volumax http://www.inf.ufpr.br/~rja00/files/volumax.zip does exactly that on wave files on a track or album basis.
Apply Max No-Clip Gain for Album (& remove clipping), what setting will do this to a wav file/album?
If your question relates to Volumax, just look at the help. If not, ignore this!
If not, ignore this!
is there any way to get a log file with wavegain?
Probably!
What do you want logged?
What do you want logged?
basically what you see in the dos window. the analysis of the wave files, the changes made. and btw, the command line i'm using now is -a -y. is this correct? i just want an album gain applied.
Yes, that command line is correct. OK, I'll see about the option to write a log.
great. and thanks for such quick responses
I'm trying to get a text file of the WaveGain options to use as a reference, but the standard DOS command line (from WinNT) doesn't work, "wavegain -h > help.txt". That line works for similar situations with LAME, how come it doesn't work with WaveGain? How do I get those options printed out without having to open a DOS command prompt? Thanks.
I think it prints to stderr. Try:
wavegain -h 2> help.txt
(I am at work so I cant see if that is right)
wavegain -h 2> help.txt
(I am at work so I cant see if that is right)
no, that doesn't seem to work. it just says "could not find file '2': The system cannot find the file specified.
i just tried --stderr C:log.log, which would work in mpcenc, but with wavegain it just says "unrecognixed option '--stderr'
The Help follows:
This version is just about to be uploaded to Roberto and has the option of writing a log file.
CODE
WaveGain v0.7 - Compiled Jul 25 2002. Copyright (c) 2002 John Edwards
Usage: wavegain [options] input.wav [...]
OPTIONS
-h, --help Prints this help information.
-a, --album Use ReplayGain Audiophile/Album gain setting, or
-r, --radio Use ReplayGain Radio/Single Track gain setting(DEFAULT).
-c, --calculate Calculates and prints gain settings - DOES NOT APPLY THEM.
This is the DEFAULT.
-y, --apply Calculates and APPLIES gain settings.
-l, --log Write log file.(WGLog.txt)
-n, --noclip NO Clipping Prevention.
-g, --gain X Apply additional Manual Gain adjustment in decibels, where
X = any floating point number between -12.0 and +12.0.
Clipping Prevention WILL be applied UNLESS '-n' is used.
FORMAT OPTIONS (One option ONLY may be used)
-b, --bits X Set output sample format, where X =
1 for 8 bit PCM data.
2 for 16 bit PCM data(DEFAULT).
3 for 24 bit PCM data.
4 for 32 bit PCM data.
5 for 32 bit floats.
INPUT FILES
WaveGain input files must be 16 bit integer wave files with
1 or 2 channels and a sample rate of 48000Hz, 44100Hz,
32000Hz, 24000Hz, 22050Hz, 16000Hz, 12000Hz, 11025Hz or 8000Hz.
Wildcards (?, *) can be used in the filename.
Usage: wavegain [options] input.wav [...]
OPTIONS
-h, --help Prints this help information.
-a, --album Use ReplayGain Audiophile/Album gain setting, or
-r, --radio Use ReplayGain Radio/Single Track gain setting(DEFAULT).
-c, --calculate Calculates and prints gain settings - DOES NOT APPLY THEM.
This is the DEFAULT.
-y, --apply Calculates and APPLIES gain settings.
-l, --log Write log file.(WGLog.txt)
-n, --noclip NO Clipping Prevention.
-g, --gain X Apply additional Manual Gain adjustment in decibels, where
X = any floating point number between -12.0 and +12.0.
Clipping Prevention WILL be applied UNLESS '-n' is used.
FORMAT OPTIONS (One option ONLY may be used)
-b, --bits X Set output sample format, where X =
1 for 8 bit PCM data.
2 for 16 bit PCM data(DEFAULT).
3 for 24 bit PCM data.
4 for 32 bit PCM data.
5 for 32 bit floats.
INPUT FILES
WaveGain input files must be 16 bit integer wave files with
1 or 2 channels and a sample rate of 48000Hz, 44100Hz,
32000Hz, 24000Hz, 22050Hz, 16000Hz, 12000Hz, 11025Hz or 8000Hz.
Wildcards (?, *) can be used in the filename.
This version is just about to be uploaded to Roberto and has the option of writing a log file.
Thanks a bunch John! I suggest adding a text file of this help file to the distribution for easy reference. It might cut down on questions.
The logfile option will be great too. Speedy programming!
The logfile option will be great too. Speedy programming!
thank you very much john33
Version 0.8, just uploaded will be available a little later from Roberto's main site. I already included a 'Help.txt'.
Happy to be of assistance!
If you can't wait!!
You can get it here .
Happy to be of assistance!
If you can't wait!!
You can get it here .
It's already available at RareWares.
Regards;
Roberto.
Regards;
Roberto.
i'm having trouble getting it, there seems to be a dead link
Yep, Roberto's link references the wrong filename!!. You can get it from the link at my post, above.
thanks
Blaaargh
Fixed.
Fixed.
john33,
I checked the help, so to be clear to apply max no clip gain/remove clipping I would:
volumax -c=input.wav -a -l -y output.wav
BTW keep in mind it's the first time I use commandline so excuse me if I'm very wrong
I checked the help, so to be clear to apply max no clip gain/remove clipping I would:
volumax -c=input.wav -a -l -y output.wav
BTW keep in mind it's the first time I use commandline so excuse me if I'm very wrong
@westgroveg
The options are:
A simple command line would, therefore, be:
This will adjust the volume on all .wav files in the directory on an album basis to a max volume no-clipping level. The output overwrites the input, so if you want to keep the original wav file, you'll need to copy it first. The '-l' options takes a value of between 0.00 and -12.00dB as a reduction in the max volume level to be applied; eg. '-l -6.25'. The '-c' option, which is the default, calculates, but does not apply the adjustment. The '-y' option causes the adjustment to be calculated AND applied.
The options are:
CODE
Volumax v0.1 - Compiled Jun 27 2002. Copyright (c) 2002 John Edwards
Usage: volumax [options] input.wav [...]
OPTIONS
-h, --help Prints this help information.
-a, --album Use Album volume setting, or
-t, --title Use Track volume setting(DEFAULT).
-c, --calculate Calculates and prints proposed volume adjustments, but
DOES NOT APPLY THEM. This is the DEFAULT.
-y, --apply Calculates and APPLIES proposed volume adjustments.
-l, --level X Apply reduction to maximum non-clipping volume in dB, where
X = any floating point number between 0.0 and -12.0(DEFAULT 0.0)
FORMAT OPTIONS (One option ONLY may be used)
-b, --bits X Set output sample format, where X =
1 for 8 bit PCM data.
2 for 16 bit PCM data(DEFAULT).
3 for 24 bit PCM data.
4 for 32 bit PCM data.
5 for 32 bit floats.
INPUT FILES
Volumax input files must be 16 bit integer wave files with
1 or 2 channels and a sample rate of 48000Hz, 44100Hz,
32000Hz, 24000Hz, 22050Hz, 16000Hz, 12000Hz, 11025Hz or 8000Hz.
Wildcards (?, *) can be used in the filename.
Usage: volumax [options] input.wav [...]
OPTIONS
-h, --help Prints this help information.
-a, --album Use Album volume setting, or
-t, --title Use Track volume setting(DEFAULT).
-c, --calculate Calculates and prints proposed volume adjustments, but
DOES NOT APPLY THEM. This is the DEFAULT.
-y, --apply Calculates and APPLIES proposed volume adjustments.
-l, --level X Apply reduction to maximum non-clipping volume in dB, where
X = any floating point number between 0.0 and -12.0(DEFAULT 0.0)
FORMAT OPTIONS (One option ONLY may be used)
-b, --bits X Set output sample format, where X =
1 for 8 bit PCM data.
2 for 16 bit PCM data(DEFAULT).
3 for 24 bit PCM data.
4 for 32 bit PCM data.
5 for 32 bit floats.
INPUT FILES
Volumax input files must be 16 bit integer wave files with
1 or 2 channels and a sample rate of 48000Hz, 44100Hz,
32000Hz, 24000Hz, 22050Hz, 16000Hz, 12000Hz, 11025Hz or 8000Hz.
Wildcards (?, *) can be used in the filename.
A simple command line would, therefore, be:
CODE
volumax -a -y *.wav
This will adjust the volume on all .wav files in the directory on an album basis to a max volume no-clipping level. The output overwrites the input, so if you want to keep the original wav file, you'll need to copy it first. The '-l' options takes a value of between 0.00 and -12.00dB as a reduction in the max volume level to be applied; eg. '-l -6.25'. The '-c' option, which is the default, calculates, but does not apply the adjustment. The '-y' option causes the adjustment to be calculated AND applied.
Can I remind people of something here:
If you're changing the volume of a .wav file, the only thing you can do is decrease the quality (slightly) - there is no way that you are increasing the quality.
So, unless you have a reason for making each album as loud as possible (e.g. crappy soundcard with lots of noise), this is a pointless exercise.
If you're trying to match the loudness of several albums, then arguably this brings about a big advantage (consistant volume) for a small disadvantage (slight decrease in quality). However, if you're just trying to make them all as loud as possible, then (with ideal equpiment) there's no advantage.
In contrast, mp3gain (and all the other format specific implementations of replaygain) create a win/win situation - you equalise the volume without sacrificing quality.
I don't want to stop anyone using this software who has a genuine reason for it (e.g. portable player is too quiet, sound card isn't great etc etc) - but it's certainly NOT something that everyone should do to every album.
Cheers,
David.
If you're changing the volume of a .wav file, the only thing you can do is decrease the quality (slightly) - there is no way that you are increasing the quality.
So, unless you have a reason for making each album as loud as possible (e.g. crappy soundcard with lots of noise), this is a pointless exercise.
If you're trying to match the loudness of several albums, then arguably this brings about a big advantage (consistant volume) for a small disadvantage (slight decrease in quality). However, if you're just trying to make them all as loud as possible, then (with ideal equpiment) there's no advantage.
In contrast, mp3gain (and all the other format specific implementations of replaygain) create a win/win situation - you equalise the volume without sacrificing quality.
I don't want to stop anyone using this software who has a genuine reason for it (e.g. portable player is too quiet, sound card isn't great etc etc) - but it's certainly NOT something that everyone should do to every album.
Cheers,
David.
May I just endorse what David has just said. I only produced this originally for a guy who had precisely the problem David described, ie, portable player with low output volume. I certainly didn't intend giving the impression this was a good thing to do in the normal course of things.
I only produced this originally for a guy who had precisely the problem David described, ie, portable player with low output volume. I certainly didn't intend giving the impression this was a good thing to do in the normal course of things.
are 2Bdecided's comments in reference to Volumax or wavegain, or both?
Let me put this in context: we're talking about a very very small reduction in quality. It's much smaller than the reduction in quality due to the very very best audio codec (e.g. mpc braindead). But it's there, so I thought I'd mention it.
If you want to use replaygain with a format that is totally unsupported, then use Wavgain. However, it's better to use the format dependent versions.
Therefore:
.wav > mp3 > mp3gain
is better than
.wav > wavgain > mp3
Cheers,
David.
If you want to use replaygain with a format that is totally unsupported, then use Wavgain. However, it's better to use the format dependent versions.
Therefore:
.wav > mp3 > mp3gain
is better than
.wav > wavgain > mp3
Cheers,
David.
Thanks 2Bdecided, but what about when going the other way?
I have mp3 files (never mind where I got them from...) and when I select some of them in order to make a compilation CD I would like to normalize them relative to this specific selection.
I don't want to alter the original mp3 files because I might be using some of them later in another selection where a different normalization level would be more appropriate.
So I thought that normalizing the intermediate wave files (which I delete after a successful burn) is the right choice.
Does this make any sense?
Thanks!
I have mp3 files (never mind where I got them from...) and when I select some of them in order to make a compilation CD I would like to normalize them relative to this specific selection.
I don't want to alter the original mp3 files because I might be using some of them later in another selection where a different normalization level would be more appropriate.
So I thought that normalizing the intermediate wave files (which I delete after a successful burn) is the right choice.
Does this make any sense?
Thanks!
QUOTE
Originally posted by ahyny
So I thought that normalizing the intermediate wave files (which I delete after a successful burn) is the right choice.
Does this make any sense?
So I thought that normalizing the intermediate wave files (which I delete after a successful burn) is the right choice.
Does this make any sense?
Qualitywise it is better to apply the changes to the mp3 before decoding. When changing the volume of the wav-files you will decrease the quality. Applying the changes to the mp3 itself is done without affecting the quality, and can be undone later.
I can understand your point of not wanting to change your "originals", but it is a better way to do so. You can apply a volume change to them many times without any quality reduction at all. And you can always make a copy before applying the changes...
/Andreas
ahyny,
Whichever. It's splitting hairs. (i.e. it makes almost no difference).
If I were doing this, and wanted the best possible results, I would copy the mp3s I wanted to burn to audio CD into a new folder, run mp3gain on them, listen to them to check I agreed with what mp3gain had done, and then decode them to .wav using Winamp with the MAD plug-in, and no DSP/EQ. Then I'd burn those .wavs to CD.
But if you decode mp3 to .wav, run wavgain, and the burn the modified .wavs, it'll be fine. The rounding errors are very small. As long as the mp3s weren't clipping (and were NOT very quiet), it probably doesn't matter. If the mp3s are clipping, or contain quiet passages, then there's a chance that you might hear the difference between the two methods.
Now, john33 tell me - does wavgain dither the result? It might be a useful option.
Cheers,
David.
Whichever. It's splitting hairs. (i.e. it makes almost no difference).
If I were doing this, and wanted the best possible results, I would copy the mp3s I wanted to burn to audio CD into a new folder, run mp3gain on them, listen to them to check I agreed with what mp3gain had done, and then decode them to .wav using Winamp with the MAD plug-in, and no DSP/EQ. Then I'd burn those .wavs to CD.
But if you decode mp3 to .wav, run wavgain, and the burn the modified .wavs, it'll be fine. The rounding errors are very small. As long as the mp3s weren't clipping (and were NOT very quiet), it probably doesn't matter. If the mp3s are clipping, or contain quiet passages, then there's a chance that you might hear the difference between the two methods.
Now, john33 tell me - does wavgain dither the result? It might be a useful option.
Cheers,
David.
At the moment, David, no it doesn't. I'm quite happy to look at adding it as an option though.
This is a very interesting and informative thread, thank you.
what about implementing replaygain with loseless formats, like monkey's or lpac? apegain... i like it
Thanks!!!
This was very helpful and educating!
ahyny.
This was very helpful and educating!
ahyny.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.