Print

[Aeon]

I haven't posted for a while, and first of all I just wanted to mentioned out ridiculously #$%$@ING retarded the password setup for this forum is. Good lord. Obviously they don't want you to actually be able to remember whatever obscenely contorted gibberish you were forced to enter in there.

Second, does anybody know of a program that will allow me to normalize several tracker files (IT and XM files in particular)? Its somewhat irritating when using multiple music files in an album only to have it change from soft and quiet to LOUD. I know there are programs such as MP3Gain which will do this for mp3 and perhaps OGG files, but I haven't heard of anything that will do it for tracker files.

[Saga Musix]

Obviously they don't want you to actually be able to remember whatever obscenely contorted gibberish you were forced to enter in there.

Obviously, you don't know what a good password is. And I even bet that you use one password for several websites. If you can't remember your passwords, use a password manager- Those even have nice functions like generating long, random passwords, which are pretty safe.

As for your question, there's a difference between normalizing and limting. With normalizing, you just can amplify the entire waveform so the loudest "peak" will be as loud as possible, but if you have one such peak in your file and the rest is pretty quiet, it *will* stay quiet. You can't normalize modules as they are not streams, but you can render your tunes to .WAV files and normalize those (e.g. using Audacity). If this is still not enough, you can try a limit plug-in, but beware - it will kill dynamics (i.e. loud drum hits) and touch the waveform in a very bad way if you do it wrong.

[m0d]

I haven't posted for a while, and first of all I just wanted to mentioned out ridiculously #$%$@ING retarded the password setup for this forum is. Good lord. Obviously they don't want you to actually be able to remember whatever obscenely contorted gibberish you were forced to enter in there.

Hey, don't bitch at me for attempting to ensure that the site is safer from miscreants who do dictionary based brute force attacks on the site, almost every day. Password security is paramount and just because other places have weak password strength security doesn't mean others should.

While I can understand your frustration to a very small degree, you perhaps need to look into formatting your passwords out of phrases instead of using plain words. i.e using the first letter of each word of a phrase, capitalize one of the letters, and add a number in place of a letter. If your password is guessed (or compromised) on one site, and you happen to use the same one across others, then you're in trouble, so another tip is to add a letter from the name of the site to the beginning or the end of the password to make it unique to the site you are using.