Axe-Edit III 1.13.11

NY Guitarist said:
Axe-Edit "Check for update" prompted me to download version 1.13.11.

Downloaded, installed, launched, loaded Axe firmware 24.00b2 successfully. :cool:

MacOS Sonoma 14.2.1
Click to expand...
I did the same. Running MacOS Sonoma 14.2. Once I download the Axe-Edit installer for 1.13.11, it completes the download, closes out of Axe-Edit, then nothing. reopen Axe-Edit then the whole routine happens again (notified of an update, re-download, auto-closes out, then nothing...)
 
tchopper said:
I did the same. Running MacOS Sonoma 14.2. Once I download the Axe-Edit installer for 1.13.11, it completes the download, closes out of Axe-Edit, then nothing. reopen Axe-Edit then the whole routine happens again (notified of an update, re-download, auto-closes out, then nothing...)
Click to expand...
Never mind - I'm an idiot... I had Stage Manager running on my Mac and it inadvertently hid the installer window with the .dmg... All good now. Sorry for any confusion...
 
This bug still exists in this version:

Typing Dyna-Cab Distance shows as "1.23 cm" instead of changing to "1.23" when doubleclicked. This results in invalid values being sent to the Axe-Fx 3 because instead of a numeric value it will try to send a string or do something weird with the value so it doesn't apply without deleting " cm" from it first. Every other control changes from "x.xx unit" -> "x.xx" when doubleclicked so this should too.
 
Michael Pickens said:
Axe-Edit III 1.13.11 is now available via auto-update or from our website:

https://www.fractalaudio.com/axe-fx-iii-edit/


RELEASE NOTES

VERSION 1.13.11
DECEMBER 19, 2023

Current Axe-Fx III Firmware Version: 23.05

SYSTEM REQUIREMENTS
  • Mac version requires OS version 10.9 or newer
  • Windows version requires Windows 7 or newer
  • Minimum firmware version 3.02

NEW IN THIS VERSION

* Support for firmware 24.00 public beta.
o Updated AMP layouts.

* Corrected the "ghost" blocks that could appear when disconnecting and reconnecting the device while leaving the editor open.
Click to expand...
Thank you - have Firmware 23.05, but latest version of Axe-Edit (1.13.11) seems to be presenting with visible bugs. For example, Tempo seems to be stuck at 250 bpm, and when I try to edit that and save new Tempo, it simply reverts to 250. Also, Save button remains lit after Save has just been done on a Preset. Those are the bugs I've discovered so far, but very, very visible this time. That's the first time any bugs have been so readily apparently since I got my Axe III two years ago. I've tried downloading Axe-Edit again and reinstallng it to my Mac, but it hasn't corrected these bugs. Is FAS aware of these bugs, and is there a set of fixes coming? Thank you!
 
Ian4924 said:
Thank you - have Firmware 23.05, but latest version of Axe-Edit (1.13.11) seems to be presenting with visible bugs. For example, Tempo seems to be stuck at 250 bpm, and when I try to edit that and save new Tempo, it simply reverts to 250. Also, Save button remains lit after Save has just been done on a Preset. Those are the bugs I've discovered so far, but very, very visible this time. That's the first time any bugs have been so readily apparently since I got my Axe III two years ago. I've tried downloading Axe-Edit again and reinstallng it to my Mac, but it hasn't corrected these bugs. Is FAS aware of these bugs, and is there a set of fixes coming? Thank you!
Click to expand...
I haven't seen any reports of similar issues. If these were bugs in the editor undoubtedly many people would have reported them by now.

Do you by chance have a DAW active or some other midi device connected?
 
Ian4924 said:
Thank you - have Firmware 23.05, but latest version of Axe-Edit (1.13.11) seems to be presenting with visible bugs. For example, Tempo seems to be stuck at 250 bpm, and when I try to edit that and save new Tempo, it simply reverts to 250. Also, Save button remains lit after Save has just been done on a Preset. Those are the bugs I've discovered so far, but very, very visible this time. That's the first time any bugs have been so readily apparently since I got my Axe III two years ago. I've tried downloading Axe-Edit again and reinstallng it to my Mac, but it hasn't corrected these bugs. Is FAS aware of these bugs, and is there a set of fixes coming? Thank you!
Click to expand...
Did you RANF?
 
possible amp layout bug for JS410 Lead Green:
  • no Global / Channel MV controls are available, unlike the other JS410 models
  • on the Axe FX III unit, Global / Channel MV controls are available
1703781531674.png
1703781548203.png
 
reposting this in here as it may be an issue with 1.13.11

Found something.
Created preset 505 for the fantastic new Brit Silver.
As I normally do, I went to add it to my "favorites layout" in axe-edit fc edit. The preset doesn't show the name in the FC edit popup.
version 24.03 and axe-edit version 1.13.11. The preset was in fact saved.

