Axe-Fx Firmware Version 21.02 Public Beta (Beta 2)

So I used to experience odd artifacting coming from the input gate/gate blocks if I pushed the threshold to high. Are people still experiencing that with this firmware?
 
Baseless speculation - Axe-EDIT will be updated along with the release of Beta 3 along side a major feature addition. Otherwise they probably would have updated Axe-Edit sooner.
Why the ire? Mine was a hopeful message. Usually a pause means something additionally cool is coming. It sure as hell wasn’t a complaint. Maybe try the bright side?
 
Why the ire? Mine was a hopeful message. Usually a pause means something additionally cool is coming. It sure as hell wasn’t a complaint. Maybe try the bright side?
I think dbg was signaling that he was indulging in some baseless speculation, not accusing you of it. That’s my read anyway.

And I like the way that speculation is going!
 

Axe-Fx III Firmware Release Notes​


21.02
  • Added Optical Sustainer type based on optocoupler-based pedal compressors.
  • Added Analog Sustainer type. This is an upwards compressor using the same “analog” gain computer as the Analog Compressor type yielding a natural soft-knee response.
  • Added JFET Sustainer type. This is based on a rare JFET-based pedal compressor where the JFET is in the op-amp’s
  • Studio FF Compressor 2 has been renamed Studio FF Sustainer.
Look forward to using the Sustainer types in the next FM9 update!
 
Maybe it's a sad commentary on my life...but every time I get the message to power off for five seconds and turn back on I get happy! Hell, most of the stuff in a firmware update I'll probably never know or use but it's still a warm fuzzy knowing I got something "new and improved" sitting on my desk.
 
I have some very, very complicated presets with all sorts of midi sample commands, so the idea of starting from scratch is pretty daunting.

I was going to change from using the Archon as my primary amp to a Mesa with a compressor in front of it (modeled after a Petrucci preset), so I'll start there and see what else needs some tweaking.
Not sure in your case, but the mods I usually to make for presets on firmware changes are pretty minimal. BMTP, sometimes sag, usually not much more than that. Of course, I only use a couple presets. If you use a preset per song then that can be a lot of work.
 
Maybe it's a sad commentary on my life...but every time I get the message to power off for five seconds and turn back on I get happy! Hell, most of the stuff in a firmware update I'll probably never know or use but it's still a warm fuzzy knowing I got something "new and improved" sitting on my desk.
And that, my friend, is the same “firmware crack rush” ALL of us feel :)
 
I have some very, very complicated presets with all sorts of midi sample commands, so the idea of starting from scratch is pretty daunting.

I was going to change from using the Archon as my primary amp to a Mesa with a compressor in front of it (modeled after a Petrucci preset), so I'll start there and see what else needs some tweaking.
The nice thing is, once you have a preset sounding how you like, and its scenes leveled, you can save the Amp block to the Library, and go to other presets where you want to reuse it and recall it from the library, or simply copy and paste it.

Typically there will need to be a small bit of additional volume leveling in the preset because of the surrounding blocks, but you won’t need to readjust the parameters that give the amp its own particular sound.

Also, Edit makes it easy to set a particular parameter in a block across multiple presets by using the Batch Parameter Set command. From the Wiki:

Parameter Batch Set​

The editors provide a hidden Parameter Batch Set function. Right-click on a parameter while holding down SHIFT to display a context menu, then select "Set In Multiple Presets". Selecting a sub-menu item will display the Preset Picker from which you can select one (like the current one) or multiple presets to batch set the parameter value.

Note that the Batch Setter only saves the current parameter value and dismisses other edits which haven't been saved yet.

Regarding the MIDI blocks, save those to the Library also, for reuse and safe keeping.

My Library is part of a directory on my drive that is nested in my Dropbox hierarchy so every change is automatically saved to the cloud. My storage for IRs and 3rd party presets are also there, and I have the Edit app for each of the modelers pointing into that space, so I can share blocks, templates, and backups for restoring, and also save Fractal-related presets to the space from my phone or iPad. It works very nicely.
 
Greg, hate to butt into convo but you are on here a lot so I’m going to ask…about Amp Reset! I’ve read the 10 thousand opinions about this. I’ve NEVER done the amp reset for any firmware updates…so I ask, if I save the whole amp block in a preset, save it to my block folder, go back and reset amp then load it back from “blocks” it will be updated and still keep those settings? I usually save the whole block whether effects or amps, etc from a preset since there is usually four channels of settings.
 
Why the ire? Mine was a hopeful message. Usually a pause means something additionally cool is coming. It sure as hell wasn’t a complaint. Maybe try the bright side?

I think dbg was signaling that he was indulging in some baseless speculation, not accusing you of it. That’s my read anyway.

And I like the way that speculation is going!

Correct, I was the one engaging in baseless speculation. And I was half joking by using the word "baseless" since we already have pretty concrete ideas of what's being worked on.
 
… if I save the whole amp block in a preset, save it to my block folder, go back and reset amp then load it back from “blocks” it will be updated and still keep those settings?
No.

The reset only applies to the block in the grid inside the modeler. The library exists on your computer disk.
 
Back
Top Bottom