Axe-Edit Issues on Arch Linux

T

TomRobinsonIO

Member
Fixed: Installed Axe-Edit in Lutris and it appears to work without issue. Thank you pmarcelll over on Reddit for the suggestion!

I am trying to get Axe-Edit working on my Arch computer. This is one of the last issues I've had to still being able to preform all of the same functions I do on my Mac.

I am currently working with Arch 5.19.7-arch1-1 and Wine wine-7.16 (Staging) but started with the default Wine install of the same version number.

I followed the instructions from the Fractal Audio Wiki entry for Axe-Fx II USB on Linux.

I have made an entry in the usb.ids file and the device is properly named.
Code: 
~ ❯ lsusb
Bus 001 Device 007: ID 2466:8003 Fractal Audio Systems Axe-Fx II

I have installed the USB Driver Linux 106

I have installed the additonal packages specified for USB and Wine.
Code: 
lib32-alsa-plugins lib32-libpulse lib32-openal

I installed the latest version of Axe-Edit for Axe-Fx II

Launched using the options listed on the Wiki.
Code: 
WINEDLLOVERRIDES=dwrite=d wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Fractal\ Audio/Axe-Edit/Axe-Edit.exe

The program launches fine. On first launch it appears to be fine. Menus seem to work, it reads the current preset, etc.

When trying to use the preset up or down arrows or attempting to make a change to a preset like selecting a block, it says it's communicating for a moment and then displays an error saying:

Code: 
Communication time-out:

Axe-Edit was unable to complete the following communication request: Query Effect All Params :
global_blocks_query

View attachment 108067

After clicking OK on the error, Axe-Edit is completely unresponsive. Won't allow me to click menus, select blocks or anything. The screen on the Axe-Fx does update however showing what's been selected, disabled, if a preset number has been changed. Reading through the forum posts I've been able to find, it doesn't seem that anyone has had any similar issues.

It may also be worth mentioning that the unit works great as an interface as is. I'm able to see the unit in Reaper using JACK and select the different outputs to monitor and record.

Things I've also tried:

  • Reboot the computer
  • Reboot the Axe-Fx
  • Reinstall Axe-Edit
  • Run the program from Wine without the DLL overrides
  • Switch USB Cable (original cable works fine on Mac)
  • Unplug all other USB devices (mouse and keyboard excluded) and reboot
  • Delete .wine folder completely and reinstall Axe-Edit
  • Switch to Wine-Staging
  • Upload stock Preset Banks A, B and C syx (Fractal-Bot works without issue)
  • Reflash Firmware Ares v2.0 (Fractal-Bot works without issue)
  • Search furiously through Fracatal forums and any other post I can find related to this setup and the error messages from the output.

Below is the output from running the program as specified in the Fractal Wiki entry:

