For testing purposes, it helps me to rename files with a 'tag' that identifies what's been done. i.e a .wav file converted to .mp3 with Lame at 320 CBR, I might add "_L320" at the end of the file name; "_LV2X" tells me I used -V2 plus Mp3Gain etc. This way, when playing the files in differant mp3 players (most w/out real tag support), a quick check of the play list tells me what I'm listening to. It really helps to have these files automatically renamed as part of the conversion process. Thanks to Greynol, I can now do this with a batch file for Lame! I have tried to set this up for Mp3Gain but, alas, I don't know what I'm doing and thus far have been unsucsessful . Any help would be greatly appreciated

maybe post your current batch?

Add'l explanation!

When encoding a .wav file to .mp3 with lame, using a batch script allows me to rename the resultant .mp3 with a 'tag-line' like "L320" or "LV2X" just to let me know what parameters were used for testing purposes i.e. "Song Title.wav" to "Song Title L320.mp3" tells me that the .mp3 was encoded at 320 CBR etc. (saves me having to rename the files manually after encoding is finished) This way, when I'm listening to tracks on my (non mp3 tag supporting) player, in the car, I can tell how the mp3 was encoded by checking the song title. Each Lame version/configuration is setup with its own corresponding batch file and renames the mp3's accordingly. Some examples:

Lame 3.90.3 > 320 CBR has the following batch script:
"C:\Program Files\Lame Convert\L390\lame.exe" -b 320 -m s -h %1 "%~dpn1 L320.mp3"

= "Song Title L320.mp3"

Lame 3.98 > V2 looks like this:
"C:\Program Files\Lame Convert\L398\lame.exe" -V2 --vbr-new -m s -q0 %1 "%~dpn1 LV2X.mp3"

= "Song Title LV2X.mp3"

etc. you get the idea; this all works great! The problem is that I can't get this to work with Mp3Gain even though I'm employing the same batch parameters and they should only be dependant on cmd.exe for executing the rename, not on lame.exe or mp3gain.exe! My goal is to rename the resultant mp3 (gain applied) with an additional tag-line like "GX" to show that gain has been applied. I can run Mp3Gain from a batch file without issue, it's only the rename part that has me stumped. Greynol... Help! Pleeeeez

@smok3

Sorry, just saw your post - hope the above helps!

To append "GX" to a filename you would use:


This essentially says: RENAME "<name><.extn>" to "<name> GX<.extn>".

Therefore, you would run MP3Gain on the file and rename it after using a command as above.

If this MP3Gain action is part of your existing batch files then I suppose it may look something like:


... but then, why not just append the GX when you create the MP3 - if you know that you are going to put it through MP3Gain?


Hopefully, there's enough in the above to let you do what you want anyway! If not, perhaps you could be more specific.

yes, that would do, addition would be checking if replaygain exited without error and then only renaming songs that were actually replaygained.


example on how i check if avisynth is installed/enabled:


only in this case you would have to negate.

Yes, a very good point.

I did mean to put in an example checking the return code of MP3Gain before renaming.

Edit: An alternative would be to use conditional execution, e.g.:


REN will only run if MP3Gain executes successfully.

cool, i have to remember the && thingy

With Synthetic Soul and smok3 on the scene, you should be more than ok.

EDIT: Didn't know that the drive and path weren't necessary for the destination on a rename operation. Thanks!

You're so right, they took gooooood care of me!

@Synthetic Soul!

Awesome! I knew you could set me strait with this and it works beautifully!! (that && thing is gold!) Thank you!!! (hey, where's the little smily that bows in worship when you need him!?) Anyway, I can't thank you enough; you really helped me out



That's probably what I'll end up with eventually but, for now, I just want to keep them seperate for testing purposes.

@smok3!



That's so cool, I didn't know that was even possible!! Great insight and advice! Thanks for your help and guidance in this.

OK, to recap, I can now take any .wav file and with a right click, choose Encode to Mp3 with Lame (any version and configuration I set up) Currently I have 3.90.3 and 3.98b3 setup with differant configurations for differant tasks and testing. As the file is encoded to .mp3 it's also renamed with a tag code that tells me which version/ config settings were used. Now I can right click on any of these resultant .mp3 files and choose to apply Mp3Gain with set options and after gain is applied (and checked!), the new file is renamed with an additional 'GX' tag to show me the file has gain applied! Wow! What can I say, Thanks again guys!

Here's the final batch script (modified to allow 'generic' renaming with Mp3Gain):

A Great thread. Im hoping this may be the right place to post this question as it is in line with what xulama was originally wanting to do.

I was wondering if I could ask you for some help. Im pretty hopeless remembering all the variables in dos CMD stuff.

What Im hoping to be able to do is:
I have a directory structure as follows:

\Artist\(year) Album name\tracks.mp3
[eg: \Pink Floyd\(1975) Wish You Were Here\1 - Shine On You Crazy Diamond (Part One).mp3]

From there, I want to run a batch file that will analyse the music using mp3gain and apply the 89db MP3 gain to every track (eventually this will be run on all my music collection and all future rips)

Once that is complete (as long as no errors are encountered), I want the mp3 files and folders (artist\album) to be moved to my \\server\music\ share that is located on my home server, ensuring that the artist folder and allbum folder is also moved.

I can pretty much understand all the MP3 gain command line stuff, but Im just having a few issues figurung out the order of things in the batch and to make sure that all the folders are correctly moved over.

Can anyone help?

Thanks for your time

BUMP!