I have observed that there are two distinct camps of Axe-Fx II users vis a vis firmware updates:
1. Those that need backwards compatibility with their existing presets, and;
2. Those that don't.
Judging from the many posts by "FractalAudio" (Cliff Chase personally, if I understand correctly), Fractal is engaged not only in an amazing ongoing development, but also in supporting (or at the very least, trying to support) backwards compatibility with existing user presets.
My concern is that if Fractal needs to ensure backwards compatibility with user presets created in previous firmware versions, this inevitably draws a significant amount of time and energy away from the otherwise unfettered process of developing the best possible results obtainable from the existing hardware. Perhaps it even imposes limitations.
I belong to the camp that does not require any backwards compatibility whatsoever. To me, the Axe is just an amp. It just happens to be the best amp in the world, and it happens to have a lot of controls. When I update firmware, I start from scratch (happily!). Like someone noted in another thread, getting new firmware is like getting a brand new amp. (Plus it's free and you get to keep your old amp!!! Some guys out there just don't seem to get this but I digress....)
I want Fractal to know that I don't need backwards compatibility. In fact, I think that the concept is counter-intuitive. The interaction of virtual components is far too complex, and you're never going to get the most out of it if you don't start from scatch and use your ears. No offense is meant to the backwards-compatible guys, but I have a hunch that the start-from-scratch guys are a much-less-vocal majority.
Anyway….those are my thoughts on the matter. My objective is simple: I (very thankfully) would like to see Fractal squeeze the absolute most out of the existing hardware, and if ignoring backwards-compatibility helps that cause, then screw backwards-compatibility. Remember, FW updates are optional.
Mack
1. Those that need backwards compatibility with their existing presets, and;
2. Those that don't.
Judging from the many posts by "FractalAudio" (Cliff Chase personally, if I understand correctly), Fractal is engaged not only in an amazing ongoing development, but also in supporting (or at the very least, trying to support) backwards compatibility with existing user presets.
My concern is that if Fractal needs to ensure backwards compatibility with user presets created in previous firmware versions, this inevitably draws a significant amount of time and energy away from the otherwise unfettered process of developing the best possible results obtainable from the existing hardware. Perhaps it even imposes limitations.
I belong to the camp that does not require any backwards compatibility whatsoever. To me, the Axe is just an amp. It just happens to be the best amp in the world, and it happens to have a lot of controls. When I update firmware, I start from scratch (happily!). Like someone noted in another thread, getting new firmware is like getting a brand new amp. (Plus it's free and you get to keep your old amp!!! Some guys out there just don't seem to get this but I digress....)
I want Fractal to know that I don't need backwards compatibility. In fact, I think that the concept is counter-intuitive. The interaction of virtual components is far too complex, and you're never going to get the most out of it if you don't start from scatch and use your ears. No offense is meant to the backwards-compatible guys, but I have a hunch that the start-from-scratch guys are a much-less-vocal majority.
Anyway….those are my thoughts on the matter. My objective is simple: I (very thankfully) would like to see Fractal squeeze the absolute most out of the existing hardware, and if ignoring backwards-compatibility helps that cause, then screw backwards-compatibility. Remember, FW updates are optional.
Mack