Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m frustrated

M-Audio Code 61 Keybed cannot send maximum value in any velocity sensitive mode

Hello.
I am a proud owner of the M-Audio Code 61, but I've just found an issue.
It seems I cannot send a maximum velocity signal of 127 from the keys no matter how hard I hit them. It will send 127 at a Velocity Setting of VF3, but any of the VC1-4 settings cannot send anything higher than 126. This is a BIG PROBLEM. Can it get fixed via a firmware update?
2 people have
this problem
+1
Reply
  • Just some more info -

    The sensitivity to high values above 124 (so, 125 and 126) is disproportionally low compared to anything below. To get a velocity value of 125 I have to strike the key very hard/fast. So hard/fast that I'm afraid to damage the unit. This MUST be fixed.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hi,

    Sorry you are having trouble with this.

    What are you using to test the velocity response with? A midi monitor?

    What software are you using with the Code? I'll have to look a little further into this on my end, but for the time being, the velocity response for the software may be adjustable. You could use this to potentially turn down the velocity response for highest level so that the samples are easier to trigger.

    Let me know and I'm sure we'll figure something out!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I'm using Ableton Live Suite 9 to record a midi track and view the recorded velocity.
    I have no issue sending maximum value with Oxygen 49 (3rd gen), Oxygen 25 (4th gen) and an Akai MPK Mini MK2. The Code is the only controller that I'm having issues with. Live has a velocity midi effect, which allows remapping the velocity, but it's not an applicable long term solution at all.
    It seems like either a off-by-one error in the firmware or something similar. Either way it seems internal. I really want to love this controller. Please tell me you can fix this :)

    P.S - this is a Windows OS.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • This reply was removed on 2015-09-26.
    see the change log
  • I’m sad
    After some experimentation with MIDI-OX I've observed the following:

    In VCrVC1 it's easy to get 124, but anything higher requires bashing the keybed. Highest I managed is 126.
    In VCrVC2 it is almost impossible to get velocity values higher than 118. (weird)
    In VCrVC3 as described earlier - can't get higher than 126.
    In VCrVC4 I've been able to get 127 occasionally. Still had to strike the keys quite hard.

    It is also impossible to avoid triggering aftertouch values when trying to achieve higher velocity values due to striking the keys with high force.

    From experimentation I've gathered that the velocity curves are as expected when playing lightly. VCrVC1-3 exhibit expected exponential curves from Low to High and VCrVC4 shows expected linear response (although it feels slightly exponential, as lower velocities are inconsistent). That is UNTIL you try to reach higher values, where you seemingly hit the ceiling of the sensors.

    The issue is definitely firmware related, as the sensor values are mapped to a range too high. A narrower sensor value range map to the velocity values in a firmware update would fix the issue entirely.

    Please, this issue needs to be fixed.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Thanks for being patient.

    We have released a firmware update to address this issue along with a few other updates. Please download the firmware installer here:

    Code Series - 1.0.3 Firmware Updater for Windows 7/8/10

    Code Series - 1.0.3 Firmware Updater for Mac 10.9.5 - 10.11

    Run the updater after it's been installed and follow the on-screen instructions to update the firmware. Try to make sure you do not have other USB devices plugged in that may interfere and avoid using any USB hubs or long cables while updating.

    Let me know how it goes!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I've just performed the upgrade. The keybed is much more responsive now! Thank you!

    It reset all my custom settings, which is expected. One new thing I noticed - the presets now have different names. It used to be PRE01-PRE12, but now they're named along the lines of HY-ABL or LM-PT. I understand this is to mirror that the presets are made for Hyper and Loom running in different DAWs. Is there a way to name presets now?
    • view 3 more comments
    • You need to dump a preset. Then I used a hex editor to change the name and uploaded it back.

      P.S. Sorry, I should have provided more detail. You need to use the MEM.DUMP function on the Code to dump the preset and save it using a SysEx librarian. On windows this functionality is provided by MIDI-OX. On Mac, I think there's just that - SysEx Librarian. After you've dumped the file you can open it with a Hex editor. On windows I used HxD. I don't know what you can use on a Mac, but it shouldn't be difficult to find an alternative. After you open the file you should see the name of the preset in the first several bytes. You can replace these bytes to change the name, but you need to keep the same number of bytes - six. You can't name something like "CUSTOM_PRESET" since it's too long, and it will offset all the other data. If the name is shorter - you should insert some spaces, like "MINE ". After that, save the modified SysEx file and use the librarian to send it back to the code. I found that to see the changes you need to switch from the preset and back again. I'll upload a photo of a custom name I made later.
    • Thanks for this!

      I did verify that changing preset names is not currently possible from the keyboard, but I will be happy to submit this as a feature request. I hope this process will at least suffice for the meantime.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I downloaded the update for my code 61 but when I open app it just shows a image ,? it doesn't say what to do? I've attached screen shot
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m sad
    Logic seems to be working okish, unfortunately a lot of my plug ins aren't working at all on the new OS X :( I should have known better!
    • Hi Jon,

      Sorry you are running into that. Unfortunately, that seems to be a known problem with that update. Supposedly, there is a new Beta version out now that fixes some problems but I'd still recommend waiting until that's fully released:

      https://ask.audio/articles/apple-fix-...

      Once Logic is running properly, the setup should be exactly the same unless there were some updates to Logic that I'm not aware of. I'd recommend to turn of any auto-updates for your system to avoid things like this. It's always good measure to wait a little while before updating, but unfortunately a lot of us learn that the hard way.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hi Corey, I was GC, and luckily they had a Code to ry on the floor. I loved the feel of the keys. I am worried about one poster that mentioned that the keys rely on one set of springs, and that playing a chord bends the keyboard?

    Also, because this is M-Audio and a part of Avid, can I safely assume that this is the best controller for Pro Tools 12 that is currently out?

    Thanks.
    • Hi Jake,

      I'm not sure on the build of the keybed but I haven't seen any problems with the keyboard or other keys bending or moving out of place when hitting a chord. I can't seem to recreate that myself. Obviously, the keybed should not bend or move when hitting any keys and as far as I have seen that's not a problem with these boards.

      M-Audio is actually completely separate from Avid now, since about 2012. But the keyboard is supported for use with Pro Tools. We have a setup guide that you can check out here:

      http://www.m-audio.com/kb/article/1869

      Let me know if you have any more questions!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • hello to everyone here, i have question. I recently bought m audio code 61 and installed an update in previous PC 32-bit , windows 7( on display wrote UPDATE), after that i bought a new pc 64-bit same operative system and purchased an updater again and it doesnt recogize a midi keyboard. I am using FL studio.
    i really need your help..
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Hi, Nikola. You're more likely to get help if you start a new thread specifically about your issue (this is an old thread about Code velocity settings).

    Also, consulting the knowledge base is always a good idea:

    http://www.m-audio.com/kb

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

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