Need help with m-audio axiom 49

[rsmus7]

I just got a used axiom49,

and it looks like new,
but I have one problem.

I tried all different velocity curves,
but it is almost impossible to hit the keys with a velocity above 120.
If I hit very hard, sometimes it reaches 123 / 124

and it looks as if the velocity is somehow randomly.

when I play as I used to do with my former keyboard,
I get only velocity values up to 110 - 114.

the touchpads have no problems with the high velocity values,
only the keys. ???

Anyone else experinencing this?
Or can the axiom be broken?

[Sascha Franck]

I think, while not being exactly normal, this is quite common. Reaching values over 120 is getting tough on a lot of controllers (I hardly manage at all on my SY-85).
But then: Does the Axiom have some velocity curve menu? Most proper master keyboards have something like that.

[rsmus7]

I think, while not being exactly normal, this is quite common. Reaching values over 120 is getting tough on a lot of controllers (I hardly manage at all on my SY-85).
But then: Does the Axiom have some velocity curve menu? Most proper master keyboards have something like that.

hi Sascha,

yes it has different curves, as I said above,
but none is really usefull for getting a velocity of 127

[Sascha Franck]

Hm, ok, sorry.
Guess it's still better than my mobile thingy, an Edirol PCR-M1 - which has two keys that don't throw out anything but velocity 127.

[rsmus7]

the axiom is imo a very nice masterkeyboard, with loads of features,
but for soundprogramming I need to try the sounds with 127,
so it would be nice if I could do it without breaking my fingers
or the keys.

I mailed m-audio support, gonna see what they answer.

[.jon]

It is also possible to send fixed velocities each time you press a key. This is useful when composing drum parts or simple synthesizer
tracks. The fixed velocities are selected by assigning curve 10 to 12 as follows:
Curve Fixed Velocity Value
F10 64
F11 100
F12 127

[Sascha Franck]

I guess fixed velocities aren't that useful when programming synth sounds, as you usually want to check out the dynamic response.
However, Stephan, to me it seems that most sounds are already at "full effect" with velocities around, say, 120 - so it might not be that much of a drawback. In addition, doesn't your host offer something like a MIDI velocity expander? Logic and Cubase do, and they're certainly useful sometimes.

[.jon]

Curve 1 gives me the highest velocities, but you really need to slam it :-/ I've never noticed this before.

I do love my Axiom, it has changed the way I make music. It feels fantastic compared to other budget controllers and better than many synths, just a joy to play. The transport buttons couldn't be better placed, I can toggle record while playing with two hands perhaps one of the best single improvements in my kit ever.

[BertKoor]

Work-around: hush over to www.midiox.com and install MidiYoke + MidiOx.

Fire up MidiOx. Options - Data Mapping - Insert:

These settings should convert incoming velocity of 110 to 127.

Then use MidiYoke to wire the output of MidiYoke to your application.

[Sascha Franck]

Does MidiYoke also offer some scalable stuff?
Must be like ages since I used it for the last time...

[rsmus7]

It is also possible to send fixed velocities each time you press a key. This is useful when composing drum parts or simple synthesizer
tracks. The fixed velocities are selected by assigning curve 10 to 12 as follows:
Curve Fixed Velocity Value
F10 64
F11 100
F12 127

I know about the Fixed Values,

but thats not what I want.

[rsmus7]

Work-around: hush over to www.midiox.com and install MidiYoke + MidiOx.

Fire up MidiOx. Options - Data Mapping - Insert:

These settings should convert incoming velocity of 110 to 127.

Then use MidiYoke to wire the output of MidiYoke to your application.

thx,
that could be a work-around,
but the axiom is also usefull as a midi controller and has it's own mapping e.g. in Live6,
I dont know if that will still work with midiOx.
But I will try it.

[BertKoor]

Yeah, it should still work. I think the mapping in Live maps the faders/knobs/buttons that send CC data to VST parameters or your master fader or whatever, like a midi learn function.

[rsmus7]

I got an answer from m-audio,

they say it is natural, because there is an aftertouch-stripe under the keys,
that dumps the velocity.

So I gonna try the work-around.

[ew]

I got an answer from m-audio,

they say it is natural, because there is an aftertouch-stripe under the keys,
that dumps the velocity.

So I gonna try the work-around.

That's a bullshit answer from M-Audio, Stefan

I use an Xboard 61 myself; it transmits full velocities PLUS it has aftertouch...

Also, if that were the case, how do all the hardware synth manufacturers get around it? My old VFX-SD has poly AT and still transmits the full velocity range. With that, there's one sensor per key. If ANYTHING would have issues, you'd think it would be that.

ew