This thread may end up proving useful to many other people, as there just aren't too many out there discussing this issue. Religion is 100% superstition and 0% confirmation! Science is 10% new data and 90% confirmation! If the mp3 itself contains some very bad frames this can skewer the calculation. The applied gain alters from file/album to file/album. But the physical alterating of a mp3-file is reversible/lossless.Ģ) The target value for mp3gain is set (-89 db, but can be altered by the user) and does not alter with newer releases. There's an unnofficiel xmms-mad-plugin that reads those tags. I just made it a habit on whatever I downloaded, I would run through mp3gain.ġ) Mp3gain supports tags-only (APE2) without altering the mp3, if need be. If you want to pick a db range (IE: 92) to normalize all your mp3s to, then use mp3gain for your existing mp3s and set that normalization in your ripping program for future mp3s. I redid my entire collection to meet 94 db on all my tracks so they all sound the same and I dont have to run over and turn the volume up or down at various songs (very annoying). Works flawlessly but sometimes faulters on calculating the gain according to actually how loud it sounds since it doesnt scan the entire mp3, just the beginning to calculate the "actual" loudness. Did my entire 4500+ mp3 collection using it. You are GROSSLY misinformed about mp3gain. Gentoo Hardened Linux 2.6.21 + svorak (Swedish dvorak) I would recommend ReplayGain (wavegain/ mp3gain/vorbisgain/etc) over normalization. Normalization only calculates the average of each track without any thoughts of perceptual hearing, while ReplayGain does take the human ear into the "equation". The quality will be a lot worse for sure.īut I would be interested in a solution without quality loss too. Well, reencoding an MP3 is a really really bad idea. I believe xmms will do this for you with the normalizing plugin and the mp3 writer plugin. This would ensure that the any tracks ripped at the same bitrate would be normalized to the same SPL. The most thorough fix would be to reencode your MP3 collection so normalize the MP3s at encode time. Location: under a car or on top of a keyboard Which app would be better for this purpose? Or would it even be possible to always set new mp3s to a preexisting setting, rather than having to re-average everything? Instead, I'd like to have a set volume level based on an original average and bring any new CDs to that preexisting level, so that I don't have to re-normalize everything whenever I rip a new CD and a new average is established. This average will become affected as a I buy new CDs to add to my collection. That's probably pretty simple to do, but both applications seem to base their normalization on an average of all the mp3s it's examining at the time. The Sony only reads ID3 v.1.1 tags, which might be relevant, but I'm not sure.Īnyway, I just want to normalize all volumes to the same level. I have ~ 22 GB of 192 kb/s CBR mp3s that I play on an older Sony DC-J01 mp3 CD player and on an MSI Mega Stick 128. I'm trying to decide which one to use for my purposes. mp3gain claims to be lossless, but (I think) normalize claims to be less intrusive, as it only adds tags for the volume differences. The two most talked-about choices are normalize and mp3gain. I have a large mp3 collection, and I'd like to normalize its volume. Posted: Sat 8:20 am Post subject: normalize vs. Gentoo Forums :: View topic - normalize vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |