Normalize plugin buggy behavior. PT 10

[JWalkerPostAudio]

When using the normalize plugin in PT10 on some dialogue tracks I've been getting some pretty inconsistent results when processing peak volume. Some clips have been rendering much lower in volume then what I've set the Normalize level to in which case I have to render the clip multiple times before it completely normalizes.

Also, for the clips that fail to normalize within the first render, if you open the Gain plugin and click on find level, the results will be off there as well, reading much louder then they actually are.

Is it possible that Pro Tools 10 isn't recognizing gain correctly on regions?

This is occurring on clips that have no volume automation or clip gain.

Can anyone else reproduce/confirm this as well?

-Justin

[jesse p]

Not seeing that here.

Why not use render clip gain?

[Brian in Charlotte]

I'm having the exact same issue. Sometimes it will perform the peak normalization and other times it won't. There have been moments when I click Render and it only normalizes slightly...if I keep hitting Render, it will incrementally go up - maybe a dB or two each time. I've experienced the same thing with Gain. If I check to see what the peak level of a clip is, it will sometimes not read it, then other times it will. VERY interruptive to my workflow.

[Brian in Charlotte]

The last two sessions I did were plagued with this nonsense - very frustrating. I sure hope they get this fixed right away! I've done all the "trashing prefs" etc., nothing has helped.

[Trent Richmond]

This smells of the same problem people are experiencing with izotope Rx. The thread can be seen here.

I would try making sure both "Whole File" is disabled and you're not setting a handle length when you process your audio. Basically making it work like in previous versions of PT.

It seems to me that PT is looking at more of your audio files than what you have in your timeline (selection plus handle length) and basing its calculations on that.

Worth a shot anyway.

[Brian in Charlotte]

Boy, what a great thought Trent - it truly does seem like it's looking at more than just the file I'm on. I'll check that right away. Whole Files is disabled. I just turned off HANDLES in the preferences....maybe this will help. I did a test and it worked correctly, but I'll need to give it some more testing. I'll make a note to post back what I find. Thanks again for the great idea!

[FilterDecay]

Having issues with Serato pitch n time pro as well

[Frank Kruse]

Originally Posted by Brian in Charlotte

Boy, what a great thought Trent - it truly does seem like it's looking at more than just the file I'm on. I'll check that right away. Whole Files is disabled. I just turned off HANDLES in the preferences....maybe this will help. I did a test and it worked correctly, but I'll need to give it some more testing. I'll make a note to post back what I find. Thanks again for the great idea!

I think this is not a bug when we´re talking about normalizing. The plugin HAS to consider the level in the handles otherwise the data in the handles will be clipped even if the selected clip is very low.
So when you select a clip with rather low level but in the handles there is full scale sound the plugin can not apply any gain change because otherwise the handles would be clipped.

There is no real way around this other than turning off the handle. If you have handles turned on the plugin will have to take audio outside your selection into consideration before applying the effect. SO it depends on the type of plugin you´re applying if handles make sense of not.

Frank.

[Brian in Charlotte]

I have absolutely HAD IT with this issue. It has been such a pain. I continue to have Normalize not working intermittently. I even turned Handles OFF and it works sometimes and other times it does not....same with using Gain to determine the Peak level of a clip. Frustrating is not even the right word.

[tj_davies]

For me the normalize audiosuite has never worked properly; especially not, when batch processing in the "region by region mode"

So nothing new here.
Sorry,
Timothy