Sonitus EQ peak dB boost. Why?

Look at your level meter. See the red dot. You have gone over. 
You should aim for just a tad under 0db. 
And myself I'd be using a compressor as that track looks like it's peaking a LOT. 
Hi pass is always a good Idea but if there was no low end content to begin with it won't change anything. 
Most mixers and pre amps have a hi pass filter so the signal was probably already processed. 
 
Once again I hate repeating myself but a program like Wave lab is easier to work with for wave editing because that's it's design purpose. Sonar is the worlds greatest multi track recorder but I use Wave lab for stereo editing. There are many other wave editors and some are even free like http://www.wavosaur.com/
Not saying you can't do it in Sonar, but without the analyzing tools your working blind. 
 
Example load the file. 
Check the peak level with the normalize tool. 
If the file has headroom say it's shows -4.5db then normalize it to -.05 db. 
If it say's 0 then it may be OK, but what about overs? 
This is where the Global Analyzer is indispensable because it will point them out for you. 
It will also check the average RMS level which to me is most important of all.
Average is a much different reading than peak. A file can have a reading of 0 db peak but it's average RMS level will be anywhere from 8 to 20 db. 8 db being about as loud as it gets, 20db might be a classical piece.  
If its RMS average is around 14 - 16 db it will be in the ball park on most playback systems. 
If it still shows 18-20 average RMS it's might be too quiet and you then proceed to use the Loudness Maximizer or your favorite limiter to kick it up 2 or 4 db,, no more if you can help it. 
If the file is that uneven in volume then there's some manual editing to do first.
That's chapter 2. 
 
If the file really must be output from Sonar then a great and easy solution is the LP64 Multi band compressor on the Master buss. It works pretty flawlessly to catch overs because it is a "look ahead" plug in. But that track would need to be turned down first it's over and that is not good. You could put a compressor in the tracks bin with a super fast attack, but I like my tracks to be under control without one. You can simply turn down the volume or gain. 

OK I see what your saying. I guess the only answer would be the Sontitus EQ is buggy and is adding a little gain even when set on 0. Would be easy to test this. 

Yes me too. so I'd be interested to see what happens if we plunk it on a test tone set at a known db level. 
Only thing I could see happening is if it was in parallel it would add a doubled signal path. But in series this should not happen.
 
One would assume that if it's output is set at 0 that it would not go over that unless more than 0 was input.
 

My thinking too. As normally I would never have any of my tracks that close to zero anyhow. But it is good to be aware that if you add that particular EQ you can expect a jump in level.

Change the slope of the hp/lp filters and see if that changes the level back close to 0db. The steeper the slope of the filter, the more the resonant spikes.

Grem
Change the slope if the hp/lp filters and see if that changes the level back close to 0db. The steeper the slope of the filter, the more the resonant spikes.

That sounds interesting, they are steep slopes. What is a "resonant spike?"

scook
The client has already started the finalizing process by normalizing the file or recorded at too high a level. There is no headroom to do anything with the file. If the client will not send the raw file or reduce the recording level your options are limited.
 

Indeed and agreed!
 
But you cain't always git what you wahnt :)
 
He just sent me a new file this morning and I will meet him on Thursday for the first time and see if I can better understand his process. Sometimes we got the play the hand that is dealt.

Cactus Music
 
My procedure for files I record live to my Tascam DR 40 involve normalizing in the first step so I can see and hear better if the file was recorded real low. This is pretty common as you certainly are better off recording low than to take a chance on an over. But I Normalize to -4 in that first stage I would not recommend going to 0 at that stage of editing.  

Excellent advice to carry with me to the client! Thanks!

When you meet with the client, ask him to actually show you how he edits the files. If you just ask for a description, he may leave something out that he doesn't think is relevant.
 
My guess is he's using the normalize function in his audio editor, thinking he's doing you a favor. If so, explain to him that you must leave some headroom any time a file is going to have further processing done to it.
 
Don't worry about hurting his feelings by criticizing his methods. Making him aware of that will greatly help your future collaborations, and make you look like a technical guru worthy of the fees he pays you.

bitflipper
 
My guess is he's using the normalize function in his audio editor, thinking he's doing you a favor. If so, explain to him that you must leave some headroom any time a file is going to have further processing done to it.

I think the issue is he does so much work of this type and most of it is perfectly fine for his purposes. It's only after a fashion that he realizes some of the files are not up to snuff. He is 69 (slightly older than me) and loathe to go back and redo things. That being said he is a very nice gentleman and founder of our local baseball team and top brewery!
 
But your kind suggestions are well taken. I'm looking forward to seeing him on Thursday. If a grant he is working on comes through, there will be much for me to do :)

The Q setting ( 1.5 ) will impart a resonant peak at the frequency setting. Set the Q to 1.
 
edit: sorry didn't read the whole thread  - already answered

bitflipper

He is 69 (slightly older than me)

Tell him the kids - the ones who wear their pants around their knees, baseball caps sideways, gaudy jewelry, hooded sweatshirts on 90-degree days and spell "beats" with a "z" - are all down with 0 dB.
 

I will do that, I'm on my way now:)