M-audio Code keyboard - pitch bend issue

Please someone with M-audio Code series keyboard compare these (I have Code 61 with latest firmware, but I think that all Code series works the same):
A. I checked pitch bend performance with 'BOME MIDI Translator' and I have:
1. maximum value: 8064 (0x1F80)
2. minimum value: -8192 (0xFFFFE000)
3. first value moving upwards: 512 (0x200)
4. first value moving downwards: -768 (0xFFFFFD00)

B. In practice it means:
1. I can't achieve maximum values in my DAW using pitch bend wheel (keyboard's screen shows 127 but in my DAW parameter I see e.g. 197 instead of 200, 124% instead of 125%)
2. The slightest movement up of pitch bend wheel cause jump of the value from 64 to 69; I can't achieve e.g. 66 or 67 (on keyboard's screen)
3. The slightest movement down of pitch bend wheel cause jump of the value from 64 to 58; I can't achieve e.g. 62 or 60 (on keyboard's screen)

C. Graphical representation:
1. http://i.imgur.com/0B7RAJN.jpg

This keyboard is really good, but this could be better (of course I hope that my keyboard isn't broken)...
Describe your results. If Code series are like this, maybe M-audio can improve it with firmware update.
4 people have
this problem
+1
Reply
  • Hi Ted,

    Thanks for the detailed research!

    I'm going to have to look into this a little further. It doesn't seem like something that would just be a hardware problem, though. I'll let you know what If I can recreate something similar.

    Thanks!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Hi!
    Did anyone find a way to fix this? I'm having exactly the same problem with my one week old Code 49. MIDI keyboard screen shows the value going up to 127 but the DAW (FL Studio 12) is stuck at +1181 cents, when it should go up a whole octave. Bending downwards works just fine. The problem started occurring today and the keyboard isn't damaged or anything, it's almost brand new.
    • view 1 more comment
    • Hi Corey,

      Thank you for your reply.

      MIDI Monitor says the max value is 127 and in MIDI-OX the pitch bend goes to 7F. Tried reseting it to factory defaults, but my DAW still can't do a full bend.
    • Hi Markus,

      If the Code is hitting 127 than it sounds like it's hitting the max pitch bend range. I would double-check that your pitch bend settings in your DAW are set correctly for your purposes.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Hi.

    My Code 61 (Firmware 1.2.2) does the same thing. It jumps from 64 to 55 when going down (which is extreme), and from 64 to 67 when going up. It's also not very precise, sometimes jumping by two numbers and such (watching the keyboard display).

    The graphical presentation that Ted posted is very similar to mine.

    Anyone found any solutions?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Mine jumps from 64 to 55 when bending down. There's no issue with bending up (the next step on the display is 66, but any recorded bends sound seamless enough).

    If you record a sequence in Reason and examine the data, you'll find that it always jumps directly from 0% to -14.1% when bending down. It's impossible to make Reason catch anything inside that span, simply because the Code 61 isn't sending it.

    14.1% of 64 = 9, which happens to correspond exactly to the 55-64 gap in display values. So it's definitely not a display issue. The display is actually doing its job here, unlike the bend wheel.

    Furthermore, it has nothing to do with the DAW. Reason, Logic, whatever... the 55>64 gap is still there. When I plug in another keyboard to said DAWs (I've tested with Axiom Pro 49 and Korg microKONTROL), pitch bend is even across the range.

    This is a dealbreaker and I need to know whether it's a software issue or if all Code 61 have shipped with faulty components, in which case I'll have to replace it with another product. Currently I have to do a lot of time consuming editing to smooth over the bend down gap.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • My Code 61 has gone one step further. Now when I touch the PW, it returns to 46 or 47 causing a real tuning issue. It stays at that value by default. Factory reset and latest firmware don't fix it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • I’m frustrated
    I have this exact problem as described by Fredrik Hägglund, above, save for slightly different values.

    This is a grab of a recorded downward pitch bend in Reason:



    As you can see there is a huge step at the start corresponding to the display on the keyboard that shows the data going from 64 - 54 with no steps in between.

    On the advice of M-Audio UK phone support, I updated the firmware and factory reset the device. Neither of these suggestions had any effect. I have since arranged for a replacement from Amazon on the further advice of M-Audio UK support. I'll let you know how the new one is.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • New, replacement Code 25 arrived, today and the pitch control is better, jumping from 64 - 58, so it's still not great.

    Can't say I'm happy with the support offered and lethargic staff response to this issue. You've got crappy pitch controls in this line of equipment, either it's something in the firmware, or the hardware itself and I'd appreciate a proper response from M-Audio.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • I have the same problem, from 64 to 55. But the great problem is not only the gap, is that when I'm playing often the pitch wheel moves a little bit and the pitch of the entire instrument is afected by this gap, making that keyboard unable for playing live.

    Does any user or anyone in the m-audio team has found a solution of this issue? I've got my keyboard updated, I did a factory reset... I've used the keyboard with Logic pro X, Ableton live and Mainstage 3

    Code 61 is my first experience as a m-audio user and I must admit that I'm really disappointed with this keyboard
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • I'm having the exact issue... and also sometimes the pitchbend starts to act crazy when I'm recording... I thought M-Audio fixed that issue with the Code... Because I had an Axiom Pro before and had the same annoying problem...
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated indifferent, undecided, unconcerned