As a sidenote, it did appear after I closed and re-opened Axe-edit. Regardless, it should have been there without the restart.

see the action here:


I have axe-edit set to not scan on startup so it must be doing some other version of a read.
View attachment 132289


When you do a 'refresh after firmware' it clearly shows that it re-reads the presets. I'll assume that Fc edit is reading a different table as only on a full app restart does it properly sync up. I then force a preset read through the GUI and it still doesn't correct things then I shut it down. After opening it is synced up again.

Here's another video showing that I have deleted a preset and the table that FC edit reads still isn't updated.



It's not a big deal
Just something I noticed
I'll restart axe edit before manipulating fc edit.
 
dean701 said:
reposting this in here as it may be an issue with 1.13.11

Found something.
Created preset 505 for the fantastic new Brit Silver.
As I normally do, I went to add it to my "favorites layout" in axe-edit fc edit. The preset doesn't show the name in the FC edit popup.
version 24.03 and axe-edit version 1.13.11. The preset was in fact saved.

As a sidenote, it did appear after I closed and re-opened Axe-edit. Regardless, it should have been there without the restart.

see the action here:


I have axe-edit set to not scan on startup so it must be doing some other version of a read.
View attachment 132289


When you do a 'refresh after firmware' it clearly shows that it re-reads the presets. I'll assume that Fc edit is reading a different table as only on a full app restart does it properly sync up. I then force a preset read through the GUI and it still doesn't correct things then I shut it down. After opening it is synced up again.

Here's another video showing that I have deleted a preset and the table that FC edit reads still isn't updated.



It's not a big deal
Just something I noticed
I'll restart axe edit before manipulating fc edit.
Click to expand...

Edit isn’t the source of truth, it only echoes what the modeler tells it to do, so I’m wondering if the modeler and Edit are having trouble talking.

Another possibility is that Edit’s ability to write to its preferences directory is being affected.

Also, it’s not necessarily to make Edit refresh everything just to reread the presets. Simply click the “recycle” button in the preset picker or manage presets windows.
 
Last edited:
Greg Ferguson said:
Edit isn’t the source of truth, it only echoes what the modeler tells it to do, so I’m wondering if the modeler and Edit are having trouble talking.

Another possibility is that Edit’s ability to write to its preferences directory is being affected.

Also, it’s not necessarily to make Edit refresh everything just to reread the presets. Simply click the “recycle” button in the preset picker or manage presets windows.
Click to expand...
I'm not having any other issues with axe edit. Just fc edit. No comm issues suspected as everything else is working without delay. Perhaps a line of code is missing for fc edit. They are definintely using different tables. Axe Edit sees the truth. Fc edit doesn't.
 
dean701 said:
reposting this in here as it may be an issue with 1.13.11

Found something.
Created preset 505 for the fantastic new Brit Silver.
As I normally do, I went to add it to my "favorites layout" in axe-edit fc edit. The preset doesn't show the name in the FC edit popup.
version 24.03 and axe-edit version 1.13.11. The preset was in fact saved.

As a sidenote, it did appear after I closed and re-opened Axe-edit. Regardless, it should have been there without the restart.

see the action here:


I have axe-edit set to not scan on startup so it must be doing some other version of a read.
View attachment 132289


When you do a 'refresh after firmware' it clearly shows that it re-reads the presets. I'll assume that Fc edit is reading a different table as only on a full app restart does it properly sync up. I then force a preset read through the GUI and it still doesn't correct things then I shut it down. After opening it is synced up again.

Here's another video showing that I have deleted a preset and the table that FC edit reads still isn't updated.



It's not a big deal
Just something I noticed
I'll restart axe edit before manipulating fc edit.
Click to expand...

@Michael Pickens

I was able to duplicate the problem by deleting a preset then checking the FC Edit preset picker. The FC Edit preset list isn't being refreshed and the window lacks the "refresh" button. Switching to the regular Preset Picker shows that the preset was deleted.
 
Hi @Michael Pickens is there a bug in the Axe-Edit Version with copying block parameter? What I have done?

1. Click on Amp-Block 2
2. Right click on the block and call copy
3. I added a new Amp-Block 1
4. Right Click on it and call paste
5. The Amp-Block will be changed to a cab-block!

With other blocks it is working instead of the amp block!
 
oson00 said:
Hi @Michael Pickens is there a bug in the Axe-Edit Version with copying block parameter? What I have done?

1. Click on Amp-Block 2
2. Right click on the block and call copy
3. I added a new Amp-Block 1
4. Right Click on it and call paste
5. The Amp-Block will be changed to a cab-block!

With other blocks it is working instead of the amp block!
Click to expand...
Did you perform a ' refresh after upgrade'?
I'm not having that issue
 
You must log in or register to reply here.
Back
Top Bottom