NI Guitar Rig

[malcarney]

I'm using this with Mixcraft and having some latency issues.

Is Guitar rig more taxing on the system than other programs?

Do I need to record tracks dry and then add the effects at the end?

If I "freeze" a track, shouldn't it stop using processor space?

Thanks

[garageband]

s Guitar rig more taxing on the system than other programs?
Yes. Well, all guitar sims are pretty CPU-intensive.
Do I need to record tracks dry and then add the effects at the end?
You can do that. Or not.
If I "freeze" a track, shouldn't it stop using processor space?
Only if you deinstantiate the plug-in.

[fortyseven]

Originally Posted by malcarney

Is Guitar rig more taxing on the system than other programs?

I think generally its accepted that guitar rig can be quite a power hog. I personally cant run more than four or five instances at onve before my machine starts to complain.

Originally Posted by malcarney

Do I need to record tracks dry and then add the effects at the end?

As GB says, it depends on you. I assume that you refer to recording with guitar rig?

Originally Posted by malcarney

If I "freeze" a track, shouldn't it stop using processor space?

Basically freezing a track 'converts' it into a temporary wav. This is done to free up resources as effects and plugins can chew at your computers capabilities.

[malcarney]

Thanks guys.

So, if I've frozen all of the tracks except for a WAV version of the drums and the single guitar track that I'm working on, the frozen tracks should not be causing the latency issues, right?

[fortyseven]

Originally Posted by malcarney

Thanks guys.

So, if I've frozen all of the tracks except for a WAV version of the drums and the single guitar track that I'm working on, the frozen tracks should not be causing the latency issues, right?

IMO latency can only occur whilst recording. For instance, the delay time from when I strum a chord on my guitar to the time I hear it come out of my monitors is its latency.
What is your definition of latency?

[malcarney]

My definition is the same but I thought the other side of it was if you reduce the latency too much then you experience pops and stutters in the tracks. Is that not right?

Also, would you clarify: is freezing a track sufficient to free up the CPU? Or do I need to temporarily disable the plug-ins (specifically Guitar rig) as well?

[richiebee]

You will need to freeze the plugins too if you haven't. And remove them. It's the plugins that use up the most CPU power (especially Guitar Rig).


R.

[fortyseven]

Ok you're referring to buffer size. Sorry I was slightly confused as to what you were asking. My fault... anyhoo, If your CPU or disk usage climbs too high you are likely to experience audio 'buffer underruns' as clicks, pops or glitches. The audio buffer is a temporary store of data waiting to be sent to the soundcard that allows your DAW to even out momentary spikes in CPU load. If the Audio Buffer runs dry, because your CPU or hard-drive can't keep up with the 'real-time' audio stream, then your Soundcard will make those terrible pop, click or stutter noises. You can obviously adjust the size of the buffer according to the capabilities of your computer.

Also, would you clarify: is freezing a track sufficient to free up the CPU?

Normally freezing a track would free up some CPU, yes.

[malcarney]

I don't see where I have the capability to change the buffer size when using ASIO in Mixcraft. That only appears to be an option if I'm using the WAVE mode and monitoring through the sound card (as opposed to using the ASIO mode and monitoring through the Mobile Pre interface). Does that sound right or am I missing something?

[fortyseven]

Unfortunately I have never used Mixcraft so Im not sure why you cannot adjust your settings. In the DAWs that I've used I've always been able to change the buffer through some variety of ASIO control panel somewhere in the audio settings.
Did your interface not possibly install its own control panel when you installed the drivers?