MacMP3Gain - 1.2Analyzes & adjusts mp3 files to have the same volume |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| Version 1.2: | |||||
| Overall Rating: | Features: | Not rated (0.0) | Support: | Not rated (0.0) | |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews
Troubleshooting
Usage Tips
Developer Notes
Commentary
Featured Reviews
Another cool tool for doing the job - Version: 1.9a, 11/15/2007 11:03AM PST
(0 of 1 users found this comment useful)
Macianer
Very happy with it! 



- Version: 1.9a, 11/30/2006 03:54PM PST
justamacuser
I had read about that little tool here on versiontracker, but didn't bother to try it - until last week, when my iPod picked ZZ Top's "Afterburner" (remastered) right after the "Best of Simon & Garfunkel" original version - quite a jump in volume (about 16 dB). While it did jerk me awake at work ;) it wasn't an experience i wanted to repeat. So, after doing the usual backup, i gave it a try.
1) for the first run, it's taking its time. Subsequent runs are much faster, since the results of the analysis are stored in the MP3 files.
2) I did not witness any "dead" files so far (contrary to some experiences mentioned below)
3) It'll write a temporary file and copy that file over the original MP3. So if you're proud of your MP3 files showing creation dates like "June 2001", you better hack together some Applescript to copy that information into the MP3 comments before you run MP3gain. Agreed, that may be overkill, but my library dates back to iTunes 1.1, and that's something i'm taking some pride in ;) - besides, scripting iTunes + disk access is a nice learning experience.
4) The progress indicator is just "barber pole" if you're running folders recursively. Also, the text output is too short for long song titles. Adding some pixels there (or having it wordwrapped on two or three lines would be nice. But that's just nitpicking.
5) Since the original gain value is stored in the MP3, adding the "undo changes" feature to the frontend would be a nice touch.
All in all, does what it claims, and does it quite good. Thanks!
1) for the first run, it's taking its time. Subsequent runs are much faster, since the results of the analysis are stored in the MP3 files.
2) I did not witness any "dead" files so far (contrary to some experiences mentioned below)
3) It'll write a temporary file and copy that file over the original MP3. So if you're proud of your MP3 files showing creation dates like "June 2001", you better hack together some Applescript to copy that information into the MP3 comments before you run MP3gain. Agreed, that may be overkill, but my library dates back to iTunes 1.1, and that's something i'm taking some pride in ;) - besides, scripting iTunes + disk access is a nice learning experience.
4) The progress indicator is just "barber pole" if you're running folders recursively. Also, the text output is too short for long song titles. Adding some pixels there (or having it wordwrapped on two or three lines would be nice. But that's just nitpicking.
5) Since the original gain value is stored in the MP3, adding the "undo changes" feature to the frontend would be a nice touch.
All in all, does what it claims, and does it quite good. Thanks!
Most Recent Replies: View All 1 Replies
- Applescript example code, if you're interested...
iPod-savvy? - Version: 1.9, 9/14/2005 08:15AM PST
(1 of 2 users found this comment useful)
gustav_wyneken
If you adjust your sound levels with this app, are they still subject to the notorious iPod firmware bug? As I understand it, any changes that you make to a track in iTunes (e.g. by moving the Volume Adjustment slider) will be magnified by a factor of 6.25 when played back on your iPod -- with often painful consequences.
Do tracks adjusted with MacMP3Gain behave the same way?
Do tracks adjusted with MacMP3Gain behave the same way?
Most Recent Replies: View All 1 Replies
And the best is: If you burn a audio CD in iTunes, you have the same gain on the CD...!!!