There were changes to the Reverbs???I loaded the latest Aries and I found the changes to the Reverb blocks to be so annoying that I blew the previous release back in. Now I get the following error message in the block library log:
/Users/Howard/Documents/Fractal Audio/Axe-Edit/blocks/Reverb/Nice Plate_20191118_173816.blk: The block was saved using Axe-Fx II XL+ firmware version Ares 2.00 and is not compatible with the connected device's firmware.
Anyone else out go through the same thing.
What FW did you update from? I don't think there were changes in either of the Ares releases except for Amp modeling.I loaded the latest Aries and I found the changes to the Reverb blocks to be so annoying that I blew the previous release back in. Now I get the following error message in the block library log:
/Users/Howard/Documents/Fractal Audio/Axe-Edit/blocks/Reverb/Nice Plate_20191118_173816.blk: The block was saved using Axe-Fx II XL+ firmware version Ares 2.00 and is not compatible with the connected device's firmware.
Anyone else out go through the same thing.
There were changes to the Reverbs???
Anything changed/saved in a particular firmware will not be readable in an older version. This is why backing up before updating is crucial.
That would be great but I'm not too sure we will see any more updates to the Axe fx 2. My hopes were up after the last unexpected update and while Cliff did state he found a way to apply the new updates across all platforms I have a feeling we may not be getting anything more for the 2. It will be a bonus if we do but I am more than happy with the box in its present state.Hey does anybody know if we're gonna get the Gain Enhancer option for the Out Comp Type in the Axe-Fx II?
Exactly, that's more than enough for me.Yup it doesn't seem logical new features will be added, it was stated clearly Axe II is EOL.
From past comments of Cliff, it doesn't even seem the II can handle any more code lines, which explains (at least technically) the EOL statement.
What the II can get, technically, is refinements of existing code lines, for example improved way to model grid conduction or cathode follower limiting/compressing... that's kind of stuff Ares 1.03 and 2.00 gave us.
I would be SUPER happy if we'll see just more of that
I upgraded from Ares 1.03 to 2.0. I had the latest FW. The reverb blocks were definitely changed.What FW did you update from? I don't think there were changes in either of the Ares releases except for Amp modeling.
You can recover your stuff:
- Update to latest FW again
- Make a backup
- Revert back to older firmware
- Use FracTool to "convert" backup to current system
- Make a donation to @AlGrenadine for creating such an awesome tool!
There were changes to the Reverbs???
Anything changed/saved in a particular firmware will not be readable in an older version. This is why backing up before updating is crucial.
Did you follow the steps I listed? FracTool should handle it, I think.I upgraded from Ares 1.03 to 2.0. I had the latest FW. The reverb blocks were definitely changed.
I only made changes to a couple of patches. I re-imported the patches but I still get the error message. Not sure what do.
It would be awesome if we could close out 2019 with an Ares for II update via Cliff's new unified data file.FWIW, I'll be porting some of the Axe-Fx III 9.xx changes this week. I woke up yesterday and figured out a way to use a single modeling data file for all products going forward so we won't have to maintain multiple files.
Haven't heard about this unified thing since few weeks, i wonder if it's been cancelledSept 29, 2019...
It would be so if we could close out 2019 with an Ares for II update via Cliff's new unified data file.