Re: [SLUG] Mp3 editor for Linux?

From: Eben King (eben01@verizon.net)
Date: Thu Jun 17 2010 - 14:10:45 EDT


On Thu, 17 Jun 2010, Pete Theisen wrote:

> Christian Brink wrote:
>> On Wed, Jun 16, 2010 at 05:09:29AM -0400, Pete Theisen wrote:
>>
>>> I have about 270 mp3 files on a Sansa clip that feeds the audio on my
>>> bike. Trouble is, they are not even close in volume. If the volume is set
>>> appropriately for one the next one might be way-the-hell too loud,
>>> creating a distraction or worse.
>>
>> Want you are looking to do is normalize.
>>
>> I suggest Mp3Gain http://mp3gain.sourceforge.net/ or VorbisGain
>> http://www.sjeng.org/vorbisgain.html
>>
>> Both use RMS instead of peak to calculate the level and adjust the gain
>> setting in the Tag. They do not actaully adjust the audio, so you get the
>> levels the same without the worry of corruption or distortion (in the audio
>> file).
>
> There are some sort-of instructions but they are for the W-word. Dylan said
> at the meeting I could do this in Linux from the command line, but he didn't
> elaborate.
>
> Well, I have normalize and mp3gain somewhere on the system. The files are in
> home/pete/media/SANSA CLIPP/MUSIC. Where do I go from here?

Check "mp3gain -h" for syntax. Here's an edited version:
Usage: mp3gain [options] <infile> [<infile 2> ...]
options:
         -v - show version number
         -r - apply Track gain automatically (all files set to equal loudness)
         -k - automatically lower Track/Album gain to not clip audio
         -a - apply Album gain automatically (files are all from the same
                       album: a single gain change is applied to all files, so
                       their loudness relative to each other remains unchanged,
                       but the average album loudness is normalized)
         -m <i> - modify suggested MP3 gain by integer i
         -d <n> - modify suggested dB gain by floating-point n
         -? or -h - show this message

Apparently the gain is stored as an integer which is mapped to dB gain (or
reduction).

> By the way, how did that space get in the path between SANSA and CLIPP? I
> copy pasted it right out of the "Location:" line. Doesn't seem right. Oh,
> Sansa is running embedded winders, so . . .

Really? I bet that makes it suck down batteries. You can try getting the
actual device with "mount" (/dev/sdc1 or some such) and doing "label
/dev/sdc1 YourNameHere". There's also a file you can tweak/add that
controls the "automatic mounting" subsystem, but I forget its name and
format.

But you can work around the embedded space by enclosing filenames in quotes,
either single or double (if you need variable/~ expansion).

-- 
-eben   QebWenE01R@vTerYizUonI.nOetP   royalty.mine.nu:81

Unix is user-friendly; it's just picky about who it makes friends with. ----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:00:40 EDT