Ubuntu 14.04.
Sound was OK from the device but using it as audio output freeze frequently.
I could not make Axe edit Work so far with wine. It crashes just after user interface display.
Anybody tried AXE-FX output sound recording on LINUX using this driver ? Works well ?
Some quesions to clear things up:
* Is your OS 32bit or 64bit?
64 bits. I use the stock kernel, not lowlatency.
* Did Bitwig Studio freeze or the Axe-Fx II?
Bitwig made some strange noise (like when a CD player plays a trashed CD, you hear a very short sample in a loop). I had to restart the audio engine of Bitwig.
* Do you get a crashdump from wine and what is being reported?
I had a register dump on a window. I will look at it this evening.
I will also try to remove the Axe-edit config and restart.
I heard that Axe edit has been written with juce, it would be cool if Fractal could recompile the stuff for Linux.
Regarding Axe-Edit 3.0.3 you can try the following (assuming installation of Axe-Edit was successful): Start winecfg, select Axe-Edit on the applications tab, head over to the libraries tab and disable dwrite.dll (Under "New override for library" type "dwrite", then click "Edit" and select "Disable").
Bitwig made some strange noise (like when a CD player plays a trashed CD, you hear a very short sample in a loop). I had to restart the audio engine of Bitwig.
Regarding Axe-Edit 3.0.3 you can try the following (assuming installation of Axe-Edit was successful): Start winecfg, select Axe-Edit on the applications tab, head over to the libraries tab and disable dwrite.dll (Under "New override for library" type "dwrite", then click "Edit" and select "Disable").
Yeahhhhhh It works! Thank you guys, disabling the shared lib worked, now I can use Axe-Edit.
Volt, it seems that it is a problem with Bitwig, I can play music without problem using desktop player and selecting the Axe.
That is very good news, htey are pretty good at fixing stuff quickly. My setup is 48Khz, but some of the stuff was recorded at various frequencies with different audio interface. It might trigger some bug in Bitwig.
Thank you for your help!
- Axe-edit runs but report the following problem on start-up :
Communication time-out : Axe-Edit was unable to complete the following communication request get_all_patch_names
- Axe-edit does not display Cab Type (and other param with list) properly but changing param values (level, mix) on axe-edit does work and set the value properly on the AXE-FX
I did try :
"Regarding Axe-Edit 3.0.3 you can try the following (assuming installation of Axe-Edit was successful): Start winecfg, select Axe-Edit on the applications tab, head over to the libraries tab and disable dwrite.dll (Under "New override for library" type "dwrite", then click "Edit" and select "Disable")."
In the VirtualBox there does not seem to be the need to install the AXE-FX driver on Linux since it is already installed on the host Mac.
- Axe-edit installs fine (but report problem opening the pdf file)
Hm, never had this error. But I guess the issue could be related to the handling of the USB port by VirtualBox / the chain OSX - VirtualBox - Debian - Axe-Edit. At first OSX handles the USB port the Axe-Fx II is connected to. Then VirtualBox hands the data of the USB port over (did not investigate how this is done) to Debian. Debian would handle this data as if the Axe-Fx is directly connected to a hardware USB port with its own driver before it gets through wine to Axe-Edit. I could imagine that this "path" just takes too long and leads to the time-out.
They appear empty.Do you mean the listboxes do not appear / are empty?
I don't think so has well, but I just gave it a try.I don't think that dwrite.dll has something to do with your issues, at least not the first one (communication time-out), as it seems to be part of DirectWrite, an DirectX-API for text layout and glyph rendering.
Did not known that.Yes, but that applies only to Linux and OSX clients: The Axe-Fx II does not need a dedicated driver on OSX and Linux as it is known from Windows. It is only needed to load the USB firmware to the Axe-Fx II. That is what the OSX and Linux "drivers" do. Once the USB firmware is uploaded to the Axe-Fx II its midi and audio should work as an usb audio device with the (general) usb driver the OS already contains. So you don't need to install drivers for the Axe-Fx II in OSX and Linux, but only because they are already there.
In contrast if your VirtualBox client would be a Windows OS you would have to install the Axe-Fx II driver for Windows, just as if you run Windows directly (without VirtualBox).
So in the end all VirtualBox clients use their own software / driver layer.