From: "Måns Rullgård" <mans@mansr.com>
To: Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk>
Cc: ML - sox-users <sox-users@lists.sourceforge.net>
Subject: Re: Creating files with RMS gain level instead of Peak
Date: Sun, 08 Jul 2018 13:39:43 +0100 [thread overview]
Message-ID: <yw1xpnzxyk8g.fsf@mansr.com> (raw)
In-Reply-To: <ddffe29668a17666d684be49fe477d88@wingsandbeaks.org.uk> (Jeremy Nicoll's message of "Sat, 07 Jul 2018 21:58:36 +0100")
Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk> writes:
> On 2018-07-07 21:47, Måns Rullgård wrote:
>> Jeremy Nicoll - ml sox users <jn.ml.sxu.88@wingsandbeaks.org.uk> writes:
>
>>> 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.
>
> Yes, I understand that gain is gain, but he has to decide how much
> gain to apply. If he's previously done that in terms of a pre-gain
> peak level, but now wants to bring RMS levels to a certain point,
> he surely has to find out what the file's RMS levels are first
> then decide how much to modify it by?
The question posed was how to obtain an RMS gain of -12 dB. The answer
is that RMS gain is equal to peak gain, so "gain -12" will perform the
desired function. If the question were how much gain to apply in order
to obtain a specific RMS level, then of course the initial value would
have to be known.
--
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-08 12:40 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
2018-07-07 20:58 ` Jeremy Nicoll - ml sox users
2018-07-08 12:39 ` Måns Rullgård [this message]
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=yw1xpnzxyk8g.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).