# Normalizing source files automatically?

**URL:** <https://qa.fmod.com/t/normalizing-source-files-automatically/16301>\
**Category:** FMOD Studio\
**Created:** [October 15, 2020, 2:17pm UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301 "2020-10-15T14:17:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Feuertopf1](https://avatars.discourse-cdn.com/v4/letter/f/839c29/32.png) [@Feuertopf1](https://qa.fmod.com/u/Feuertopf1)\
**Post date:** [October 15, 2020, 2:17pm UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/1 "2020-10-15T14:17:08Z")

</div>

Hi everyine,

I have several explosion source WAVs. I want to randomize between them. Unfortunately, the source files all have different levels. I would like to normalize them, so that the peak of each source file is at 0db.

Is there a feature in FMOD Studio to do that? Some kind of “Normalize” checkbox on the asset?

---

<div class="post-metadata">

**Author:** ![richard\_simms](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/richard_simms/32/261_2.png) [@richard\_simms](https://qa.fmod.com/u/richard_simms)\
**Post date:** [October 19, 2020, 12:42am UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/2 "2020-10-19T00:42:37Z")

</div>

There currently isn’t a feature in FMOD Studio to normalize assets. It’s recommended to use an external DAW to normalize audio files.

---

<div class="post-metadata">

**Author:** ![jojojo](https://avatars.discourse-cdn.com/v4/letter/j/96bed5/32.png) [@jojojo](https://qa.fmod.com/u/jojojo)\
**Post date:** [October 19, 2020, 8:34am UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/3 "2020-10-19T08:34:51Z")

</div>

Personally I wouldn’t recommend a DAW but an audio editor like Audacity or (much better) Acoustica from Acon Digital. There are a lot of good editors out there but anything is better than a DAW because you can work much faster with individual audio files.

---

<div class="post-metadata">

**Author:** ![Panagiotis\_Kouvelis](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/panagiotis_kouvelis/32/74_2.png) [@Panagiotis\_Kouvelis](https://qa.fmod.com/u/Panagiotis_Kouvelis)\
**Post date:** [October 20, 2020, 9:19pm UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/4 "2020-10-20T21:19:48Z")

</div>

I don’t know about Audacity, it’s ok for simple work, but it doesn’t perform so good when resampling, so keep in mind that every step you take destroys a little bit of your assets’ fidelity.

Here’s some comparisons of noise introduced in SRCs with Audacity and Reaper (which also features a great batch processor):

 ![SRC comparisons 1](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/7/73c694f161ed378c2d39a5e5f1345cc5becb715f.png)

Here is a clearer image of the noise and alias frequencies that are generated by each program:

 ![SRC comparisons 2](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/1/13358ebbb7e69f3566c9391f831a16f7b3f5dfb2.png)

Again, Acon Acoustice against Reaper:

 ![SRC comparisons 3](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/f/f2f0015ecc97a5d5e608bbb2a8e6c0dcde0cbda6.png)

And the same programs in the noise spectral view:

 ![SRC comparisons 4](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/1/1b559698d4fcc08ad1593167a2f26d8a94f06774.png)

The latest Adobe Audition also features awesome performance on conversions of such kind:

 ![SRC comparisons 5](https://canada1.discourse-cdn.com/flex036/uploads/fmod/original/2X/e/e055967916f4865dd21172a74bf12499ad3502f6.png)

Of course you might not do any SRC during your workflow, but sometimes you can normalize and export at the same time, so usually game developers do that kind of mistake. And by the looks of it, it seems that Audacity, which is great as a free alternative, might have low quality mathematics/processing in other modules too. So it might be better to find an alternative if possible.

By the way, @Feuertopf1 do you want your files to be normalized by their peak values or perceived loudness?

---

<div class="post-metadata">

**Author:** ![jojojo](https://avatars.discourse-cdn.com/v4/letter/j/96bed5/32.png) [@jojojo](https://qa.fmod.com/u/jojojo)\
**Post date:** [October 20, 2020, 11:30pm UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/5 "2020-10-20T23:30:29Z")

</div>

I don’t use Audacity, just mentioned it cause it’s free. The workflow is also not so great.

---

<div class="post-metadata">

**Author:** ![Panagiotis\_Kouvelis](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/panagiotis_kouvelis/32/74_2.png) [@Panagiotis\_Kouvelis](https://qa.fmod.com/u/Panagiotis_Kouvelis)\
**Post date:** [January 11, 2021, 8:13am UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/6 "2021-01-11T08:13:02Z")

</div>

I agree. I use Reaper for everything, as it can be used easily as a sample editor without the DAW part getting in the way, and it’s free to try and very cheap if you are eligible for the discounted license: [REAPER | Purchase](https://www.reaper.fm/purchase.php). Also, it’s the go-to for game audio from day one.

But for simple standalone tasks, what about SoX? They feature awesome quality conversion and it’s command line with many tutorials online, so you could make your life easier with a batch file normalization.

Here’s the website: [http://sox.sourceforge.net/](http://sox.sourceforge.net/)

Have in mind that SoX doesn’t handle metadata well, but in most cases you don’t need them anyway.

Cheers!

---

<div class="post-metadata">

**Author:** ![AlexM](https://avatars.discourse-cdn.com/v4/letter/a/3da27b/32.png) [@AlexM](https://qa.fmod.com/u/AlexM)\
**Post date:** [January 11, 2021, 11:11am UTC](https://qa.fmod.com/t/normalizing-source-files-automatically/16301/7 "2021-01-11T11:11:12Z")

</div>

Ocenaudio is pretty cool and free for fast audio treatment (but I don’t know about quality of processing).

However, normalizing sounds isn’t a good idea: maybe some files will have a peak, not audible but still there, that will block the normalization at a level that may not sound the same than another file. A manual levelling (and maybe limiting) is required.
