Agreed, it sucks, but this isn’t what Ctrlr is for. Ctrlr is aimed at providing a software surface within a DAW which maps input to CC/sysex controls on hardware synths. The Axiom doesn’t have any hardware which can be controlled by CC or sysex; in fact, it’s got more in common with Ctrlr itself than it has with a hardware synth. The Axiom *also* maps user input (either by playing the keys or by sending commands over USB from a DAW) to a sound-producing synth, whether hardware or software.
Enigma is designed specifically to deal with the Axiom’s on-board operating system – it speaks the same language, and that’s a language M-Audio probably keeps to itself. Even if it were possible to change the Axiom’s mappings via CC or sysex (which I kind of doubt), Ctrlr would still be an inappropriate tool as it doesn’t do any sysex librarian stuff, nor can it store snapshots or controller templates. Enigma is still the best way to program your Axiom and will probably remain so.
I have an Axiom 61 (and used to have an Axiom 49), and for the most part I leave it set to its defaults. If I need to map it to software, I abstract the values in the DAW using things like Ableton Live’s MIDI-learn function. If I use it to control hardware, I send everything through a computer first anyway.
If you’re asking in general if somebody can create this, not necessarily with Ctrlr (because, like I say, this is not what Ctrlr is intended for), then yeah, I’m sure it’s possible…but it would be a massive amount of work and would mostly be replicating work that M-Audio have already done. I doubt you’d find a programmer who could get interested in reinventing the weel, even if there was an opportunity to make it a *slightly* more user-friendly wheel ” title=”Wink” />