11 posts
Page 1 of 1
When I normalise it just happens and the normalised levels are all over the place, while I need all files at the same level. How do I determin the amount of normalisation, or to which level I want to normalise?

Cheers!
Maarten
______________________________________________________
MB: MSI Z370A-Pro, CPU: i7-8700 @ 5GHz, RAM: 16GB HyperX @ 3200MHz
Software: Windows10 x64, Studio One 5 Pro
I/O: Quantum 2626 via Gigabyte Titan Ridge
User avatar
by Jemusic on Thu Jul 18, 2019 4:01 pm
For a start peak normalisation is pretty useless. It will only bring the highest peaks up to or close to 0 dB FS. This does not take into account what the rms levels are below them.

RMS normalisation would be much better but you may need an editing program to be able to do that.

Best way to keeps levels consistent right across the board is use a VU meter on your tracks to start with. Choose a reference level e.g. -18 db FS = 0 dB VU. Record your tracks so you are averaging 0 db VU on the meter. Adjust tracks as well (if they were not recorded by you that is) to bring them to 0 dB VU.

RMS levels are much closer to representing how loud a signal actually is. VU metering can be used on buses and the final output as well. Its possible with care to get the same VU readings in all three areas. e.g. at t e reference level.

The free PreSonus meter is not ideal but does work OK. Invest in a 3rd party meter such as Klanghelm or Waves. You can use the bundled Level Meter plugin though and switch it into K system mode e.g. -14 or -20. Aim for the bar graphs to be hovering around the 0 dB VU mark.

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.



Specs i5-2500K 3.5 Ghz-8 Gb RAM-Win 7 64 bit - ATI Radeon HD6900 Series - RME HDSP9632 - Midex 8 Midi interface - Faderport 2/8 - Atom Pad- iMac 2.5Ghz Core i5 - High Sierra 10.13.6 - Focusrite Clarett 2 Pre & Scarlett 18i20. Studio One V5 (Mac), Notion 6.7, Ableton Live 10 Suite, LaunchPad Pro
User avatar
by maartenfranken1 on Thu Jul 18, 2019 4:34 pm
I do that when recording full tracks, but right now Im adjusting speaker IRs, which are not much more than the initial peak, thats why Im using the normalisation function.
But shouldnt normalising be adjusting to a specified level? Thats how I was taught normalisation works and how Ive always done it.
What I see happening now doesnt make much sense to me, one time the level is increased, while another time its decreased, while levels of both files are very low. Also one time I end up with -2dB with a file that starts at -5dB and the next with -8dB for another file that also starts at -5dB. Im still talking about the initial peak only, compared between files of similar structure. I find no recognisable structure in how the function works, right now Im not sure if I understand what normalisation exactly is, to be honest.

Im simply exporting the files, Im not making a mixdown, and I tried adjusting the level with the fader, but I get the impression that the fader-level doesnt affect the exported file. How can I adjust the exported level if not by normalising, or increasing volume level of the channel?

Cheers!
Maarten
______________________________________________________
MB: MSI Z370A-Pro, CPU: i7-8700 @ 5GHz, RAM: 16GB HyperX @ 3200MHz
Software: Windows10 x64, Studio One 5 Pro
I/O: Quantum 2626 via Gigabyte Titan Ridge
User avatar
by Jemusic on Thu Jul 18, 2019 4:52 pm
What version of Studio One 4 are you running? I am seeing some strange behaviour as well. I have got a piano track that is quite low in level and there are no peaks to speak of. After normalisation it only raised the level a few dB. I have checked the file and there are no hidden or short peaks or spikes anywhere which can do this. I will run some more tests.

I don't think Studio One allows you to set what level it is going to normalise to either.

