Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Code 61 Rotary Sensitivity

I had this crazy idea that turning a rotary on my Code 61 midi controller would have a 1:1 relationship with the knob on my DAW (FL Studio 12). I know it sounds CRAZY, but bear with me. I was not a huge fan of the acceleration that is used by default on the Code 61. If I turn it 30 degrees on the controller I expect a 30 degree change on my DAW regardless of how fast I change it. I have tried modifying the settings but can't achieve this behavior... or anything remotely close to this behavior.

The first thing I did was read the manual and found the curve settings for the encoders. I changed the curve value to ECrVOf (no acceleration). I thought, "GREAT this is exactly what I need!". It did remove the acceleration, BUT the speed is now FAR too slow. If I want to go from the minimum value of 0 to the maximum value of 127 I have to make more than 4 full revolutions (1440 degrees). That aside the readings are somewhat inaccurate, especially at low speeds.

Regardless, one problem at a time. Is there ANY way to reduce the resolution of the encoders so that roughly one revolution equals a change of 127 in the midi value of the encoder? Turning it one full revolution and only seeing a quarter revolution on my DAW is not something that I would consider "acceptably accurate"

I know that other people have asked similar questions about M-Audio controllers in the past 3 years at least with little more than a less-than-genuine "We care about your feedback, (just don't expect us to prove it)" response and I know you guys have been working hard to get aftertouch working (which is working well now as of firmware 1.2).

It truly is a pity because I love everything else about this controller, but I didn't pay all that cash to make use of 70% of the needed controls that the controller provides.
4 people have
this question
+1
Reply
  • Corey S (Official Rep) June 07, 2016 13:40
    Hi Nathan,

    Thanks for posting! Sorry you are having trouble with the knobs.

    The knobs on the Code series are very high resolution to support the acceleration feature. To help this work better for your purposes, you may just want to try different acceleration curves instead of turning it off entirely. Velocity curve 01 should be fairly 1:1, but you may still notice a slight acceleration jump if moved too quickly. I think this may be the best one for you.

    Personally, I use the highest velocity setting. It may take some getting used to if you're not familiar with accelerated knobs but I think it makes automating volume changes a lot easier.

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

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

  • 1
    Nathan -- in Logic Pro X there's a field in the controller assignments panel called MULTIPLY that let's you scale incoming MIDI signals. The default is 1 (it's a ratio). But if, let's say, you want your parameter to change more than it currently is when you turn the encoder you could bump that up to something like 1.5.

    I haven't used FL in a very long time, but is there anything similar in FL that might solve you're problem?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m frustrated
    @Corey So in summary, no, there is nothing I can do to get what I want with the current firmware and no, there is nothing M-Audio will do about it. I would settle for getting the development toolchain for the firmware and changing it myself, but I'm willing to bet that M-Audio is more concerned with protecting trade secrets then helping customers in this case as well.

    @STF Possibly but then you lose accuracy. With a 4x multiplier I can only have 31 (127/4) possible values. If midi allowed for a greater resolution then this wouldn't be a problem, but it may be the only solution since M-Audio isn't willing to do anything about it.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • 1
    Hey, I strongly agree with Nathan. I got my code 49 a couple of weeks ago and the rotaries don't feel right to me either. All the previous midi keyboards I had (including Axiom 61) had a great feel and a 1:1 relationship with the connected event which means 1 full circle of the rotary goes from min to max.

    I can't get used to the acceleration, it feels so awkward. Sometimes I get the result that I want but most of the time is frustration. I played with all the curves but none seem to work for me. So I ended up not using them at all and using only the x/y pad.

    Setting a multiplier from the software side can remedy the problem but indeed the resolution is decreased dramatically, and since a 1:1 relationship needs the rotary to rotate around 4 times to go from min to max then you end up having a resolution of 31 steps which is too low and also the DAW needs to support this feature.

    The most effective way is for the firmware to be edited. If the firmware multiplies the received data from the hardware interface then it can assign that multiplied input to a range of 0-127 and that would make all of us happy (acceleration lovers and haters!) and that would be great!

    Then, an extra couple of settings can be introduced in the Edit function that could add a couple of options for that feature like:

    ECrVx2: 2x Multiplication
    ECrVx4: 4x Multiplication

    or ideally but a bit harder to implement...

    ECrVxN: Custom Multiplier (requires user input).

    I can understand, being a firmware developer myself, that most of the time work is a matter of priority. I'm sure that the devs have already plenty of work to do but I guess they would agree that implementing this is not a big hassle either and it will get a lot of people happy!

    Thanks for reading, I really hope this gets implemented and I'm looking forward for the upcoming firmware updates!
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Is there any firmware fix for this yet? It kind of surprises me that unaccelerated motion is not the default. I mean, no analog gear I know of have accelerated knob movements.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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