From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS6130 216.105.38.0/24 X-Spam-Status: No, score=-3.6 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS,SPF_PASS,T_DKIM_INVALID shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 2DB651F62D for ; Sat, 7 Jul 2018 20:47:50 +0000 (UTC) Received: from [127.0.0.1] (helo=sfs-ml-1.v29.lw.sourceforge.com) by sfs-ml-1.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1fbu7N-0003Fr-MJ; Sat, 07 Jul 2018 20:47:45 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-1.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1fbu7N-0003Fj-C9 for sox-users@lists.sourceforge.net; Sat, 07 Jul 2018 20:47:45 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version :Message-ID:In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=5Q93H8UHINPOFM1VPruExb6CHJ9xDsCBgd9oJFG8bYU=; b=HWg6GeH4yaXTM6LHXSiElbqQaw h7dZrrAUoEh8zEMZaW2V+54MgS2OleWTHZ5ejUYGk32lleIIpGyjxGS9sRlONZTItkn3rTzOwxgQy 6zW14ADWSsu1CJtroBkWfh1aidvSz57Sg+oPR83XPv1qNCW6fr4w4UlSDg7s9EBAMDqQ=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID: In-Reply-To:Date:References:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=5Q93H8UHINPOFM1VPruExb6CHJ9xDsCBgd9oJFG8bYU=; b=Jm3oyItj5YXTjUA4WTXk8oTl9j OnUK5eTEvRanBW5GfCpcMOiIRxO6RAAWrUF4LiF0cdl++eC9gMgs96MTJEyAkM+opdAzdtJu7Vbb1 1EkolYsItt68Fv4qC8QXA7b7K5XtqsO0qyEuEZa9x5VzzygJJDCIrnstxqa6pRy5U2NY=; Received: from unicorn.mansr.com ([81.2.72.234]) by sfi-mx-3.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) id 1fbu7L-00CNui-6d for sox-users@lists.sourceforge.net; Sat, 07 Jul 2018 20:47:45 +0000 Received: by unicorn.mansr.com (Postfix, from userid 51770) id 9C8D11538E; Sat, 7 Jul 2018 21:47:33 +0100 (BST) From: =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= To: Jeremy Nicoll - ml sox users References: <109205cf6d76dd28724114e96149054e@wingsandbeaks.org.uk> Date: Sat, 07 Jul 2018 21:47:33 +0100 In-Reply-To: (Jeremy Nicoll's message of "Sat, 07 Jul 2018 20:52:28 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 X-Headers-End: 1fbu7L-00CNui-6d Subject: Re: Creating files with RMS gain level instead of Peak X-BeenThere: sox-users@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: sox-users@lists.sourceforge.net Cc: sox-users@lists.sourceforge.net Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: sox-users-bounces@lists.sourceforge.net Jeremy Nicoll - ml sox users writes: > On 2018-07-07 19:19, M=E5ns Rullg=E5rd wrote: >> Jeremy Nicoll - ml sox users writes: >> >>> On 2018-07-07 16:05, James Trammell wrote: >>> >>>> How can I get gain of -12dBFS RMS? >>> >>> I don't understand the difference, but even I can see >>> that the manual describes -B and -b options for the >>> gain effect, in terms of RMS rather than peak levels. >>> >>> I do not know if one or other of these options will do >>> what you want. >> >> Those options are for equalising channels using either peak or RMS >> value as reference. > > Ah, I read about the equalising and then forgot it... > >> For a fixed scaling, the peak and RMS values are affected equally. >> Dividing every sample by two, say, will halve both the peak and RMS >> values. > > Yes. So does that mean that the OP should use something like the > 'stat' effect to find out the peak RMS level of the audio file, > then work out how much gain or attenuation is needed, then use > a 'gain' effect with that calculated value? No, he should just use the gain effect. It adjusts both RMS and peak values by the same amount because that is what happens when you multiply each sample by a fixed amount, which is what the gain effect does. The channel equaliser has both options because the crest factor is unlikely to be exactly the same for all channels, so the gain required to match the peaks won't be the same as that for matching the RMS values. -- = M=E5ns Rullg=E5rd ---------------------------------------------------------------------------= --- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Sox-users mailing list Sox-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sox-users