What's new

IZotope Neutron

Hmm, well Neutron's input is clipping but its output isn't. You can see the orange "-0.1" that it has .1 dB of headroom.
Are you sure that there still isn't a volume envelope or the fader or you might have been nudged accidentally? (Or are you saying all is good now and the automation sorted it?)
 
Hey I already own ozone 7 and alloy 2. Can anyone tell me if the track assistant (i think that's what it's called) and the eq masking feature are really making their mixes better and FASTER? Who is using this all the time now?

I'm actually not using these features too much, however, i love Neutron's EQ section.
The EQ masking feature for sure is nice.
 
Hmm, well Neutron's input is clipping but its output isn't. You can see the orange "-0.1" that it has .1 dB of headroom.
Are you sure that there still isn't a volume envelope or the fader or you might have been nudged accidentally? (Or are you saying all is good now and the automation sorted it?)

If you take a look at the volume envelope on the master channel I'd added just under 3db of volume to it so it's this that's causing the input the clip. I thought that a limiter would limit and peaks and make everything come out the other end at a max of 0.1db. I think the problem is that I don't really understand limiters, true peaks or anything about what I'm doing with it! I need to go and find a dummies guide to limiters and read up a bit :) I did get it all sorted by addressing that +3db gain on the master buss and evening out the volume of the two sections using faders and velocity controls on the midi.
 
Automation is usually post insert, in other words happens after Neutron's limiter. So it seems like you're clipping Neutron's input before the plugin, and it sounds like you think automating the master fader is adjusting Neutron's input volume. Does that sound that right?

Signal flow typically happens in the is order: Audio/instrument->insert effects->fader. So the automation causes volume changes to happen after Neutron. Your master fader is the final volume leaving your DAW. Turning that up over 0 will always clip... (Channel faders typically work like this too.)

What you want is to send everything to a buss before you send to the master fader and turn the buss down and send that top the master out... (VCA faders work too but that's a little more complicated if you don't normally use them. I don't know Reaper at all so don't know how or if they use these...)

Ture Peaks are a little complex. I'll write back later tonight explaining what they are and why they change whether you see clipping or not...
 
@Mornats So 'True Peaks' are complicated. Theoretically they're not actually peaks (or clipping as we might normally call it). They're not peaks as far as your DAW or audio editing program is concerned, and they won't show up on your audio program's level meters as a result... They only show up on a plugin with True Peak metering...

So what in hell are they then?

True peaks (also commonly referred to as "Inter-Sample Peaks") are a byproduct of converting audio from a digtial signal into an analog signal, or converting audio between formats. So for example, every time you play a digital file from your computer on speakers there's the off chance you might hear clipping.

Why would that matter? The classic example is if you bought a CD that was mastered professionally. All should be well... it was produced to commercial standards after all.... But for some weird reason when you listened to it at home you heard occasional digital clicks or clipping.... Rare, but possible... Either way, whoever mastered this CD obviously had their head up their ass... You'd think, but it's more complicated...

The problem is as audio gets converted from digital 1s and 0s it has to be turned back into an analog waveform, using your soundcard or stereo's DAC converters. Unless played back with the same components playback system there's no guarantee that they won't interpolate the audio differently. Since you don't have the same signal path as that mastering engineer there's a TINY chance you'd experience this, but 99% time no one does... (IT'S RARE.)

So then why the hell does it matter if virtually no one ever experiences this? it's all theory right?

You would think so, and for a long time that was the scoop... But here's the catch... We live in the age of streaming audio... An example of this we have all heard, but may not have understood, would be listening to a youtube video and hearing clicks. Or listening to a soundcloud track and heard clipping... It shows up regularly now that we compress file sizes...

99% of the time CD/DVD or home entertainment playback are fine... The conversions work well and you don't hear it... When converting to a compressed format however, (like MP3 or AAC) that's a whole other beast... All of those theoretical 'True Peaks' rear their ugly head in a very audible way...

Converting audio to a lesser format means less dynamic range. The short version is as you throw away information you collapase dynamic range, and errors show up that we've all heard at some point listening online... So when you enable 'True Peak' limiting, or 'show true peaks' with an anlyzer you're looking at theoretical (but pretty accurate) peaks that will show up when compressing down to lower fidelity...

Showing true peaks is desigend to help you slide the output down to where you don't see Inter-Sample Peaks anymore... Limiting true peaks is designed to prevent them from happening in the first place...

So that's what Neutron's True Peak option is for. With it off you won't see peaks, and this generally alright for CDs... With it on you will see peaks, and this is important considering all audio winds up compressed online at some point....

As I said it's complex ;)

Best practice is to use Ozone 7 if you have it. If you don't, don't get freaked out... Use sensible headroom and bounced a few compressed files until it sounds good...

If you do have Ozone 7 and want some help post back or give me a holler....
 
Last edited:
Thank you so much for your awesome replies and taking the time to write some really good explanations. Your explanation of the signal chain answers the question of why my track was clipping perfectly.

All of my tracks get uploaded to Soundcloud although I actually listen to the 24 bit/44.1khz wavs on my Sony Xperia so I'd rarely hear any clicks from the compression on there. Good to know I can get around that now :)

I don't have Ozone but I'm looking at Ozone Elements when it comes out on Tuesday (got a heads-up about it from the Time+Space newsletter but nothing else online yet). I'm building up a library of reference tracks that I can use to master against.

Thanks again!
 
Thank you so much for your awesome replies and taking the time to write some really good explanations. Your explanation of the signal chain answers the question of why my track was clipping perfectly.

All of my tracks get uploaded to Soundcloud although I actually listen to the 24 bit/44.1khz wavs on my Sony Xperia so I'd rarely hear any clicks from the compression on there. Good to know I can get around that now :)

I don't have Ozone but I'm looking at Ozone Elements when it comes out on Tuesday (got a heads-up about it from the Time+Space newsletter but nothing else online yet). I'm building up a library of reference tracks that I can use to master against.

Thanks again!

You bet! :)

There are also a number of other great limiters that catch true peaks. The most popular option to Ozone being FabFilter Pro-L...

Didn't know about them releasing elements. Looking it up now seems like a good option at a great price...

Best of luck and enjoy the holidays!
 
Top Bottom