I've found any Fractal factory presets are automatically updated and use the latest Quantum 4.0 modelling.
Any presets you made yourself previous to updating will have to be manually set to 'latest', found in preamp tab of Amp block in Axe-Edit
Check it out with Axe-Edit.
This is not what I am finding at all.
I loaded Q 4.0 and then scanned through my factory presets and for example, CE-1 Chorus shows 2.04, Comp Cln shows 2.04, 1959 SLP show 3.xx, after searching a bunch of them, I don't find any at Q 4.0 and yet my system and axe edit clearly show 4.0 is loaded. Even if I freshly import a factory preset it still shows Q3.xx.
I find this really frustrating. Does this mean I have to step through 384 factory presets to manually bring them all up to Q 4.0?
I get the feeling that I'm in the minority here but I think that if I load Q 4.0, I should expect to hear all my presets using Q 4.0 without having to spend hours telling each and every one of them that yes, I really do want to use 4.0!
For those people who have a small number of highly developed presets and want to compare 4.0 to 3.xx, they are already committed to spending hours if not days on a particular preset and will switch back and forth between 4.0 and 3.xx many times, so it doesn't really matter if the preset starts off in 4.0 or 3.xx or whatever.
Those of us who simply want to run with the best that Cliff has to offer and use that as our starting point, starting out in 4.0 saves us a lot of work especially if, for example, you rely on the factory presets as your starting point and want to hear them all in 4.0 or if you've purchased presets from an external source ( e.g. Fremen ) and want to hear them in 4.0.
One other point, if this is the way that we will be going in the future, it would be nice to have the Modeling Version Option at the top of Axe Edit, so that you don't have to drill down so far into Axe Edit (Preset->Amp->Pre-Amp->Revision ). With a small # of presets, no big deal. With having to convert 384 of them, it adds up.
Mentioned this earlier, but a batch conversion tool that reads a file with a list of presets and modeling version as data pairs, could make this approach work for everyone. At the very least, having a set of factory presets available that were set up to use 4.0 as a default could also save some time.
End of story --- back to manually converting the factory presets to 4.0!