Wish An off-line edtor mode?

Sauro_on_guitar

Inspired
Vendor
Is there a precise reason why it is impossible to use the editor in offline mode (without ax8 being connected)? It would be very useful to do it, you could practice using the editor and learn many functions of the machine, or organize or rename presets etc ...
 
Just because it existed on the AxeFx II beginning but quickly tend to produce presets inconsistency and errors
 
why it's not possible? Just let save changes in a new preset when exit from the offline editor and if you want to use the new preset with ax8 you have to import it.
 
Well TBH it's very possible but it would be dangerous if the offline editor doesn't follow each new firmware change
What can be dangerous about that? And how is that different than loading a preset created with an older firmware?

Not arguing here, just curious :)
 
What can be dangerous about that? And how is that different than loading a preset created with an older firmware?

Not arguing here, just curious :)
Because the offline editor would have to know each firmware difference and be updated with each firmware.
You'd say "today's editor is updated with each firmware too". Yes, but each editor update is only a layout change or parameter add.
With an offline editor, each update would have to handle what the axefx firmware also handles, like parameters transformations when value ranges change,
parameters defaulting when a major upgrade is introduced, creating non-existing parameters when loading an old preset and saving to a newer version,
loading old presets with very different parameters etc... programming nightmare
With client/server architecture used in today's editor, this nightmare is centralized in a unique place : the axefx firmware.
 
Because the offline editor would have to know each firmware difference and be updated with each firmware.
You'd say "today's editor is updated with each firmware too". Yes, but each editor update is only a layout change or parameter add.
With an offline editor, each update would have to handle what the axefx firmware also handles, like parameters transformations when value ranges change,
parameters defaulting when a major upgrade is introduced, creating non-existing parameters when loading an old preset and saving to a newer version,
loading old presets with very different parameters etc... programming nightmare
With client/server architecture used in today's editor, this nightmare is centralized in a unique place : the axefx firmware.
Thanks for the explanation, that makes sense
 
Back
Top Bottom