Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: MP3Gain 1.3.0 (Read 6938 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

MP3Gain 1.3.0

https://sourceforge.net/project/showfiles.php?group_id=49979

New features:
  • Limited Unicode support
  • Play mp3 files by double-clicking (simply opens the file with default mp3 player)
  • (back end) "apply track gain" skips all album processing
I wish I hadn't made the GUI for MP3Gain in Visual Basic in the first place.
As it turns out, Visual Basic always uses Unicode internally, but the default controls won't display Unicode characters 
So I've added extremely limited Unicode support. Just enough so that you can load, analyze, and adjust the gain on mp3 files. Any unicode characters in the file name show as "?" in the list, though.

As a result of this frustration, I've finally decided to re-write the GUI from scratch.
I'm planning on using wxWidgets (formerly wxWindows), meaning that not only will Unicode support be available, but the GUI will be available in Linux and Mac.

So this 1.3.0 release will be the final one for this architecture.

-Glen

MP3Gain 1.3.0

Reply #1 –
Awesome!
Thank you for continuing to advance MP3Gain. Many of us appreciate your work.
I look forward to experimenting with it when sf.net comes back up.

Sorry to hear about the GUI. In the end I think you will have made the best decision regarding moving to WxWidgets.

Thanks, tec

Glad to see you're still around, btw.

MP3Gain 1.3.0

Reply #2 –
Quote
As a result of this frustration, I've finally decided to re-write the GUI from scratch.
I'm planning on using wxWidgets (formerly wxWindows), meaning that not only will Unicode support be available, but the GUI will be available in Linux and Mac.

So this 1.3.0 release will be the final one for this architecture.



good move !
I'm impatient to try mp3gain with a gui on my linux.

I wish more audio apps / taggers were designed with multi-plaform in mind.
With the proper choice of libs, it's not much more constraining anyway..

MP3Gain 1.3.0

Reply #3 –
Quote
Glad to see you're still around, btw.


Yeah, I haven't been around for a little while. Losing my job and my housing at the same time kinda messed things up a bit. Feeding my family has priority over appeasing the demands of MP3Gain users

Plus, to be perfectly honest, I'd grown tired of MP3Gain. That was partly my fault, though, because I'd written the original code so sloppily that further code changes were becoming more and more difficult.

<tangent>
mp3gain started out as an "is this possible?" experiment, which grew into a tool for myself, which grew into a tool for a few people, which suddenly exploded into a popular tool for thousands of people. Somewhere along the way there, I should have stopped and done a re-write in the first place. My original screwy experiment code is still in there.
</tangent>

But I love learning new languages and toolsets, though, so this complete rewrite has re-ignited my interest. I'm actually planning things out before I start to code this time, so things should be a lot cleaner.
...should be 

-Glen

MP3Gain 1.3.0

Reply #4 –
Glen, I really like MP3gain so I started using 1.3.0 also.

I have a problem though: 1.3.0 changes the whole filename to 'Lower case characters'. I use EAC to make the mp3 files. Can you confirm that MP3gain does that? Or is something going wrong here?

E.g. from '04 - The Exile.mp3' the filename changes to '04 - the exile.mp3'.

The info in the ID3v1 stays perfect, 'Upper Case For First Character'.


Greetz, Geebee

MP3Gain 1.3.0

Reply #5 –
Quote
But I love learning new languages and toolsets, though, so this complete rewrite has re-ignited my interest. I'm actually planning things out before I start to code this time, so things should be a lot cleaner.
...should be 


i would presonally recomend delphi/kylix (win/lin) or lazarus (win/lin/mac)

MP3Gain 1.3.0

Reply #6 –
Quote
I have a problem though: 1.3.0 changes the whole filename to 'Lower case characters'. I use EAC to make the mp3 files. Can you confirm that MP3gain does that? Or is something going wrong here?


Ah, crap.

You're right, MP3Gain is doing it. Stupid bug on my part. I know exactly what I did.
I'll go take it offline ASAP and have a fixed version up real soon.

-Glen

MP3Gain 1.3.0

Reply #7 –
Quote
I'll go take it offline ASAP and have a fixed version up real soon.
-Glen


Great, I'll be waiting :-), thanks.

Geebee

MP3Gain 1.3.0

Reply #8 –
Quote
Quote
I'll go take it offline ASAP and have a fixed version up real soon.
-Glen


Great, I'll be waiting :-), thanks.



You didn't have to wait long.
Version 1.3.1 Beta is now available:

http://mp3gain.sourceforge.net/download.php

Fixing that lower-case bug is the only change from 1.3.0 beta

-Glen

MP3Gain 1.3.0

Reply #10 –
Glen, thanks for the quick fix.

Question: why don't you remove the 'Enable maximizing features" from all coming releases of MP3gain? MP3Gain is meant to replace maximizing, ain't it?

For users who are struggling with the difference between 'maximizing' and 'mp3gain-ing' the availability of both features is very confusing.

Would there be any good reason to use the maximizing features in MP3gain? I think not...

Other question: I would love an option like this: 'apply the maximum target volume possible, without clipping, to an album with songs'.

- MP3gain would do an Album Analysis
- It would check whether there is still clipping in songs if Target volume is 89
- If there is still clipping, it would do an Album Gain with the appropriate Target Volume, eg 88
- Or it would do an Album Gain with the highest possible Target Volume without clipping, eg 94.

This would be handy if someone wants the loudest mp3's possible in an album  without clipping, and does not care about 'even volume' accross albums.

Greetz, Geebee

MP3Gain 1.3.0

Reply #11 –
Quote
As a result of this frustration, I've finally decided to re-write the GUI from scratch.
I'm planning on using wxWidgets (formerly wxWindows), meaning that not only will Unicode support be available, but the GUI will be available in Linux and Mac.


You might consider wxPython instead of wxWidgets. Coding using Python is a lot faster than C++. Issues involved might be bundling for distribution, but there packages like py2exe which will let you do just that!

rajas

MP3Gain 1.3.0

Reply #12 –
Quote
Question: why don't you remove the 'Enable maximizing features" from all coming releases of MP3gain?


It wasn't in there to start with, but people kept requesting it, or something similar.
In fact, your "other question" is just such a request!

But the maximizing stuff is a little obscured (off by default, and you have to go to "Options - Advanced..." to turn it on). So the casual user will just use MP3Gain for its original purpose-- to make all mp3s the same volume.

Quote
Other question: I would love an option like this: 'apply the maximum target volume possible, without clipping, to an album with songs'.


Enable the maximizing features. Then look under the "Modify Gain" menu for "Apply Max No-clip Gain for Album". That will do exactly what you described.

Quote
You might consider wxPython instead of wxWidgets. Coding using Python is a lot faster than C++. Issues involved might be bundling for distribution, but there packages like py2exe which will let you do just that!


Yeah, I considered it. Very strongly, in fact. But the distribution issue you mentioned is precisely why I (sadly) decided against it.

-Glen

MP3Gain 1.3.0

Reply #13 –
Quote
Glen, thanks for the quick fix.

Question: why don't you remove the 'Enable maximizing features" from all coming releases of MP3gain? MP3Gain is meant to replace maximizing, ain't it?


[a href="index.php?act=findpost&pid=241951"][{POST_SNAPBACK}][/a]


There are still many people that use mp3gain only to remove clipping, and these features are handy then.
"You can fight without ever winning, but never win without a fight."  Neil Peart  'Resist'

MP3Gain 1.3.0

Reply #14 –
Quote
i would presonally recomend delphi/kylix (win/lin) or lazarus (win/lin/mac)
[a href="index.php?act=findpost&pid=241514"][{POST_SNAPBACK}][/a]


Delphi? Be prepared to kiss decent Unicode support goodbye then. It's about as Unicode -compliant as VB, maybe less so.

MP3Gain 1.3.0

Reply #15 –
First, thanks for all the work on Mp3Gain!

A question about the command line version of mp3gain.exe (v1.4.4):
I have noticed that after gaining the Mp3 file size has changed by 96 bytes in almost all cases.
Is that any added gain status information the expression 'stored tag info' out of the help ('mp3gain.exe /?') refers to?

I'm just a bit unsecure what it really does. Some tools report a broken Mp3 or simply call it junk...

MP3Gain 1.3.0

Reply #16 –
Does it change compared to the GUI version? Then I don't know.

Otherwise I suppose it is the undo & replaygain info that is stored in an APEv2 tag. Lots of tools doesn't recognize APEv2 tags and may very well call that "junk"

MP3Gain 1.3.0

Reply #17 –
Mp3gain 'command line' adds always(?) 96 bytes. Mp3gain 'GUI' adds about 206 bytes.

According to my hex editor and other posts these additional bytes really seems to contain an APE tag with undo information.
This special (undo) tag info is placed after the last music frame and in front of the ID3 tag v.1x (if it exists). Winamp (2.9x/5.0x) have no problem still finding the ID3 tag behind these APE tag bytes, but Foobar2000 v0.8.3 don't display the ID3 tag any longer (as far as i have experienced it).


For the moment i don't want to re-think my Mp3 playback and tagging 'concept' so i appreciate the pure existence of the option '/s s' (on the command-line) in order to: skip (ignore) stored tag info (do not read or write tags).
On the GUI it would be: 'Options'=>'Tags'=>'Ignore (do not write or read tags)'
... may the user make up his own mind.

Thanks again for mp3gain and its features!


By the way: is there a fixed byte-length (depending on the interface i use) of these tags?
 

MP3Gain 1.3.0

Reply #19 –
First of all, let me add one more post to the "thanks for such a great program" pile! A couple of things I thought of while trialling the program...

1) I did some test encodes with LAME 3.96.1, and it calculates track ReplayGain on the fly, storing it in the LAME header within the file. When I ran MP3Gain on the file it took a while, presumably decoding and analysing the MP3 data. It would be great if MP3Gain had an option to pick up this pre-computed ReplayGain figure and use that in its processing! Especially for slower computer owners like me, processing a whole folder full of files would then be a lot faster...

2) I messed around with EAC and WAPET, given the "foobar2000 doesn't like empty-ish APEv2 tags" issue, with the goal of pre-tagging my files during the ripping process. However, adding APEv2 tags with WAPET seems to mess with Winamp's ability to read ID3v1, as it inserts APEv2 after ID3v1. So, I think I'll probably steer clear of APE tags for a bit. Would it be possible to add an option to store the "Undo" information in an ID3v1/v2 "Comment" field? I have no other real use for the comment field, and if it let me stick with the "standard" tag formats while still retaining un-MP3gain-ability even after processing with all major tag editing applications, that would be great.