From: "Måns Rullgård" <mans@mansr.com>
To: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
Cc: sox-users@lists.sourceforge.net
Subject: Re: Creating files with RMS gain level instead of Peak
Date: Sat, 07 Jul 2018 21:47:33 +0100 [thread overview]
Message-ID: <yw1xtvpaydqy.fsf@mansr.com> (raw)
In-Reply-To: <f3d0c85cd634ecaf4af01d04defdf444@wingsandbeaks.org.uk> (Jeremy Nicoll's message of "Sat, 07 Jul 2018 20:52:28 +0100")
Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk> writes:
> On 2018-07-07 19:19, Måns Rullgård wrote:
>> Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk> 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åns Rullgård
------------------------------------------------------------------------------
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
next prev parent reply other threads:[~2018-07-07 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-07 15:05 Creating files with RMS gain level instead of Peak James Trammell
2018-07-07 17:25 ` Jeremy Nicoll - ml sox users
2018-07-07 18:19 ` Måns Rullgård
2018-07-07 19:52 ` Jeremy Nicoll - ml sox users
2018-07-07 20:47 ` Måns Rullgård [this message]
2018-07-07 20:58 ` Jeremy Nicoll - ml sox users
2018-07-08 12:39 ` Måns Rullgård
2018-07-08 13:36 ` Mikko Olkkonen
2018-07-08 14:45 ` James Trammell
2018-07-08 15:39 ` Mikko Olkkonen
2018-07-08 16:21 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-users
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xtvpaydqy.fsf@mansr.com \
--to=sox-users@lists.sourceforge.net \
--cc=jn.ml.sxu.88@wingsandbeaks.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).