Ant Music
Fractal Fanatic
There a many different devices and even Apps that now compete with Fractal. Some of them look and sound amazing and offer a variety of pros and cons with their own individual appeal. Having been a long time Fractal user I find it difficult to ignore some of the different directions and advancements made by other companies etc.
Whilst Fractal has well and truly set the standard for tones and modelling accuracy I think User Interface is something that that has taken a back seat. I'm thankful that we now have a robust and stable Axe Edit but I have seen a number of other devices and apps that are far more immediate and intuitive.
One thing I find disappointing is the fact that when modelling a device like a Drive pedal, an Amp or a Delay the Axe Fx displays a generic set of controls for tone shaping across all modelled devices (particular to that device type). For instance all of the Amps have the exact same set of controls available.
When trying to emulate the authentic tone and behaviour of a particular device I often find myself just wanting access the actual controls that are native to the real device and nothing more. I often feel the wide and varied generic controls are of course incredibly useful but I'd prefer to have an additional tab in Axe Edit listed native which would give ONLY the controls that are specific to the actual device. Perhaps even an idealised graphic of the device as is seen in the BIAS apps would help to make the experience of tweaking far more intuitive.
Of course deeper parameters control should be available but there is a tangible barrier between clicking and scrolling on a computer screen and using familiar real world hardware. It is far too easy at least for me and others I've spoken to, to get overloaded and bombarded with options. Whilst it is easy to say "Just use your ears" someone less confident in their tweaking can wonder if they are taking the right steps toward achieving their tone and begin to second guesse their own inuition and thus down the rabbit hole you go. One can easily think they are doing something wrong in the face of so many options.
I find it much easier to get positive results quickly when starting out with an accurate model, (which the Axe Fx has) and a limited number of real parameters native to the device. in the example of an Amp Block; If you can't get the desired tone from the modelled device with the native controls then perhaps it's more likely this is not the Amp for you and not a result of hap hazard tweaking. Move on and try another one instead of menu diving and an endless and thoroughly unenjoyable tweakfest.
I think ultimately the Axe Fx is an incredibly complex and capable tool but having confidence in using such a complex instrument is not always so easy to come by. By providing a list of native parameters it is much easier for one to have confidence that they are achieving the authentic tones of the device as if it were there infront of them with the added bonus of deeper controls should they desire them. Sometimes, less is more.
Whilst Fractal has well and truly set the standard for tones and modelling accuracy I think User Interface is something that that has taken a back seat. I'm thankful that we now have a robust and stable Axe Edit but I have seen a number of other devices and apps that are far more immediate and intuitive.
One thing I find disappointing is the fact that when modelling a device like a Drive pedal, an Amp or a Delay the Axe Fx displays a generic set of controls for tone shaping across all modelled devices (particular to that device type). For instance all of the Amps have the exact same set of controls available.
When trying to emulate the authentic tone and behaviour of a particular device I often find myself just wanting access the actual controls that are native to the real device and nothing more. I often feel the wide and varied generic controls are of course incredibly useful but I'd prefer to have an additional tab in Axe Edit listed native which would give ONLY the controls that are specific to the actual device. Perhaps even an idealised graphic of the device as is seen in the BIAS apps would help to make the experience of tweaking far more intuitive.
Of course deeper parameters control should be available but there is a tangible barrier between clicking and scrolling on a computer screen and using familiar real world hardware. It is far too easy at least for me and others I've spoken to, to get overloaded and bombarded with options. Whilst it is easy to say "Just use your ears" someone less confident in their tweaking can wonder if they are taking the right steps toward achieving their tone and begin to second guesse their own inuition and thus down the rabbit hole you go. One can easily think they are doing something wrong in the face of so many options.
I find it much easier to get positive results quickly when starting out with an accurate model, (which the Axe Fx has) and a limited number of real parameters native to the device. in the example of an Amp Block; If you can't get the desired tone from the modelled device with the native controls then perhaps it's more likely this is not the Amp for you and not a result of hap hazard tweaking. Move on and try another one instead of menu diving and an endless and thoroughly unenjoyable tweakfest.
I think ultimately the Axe Fx is an incredibly complex and capable tool but having confidence in using such a complex instrument is not always so easy to come by. By providing a list of native parameters it is much easier for one to have confidence that they are achieving the authentic tones of the device as if it were there infront of them with the added bonus of deeper controls should they desire them. Sometimes, less is more.
Last edited:
