No, the whole point of editing software is ease of use. Offline editing is merely a feature.Really, the whole point of having editor software is for the very purpose of using it offline. If you have an Axe-FX in front of you, you can simply use the front panel as everyone did for the time when there was no Axe-Edit software.
I can't think of another piece of audio gear that limits the editor usage to online only.
No manufacturer of a digital mixing console, for example, would ever create an online-only version of their editor. It would be pointless and they would definitely lose sales because of it.
No, the whole point of editing software is ease of use. Offline editing is merely a feature.
And.. that is why AE v3.* was re-written from scratch to poll settings from the hardware and why offline editing was removed. [/I]AE can keep up and no longer requires a release for each firmware.
None taken, but I can assure you - I was far closer to the situation than most, and have full appreciation and understanding of why FAS made the decisions they did regarding offline editing.No offence but not so true. It's just 1's & 0's. It may be harder to properly align the 1's & 0's for off-line editing but certainly very doable and still being able to keep the same "upward mobility" that we've all come to enjoy. It may mean reading the latest sysx and creating a "virtual Axe-Fx" in memory/cache that can "polled" when a real one is not available. Lots of possibilities. While the physical box is magical, it's not THAT magical.
Thank you for your reply.Those who've been around here for some time are well aware of the limitations and challenges faced by earlier versions of AE, which USED TO support off-line editing for Standard, Ultra and [initially] AF2 models. It was a PITA and caused all sorts of issues with coding, regression testing and matching releases of AE as each new firmware from Cliff [usually] required coding changes to support new features (eg: Tone Matching, Scenes), and mapping between preset versions created with each firmware to support version compatibility for offline editing.
And.. that is why AE v3.* was re-written from scratch to poll settings from the hardware and why offline editing was removed. AE can keep up and no longer requires a release for each firmware.
These same folks are also aware that the FREE prolific firmware upgrades from Cliff do NOT occur with most other "audio gear". Those platforms tend to be more "stable" and if you look, you will find that offline editing usually occurs ONLY for compatible firmware/editor versions.
For example.. (you mentioned consoles).. my B*ringer X32 and Presonus 16.4.2 editors support offline edits.. but both require firmware versions match the editor and are not backward compatible. So settings saved with X32 v2 firmware editor cannot be loaded into an X32 v1.6 firmware loaded console.
Think I'll stick with getting new firmware versus offline editing in AE.
And.. that is why AE v3.* was re-written from scratch to poll settings from the hardware and why offline editing was removed. AE can keep up and no longer requires a release for each firmware.
Also, your point about the editor being useable with different firmware is simply wrong. The other day I downloaded the latest editor, 3.1.0 at the time, and tried to connect to my guitarist's Axe-FX which had 13.07 on it. What do you know? It wouldn't allow me to connect until I updated the firmware.
So the whole argument of not needing to have the firmware match the editor version is simply false. It might have been the intention, but it's not the way it actually works.
As I say, the original concept has failed, so the "advantage" to the new paradigm is moot.I think you're both right. I haven't been around that long (firmware 9 I believe) but I believe both points are valid on certain releases. Some releases you need to upgrade the editor and others can "get by" but just not always getting all the new things...but still useable for most editing tasks.
I haven't tried that, but will (when I get time). The editor should update stored blocks/parameters to match the firmware.. tho' to be honest, idk if 3.1.0 supports 13.07 - that's fairly old.Also, your point about the editor being useable with different firmware is simply wrong. The other day I downloaded the latest editor, 3.1.0 at the time, and tried to connect to my guitarist's Axe-FX which had 13.07 on it. What do you know? It wouldn't allow me to connect until I updated the firmware.
It doesn't. I'll bet each release of the editor only supports the firmware available at that time. i.e. when a new firmware comes out, so does a new editor. Check it and see if you like, I've only tested 3.1.0 with 13.07.idk if 3.1.0 supports 13.07 - that's fairly old.
Been busy, gigs, etc. and haven't had time to reload older firmware/AE versions to confirm your observations... and may not have time in the near future to do so (work, gigs, etc.). Meanwhile, it is what it is..Hmmm... It suddenly got very quiet in here... [emoji88]
Yes, you are correct. The truth is, the editor has NEVER worked with ALL/ANY version of the firmware, not even back in the days when the Std/Ultra were the only available FAS models. The developer(s) tried to support it (along with offline editing), but as I mentioned already.. there's a whole plethora of challenges caused by frequent firmware upgrades.I understand. It's an important point though that any single version of the editor DOES NOT work with any version of the Axe-FX firmware, and people should stop touting that as a benefit of the new paradigm.
The 'challenges' with proper coordination between AFX and Editor should be very simple.but as I mentioned already.. there's a whole plethora of challenges caused by frequent firmware upgrades.
The 'challenges' with proper coordination between AFX and Editor should be very simple.
When a firmware is released that the current editor doesn't support, a new Axe-Edit is released, just as happens currently.
If an old preset is opened in an offline version if Axe-Edit, it gets coverted to the be a preset matching the version of Axe-Edit, just like it does now when loaded into the Axe-FX.
If loading a preset newer than the version of Axe-Edit or the Axe-FX is attempted, AE or AFX simply rejects it.
All pretty simple. So what's the big challenge? Nobody has actually ever said.
I commute an hour x 2 every day on a bus between Central Joyzee and NYC.
Obviously, this would be huge for me - I could build on the bus and tweak at home.