Axe-Edit 1.9 is offered as an unsupported beta. It contains bugs, though we believe those which might cause data loss have been solved or identified.

Here are the most important issues to be aware of:

1. Axe-Fx II Firmware version 10 or newer is required.
2. Only the AXE-FX Source is fully supported. When using PRESET FOLDER source, pressing SAVE will save to your Axe-Fx instead of your computer; When using BANK FILE source, pressing SAVE will save to your Axe-Fx instead of your computer. The latter problem is thought to exist under Windows only. For all versions, SAVE AS:Export to Preset File does not work for BANK or PRESET FOLDER sources. No file is created on the disk.
3. Creating backup banks from within Axe-Edit may be unreliable, though some testers reported no problems. Note: Backup capability will be added to Fractal-Bot by the end of April 2013. Meanwhile, for 100% reliability, use MIDI-OX or Snoize, or use the onboard BACKUP utilities located on the PRESET page of the Axe-Fx UTILITY menu.
4. An issue makes this beta slower and less smooth than previous versions. Working too quickly can cause stability problems. Many of these can be solved by selecting another block in the grid, then returning to the one you were working on. Watching the MIDI I/O indicators can help you avoid problems.
5. Some testers had problems with constant crashing. These were solved by restoring a clean system backup to their Axe-Fx. Note that this overwrites all user cabs in your hardware. This file can be downloaded from http://www.fractalaudio.com/downloads/firmware-presets/axe-fx-2/10.0/FW10-SYSTEM-CLEAN.syx
6. Hue/Sat/Bright/Contrast sliders in GUI prefs are disabled.
7. After COPY X to Y, values on screen may be incorrect. Manually change X/Y switches to refresh
8. Axe-Edit Total Sync is problematic. It is recommended that this be left disabled (under Settings/MIDI)
9. Axe-Manage may have undocumented bugs. Be sure to have backups of any data that you handle using this application.
10. Working with MODIFIERS can sometimes cause crashing.
11. Other issues are detailed in release notes (note that release notes may refer to version 2.0, a status which this beta did not attain.)