Quote:
on 3 of them I have guitar rig on each,
|
Woah, woah, woah... you can stop right there.
Guitar Rig (or any amplifier simulator) is an extreme CPU hog. Even just one instance will drain your computer of most of it's power, and you're using 3?
Most times it is recommended and preferable to "print" guitar tracks that use amp simulators.
Here's my typical method for using amp simulators, maybe you will find it useful. My personal preference is Amplitube, so I use that in my description. Just replace "Amplitube" with "Guitar Rig" whenever I mention it as the same procedure applies;
- Create two audio tracks
- label one Guitar DI, and label the other Guitar Print (labeling is at your discretion, just make sure you can tell the two tracks apart, and that they are somehow linked to each other name-wise).
- set the input of the track labeled Guitar DI to the input where you have your guitar plugged in
- set the output of the track labeled Guitar DI to an available bus
- set the input of the track labeled Guitar Print to be the same bus
- Insert Amplitube(or GR in your case) on the Guitar DI track
- record arm both tracks
- record your parts
- disable and hide the track labeled Guitar DI
Now you have an audio track with the printed output from amplitube (or GR in your case), and you still have the original DI from the guitar. If you ever want to change the tone, you activate the Guitar DI track, change the tone, record arm only the Guitar Print track, and press record. Then deactivate the DI track again, and you're all set. When the DI tracks are deactivated, so are the amplitube (or GR in your case) plugins on them, so they use no CPU, and you still have the printed tracks as audio tracks in the session.
Keep in mind that when using this method, you
must be in record mode to monitor your input, and you must be in the proper monitoring mode (Input Only) if you want to monitor the incoming signal continuously.
Also, which numeric versions of these plugins are you using? Are you sure they are up to date and compatible? If you could, please post a plugin list using the utility in the
Tech Support Folder, That help us identify if the plugin versions might be causing your problem.