Is there a way to incorporate MP3Gain into my EAC process? Or am I going to have to remember to run MP3Gain on all my newly ripped files?
Jake
Full Version: Incorporating MP3Gain into EAC Process?
I am not aware of any method of doing this. It sure would be nice to be able to do it though. I guess if enough people bug Andre with it, maybe he'll add it 
.
.
Hmm... a few possibilities (none of which I've tried myself, just brainstorming)
1) mp3gain.exe (the "Back end" half of mp3gain) is a command-line program that does all the real number crunching and file modifications. You could probably work up some sort of batch file that first calls your encoder (I hope you're using LAME) and then immediately calls mp3gain. Then in EAC, in the Compression options, go to External Compression and put in this batch file as your user-defined compression program.
2) If Andre really does incoporate something directly into EAC, he'd probably be better off simply incorporating the Replay Gain algorithm to analyze the raw data as it comes in. That would be simpler than reading the raw data, encoding to mp3, and then having mp3gain decode back to raw data for processing it through Replay Gain (which is what mp3gain does internally for "Analysis").
The Replay Gain algorithm is included in the mp3gain back end source code at
http://www.geocities.com/mp3gain
Just some thoughts...
-Glen
1) mp3gain.exe (the "Back end" half of mp3gain) is a command-line program that does all the real number crunching and file modifications. You could probably work up some sort of batch file that first calls your encoder (I hope you're using LAME) and then immediately calls mp3gain. Then in EAC, in the Compression options, go to External Compression and put in this batch file as your user-defined compression program.
2) If Andre really does incoporate something directly into EAC, he'd probably be better off simply incorporating the Replay Gain algorithm to analyze the raw data as it comes in. That would be simpler than reading the raw data, encoding to mp3, and then having mp3gain decode back to raw data for processing it through Replay Gain (which is what mp3gain does internally for "Analysis").
The Replay Gain algorithm is included in the mp3gain back end source code at
http://www.geocities.com/mp3gain
Just some thoughts...
-Glen
If you want the clipping prevention of mp3gain to work, you cannot void encode and decode.
--
GCP
--
GCP
QUOTE
Originally posted by Garf
If you want the clipping prevention of mp3gain to work, you cannot void encode and decode.
If you want the clipping prevention of mp3gain to work, you cannot void encode and decode.
Good point. I'd forgotten about that.
-Glen
But I'm still waiting for someone to email me a sample that clips at an 83dB target level. So it wouldn't be much of a problem.
(actually, I have one sample, but it's a cannon going off in the middle of 1 minute's worth of silence!)
Cheers,
David.
(actually, I have one sample, but it's a cannon going off in the middle of 1 minute's worth of silence!)
Cheers,
David.
QUOTE
Originally posted by 2Bdecided
But I'm still waiting for someone to email me a sample that clips at an 83dB target level. So it wouldn't be much of a problem.
(actually, I have one sample, but it's a cannon going off in the middle of 1 minute's worth of silence!)
Cheers,
David.
But I'm still waiting for someone to email me a sample that clips at an 83dB target level. So it wouldn't be much of a problem.
(actually, I have one sample, but it's a cannon going off in the middle of 1 minute's worth of silence!)
Cheers,
David.
All implementations are using 89dB target level...where this does occur.
I have one where the peak value after replaygain is 59000. With 6dB
attenuation (to get to 83dB) this is 29500. Close
--
GCP
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.