midiin/ctlin doesn't see CC anymore if already seen ..??

Dec 20, 2013 at 5:52am

midiin/ctlin doesn't see CC anymore if already seen ..??

Hi everybody !
Sorry for my english, this is not my native language :)
Here’s my situation : I’m building a very simple patch that uses midiCC in, and use footboard FCB1010 for debugging.
Problem is when I load the patch (or liveset), the first trigger of a CC ctl (like CC1 value 127 channel 1) is seen in M4L as expected, ok good…
but when I trigger this exact same CC once again, it is not seen anymore in Max4Live… nothing appends no output, nothing (midiin nor ctlout nor midiselect).
When I then try with another CC (like CC2 value 127 channel 1), same thing happends : the first one is seen, but none of the ones after it…

The only thing working is the exp pedal, which sends DIFFERENTS CC values on (almost) each time…

SO I’m guessing Max4Live is bypassing incoming CC data if the value is the same as it has last reveived from this channel/number couple, it only forwards data if the value is different…

Plus Ableton itself sees right ALL of the CC, yellow square is flickering, data incoming is showing in the track In, AND I can use right the native MIDIMAP feature of ableton, to trigger a clip for exemple, it reacts as expected…

I’ve just updated MAX4LIVE to the latest version, same occurs, does anyone get the same pb ? Is there a way to make it work correctly…?
Thanks you all

#276288
Dec 20, 2013 at 8:15am

Consecutive equal CC values are filtered by Live. It’s oft-complained about.

-A

#276304
Dec 21, 2013 at 2:53am

ok thanks andrew…
guess I will have to find another way, FCB1010 can send midinotes too… might be the solution.

Thanks again

#276349

You must be logged in to reply to this topic.