From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o0D06SYm025065 for ; Tue, 12 Jan 2010 19:06:28 -0500 Received: from mx1.redhat.com (ext-mx07.extmail.prod.ext.phx2.redhat.com [10.5.110.11]) by int-mx04.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id o0D06NMB032236 for ; Tue, 12 Jan 2010 19:06:23 -0500 Received: from ewr.djernes.net (ewr.djernes.net [97.107.141.189]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o0D067hn029450 for ; Tue, 12 Jan 2010 19:06:07 -0500 Received: from data.home (unknown [109.67.184.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ewr.djernes.net (Postfix) with ESMTPSA id 0E63A38928 for ; Wed, 13 Jan 2010 00:06:05 +0000 (UTC) Date: Wed, 13 Jan 2010 02:05:58 +0200 (IST) From: Geoff Shang X-X-Sender: geoff@data.home To: Linux for blind general discussion Subject: Re: analyze a .wav or .mp3 file In-Reply-To: <4B4BB073.6000800@thechases.com> Message-ID: References: <201001112126.o0BLQh88029576@mx1.redhat.com> <4b4baaab.0603c00a.7198.ffffff20@mx.google.com> <4B4BB073.6000800@thechases.com> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-RedHat-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.67 on 10.5.11.17 X-Scanned-By: MIMEDefang 2.67 on 10.5.110.11 X-loop: blinux-list@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: Linux for blind general discussion List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jan 2010 00:06:28 -0000 On Mon, 11 Jan 2010, Tim Chase wrote: > I was about to fire off a similar email, but Chris beat me to the punch. If > you just want the volume adjustment, you can add "-v" at the end of the > command: > > sox my_file.wav -n stat -v > > and all it reports is the volume number with no extra information. Can be > useful for scripting purposes too. My suggestion also. One thing to keep in mind - at least the versions I've used send this number to stderr instead of stdout. No idea why, but if you want to use it in a script, you need to keep this in mind, assuming it hasn't changed. Geoff.