Revision as of 12:36, 6 January 2016

Axe-Fx II USB driver for Windows and Mac

USB drivers for Mac and Windows are required and available for download here. If the USB driver is not installed, utilities such as Axe-Edit, Fractal-Bot and Cab-Lab won't recognize the Axe-Fx II.
When using the USB interface, there's no need for an additional audio interface.
An external audio interface will be required when connecting the analog Axe-Fx II outputs to a computer (not using USB).
A MIDI interface is not required to connect the Axe-Fx II to a computer. The Axe-Fx II itself operates as an USB-to-MIDI adapter. MIDI interfaces can still be used, and editing through a MIDI interface also is still possible.
Cliff: "The driver that we supply for OS-X computers is NOT an audio driver. It is a firmware installer. The Axe-Fx II uses a "soft" USB controller. It gets its code from the host computer. When you turn the Axe-Fx II on it requests firmware from the host. This is superior to a hard-coded controller in that updates merely require a new host image rather than reflashing the controller."

The Axe-Fx II can be used as an USB-to-MIDI interface to update the firmware on the MFC-101, using Fractal-Bot or a MIDI librarian. Walkthrough.
Cliff: "The USB Adapter feature was added for simple USB-to-MIDI functionality, specifically firmware updates for the MFC-101. It is a low priority task since audio processing is the Axe-Fx's primary usage. Latency is not guaranteed. It is not intended as anything more than a no-frills, simple MIDI adapter for non-critical tasks." source

Creating an USB connection increases CPU utilization. This is by design. If a preset uses much CPU, you may run into CPU overload problems when connecting the Axe-Fx II to a computer through USB. source and source

USB features.png

High-pitched noise may be caused by a ground loop.
- Cliff: "The USB spec calls for grounding the cable at both ends (mistake). This can create an USB ground loop. Make sure everything is plugged into the same outlet strip." source
When experiencing problems such as dropped connections or an Axe-Fx II which freezes after connecting USB, always replace the USB cable first. Example
Cliff: "An occasional flicker when hooked up to USB is not unusual. This is due to the screen redraw being interrupted by the USB thread." source
Handy tip for resolving audio dropouts in your Windows DAW

@@ Line 10: / Line 10: @@
 * Cliff: "The USB Adapter feature was added for simple USB-to-MIDI functionality, specifically firmware updates for the MFC-101. It is a low priority task since audio processing is the Axe-Fx's primary usage. Latency is not guaranteed. It is not intended as anything more than a no-frills, simple MIDI adapter for non-critical tasks." [http://forum.fractalaudio.com/axe-fx-ii-discussion/90520-usb-adapter-mode-roland-td-20-%3D-evil-midi-dropout-hell.html#post1090552 source]
-=USB connection and CPU usage=
+=USB and CPU usage=
 * Creating an USB connection increases CPU utilization. This is by design. If a preset uses much CPU, you may run into CPU overload problems when connecting the Axe-Fx II to a computer through USB. [http://forum.fractalaudio.com/axe-fx-ii-discussion/41013-usb-connection-raises-preset-cpu-utilization-5%25.html#post551466 source] and [http://forum.fractalaudio.com/axe-fx-ii-bugs/40246-global-cab-sim-cpu.html#post573202 source]