S
Swan1
Guest
I like the idea. I had once suggested that they create a utility that converts previous firmware patches to the newest firmware as Fractal knows what has changed in each update and by how much. This way the sound would sound the same (or very close to it).I still think there may be ways to compromise on this issue - by making it easier to recover from an upgrade. What about focusing our requests on the AxeEdit team instead of the modeling code? Since AxeEdit has to reread the block defs after every upgrade, how about asking for a way to highlight where they don't match so we can easily see what parms need to be checked after the update? Highlighing deep parms that will get reset? Asking if we want to reload default deep parms, or keep existing?
The point is, I think there are ways to simplify the recovery process - which may make the frequent model updates much easier to handle.
Just my opinion obviously...
RR