FWIW, I know we've taken a lot of heat over Axe-Edit and rightly so. Ultimately I'm the one to blame (as in "the buck stops here"). I suppose the one thing I am most guilty of is giving people too much benefit of a doubt. Ultimately, though, I had to make some difficult decisions and that involved doing something no manager enjoys. In retrospect I should've made that decision far earlier.
The good news is the new software team is fantastic. I check in with them every morning and they are making great progress on Axe-Edit and the associated programs. Axe-Edit is now at the point where the edit menus are being completed. I was given a working demo this morning where you can edit the grid and change parameters in some effects (including most notably the amp block). The underlying framework is mostly complete and now it's just the grunt work of editing XML files and cleaning things up. At the current rate of progress I expect a beta version soon. I can't give a hard date yet but I wouldn't be surprised if it was early July or even sooner.
I believe you will all greatly enjoy the new editor. It finally implements my vision of an "RPC editor" (as in Remote Procedure Call) where the Axe-Fx does all the work and the editor is mainly a remote terminal. This ensures that presets cannot be corrupted and should lead to vastly greater stability.
