 |
|
| Try for yourself |
|
|
By Ram - Posted on October 10, 2006 - 00:03:53 (#20746)
Current version when comment was posted: 1.3.1 |
|
|
-d 11 doesn't fill up the spectrum. Try the option for yourself and see, should work fine.
|
|
| d 11 |
|
|
By BeOS Mr X - Posted on October 9, 2006 - 17:52:43 (#20744)
Current version when comment was posted: 1.3.1 |
|
|
I find that -d 5 doesnt make the Mp3s loud enough. Does 11 mostly fill up the spectrum analiser ? Because 5 doesnt enough I found. Below appears a tip: recompile the sources with the -O3 flag to get a nice boost in the speed. I havent tried that yet. How would I do that ?
|
|
| Re: Slow |
|
|
By Ram - Posted on October 8, 2006 - 04:47:02 (#20739)
Current version when comment was posted: 1.3.1 |
|
|
Yes when compared to the Linux version this one is extremely slow. Maybe its not the latest? I don't know.
I use it like this:
mp3gain -r -d 11 -c *.mp3
Works great though!!! I use it all the time!!
|
|
| works good but is too slow |
|
|
By BeOS Mr X - Posted on October 7, 2006 - 12:13:29 (#20736)
Current version when comment was posted: 1.3.1 |
|
|
The new recommended settings are:
mp3gain -r -d 5 -f -q -c *.mp3
The above wont bother you with interuptions.
Took two days and a half on 3510 files (1.8ghz P4). There is an easy way to make the program run on all your mp3 files. Create a folder called mp3 links. Now alt-f and pick the drive you want. Search for mp3 file. When searching is done, ctrl-a on the search results. Drag and drop the files into the mp3 links folder while holding down ctrl. Now choose create link from the menu. Summon a terminal into the mp3 links dir and paste the above setting now you can easily normalise all your mp3 files. The mp3 links folder can be deleted when finished.
|
|
| Thank you |
|
|
By Jess - Posted on April 21, 2003 - 16:28:42 (#6979)
Current version when comment was posted: 1.3.1 |
|
|
Thank you for the explanation. In truth I should have contacted you first in the past two weeks of research. I have been doing professional audio work for years now I find this app perplexing but thought it's usefullness could be great. I think it could be VERY usefull but as it is now it's rather useless for my purposes. For you -c may not result in anything audible but for me it does. I have tried many differant things to figure out what the meanings of things meant & using Danes suggested settings managed to get noticable clipping. I do not sit infront of average PC speakers. I sit in front of Engineering Monitors - I hear things if something is wrong. Allowing the -c option seems like some one trying to pump up the level via mix down to a DAT. The end result sounds about the same as pumping way too much into a DAT mastering. It does not result in distortion but a pop or click sound depending on how you want to describe it. True Digital distortion is nothing like analog distortion & so even when cliping this does nto produce digital distortion but pops & anomalies. Terribly sorry for all the fuss as this cannot due what I had hoped it could.
|
|
| Re: yes but |
|
|
By BGA - Posted on April 21, 2003 - 15:56:56 (#6978)
Current version when comment was posted: 1.3.1 |
|
|
No, -c is not stupid. First of all the clipping will happen only on the peaks and most of the time, the clippin will not even be perceptible (for instance if you only lose 1 bit of resolution due to clipping). That option is provided so you don't need to confirm all the time it happen. Maybe there should be another option that would simply not apply the gain and keep going but the fact this option does not exist does not make the -c option useless. As I said I applied mp3gain on *ALL* my MP3s. Lots of them resulted in the warning and none had any noticeable distortion.
The fact that I only ported it does not mean I won't care when someone calls the app stupid. It *IS NOT* stupid. If it was I would have not ported it. Also, check previous comments and you will see people tend to agree with me on this respect.
I suggested you to read the code because *YOU* said the way it works is stupid. Sayind that without being able to understand the code is as ridiculous as asking a non-coder o check the code.
You need an script to be able to process zillions of files. There is a limit on how many files you can pass as a parameter on the command line. That's the only reason you need one.
With the method used it is *NOT POSSIBLE* to get the volume to the peak. his happens because the Gain factor changed inside the MP3 file is a integer and it is very likelly that at some point you have 95% of the peak in the file and increasing the gain Gain factor by one would result in 110% of the peak. There is no way around that and the only way to do it is by decoding, normalizing and reencoding (or with a lot of lucky, as it is possible to find filesthat will reach the 100% peak though it is improbable).
I already said but I will say again. It will apply the same normalization is the entire file. There is no mid boost or anything like that.
Again, here is what the README says:
3 - Recommended parameters (according to Dane Scott, from BeOS Radio) are:
mp3gain -r -d 5 mp3file
This will make the file ready for broadcasting via SoundPlay, for example.
This will normalize the file to as near 0 dB as possible (given the restrictions I mentioned). Some files *WILL* give the clip warning, also due to the reasons I mentioned above but, as I said, it usually won't matter.
-Bruno
|
|
| yes but |
|
|
By Jess - Posted on April 21, 2003 - 14:45:57 (#6977)
Current version when comment was posted: 1.3.1 |
|
|
I don't mention decoding or re-encoding. I do not care how things are done it's a simple matter of making sense. -c is a rather dumb fag IMO & note again you only ported this so chill. I fail to see reversable or not why you would say -c "Yes make it sound crackely & horrid so I will have to undo all this." The command line options are not worded in a understandable mannor - to you they are because you ported it so you know each function... your suggestion to read the code is rediculas to a non-coder. It is also not YOUR responsibilty to provide documentation when then original site doesnt even have any. The read me tell me nothing. Yes lossless - lossless has nothing to do with what I asked. I don't care if things are reverseable - if the forward function is not understandable I doubt undoing it will make much sense either thus making it trivial as well as who wants to "normalize" files for 18 hours to have to undo 18 hours worth of "normalizing"? Why should there need to be a script to bring the peak of an mp3 to unity? I fail to see the variables that need to be played with here. I'm not asking for multiband compression, normalization, or mastering here. Just up the volume to max. As for the analysis the reame m& web site describes it as dealing with how things sound to the human ear... this to me sounds like it's going to boots mids or anything present in certain freq ranges. I WANT to use this app... I just wish it made sense. It's frustrating to try to read up on it & figure it out when you ask a question and get responses like the apps gives you... make change to what!? DB or file is that so hard to define? Also -g this is just as confusing... apply gain i to mp3 with out doing any analysis... so if I type mp3gain -i 100 /boot/home/somemp3.mp3 does that mean it will be normalized to 100DB? 0 DB? 100DB plus it's current DB level? I mean -g 100 could give you a gain of 180DB. Can you at least see why this does not make itself clear? Is gain measeaured in DB? It's too bad RTFM is the type of answer I get... I didnt rant off the bat... I asked around - I read on sites... so I post here & basically get RTFM & RTFC ya read the code... thanks I'm on it... why not give me the code in hebrew on top of it so I can try to figure out 2 things I don't know to make it more fun.
|
|
| Re: stupid? Beware the rant... |
|
|
By BGA - Posted on April 21, 2003 - 14:24:51 (#6976)
Current version when comment was posted: 1.3.1 |
|
|
I am not even sure why I bother answering an email with this tone. Sufice to say this is the last time I do it so if you want to get my attention to a problem you found with one of my BeBits releases, B_DONT_DO_THAT.
No, the app is not stupid at all. If it was I would not release it. Also I don't see a problem with the way the command line options are worded. They may not be the best description one could come up it but implying the application is useless/stupid due to that is... Well... Plain stupid.
Here is what the -c switch description says:
-c - ignore clipping warning when applying gain
This seems pretty obvious to me but I will try to explain it anyway: If you use the -c flag you are telling mp3gain to ignore the clipping warning or, in other words, it will not ask you about applying or not the gain to a file. It will simply apply it even if the file would clip.
Concerning your next question, either you didn't read the README file or you're completelly misunderstood what this application does. Let me quote again (this time, from the README):
"Also, the changes MP3 Gain makes are completely lossless. There is no quality lost in the change because the program adjusts the mp3 file directly, without decoding and re-encoding. This also means that all changes are 100% reversible."
The key here is "all changes are 100% reversible". This should answer you question.
You asked if it would change the gain or clip the audio. On that case it would do both. *BUT* the change is 100% reversible as stated in the README.
Nothing is wrong about normalizing the audio files. But it is a non-trivial thing to do. decoding, normalizing and reencoding is easy, but you will lose quality. Normalizing without decoding is only possible in MP3 files and, again, it is not trivial. Check the sources and you will see what I mean.
The app does what it is supposed to do. It normalizes one file. To normalize multiple files and/or do directory recursion you *WILL* need some form of script around it.
Now that was a good one. So you actually read the code and completelly understood what it does and concluded it is stupid? It is not stupid. Something is not stupid becase it does not work the way *YOU* think it should.
And, BTW, you're wrong about how it works. It normalizes the entire file but does that based on a statistical analysis of how the file sound. It does not normalize parts of the file differently as it looks you're implying it does. Also it wll only do that if you use the -r or -a options. You can simply use the -g option to set a gain.
That said, I used it on all my MP3 files in a batch and it worked perfectly. And, you know, you're not forced to use it if you do not want to.
-Bruno
|
|
| stupid? Beware the rant... |
|
|
By Jess - Posted on April 21, 2003 - 13:46:23 (#6975)
Current version when comment was posted: 1.3.1 |
|
|
Ok is this app stupid? No serious! I want to know... so far I have done as much research as the 100% lack of info on this has allowed. Every option is worded in the most retarted way Imaginable.
If you do not specify -c, the program will stop and ask before
applying gain change to a file that might clip
so if you add -c does that mean it will just let it clip? All these scripts running around & info saying use -c well hell no if it just allows it to clip? does it doesnt it?
WARNING: /boot/home/Stuff/Music/The Cult/The Cult - She Sells Sanctuary (Long Version).mp3 may clip with mp3 gain change 3
Make change? [y/n]:
Make change to WHAT!!!??? the damn gain or the mp3!?
it it going to change the DB it's supposed to change or does make change "no" mean no let it clip?
What is so wrong about normalizing the damn audio files?!
This app should simply normalize all audio in a given directory with the option for recursion to 0 unity. The analysis this does to make it louder to the human ear is stupid. I dunno what they have decided to allow to be boosted but untill I see some hard info I'm gonna go ahead & say great 1K sounds loud to the human ear so it's gonna boost the mid range till everything sounds like crap! Gee THANKS! Tests I have run have given me less then useable results & I don't feel like running this on a few thousand mp3's till some one drops some info out there on what the hell these option wordsings are referring to? "Make change" for all we know this means --> to your socks.
|
|
| Nice one (Tip included) |
|
|
By BiPolar - Posted on February 28, 2003 - 08:20:06 (#6106)
Current version when comment was posted: 1.3.1 |
|
|
This little proggie is really a "must have" for any "melómano" (music lover, according to "Lingua" =) ) out there.
Little tip: recompile the sources with the -O3 flag to get a nice boost in the speed.
In my test (mp3 duration = 1m31s), with "mp3gain Test.mp3" (repeated two times each, figures are from the second run):
standard exe:
real 0m6.323s
user 0m6.023s
sys 0m0.135s
recompiled exe:
real 0m1.721s
user 0m1.590s
sys 0m0.067s
--BiPolar.
|
|
| Thanks mmu_man |
|
|
By J.Seemer - Posted on November 20, 2002 - 11:25:25 (#4254)
Current version when comment was posted: 1.3.1 |
|
|
Very good! Worked like a charm!
|
|
| Re: one more thing |
|
|
By mmu_man - Posted on November 19, 2002 - 15:43:59 (#4243)
Current version when comment was posted: 1.3.1 |
|
|
That one is a BeOS-specific feature... so I don't think the author will bother...
anyway, just open the mp3gain.c file, search for the lines:
int main(int argc, char **argv)
{
then:
gSuccess = 1;
and add this one just after:
set_thread_priority(find_thread(NULL), B_LOW_PRIORITY);
And add this line at the top of the file:
#include <OS.h>
Then run :
make
from the Sources/ folder in a Terminal, and it should work.
|
|
| one more thing |
|
|
By J.Seemer - Posted on November 19, 2002 - 10:52:58 (#4238)
Current version when comment was posted: 1.3.1 |
|
|
I just remembered one more thing, easy to fix:
mp3gain's working thread has a default priority of normal (10). On my tiny notebook this slows down the system considerably (foremost Mozilla...)
I changed the prio to low (5), and everything's running smoothly again. Maybe it should be compiled like that from the start.
rain: I think you're right, I'll forward my option requests to the original author.
And don't expect me to whip up (well, it'll surely be more like a tedious, straining and time consuming labour for me...) a GUI for mp3gain any time soon :)
I have no idea how to code the front-ends logic (what option is available when and how does it influence other choices) or how to save, load and apply preferences... the basics, basically.
Best would be a complete front-end as source with detailed comments. Anyone got a link? Mail me.
|
|
| Re: mp3 gain gui |
|
|
By marcone - Posted on November 18, 2002 - 21:29:58 (#4233)
Current version when comment was posted: 1.3.1 |
|
|
For those that feel GUI programming is a burden, I highly recommend liblayout, which can be found right here on BeBits :)
It's not a graphical UI builder, but it does make creating a UI a lot simpler than using the standard Be classes.
|
|
| Re: J.Seemer |
|
|
By rain - Posted on November 18, 2002 - 19:36:07 (#4232)
Current version when comment was posted: 1.3.1 |
|
|
I personally think that you should ask the original developer about new features so BGA can focus on other things :)
About front end programming. There's really not a lot more to it than simple GUI programming, and you can find several articles and code examples of that on the net. A frontend is a good first project when you want to learn simple GUI programming. I was thinking about doing this one myself, but it would be better if you choose to do it cause we need more BeOS programmers :)
|
|
| further options? |
|
|
By J.Seemer - Posted on November 18, 2002 - 14:03:37 (#4231)
Current version when comment was posted: 1.3.1 |
|
|
Nice app, BGA! Can you add some more options or is this a "porting-only" endeavor?
Two options that could be useful IMO:
When mp3gain warns that there'd be some clipping if the gain is applied, you're presented with a simple dialog if that's OK, "yes/no". There is an option:
-c - ignore clipping warning when applying gain
which would mean a default "yes" to the above question. What if I'd like always a "no" for all the input files?
Another thing, also related to clipping:
How about telling the user how many samples would be clipped? I guess I can live with a few pops on some material (that's the worst case result of a clip, right?) but things would be different if there were 82273 clippings...
On GUI programming: I'm in no way a programmer, but I have looked a bit into C++ and BeOS programming. I'd really like to be able to code a simple front-end to a command line app. Is there anywhere a tutorial about that?
|
|
| RE: GUI Frontend |
|
|
By tb100 - Posted on November 17, 2002 - 05:11:35 (#4217)
Current version when comment was posted: 1.3.1 |
|
|
I'm quite bust right now writing a BeOS native MSN client (and learning C++ and the4 BeAPI in the process). But if this offer's still open in a month then I'll look into doing a GUI for this.
Simon.
|
|
| GUI Frontend? |
|
|
By BGA - Posted on November 16, 2002 - 18:54:36 (#4211)
Current version when comment was posted: 1.3.1 |
|
|
Ok, I just discovered I *HATE* GUI programming. Anyone around would like to help by creating a GUI frontend to this program? Even better, create a new program around the gain_analysis interface (mp3gain is just an example on how to use that interface).
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
 |
| |
Recent Downloads - # 2,224
Total Downloads - # 1,274
Total Views - # 1,122
User Ratings - N/A
|
|
|
|
 |
| |
Misc. Audio Tools
MP3 Tools
MP3 Utilities
|
|
|
|
 |
|
1. BePodder - 9.80
2. QEMU - 9.68
3. ScummVM - 9.57
4. Jukebox - 9.44
5. Haiku AGP busm... - 9.35
6. cpu_fix - 9.31
7. vim6 - 9.31
8. VNCServer - 9.30
9. Beezer - 9.26
10. HandBrake - 9.25
|
|
|
|
 |
|
1. Ati Radeon G... - 32,893
2. BeOS 5 Perso... - 32,462
3. Realtek RTL8... - 20,354
4. Ensoniq Audi... - 17,699
5. USB Joystick... - 16,559
6. BePDF - 15,354
7. ATI Rage 128... - 13,355
8. S3 Trio 64 v... - 10,306
9. VLC Media Pla... - 9,562
10. DOSBox - 9,476
|
|
|
|
 |
| You are not logged in.
Login
|
|
|
|
 |
|
