Axe-Fx III Firmware Version 20.00

Sounding great! I don't know if this is a bug or not but my bank size was on 10 after this update and I'm pretty sure I had it on 9 before. It could be that I'm mistaken but it was an easy fix so no biggie if it is a bug.
 
https://www.fractalaudio.com/downloads/firmware-presets/axe-fx-3/20p0/axefxiii_dsp_rel_20p00.zip

Axe-Fx III Firmware Release Notes​


20.00

New “Block Mixer” algorithm results in faster/quieter scene and channel changes. This new algorithm allows placing Amp blocks in series without the concomitant sound bursts that would normally occur when switching scenes.

New Speaker Drive algorithm in Amp block. This new algorithm more accurately models the frequency dependent distortion of guitar loudspeakers. The default value (upon resetting the block) is 2.0 which gives roughly 1 dB of compression. Setting the value to 0.0 defeats the speaker drive modeling. Higher values give a smoother and more focused sound, rounding off the “sharp edges” and yielding greater compression.

Added new “Dynamic Distortion” block. This effect distorts the input signal dynamically, applying more distortion to different frequency ranges depending upon the shape of the filter. When the signal level is low the output will be the same as the input. As the signal level increases more distortion will occur in those bands boosted by the filter shape. This is a powerful tool for final shaping/mastering of your tone. The block contains a handful of presets which demonstrate the basic technique.

Added ability to use Pre-Delay in Reverb block as a simple echo. Pre-Delay now features Tempo, Feedback and Mix parameters. The pre-delay time has also been increased to 1s. Several types have been added demonstrating the capabilities.

Fixed Amp block Scene Ignore not being recalled correctly in some cases.

Fixed USB buffer level setting not sticking between power cycles.

Layout Link configured on a tap function for a footswitch will no longer incorrectly execute when activating the switch exits the Tuner.

Various other fixes and improvements.

NOTE: THIS FIRMWARE IS NOT COMPATIBLE WITH PREVIOUS VERSIONS OF AXE-EDIT. A NEW VERSION OF AXE-EDIT IS REQUIRED FOR USE WITH THIS VERSION.

NOTE: If you installed firmware 20.00 beta 4, you may find that some FC effect switches are now mapped to the wrong effects. For example, a switch that was set to bypass REVERB 1 may now bypass AMP 1 instead. This release prevents this problem from occurring you are upgrading from 19.x or older.


If you installed 20.00 beta 4, however, this will have already modified your layouts, so you will need to either restore them from a backup, or adjust the individual switches manually. Layouts can be restored using a "System" backup from Fractal-Bot, or a "Layouts" file from Axe-Edit. If you'd rather reset to the factory default FC layouts, find this under SETUP> FC Controllers> Reset.
WOOHOO!!! I was checking for it! So much more stuff to try out! THANK YOU!
 
This is not a DSP firmware issue. It's a driver issue and Amandio is working with the driver provider on it.

That's a different problem. Amandio discovered that, but I've never seen that myself. I'm just talking about the problems I reported to him.
 
Just in time for the gigs this weekend! I was on the beta. Was concerned about FC switches but didn't want to roll back. Didn't know if I should be manually adjusting each switch or not. Happy to do it now.
 

That workaround doesn't work quite as well now with dsp firmware version 20. The situation has definitely improved, but there are new problems to contend with now. I think things are in flux at the moment and we're at an awkward intermediate stage on the way to a good solution to the problem. Hopefully that will be soon and there won't be any need to update the workaround instructions, except to delete them.
 
That workaround doesn't work quite as well now with dsp firmware version 20. The situation has definitely improved, but there are new problems to contend with now. I think things are in flux at the moment and we're at an awkward intermediate stage on the way to a good solution to the problem. Hopefully that will be soon and there won't be any need to update the workaround instructions, except to delete them.
Thanks for your time to reply appreciate it 👊🏻
 
Back
Top Bottom