Code: 
~ ❯ WINEDLLOVERRIDES=dwrite=d wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Fractal\ Audio/Axe-Edit/Axe-Edit.exe
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.16 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 042D2B78): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (0001006A 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 0001006A 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0001006A 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0001006A 49 1 00000000
010c:err:ole:com_get_class_object class {4ce576fa-83dc-4f88-951c-9d0782b4e376} not registered
010c:err:ole:create_server class {4ce576fa-83dc-4f88-951c-9d0782b4e376} not registered
010c:err:ole:com_get_class_object no class object {4ce576fa-83dc-4f88-951c-9d0782b4e376} could be created for context 0x6
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 042D2B78): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (0002006A 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 0002006A 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0002006A 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0002006A 49 1 00000000
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 04535950): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (0001007A 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 0001007A 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0001007A 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0001007A 49 1 00000000
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 04535950): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (0002007A 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 0002007A 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0002007A 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 0002007A 49 1 00000000
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 0456C1E8): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (00010080 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 00010080 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00010080 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00010080 49 1 00000000
0054:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub
0054:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 0456C468): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (00020088 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 00020088 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00020088 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00020088 49 1 00000000
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 0456C730): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (00010090 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 00010090 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00010090 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00010090 49 1 00000000
010c:fixme:combase:RoGetActivationFactory (L"Windows.UI.ViewManagement.UIViewSettings", {3694dbf9-8f68-44be-8ff5-195c98ede8a6}, 0456C9C8): semi-stub
010c:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.UIViewSettings"
010c:fixme:win:RegisterTouchWindow (00010096 00000000): stub
010c:fixme:msg:ChangeWindowMessageFilterEx 00010096 233 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00010096 4a 1 00000000
010c:fixme:msg:ChangeWindowMessageFilterEx 00010096 49 1 00000000
010c:fixme:imm:ImeSetActiveContext (00010060, 1): stub
010c:fixme:imm:ImmReleaseContext (0002006A, 00010060): stub
010c:fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DISABLE_AUTODIAL; STUB
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DATA_RECEIVE_TIMEOUT (30000): STUB
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DISABLE_AUTODIAL; STUB
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DATA_RECEIVE_TIMEOUT (30000): STUB
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DISABLE_AUTODIAL; STUB
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_DATA_RECEIVE_TIMEOUT (30000): STUB
010c:fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 30000
010c:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (011CFBDC 1 C) semi-stub
010c:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (011CFA04 1 C) semi-stub

Any insight into what I may be able to try next would be greatly appreciated. I've been working on this for several days and I'm simply out of ideas. Thank you!
 
Last edited:
I appreciate the reply, ghosty. I'll edit the original post with a solution if I ever come up with one. Any specific USB packages you think might help? I'd be willing to give them a try.

Another thought: if you've got some free time, would you mind installing axe-edit on Mint through Wine and see if you have the same issue? All of the old Linux threads on the forums here are several years old. I'm wondering if everything still works for most or if things have become broken over time with kernel and package updates.
 
Last edited:
AlbertA said:
so only when changing patches? Everything else works ok? Like editing blocks, etc?
Click to expand...
No, sorry if that was unclear. If I try to select a block at all, it freezes. It never gets to the point where it shows the controls for the selected block. I am able to change patches from the presets button to the left of the current preset indicator without issue and that's about it. Anything else produces an error. Double clicking on a block, for example, will actually disable the block and light the edited indicator on the unit, but won't reflect the change on Axe-Edit and will instead show the error as though it's not getting a confirmation from the unit.
 
I tried a bit more messing around with adding DLLs via Wine Tricks yesterday trying to chase down the error message rabbit. That made the issue worse and caused me to have to reset my Wine folder again. I also tried changing the reported Windows version within the winecfg. Doesn't seem to make much difference between Windows 10/7. I plan to do more troubleshooting over the weekend.

@AlbertA, if you have any ideas, I'd really appreciate it.
 
I know this is a lateral step... but you could run a VM of Windows inside Arch whilst you wait for a solution with Wine.
I remember having many issues with the AxeFX Ultra in Linux with a MIDI to USB cable. Eventually I swapped out the cable and somehow it worked...
 
Try using amidi on the linux side - send a Sysex message that expects a response and see if you get it.

Look at wine config and see if there's anything off in the midi configuration (mapping to ALSA)
 
Hmm I'm running on Fedora 35 with Wine 7.10 (haven't updated in a while) and not having this issue. But I do run axedit like this:

Bash: 
#!/usr/bin/bash
export WINEDLLOVERRIDES=dwrite=d
export LD_PRELOAD=~/lib/libaxe-edit-cursor.so
wine ~/.wine/drive_c/Program\ Files/Fractal\ Audio/Axe-Edit\ III/Axe-Edit\ III.exe

That library is from this post: https://forum.fractalaudio.com/threads/linux-folk-disappearing-mouse-cursor.138625/

Can't think of what might be the problem, unfortunately.
 
AlbertA said:
Try using amidi on the linux side - send a Sysex message that expects a response and see if you get it.

Look at wine config and see if there's anything off in the midi configuration (mapping to ALSA)
Click to expand...
First of all, thank you again for your reply.

I'm no expert in this by any means. I did a bit of searching around and tried to run a command using amidi, which appears to be getting data back.

Code: 
amidi -l
IO  hw:4,0,0  AXE-FX II AXE-FX II MIDI Out

amidi -p hw:4,0,0 -S F0411042110C000000000074F7 -r dump.syx -t 1
I waited several minutes and Ctrl+c the command.

Code: 
^C 6062 bytes read

ls -la
-rw-r--r-- 1 tom tom 6062 Sep 10 11:53 dump.syx
To me, I think that indicates that midi to the linux side is receiving messages back from the Axe-Fx? I also have used Fractal-Bot in Wine to push/pull files without issue, which I would assume should be functioning in a similar way to Axe-Edit for send/receive? I've also found by messing around that if I select Settings > Refresh after new FW, it will read all of the block definitions and complete successfully.

As for the winecfg, audio appears to be working. I am using winepulse.drv as the selected driver. I tried changing that to winealsa.drv and relaunched Axe-Edit. That doesn't appear to change anything. I'm still able to select blocks, the screen on the Axe-Fx itself changes to the settings for the block that was selected in Axe-Exit. Axe-Edit says "Please wait... Communicating." for a bit and then throws the error again.

I am still scratching my head.
 
TomRobinsonIO said:
I've also found by messing around that if I select Settings > Refresh after new FW, it will read all of the block definitions and complete.
Click to expand...

