Ableton Forum

I've got this weird "bug". It took me a while to figure out what is happening.

All I want to do is take an incoming relative CC (value of 63 when turning the knob CCW, 65 CW), and use it to increment/decrement a value.
In PLAIN Max, it works just great with any CC number.
But when loaded as a M4L device in a MIDI track (monitored to IN), it only responds correctly to CC #0. All the other CCs are acting as if they were only sending the CC value when it changes.
Is Live blocking repeating CCs values for every CC except CC #0 in Track Input ?

Here's a max patch example : <pre><code>
----------begin_max5_patcher----------
681.3ocuWtsaiCBDF9ZmmBj0dYZUvmTxd29brZUD1glRkMDA3roppu6KGLMN
aww3VmbCNFFO+LeLd7j2VDEWxNgEwfeB9MHJ5sEQQlozSD0ceTbC5TUMRXLK
l11Th4wKsKoti0JqwRyhIcyJjuViMV6r6.RV8LgteKGWIsxsN6wUKAvTyk7U
5wD0H3OcOh0uxWOfs1q7EHtDQ2G+gIG3XAlJQRBiNAOS1Y1arxWdn37FjiZv
RLeKlhJs69UmCRB0EiP8buuXgdXYnLC+WkXNoj3SlMZr.Hp3r55s+xONWMEb
VXh4MP8khjOEyCfpQdpdjJMO9FiCInD7.bFxrrAEzbvmVLdhkIoRkbQnx3v.
1f9tGvfo2CfMG7JKsePkNu.aLm2mXI2ZhgppZa7SL3zyvxLuvjkMNvBOyZPe
1mSPubJcFqLgqAEofhb+rJcxrZs43Oec34VtqgwsA8eOrsY1nVCVHP6wdvlD
7C3bkekXFyfA7kwfXzf9qGix7xnju.ipIGwOpaVPYUmOOh3T0GYGZY+UvFhN
YmeOAlOVaCOUyPA9F3P9sGjRtVSCPukvbG9ni3caQRImT1Jwm+knijcnTyp5
VL6I2zt46qoKF6ZS3h0ZoD4GYZ9LnlQ2ekCiKrU7LiK8Zr0VSlg6x7T.pRVS
nfUyUy.4og9pjtR8TZEXPO2ud8neVy7TJxR++dwMAjd9KQnf0xqba4tZafyZ
uCKjDpY+1yFcCIZi7dJMEgfiITxLHTVHQzLnSR.5jMC53n+0CH3boDLDkfeW
kRtawTxcKlfADSEWXCiuS8Oh0EZu8Jq+aX9jF98jN.k27oiQaUKzgCGwbQmw
FITk3egY1VqWZtkPs2Z9RTLGej3r2NChqJaKUUVa41B5mJrchD2vTAHskzEi
Jkeew+.My5Mm
-----------end_max5_patcher-----------
</code></pre>

In fact, Live blocks repeating CC values except for CC#0 and CC#32 (bank, subbank).

Thanks a lot. I'm not crazy.
Any other idea to use a relative CC to increment/decrement a value ?
I use it to scroll i a umenu populated with lots of files.

Any reason why you can't use MIDI Learn for that parameter?
Give a dial a float value so you have more than 128 options. Then all you have to do is scale the menu length to a 0.-1. range.
There are nastier workarounds than this, but that'd involve using plain Max or some other remapper.

hoffman2k wrote:Any reason why you can't use MIDI Learn for that parameter?
Give a dial a float value so you have more than 128 options. Then all you have to do is scale the menu length to a 0.-1. range.

I need to try this, but I thought it would still give me 128 values in the end.

Well, it won't work in my case.
The smallest division it can output seems to be 1/333 of the range, regardless the min and max values. The umenu is currently populated with ~500 items so it not precise enough to scroll through all items.

I suppose using an integer might work if large enough. A dial with a range of 16384 for example.
Though its weird you only get 1/333th division. When working with relative encoders, I usually work with inc & dec objects and use the offset from 0 or 127 to calculate the steps to move.
Plenty of ways to go about it. Just using a CC as intended would be way to easy for MFL