Axe-Edit 3.14.2 Released

Thanks FAS. Love using Axe edit!
P.S,
Just updated, unlike every other time this update caused Avast Free Anti Virus to Flag this as suspicious and stopped the updater (Both from with the app (Win 7) and when downloading the file and launching the installer. I had to turn off the Anti virus to install. Just letting you know, perhaps Avast has changed it's screening processes?
 
Does anyone know why I can't download axe edit from fractal.com ? when I right click and
"save as" it doesn't download , and if I click on the download button it says "this site can't be reached".on both chrome and firefox , if no luck what;s that axe fx site that has all teh previous firmwares and such for download ?
Thanks
 
Michael, have you noticed a glitch with show available devices not connecting with a second device because the midi Channel is stuck in the settings tab on the current device? When I look for my second device I have to manually reset in the settings tab to connect to my XL+ from the XL.
 
I have regularly connection time out messages and have to restart the Axe FX. Is there any known solution to this problem in the meanwhile? I have no other device connected and have only Reaper running. Thanks.
 
don_joe said:
I have regularly connection time out messages and have to restart the Axe FX. Is there any known solution to this problem in the meanwhile? I have no other device connected and have only Reaper running. Thanks.
Click to expand...
Unfortunately no. If you check the Bugs section, you will see a number of us reported it, but because we could not come up with a pattern that causes the crash just describing the situations, it seems the source of the bug was not found as of this date as it does not seem to be happening for FAS or any of the beta testers.

Here are a couple of threads to look at:
https://forum.fractalaudio.com/threads/axe-edit-constant-crashes.127344/
https://forum.fractalaudio.com/threads/communication-timeout-with-q-8.128731/#post-1532830
 
dr bonkers said:
Unfortunately no. If you check the Bugs section, you will see a number of us reported it, but because we could not come up with a pattern that causes the crash just describing the situations, it seems the source of the bug was not found as of this date as it does not seem to be happening for FAS or any of the beta testers.

Here are a couple of threads to look at:
https://forum.fractalaudio.com/threads/axe-edit-constant-crashes.127344/
https://forum.fractalaudio.com/threads/communication-timeout-with-q-8.128731/#post-1532830
Click to expand...

OK, thank you for the info and for the links to these other threads.
 
dr bonkers said:
Unfortunately no. If you check the Bugs section, you will see a number of us reported it, but because we could not come up with a pattern that causes the crash just describing the situations, it seems the source of the bug was not found as of this date as it does not seem to be happening for FAS or any of the beta testers.

Here are a couple of threads to look at:
https://forum.fractalaudio.com/threads/axe-edit-constant-crashes.127344/
https://forum.fractalaudio.com/threads/communication-timeout-with-q-8.128731/#post-1532830
Click to expand...

I have noticed it appears for me to be a problem with Cubase 9 on Windows 10. Any time I try to run cubase 9 and axe-edit I get the timeout error lockup thing. If I run axe-edit by itself no problem as soon as fire up cubase, or have cubase running and try to fire up axe-edit it crashes. . Is there a solution to this? Could it be both software are trying to use same port? I am not a computer expert so I am just guessing.
 
Mehl Anoma said:
I have noticed it appears for me to be a problem with Cubase 9 on Windows 10. Any time I try to run cubase 9 and axe-edit I get the timeout error lockup thing. If I run axe-edit by itself no problem as soon as fire up cubase, or have cubase running and try to fire up axe-edit it crashes. . Is there a solution to this? Could it be both software are trying to use same port? I am not a computer expert so I am just guessing.
Click to expand...
I am using Windows 7 and I will get that error with a variety of different DAW's even with all MIDI turned off on MY DAWs.
 
You must log in or register to reply here.
Back
Top Bottom