JazzMac251
Inspired
Hi all. I'm trying to get the most out of my AxeFX 2 setup. I was trying to figure out how I could achieve these things with my setup:
1) Use my Axe2 to interface with my DAW (Cubase 5) so I can easily record.
2) Interface the Axe2 with my computer via USB so I can still use Axe Edit to manipulate patches.
3) Use my PC speakers to monitor (I know, I'll get some powered monitors when I get a chance - my current 2.1 system isn't too bad, though), and do this with as little latency as possible
4) Use my Axe2 + PC as a practice amp when the Axe is home (i.e. not being used for digital-only gigs)
5) Do all of this with a minimum of cable-switching and fiddling with system properties
Here's the solution I came up with.
1) I interface the Axe with the PC via USB. This satisfies #1 and #2
2) To address the input/output latency issue, I installed ASIO4all, set it up to use the Axe as the input device, plugged Output 1 of the axe into the rear 1/4in INPUTS of a Focusrite Saffire Pro14 firewire audio interface I already had, plugged my PC speakers into the Focusrite box's monitoring Outputs, and set ASIO4all's Output device as the Focusrite box. The Saffire sums for monitoring all inputs and outputs in the box itself (without involving the PC directly), and this provides me with both PC audio AND 0-latency monitoring from the AxeFX. The recording latency is down to 2.6ms on both the output and input sides. This achieves #3 and #4.
3) Why not just use the Axe as a soundcard? Because in that setup the Axe has to either be on all the time to route PC audio, or I have to go through the hassle of resetting my default audio devices, crawling under my desk to get to my PC speakers and plugging them into the Axe whenever I want to record or practice. That is impractical. With this setup, all I have to do to record or practice is turn on my Axe. Much better!
Here's the problem:
I'm getting some wicked ground buzzing with the Axe's outs plugged into the Focusrite's ins. It's only on the Focusrite side, too. My recordings are dead quiet. Do I just need to get some Humbuster cables or what? What could be causing this issue?
1) Use my Axe2 to interface with my DAW (Cubase 5) so I can easily record.
2) Interface the Axe2 with my computer via USB so I can still use Axe Edit to manipulate patches.
3) Use my PC speakers to monitor (I know, I'll get some powered monitors when I get a chance - my current 2.1 system isn't too bad, though), and do this with as little latency as possible
4) Use my Axe2 + PC as a practice amp when the Axe is home (i.e. not being used for digital-only gigs)
5) Do all of this with a minimum of cable-switching and fiddling with system properties
Here's the solution I came up with.
1) I interface the Axe with the PC via USB. This satisfies #1 and #2
2) To address the input/output latency issue, I installed ASIO4all, set it up to use the Axe as the input device, plugged Output 1 of the axe into the rear 1/4in INPUTS of a Focusrite Saffire Pro14 firewire audio interface I already had, plugged my PC speakers into the Focusrite box's monitoring Outputs, and set ASIO4all's Output device as the Focusrite box. The Saffire sums for monitoring all inputs and outputs in the box itself (without involving the PC directly), and this provides me with both PC audio AND 0-latency monitoring from the AxeFX. The recording latency is down to 2.6ms on both the output and input sides. This achieves #3 and #4.
3) Why not just use the Axe as a soundcard? Because in that setup the Axe has to either be on all the time to route PC audio, or I have to go through the hassle of resetting my default audio devices, crawling under my desk to get to my PC speakers and plugging them into the Axe whenever I want to record or practice. That is impractical. With this setup, all I have to do to record or practice is turn on my Axe. Much better!
Here's the problem:
I'm getting some wicked ground buzzing with the Axe's outs plugged into the Focusrite's ins. It's only on the Focusrite side, too. My recordings are dead quiet. Do I just need to get some Humbuster cables or what? What could be causing this issue?