Fractal Audio Wiki - User contributions [en]

USB

2016-08-03T15:47:51Z

Volt:

=Axe-Fx II USB driver for Windows and Mac=
* USB drivers for Mac and Windows are required and [http://www.fractalaudio.com/drivers.php 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."

=Using the Axe-Fx II as an interface to update the MFC-101 firmware=
* 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. [http://wiki.fractalaudio.com/index.php?title=Yeks_MFC-101_How-Tos_page#How_to_upgrade_its_firmware 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." [http://forum.fractalaudio.com/axe-fx-ii-discussion/90520-usb-adapter-mode-roland-td-20-%3D-evil-midi-dropout-hell.html#post1090552 source]

=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]

=Axe-Fx II and USB Audio=
* [[Digital audio (USB, SPDIF, AES)]].

[[image:USB features.png|link=]]

=Axe-Fx II and USB troubleshooting=
* 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." [http://forum.fractalaudio.com/axe-fx-ii/38038-usb-noise.html#post520349 source]
* When experiencing problems such as dropped connections or an Axe-Fx II which freezes after connecting USB, always replace the USB cable first. [http://forum.fractalaudio.com/axe-fx-ii-bugs/68591-v10-02-hangs-3.html#post849205 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." [http://forum.fractalaudio.com/axe-fx-ii-discussion/54367-brand-new-axe-ii-suffers-screen-flickering.html#post689669 source]
* [http://forum.fractalaudio.com/lounge/65880-very-useful-resolving-audio-dropouts-your-daw.html Handy tip for resolving audio dropouts in your Windows DAW]

=Axe-Fx II and Linux=
* The Axe-Fx II works as an audio and MIDI interface just as on Windows or OSX, although Linux is [http://forum.fractalaudio.com/threads/linux-support.108934/#post-1303324 not supported officially].
* As explained by Cliff (see bullet 5 of the section [[Axe-Fx_II_and_USB#Axe-Fx_II_USB_driver_for_Windows_and_Mac | "Axe-Fx II USB driver for Windows and Mac"]]) the Axe-Fx II uses a "soft" USB controller. This controller needs to be loaded with its ''own'' firmware. The way to do this on Linux is using a tool called [http://linux.die.net/man/8/fxload "fxload"] executed by an appropriate UDEV rule. There is a BASH script available which generates and installs such a UDEV rule. A package containing the script and the mentioned USB controller firmware file [http://archive.axefx.fr/Drivers is available for download here]. The additionally required tool "fxload" is typically not preinstalled by current Linux distributions but needs to be installed by the user.
* After the USB controller got loaded with its firmware the Axe-Fx II will be recognized as a USB soundcard. It will be reported as a USB device with Vendor ID 2466 and Product ID 8003. For a named output adequate entries for Fractal Audio Systems and the Axe-Fx II need to be added to a file called "usb.ids". [http://forum.fractalaudio.com/threads/axe-fx-ii-and-linux-again.79061/page-5#post-1315786 source]
* Since the Axe-Fx II is an Audio Class 2.0 compliant device no audio driver is required. (For systems with a kernel older than 3.10 read further instructions [http://forum.fractalaudio.com/threads/axe-fx-ii-and-linux-again.79061/ here]).
* Threads about using Axe-Fx II with Linux:
** [http://forum.fractalaudio.com/axe-fx-ii-discussion/79061-axe-fx-ii-linux-again.html Thread.]
** [http://forum.fractalaudio.com/threads/linux-support.108934/#post-1303324 Thread.]

[[category:Axe-Fx]]
[[category:Connecting]]

USB

2012-11-05T08:24:01Z

Volt:

=Manual=

{{0 Disclaimer}}

{{2.3 Computer Integration}}

{{2.3.1 Minimum requirements}}

{{2.3.2 Software Installation}}

{{2.3.3 Capabilities}}

----

{{3.4.9 Computer Audio Interface}}

----

===Diagram: USB features===

[[image:USBFeatures.png|800px]]

=User contributions=

==USB driver==
* Drivers for Mac and PC which add USB connectivity are [http://www.fractalaudio.com/support.php#drivers available for download here.]
* It's not an USB driver in the conventional sense. It's a daemon that waits for the Axe-Fx USB port to appear and then downloads software to the port to make it USB class-compliant. The plist-file is located here: /Library/LaunchDaemons/com.fractalaudio.axefx2load.plist.
* The USB driver control panel should not be used for configuration. Ignore error messages when clicking on the controls. [http://forum.fractalaudio.com/axe-fx-ii/38336-trouble-usb-audio.html#post524487 Source1] [http://forum.fractalaudio.com/axe-fx-ii/38107-axe-fx-ii-firmware-version-1-02-a-3.html#post521432 Source3]
* The names of the Axe-Fx channels on the computer are assigned by the computer, not by the Axe-Fx. [http://forum.fractalaudio.com/axe-fx-ii-bugs/41375-audio-devices-channel-tags-os-x-lion.html#post554574 Source]
* If using AxeEdit, you will need to go to Settings > MIDI Settings and select the Midi In and Out ports for it to use. They are named something like "AXE-FX II MIDI In" and "AXE-FX II MIDI Out". The Axe-II must be connected via USB and powered up for the MIDI ports to appear in the settings list.

==MIDI interface and audio interface not required==
* When using the USB interface, there's no need for an additional audio interface. An audio interface is still required when connecting the ''analog'' Axe-Fx II outputs to a computer instead of through USB.
* A MIDI interface is not required to connect the Axe-Fx II to a computer. USB suffices (MIDI-over-USB). The Axe-Fx II itself operates as an USB-to-MIDI adapter. MIDI interfaces can still be used and editing with the help of a MIDI interface is also still possible.

==Using the Axe-Fx II to update the MFC-101 firmware==
* The Axe-Fx II can be used as a USB-to-MIDI interface to update the firmware on the MFC-101. [http://wiki.fractalaudio.com/index.php?title=Yeks_MFC-101_How-Tos_page#How_to_upgrade_its_firmware Here's a walkthrough]

==USB connection increases CPU utilization==
* 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 Source1] [http://forum.fractalaudio.com/axe-fx-ii-bugs/40246-global-cab-sim-cpu.html#post573202 Source2]

==Handling latency==
* When monitoring audio via the Axe-Fx II, latency is none.
* When monitoring the audio signal via the computer's output, the latency depends on the computer.

==Solving USB noise==
* 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." [http://forum.fractalaudio.com/axe-fx-ii/38038-usb-noise.html#post520349 Source]

==Disabling the Axe-Fx output signal when monitoring through a DAW==
* When the Axe-Fx is connected to a DAW through USB, you're using monitors connected to the Axe-Fx, and you're recording, you may want to monitor just the DAW signal, not the signal from the Axe-Fx. To accomplish this, turn down the preset level in Axe-Edit. Or set USB/Digi Out Source to Out 2, then route guitar to FXL only. [http://forum.fractalaudio.com/axe-fx-ii-discussion/44923-avoid-double-signal-phasey-sound-when-using-daw-2.html Source]

==USB storage media==
* The Axe-Fx II cannot connect to an USB stick. [http://forum.fractalaudio.com/axe-fx-ii-discussion/35997-axe-fx-ii-technical-questions-thread-34.html#post491613 Source]

==Screen flicker==
* 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." [http://forum.fractalaudio.com/axe-fx-ii-discussion/54367-brand-new-axe-ii-suffers-screen-flickering.html#post689669 Source]

==Linux==
* Linux is not officially supported by FAS. Nevertheless all USB features can be obtained under Linux, too.
* The Axe-Fx II is fitted with a Cypress USB chip (FX-LP2) which needs to be loaded with firmware (this is not the Axe-Fx II firmware but a dedicated bootloader) to achieve its functionality.
* The firmware hex file can be extracted from the Mac OSX driver package (Axe-Fx_II_USB_Driver_Setup.dmg from [http://www.fractalaudio.com/support]).
* With fxload ([http://linux.die.net/man/8/fxload]) you could upload the USB firmware manually, which would be pretty inconvenient. But with a proper udev rule executing fxload, it is also possible to upload the USB firmware file automatically to the Axe-Fx II.
* You may write your own udev rule or use the already existing bash script ([http://forum.fractalaudio.com/axe-fx-ii-discussion/59064-axe-fx-linux.html#post737408]) to setup a Linux system to recognize the Axe-Fx II each time it is connected to a USB port and then upload the USB firmware.
* After executing the script or applying your own udev rule and then switching on or rebooting the connected Axe-Fx II lsusb will report a new USB device with VID 2466 for Fractal Audio Systems and PID 8003 for the Axe-Fx II. If you like to have a named output you can add adequate entries to the file called usb.ids which is usually located under /usr/share.
* Linux recognizes the Axe-Fx II as a generic USB audio and midi device. As such it is handled by the snd-usb-audio respectively the snd-usbmidi-lib module. Unfortunately only MIDI over USB works out of the box but not the USB audio interface. The latter needs some handwork:
* Since the Axe-Fx II (at the moment) neither responds to set sample rate requests nor get sample rate requests, it is necessary to patch the files clock.c and format.c (located under /usr/src/linux-kernelversion/sound/usb/) as described here [http://forum.fractalaudio.com/axe-fx-ii-discussion/44765-anybody-tried-usb-interface-linux-yet-3.html#post651754]. After applying the patch the snd-usb-audio module has to be recompiled. Once the previous version of this module has been removed from the kernel (rmmod) and the newly built module has been added to the kernel (modprobe), playback and capturing devices of the Axe-Fx II appear and are functional.

[[category:About the Axe-Fx II]]
[[category:Axe-Edit]]
[[category:Connecting to a computer or digital device]]
[[category:System and firmware]]

USB

2012-04-27T13:42:57Z

Volt:

=Manual=

{{0 Disclaimer}}

{{2.3 Computer Integration}}

{{2.3.1 Minimum requirements}}

{{2.3.2 Software Installation}}

{{2.3.3 Capabilities}}

----

{{3.4.9 Computer Audio Interface}}

----

===Diagram: USB features===

[[image:USBFeatures.png|800px]]

=User contributions=

==Driver for USB connectivity==
* Drivers for Mac and PC which add USB connectivity are [http://www.fractalaudio.com/support.php#drivers available for download here.]
* It's not an driver in the conventional sense. It's a daemon that waits for the Axe-Fx USB port to appear and then downloads software to the port to make it USB class-compliant. The plist-file is located here: /Library/LaunchDaemons/com.fractalaudio.axefx2load.plist.
* The USB driver control panel should not be used for configuration. Ignore error messages when clicking on the controls. [http://forum.fractalaudio.com/axe-fx-ii/38336-trouble-usb-audio.html#post524487 Source1] [http://forum.fractalaudio.com/axe-fx-ii/38107-axe-fx-ii-firmware-version-1-02-a-3.html#post521432 Source3]
* The names of the Axe-Fx channels on the computer are assigned by the computer, not by the Axe-Fx. [http://forum.fractalaudio.com/axe-fx-ii-bugs/41375-audio-devices-channel-tags-os-x-lion.html#post554574 Source]
* If using AxeEdit, you will need to go to Settings > MIDI Settings and select the Midi In and Out ports for it to use. They are named something like "AXE-FX II MIDI In" and "AXE-FX II MIDI Out". The Axe-II must be connected via USB and powered up for the MIDI ports to appear in the settings list.

==No MIDI interface or audio interface required==
* When using the USB interface, there's no need for an additional audio interface. An audio interface is still required when connecting the analog Axe-Fx II outputs to a computer instead of through USB.
* A MIDI interface is also not required to connect the Axe-Fx II to a computer. USB suffices (MIDI-over-USB). The Axe-Fx II itself is an USB-to-MIDI adapter. MIDI interfaces can still be used though and editing with the help of a MIDI interface is also still possible.

==Using the Axe-Fx II to update the MFC-101 firmware==
The Axe-Fx II can be used as a USB-to-MIDI interface to update the firmware on the MFC-101. [http://wiki.fractalaudio.com/index.php?title=Yeks_MFC-101_How-Tos_page More information]

==USB connection increases CPU utilization==
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 Source1] [http://forum.fractalaudio.com/axe-fx-ii-bugs/40246-global-cab-sim-cpu.html#post573202 Source2]

==Latency==
When monitoring audio via the Axe-Fx II, latency is none.
When monitoring the audio signal via the computer's output, the latency depends on the computer. [http://forum.fractalaudio.com/axe-fx-ii/38038-usb-noise.html#post520349 Source]

==Solving USB noise==
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." [http://forum.fractalaudio.com/axe-fx-ii/38038-usb-noise.html#post520349 Source]

==Disabling the Axe-Fx output signal when monitoring through a DAW==
When the Axe-Fx is connected to a DAW through USB, you're using monitors connected to the Axe-Fx, and you're recording, you may want to monitor just the DAW signal, not the signal from the Axe-Fx.
To accomplish this, turn down the preset level in Axe-Edit. Or set USB/Digi Out Source to Out 2, then route guitar to FXL only. [http://forum.fractalaudio.com/axe-fx-ii-discussion/44923-avoid-double-signal-phasey-sound-when-using-daw-2.html Source]

==USB storage media==
The Axe-Fx II cannot connect to an USB stick. [http://forum.fractalaudio.com/axe-fx-ii/35997-axe-fx-ii-technical-questions-thread-34.html#post491613 Source]

==Linux==
Linux is not officially supported by FAS. Nevertheless all USB features as described above ([[USB_connectivity#Diagram:_USB_features]]) can be obtained under Linux, too.

The Axe-Fx II is fitted with a Cypress USB chip (FX-LP2) which needs to be loaded with firmware (this is not the Axe-Fx II firmware you can download from Fractals support page but a dedicated bootloader) to achieve its functionality.

The firmware hex file can be extracted from the Mac OSX driver package (Axe-Fx_II_USB_Driver_Setup.dmg from [http://www.fractalaudio.com/support]).

With fxload ([http://linux.die.net/man/8/fxload]) you could upload the USB firmware manually, which would be pretty inconvenient. But with a proper udev rule executing fxload, it is also possible to upload the USB firmware file automatically to the Axe-Fx II.

You may write your own udev rule or use the already existing bash script ([http://forum.fractalaudio.com/axe-fx-ii-discussion/44765-anybody-tried-usb-interface-linux-yet.html#post593209]) to setup a Linux system to recognize the Axe-Fx II each time it is connected to a USB port and then upload the USB firmware.

After executing the script or applying your own udev rule and then switching on or rebooting the
connected Axe-Fx II lsusb will report a new USB device with VID 2466 for Fractal Audio Systems and PID 8003 for the Axe-Fx II. If you like to have a named output you can add adequate entries to the file called usb.ids which is usually located under /usr/share.

Linux recognizes the Axe-Fx II as a generic USB audio and midi device. As such it is handled by the snd-usb-audio respectively the snd-usbmidi-lib module. Unfortunately only MIDI over USB works out of the box but not the USB audio interface. The latter needs some handwork:

Since the Axe-Fx II (at the moment) neither responds to set sample rate requests nor get sample rate requests, it is necessary to patch the files clock.c and format.c (located under /usr/src/linux-kernelversion/sound/usb/) as described here [http://forum.fractalaudio.com/axe-fx-ii-discussion/44765-anybody-tried-usb-interface-linux-yet-3.html#post651754]. After applying the patch the snd-usb-audio module has to be recompiled. Once the previous version of this module has been removed from the kernel (rmmod) and the newly built module has been added to the kernel (modprobe), playback and capturing devices of the Axe-Fx II appear and are functional.

[[category:About the Axe-Fx II]]
[[category:Axe-Edit]]
[[category:Connecting to a computer or digital device]]
[[category:System and firmware]]

USB

2012-04-18T18:50:29Z

Volt:

=Manual=

{{0 Disclaimer}}

{{2.3 Computer Integration}}

{{2.3.1 Minimum requirements}}

{{2.3.2 Software Installation}}

{{2.3.3 Capabilities}}

----

{{3.4.9 Computer Audio Interface}}

----

===Diagram: USB features===

[[image:USBFeatures.png|800px]]

=User contributions=

==Driver for USB connectivity==
* Drivers for Mac and PC which add USB connectivity are [http://www.fractalaudio.com/support.php#drivers available for download here.]
* It's not an driver in the conventional sense. It's a daemon that waits for the Axe-Fx USB port to appear and then downloads software to the port to make it USB class-compliant. The plist-file is located here: /Library/LaunchDaemons/com.fractalaudio.axefx2load.plist.
* The USB driver control panel should not be used for configuration. Ignore error messages when clicking on the controls. [http://forum.fractalaudio.com/axe-fx-ii/38336-trouble-usb-audio.html#post524487 Source1] [http://forum.fractalaudio.com/axe-fx-ii/38107-axe-fx-ii-firmware-version-1-02-a-3.html#post521432 Source3]
* The names of the Axe-Fx channels on the computer are assigned by the computer, not by the Axe-Fx. [http://forum.fractalaudio.com/axe-fx-ii-bugs/41375-audio-devices-channel-tags-os-x-lion.html#post554574 Source]
* If using AxeEdit, you will need to go to Settings > MIDI Settings and select the Midi In and Out ports for it to use. They are named something like "AXE-FX II MIDI In" and "AXE-FX II MIDI Out". The Axe-II must be connected via USB and powered up for the MIDI ports to appear in the settings list.

==No MIDI interface or audio interface required==
* When using the USB interface, there's no need for an additional audio interface. An audio interface is still required when connecting the analog Axe-Fx II outputs to a computer instead of through USB.
* A MIDI interface is also not required to connect the Axe-Fx II to a computer. USB suffices (MIDI-over-USB). The Axe-Fx II itself is an USB-to-MIDI adapter. MIDI interfaces can still be used though and editing with the help of a MIDI interface is also still possible.

==Using the Axe-Fx II to update the MFC-101 firmware==
The Axe-Fx II can be used as a USB-to-MIDI interface to update the firmware on the MFC-101. [http://wiki.fractalaudio.com/index.php?title=Yeks_MFC-101_How-Tos_page More information]

==USB connection increases CPU utilization==
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 Source1] [http://forum.fractalaudio.com/axe-fx-ii-bugs/40246-global-cab-sim-cpu.html#post573202 Source2]

==Latency==
When monitoring audio via the Axe-Fx II, latency is none.
When monitoring the audio signal via the computer's output, the latency depends on the computer. [http://forum.fractalaudio.com/axe-fx-ii/38038-usb-noise.html#post520349 Source]

==Solving USB noise==
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." [http://forum.fractalaudio.com/axe-fx-ii/38038-usb-noise.html#post520349 Source]

==Disabling the Axe-Fx output signal when monitoring through a DAW==
When the Axe-Fx is connected to a DAW through USB, you're using monitors connected to the Axe-Fx, and you're recording, you may want to monitor just the DAW signal, not the signal from the Axe-Fx.
To accomplish this, turn down the preset level in Axe-Edit. Or set USB/Digi Out Source to Out 2, then route guitar to FXL only. [http://forum.fractalaudio.com/axe-fx-ii-discussion/44923-avoid-double-signal-phasey-sound-when-using-daw-2.html Source]

==USB storage media==
The Axe-Fx II cannot connect to an USB stick. [http://forum.fractalaudio.com/axe-fx-ii/35997-axe-fx-ii-technical-questions-thread-34.html#post491613 Source]

==Linux==
Linux is not officially supported by FAS. Nevertheless all USB features as described above ([[USB_connectivity#Diagram:_USB_features]]) can be obtained under Linux, too.

The Axe-Fx II is fitted with a Cypress USB chip (FX-LP2) which needs to be loaded with firmware (this is not the Axe-Fx II firmware you can download from Fractals support page but a dedicated bootloader) to achieve its functionality.

The firmware hex file can be extracted from the Mac OSX driver package (Axe-Fx_II_USB_Driver_Setup.dmg from [http://www.fractalaudio.com/support]).

With fxload ([http://linux.die.net/man/8/fxload]) you could upload the USB firmware manually what would be pretty inconvenient. But with a proper udev rule executing fxload, it is also possible to upload the USB firmware file automatically to the Axe-Fx II.

You may write your own udev rule or use the already existing bash script ([http://forum.fractalaudio.com/axe-fx-ii-discussion/44765-anybody-tried-usb-interface-linux-yet.html#post593209]) to setup a Linux system to recognize the Axe-Fx II each time it is connected to a USB port and then upload the USB firmware.

After executing the script or applying your own udev rule and then switching on or rebooting the
connected Axe-Fx II lsusb will report a new USB device with VID 2466 for Fractal Audio Systems and PID 8003 for the Axe-Fx II. If you like to have a named output you can add adequate entries to the file called usb.ids which is usually located under /usr/share.

Linux recognizes the Axe-Fx II as a generic USB audio and midi device. As such it is handled by the snd-usb-audio respectively the snd-usb-midi module. Unfortunately only MIDI over USB works out of the box but not the USB audio interface. The latter needs some handwork:

Since the Axe-Fx II (at the moment) neither responds to set sample rate requests nor get sample rate requests, it is necessary to patch the files clock.c and format.c (located under /usr/src/linux-kernelversion/sound/usb/) as described here [http://forum.fractalaudio.com/axe-fx-ii-discussion/44765-anybody-tried-usb-interface-linux-yet-3.html#post651754]. After applying the patch the snd-usb-audio module has to be recompiled. Once the previous version of this module has been removed from the kernel (rmmod) and the newly built module has been added to the kernel (modprobe), playback and capturing devices of the Axe-Fx II appear and are functional.

[[category:About the Axe-Fx II]]
[[category:Axe-Edit]]
[[category:Connecting to a computer or digital device]]
[[category:System and firmware]]