I have a project and I am trying to add reverb to a guitar bus.
 
As soon as I add ANY reverb effect (like Breverb or the Sonitus one),
I get popping and or crashing immediately.
 
PROCHANNEL:
I have prochannel settings active on both the individual tracks and the bus (tube, console, EQ).
If I turn off tube and console on ONE of the signals (either the guitar tracks or the bus) it works
fine.
 
Why is this happening?
 
Is there a workaround? - Maybe turn them off on the track and turn up the effect in the bus?
 
My specs:
16 gig ram. 2 CPU (8 core) system.
Audiophile 192 - 192k at 48.
Project on 192 at 48.
 
 
 

Shouldn't be a problem. Maybe some interaction with another 3rd-party plug-in? See if you can reproduce it in a minimal project started from SONAR's Normal template. If not, it's something project-specific. But if you can reproduce it, there might be some interoperability problem with hardware, drivers, or some other software on your system.
 
 

Sounds like the Mixing Latency needs adjustment in Preferences.
 
Try adjusting it up and down until the popping stops.
 
If your using ASIO and/or an outboard audio interface, it may have it's own utility for that.
 
Steve

Yeah, sounds like a some resource-Bogarting is going on and the latency cannot keep up. Increase your latency buffer size and test again.

Musicalguit
I have a project and I am trying to add reverb to a guitar bus.
 
As soon as I add ANY reverb effect (like Breverb or the Sonitus one),
I get popping and or crashing immediately.
 
PROCHANNEL:
I have prochannel settings active on both the individual tracks and the bus (tube, console, EQ).
If I turn off tube and console on ONE of the signals (either the guitar tracks or the bus) it works
fine.
 
Why is this happening?
 
Is there a workaround? - Maybe turn them off on the track and turn up the effect in the bus?
 
My specs:
16 gig ram. 2 CPU (8 core) system.
Audiophile 192 - 192k at 48.
Project on 192 at 48.
 
 
 

 
You might try recording at a lower sample rate than 192 if I'm reading your post correctly.

Use 24 bit 44.1K. 

"Project on 192 at 48"
 
Bit depth 48? Very uncommon IMO. There's no reason IMO to have samplerate set higher than 24 bits.
Is there a particular reason  to use such a high sample rate - 192 kHz? You spend huge amounts of HDD space gaining practically nothing.
I don't know about Prochannel and Breverb, but AFAIK there are lots of plugins which can not operate with such settings, so you might bump into unpleasant surprises in the long run - wanting to add an FX or soft synth which can't be used with those settings. And you can not change them just like that in the middle of a project.

I know people who are truly in the music industry (not hobbyists) and the pros ALWAYS use 192.
 
Resources:
I already have my card set on the maximum buffer size, and the playback buffer (in sonar) to the max also. I'm not just hitting the resource limit because as long as I don't do that specific combination everthing is fine (I can add as many prochannel effects and reverb as I like). - To as many channels as I like.
 
No Idea why it's happening...
 
I will try to replicate it in another slim project and also see if I can bounce down with it. 
For now I need to get on with my recording so won't respond again unless anyone knows exactly why that's happening (or what can be done).
 
Thanks. 
 
 
 

My specs:
16 gig ram. 2 CPU (8 core) system.
Audiophile 192 - 192k at 48.
Project on 192 at 48.

I can use both on my system. You need to look at your sample rate and bit depth. I never heard of a bit depth of 48 and 192kHz is OVERKILL. The only thing you achieve at 192kHz are using more hard drive space and using more CPU and resources.
 
There are no positives for running at 192kHz. Run at 88kHz, 48kHZ or 44.1kHz and always use 24bit, as this is the highest non floating bit depth you can get.
 
CJ

Musicalguit
I know people who are truly in the music industry (not hobbyists) and the pros ALWAYS use 192.
 
Thanks. 
 

No they don't.