Thoughts on upgrading from version 5.19 to 10.2

StudioCat

Member
I'm upgrading my Ultra from firmware version 5.19. Support at Fractal has suggested an incremental upgrade. Perhaps 7.x and then 10.x running "update presets" in between. Has anyone out there done this or heard of this before. I gig with the Axe-FX almost every week and have created lots of presets I love. However, I want to be able to use the editor. Any thoughts or advice would be greatly appreciated. Thanks in advance, SC
 
Just prepare to spend some time re-tweaking your patches. There's a couple of things that sound quite different going from 5 to 10 so just be prepared, don't upgrade 2 hours before your next gig. But it's worth it, so go for it!
 
Hard to know what exactly what they mean. If you have a load of presets you like then updating to 7.x then re-tweeking your presets might be an idea then tweeking again when 10.x is installed? Maybe the hardware won't take to it but I can't see that (but then again I didn't design the hardware!!!!!) as what your doing is overwriting the rom or whatever :lol: .

I got every firmware as they came but if it was my rack in your situation, I'd set a weekend aside, update to 10.01/02 then redo all the presets. But then I'm lairy and lucky.......

Mark.

p.s. Do what FAS say to be safe (even tho I don't understand why doesn't mean there isn't a reason!)
 
ESP MM-270 said:
Hard to know what exactly what they mean.
It's really pretty easy if you read the release notes. Because a number of firmware revisions introduced parameters and functionalities that were not present in previous ones, they came with an "Update Presets" command. Executing this command does the necessary housekeeping to translate old parameter settings and to initialize new ones that were not present before.
 
Or the manual.

From the wiki version (http://axefxwiki.guitarlogic.org/index.php?title=Axe-Fx_Wiki_Manual):

Preset Update
This function allows you to update all presets to the latest protocol. The Axe-Fx can read presets
stored in either the current version or one version prior. When a preset is saved it is saved in the
latest protocol. If you’ve just updated the firmware to a major revision you can convert all your
presets to the latest protocol by using this function.

So skipping too many firmware revisions may not update the presets properly.

I think there are some notes around the wiki about what value should one set new settings in newer firmwares to, to match the sound in older revisions.
 
Jay Mitchell said:
[quote="ESP MM-270":9a853ozl]Hard to know what exactly what they mean.
It's really pretty easy if you read the release notes. Because a number of firmware revisions introduced parameters and functionalities that were not present in previous ones, they came with an "Update Presets" command. Executing this command does the necessary housekeeping to translate old parameter settings and to initialize new ones that were not present before.[/quote:9a853ozl]

I'm not sure that it translates or initializes parameter settings that weren't there before. I thought it just updated the preset storage protocol when he tweaked its structure. I thought this was so old preset could be read. From what I remember the axe-fx can only read one preset format change prior. So the update preset would keep it so you could read Any time you hit save it saves it in the new format. I was under the impression that all the update presets function did was essentially hit save for each preset. I think Cliff has made it so this is not necessary any more.

Here is an very old post stating what happens when you don't update presets:
"If you updated from a firmware revision prior to 2.0, then your presets would be lost as support for preset protocol version 1.0 has been removed (see the release notes).

All three banks are identical. They just allow you to easily install the factory presets into a different bank so that you can, for example, use BankA for your own presets.

If you need to get your old presets back they're still in there but you'd have to flash back to a version 2.xx firmware and then run the "update all presets" utility under the Utility menu."
 
pholklore said:
Or the manual.

From the wiki version (http://axefxwiki.guitarlogic.org/index.php?title=Axe-Fx_Wiki_Manual):

Preset Update
This function allows you to update all presets to the latest protocol. The Axe-Fx can read presets
stored in either the current version or one version prior. When a preset is saved it is saved in the
latest protocol. If you’ve just updated the firmware to a major revision you can convert all your
presets to the latest protocol by using this function.

So skipping too many firmware revisions may not update the presets properly.

I think there are some notes around the wiki about what value should one set new settings in newer firmwares to, to match the sound in older revisions.


Right, I believe you for 5.19 to 10.2 you need to update in 2 phases to keep the presets readable.

First, hit update presets (on the 5.19) before updating. then update to something like 7.18 (after 5.23 before 8.0). hit update presets again. then update to the latest.
 
javajunkie said:
Right, I believe you for 5.19 to 10.2 you need to update in 2 phases to keep the presets readable.

First, hit update presets (on the 5.19) before updating. then update to something like 7.18 (after 5.23 before 8.0). hit update presets again. then update to the latest.

Ok I've never done that but only use my own presets and always tweeked/stared from scratch after an update. Does this mean the newer parameters don't work on my Axe? I just figured they were subtle? Maybe freaking for no reason so if Jay/Java can just say yes/no to what I said/did ie Do newer parameters work having not 'Hit update presets' I would appriciate :)

Mark
 
Jay Mitchell said:
It's really pretty easy if you read the release notes. Because a number of firmware revisions introduced parameters and functionalities that were not present in previous ones, they came with an "Update Presets" command. Executing this command does the necessary housekeeping to translate old parameter settings and to initialize new ones that were not present before.

The bold bit in the above is what freaked me, initialize new parameter...... :)

Prolly just ment settings but I wanna make sure.
 
ESP MM-270 said:
javajunkie said:
Right, I believe you for 5.19 to 10.2 you need to update in 2 phases to keep the presets readable.

First, hit update presets (on the 5.19) before updating. then update to something like 7.18 (after 5.23 before 8.0). hit update presets again. then update to the latest.

Ok I've never done that but only use my own presets and always tweeked/stared from scratch after an update. Does this mean the newer parameters don't work on my Axe? I just figured they were subtle? Maybe freaking for no reason so if Jay/Java can just say yes/no to what I said/did ie Do newer parameters work having not 'Hit update presets' I would appriciate :)

Mark

Yes, newer parameters work fine.

Occasionally Cliff changes the format of the presets. He maintains compatibility for at least one version back (usually a lot more). There has been a few times where the update all presets have been necessary. Before 5.23 and 8.00 are 2 of them.
If the presets were too old and you did not hit the update presets button or had not saved the preset (which accomplishes the same thing, I believe), the would not show up once you upgraded. It would appear as a blank preset. To get it back, you would have to downgrade to a lower firmware, hit update presets, then upgrade again.

I have not seen the update preset have any effect on parameters, As far as I have seen, any changes in paramters have to be reset manually. This is pretty much always noted in the release notes.
 
ESP MM-270 said:
[quote="Jay Mitchell":1u33raa9]It's really pretty easy if you read the release notes. Because a number of firmware revisions introduced parameters and functionalities that were not present in previous ones, they came with an "Update Presets" command. Executing this command does the necessary housekeeping to translate old parameter settings and to initialize new ones that were not present before.

The bold bit in the above is what freaked me, initialize new parameter...... :)