Also what you are doing too (IR's) is quite different from what I was posting about. It's good advice but not directly relevant to you.

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.



Specs i5-2500K 3.5 Ghz-8 Gb RAM-Win 7 64 bit - ATI Radeon HD6900 Series - RME HDSP9632 - Midex 8 Midi interface - Faderport 2/8 - Atom Pad- iMac 2.5Ghz Core i5 - High Sierra 10.13.6 - Focusrite Clarett 2 Pre & Scarlett 18i20. Studio One V5 (Mac), Notion 6.7, Ableton Live 10 Suite, LaunchPad Pro
User avatar
by Lawrence on Fri Jul 19, 2019 6:44 am
Use macros:

- Audio | Normalize Audio
- Audio | Edit Volume - Level ('-10"), Relative ("0")

You can Select All and fire that to normalize all audio events to -10 max peaks for example before starting to mix stems, whatever..
User avatar
by Tacman7 on Fri Jul 19, 2019 7:00 am
maartenfranken1 wrote I tried adjusting the level with the fader, but I get the impression that the fader-level doesnt affect the exported file. How can I adjust the exported level if not by normalising, or increasing volume level of the channel?



Plugins!

I raise up the gain on lots of things with compressors or preamp plugins and limiters.

Bring it up but keep it from clipping.

When I record guitar I have an almost invisible track, normalize really makes that show up.

The fader is monitor volume apparently.

Forum Moderator.
Please add your specs to your SIGNATURE.
Search the STUDIO ONE 5 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.


Studio OnePro5.1 64bit Melodyne Studio
Studio Computer - Nectar Impact LX25+
Win10 i7 7700k 16gb ram 1TB SSD AsusH270M-PLUS interface:StudioKonnekt 48
Kitchen Computer
Win10 Ryzen 5 3600 - Radeon RX 590 - 16GB DDR4 3000MHz - 512GB SSD interface:Komplete Audio 6
User avatar
by maartenfranken1 on Sun Jul 21, 2019 7:26 am
I using SO v4.5.2

Thanks for the input, guys. Im gonna try some things, see what I can make of it.

Cheers!
Maarten
______________________________________________________
MB: MSI Z370A-Pro, CPU: i7-8700 @ 5GHz, RAM: 16GB HyperX @ 3200MHz
Software: Windows10 x64, Studio One 5 Pro
I/O: Quantum 2626 via Gigabyte Titan Ridge
User avatar
by BobF on Sat May 30, 2020 8:54 am
Here is a macro as Lawrence described. I prefer neg 3 most of the time.

Drop this in your StudioOne > Macros folder and map to a keyboard shortcut or macro toolbar button.

Edit/rename to taste

Attachments
Norm Neg 3.studioonemacro
(436 Bytes) Downloaded 26 times

-

-------------------------------------------------------------
Studio One Pro - latest
Win10Pro x64 (latest) i7-6700 @3.8Ghz / 32G / 43" 4K
UMC1820 / Event PS8 / FaderPort Classic / KKS61MK2
Maschine MK3 / Waves Gold / Nomad IS3 / IKM Max / K12CE
User avatar
by miked7 on Sun May 31, 2020 7:19 am
Jemusic wroteFor a start peak normalisation is pretty useless. It will only bring the highest peaks up to or close to 0 dB FS. This does not take into account what the rms levels are below them....

I respectfully disagree. I use the Normalization function when I'm starting a new mix. I find Normalizing to 0dB FS is super useful to see where a track, especially one with sharp transients like drums, is peaking. Then you can clip gain any transients that are way out of whack with the rest of the track to get a quick and more accurate level and bring any wild peaks into line. Once you handle the crazy peaks in your tracks, simply select them all and hit the "-3dB" button until they're all where you want them.

I do agree, however, it would be wonderful to have the ability to Normalize to a specific RMS level. :+1

HoRNet Plugins has a few plugins that do similar things at ridiculously low prices.

It would be great if Studio One had this sort of thing type built in... :mrgreen:

---- - ----
Mike Derrick | Studio One Professional 4.6, Win10 Pro 64, Intel Core i3, 8GB RAM, 1TB SSD, Focusrite 2i4
BandCamp
SoundCloud
User avatar
by frank.crow on Sun May 31, 2020 11:48 am
When I prep a mix to get erratic tracks under control (usually vocal tracks) I slice them up and normalize by event.

I’m not certain of your specific task but another option for me to get a more even Vocal & Bass tracks is:

Vocal Rider & Bass Rider plugins followed by Hornet Gain Stage plugin across everything.

Mac Mini (Late 2014)
Processor: 3.0 GHz Intel Core I7
Memory: 16 GB
Presonus. Studio One Pro V5
Presonus Quantum
Line 6. BassPOD XT Pro
Hardware DBX 160a
Hardware DBX 160XT
Art Pro Pro VLA II
WA76 1176 (clone)
EQP-KT Pultec (clone)
Softube. Console 1 MKII
Presonus. FaderPort & Faderport 8


"God's grace" :D
User avatar
by darrenporter1 on Sun May 31, 2020 4:08 pm
Normalizing is one of those hot topics that people wildly disagree on... my take... if it works for you OK go ahead and do it, but it can really mess with your gain-staging if you are using a lot of analog-modeled plugins. You could end up driving them way too hot. Running out of mix headroom happens a lot faster too.

Another "secret weapon" to EASILY tame wild tracks is Waves MV2. Used correctly it can save a LOT of time and effort.

You'll know you're an old rock-n-roller when the only spandex in your pants is in the elastic waistband. :D


Studio One Professional 4.6.1
i5-8400, 16GB RAM, 512 GB SSD, 2TB HD, Win10 Pro
Audient iD44, TASCAM US16x08, Presonus 1810
FaderPort 8, Console 1, JBL 306P Mk.II Monitors
UAD-2 PCIe DUO (two of them), v9.11

11 posts
Page 1 of 1

Who is online

Users browsing this forum: pawelhebda, Tacman7 and 40 guests