Oh ok so it is able to receive Midi data, the yeah its a head scratcher for sure.


I would try winedbg to launch AxeEdit and See if some thread is stuck when doing the actions that cause it to hang. Maybe that can give you some leads.
 
AlbertA said:
Oh ok so it is able to receive Midi data, the yeah its a head scratcher for sure.


I would try winedbg to launch AxeEdit and See if some thread is stuck when doing the actions that cause it to hang. Maybe that can give you some leads.
Click to expand...
As soon as I try to attach winedbg, it crashes Axe-Edit completely. I have to completely kill wineserver to get it to close.

Code: 
info process
pid      threads  executable (all id:s are in hex)
0000015c 5        'Axe-Edit.exe'
00000128 1        'start.exe'
00000138 1        \_ 'winedbg.exe' =
00000140 1           \_ 'winedbg.exe'
00000130 2        \_ 'conhost.exe'
0000004c 3        'explorer.exe'
00000038 7        'services.exe'
000000d8 7        \_ 'rpcss.exe'
000000b4 3        \_ 'svchost.exe'
0000009c 4        \_ 'plugplay.exe'
00000070 9        \_ 'winedevice.exe'
00000044 7        \_ 'winedevice.exe'

Wine-dbg>attach 348

0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 0144:fixme:dbghelp:elf_search_auxv can't find symbol in module 
0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 
0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 
0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 
0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 0144:fixme:dbghelp_dwarf:dwarf2_virtual_unwind mismatch in cpu 
0x0000007bc56a41 ntdll+0x56a41: ret
 
That "can't find symbol" message usually means you've got an incompatible shared library version... which one is often not easy to determine.
 
I had some time to grab another PC and install Arch and Ubuntu in Virtual Box. First I tried a clean Arch install just to make sure something else in the way I had my system configured wasn't breaking it. Following the same steps as I did in the first post, it appears to behave the same way.

Next I tried installing Ubuntu 22.04 and using the @AlbertA PPA to install everything. I had the same problem on the fresh Ubuntu VM using the PPA and Wine from WineHQ. Then I reverted to a snapshot I took of the VM at first launch and this time installed Wine64 (version 6) directly from the Ubuntu source and used the @AlbertA PPA again. Again, same problem.

So now I'm wondering if the driver hex isn't compatible with the Ares firmware. I know with MacOS, there's was a driver update on Oct 15 2019. I downloaded both the older and newer MacOS installers, took a look in the .pkg files and found the axefx2load.hex. They appear to be different files in the two different versions.

Just for fun, I tried using the 2019 MacOS version of the hex file in place of the Linux 106 hex file and it doesn't work either.

Would anyone be able to tell me if I'm on to something here? If the issue is that the firmware on the Axe-Fx is too new for the driver from the Linux Driver 106 package, am I just out of luck? I'm starting to feel like that might be the case.
 
Last edited:
TomRobinsonIO said:
Would anyone be able to tell me if I'm on to something here? If the issue is that the firmware on the Axe-Fx is too new for the driver from the Linux Driver 106 package, am I just out of luck? I'm starting to feel like that might be the case.
Click to expand...
Wait, what Linux driver? I'm not using any such thing...

Also not sure I'm following along with the Virtualbox thing, I'm just running plain old Wine with no VM.

Actually I just read back and I totally didn't realize you're using an AxeFX-II - I'm using a III, sorry for leading you down possibly the wrong path here. I clicked on the thread in the "new posts" tab without realizing which forum we were in.
 
alertedsnake said:
Wait, what Linux driver? I'm not using any such thing...

Also not sure I'm following along with the Virtualbox thing, I'm just running plain old Wine with no VM.

Actually I just read back and I totally didn't realize you're using an AxeFX-II - I'm using a III, sorry for leading you down possibly the wrong path here. I clicked on the thread in the "new posts" tab without realizing which forum we were in.
Click to expand...
Haha no worries! From what I understand the III loads its driver from the unit itself after it boots. I am still using the "ancient" Axe II XL+ though. Maybe it's time for an upgrade. I didn't even realize it but after I looked for my original order the other day, I think I got it in 2012. Time really flies but it still works great.
 
It appears as though I finally found my answer after all. I posted my issue on a few subreddits as well and someone over there suggested I install Axe-Edit in Lutris. I don't know what the difference between installing Axe-Edit in Wine and in Lutris' Wine "runner" but it seems to work well. Hopefully this helps someone else out in the future and I appreciate everyone who helped out along the way!
 
I'm betting it works because it's a carefully curated set of compatible libraries and supporting tools. In other words, ideal for stuff exactly like this. What a great find!
 
You must log in or register to reply here.
Back
Top Bottom