Prolly just ment settings but I wanna make sure.[/quote:1u33raa9]


I could be wrong but I don't think it initializes or translates parameter settings. There have been many updates not requiring the update presets that have added new parameters.
 
OK, I'm almost ready to begin the upgrade process. I've spent some time recording 30 second clips of all my patches to remember what they sound like. 126 patches took a while to record. I think my upgrade path will be:
Update current 5.19>5.23 ( + update) > 6.09 ( + update) > 7.18 ( + update) > 10.02.

My question is; what's the correct syntax for accessing the old firmwares. I see it's covered here;
http://axefxwiki.guitarlogic.org/index. ... ersions.3F

And the example links will work either by clicking on them, or copy and paste into the URL, but using the same syntax below will not;
http://www.fractalaudio.com/Documents/V ... ra7_01.zip
or
http://www.fractalaudio.com/Documents/V ... /ultra7_01
or
http://www.fractalaudio.com/Documents/V ... ultra7_01/

I’ve also tried it in Firefox, as compared to Safari.
Any help would be greatly appreciated.

Finally, I'm really looking forward to the new features when the upgrade is complete. I'm not sure what I was waiting for. Lots of nice new amps and feature.
 
StudioCat said:
OK, I'm almost ready to begin the upgrade process. I've spent some time recording 30 second clips of all my patches to remember what they sound like. 126 patches took a while to record. I think my upgrade path will be:
Update current 5.19>5.23 ( + update) > 6.09 ( + update) > 7.18 ( + update) > 10.02.

My question is; what's the correct syntax for accessing the old firmwares. I see it's covered here;
http://axefxwiki.guitarlogic.org/index. ... ersions.3F

And the example links will work either by clicking on them, or copy and paste into the URL, but using the same syntax below will not;
http://www.fractalaudio.com/Documents/V ... ra7_01.zip
or
http://www.fractalaudio.com/Documents/V ... /ultra7_01
or
http://www.fractalaudio.com/Documents/V ... ultra7_01/

I’ve also tried it in Firefox, as compared to Safari.
Any help would be greatly appreciated.

Finally, I'm really looking forward to the new features when the upgrade is complete. I'm not sure what I was waiting for. Lots of nice new amps and feature.

http://www.fractalaudio.com/Documents/V ... ra7_03.zip

There were probably bugs in 7.01 so it may have been pulled
 
Back
Top Bottom