eric larrieux

i forgot to come back to update this post, but the folks at cycling confirmed that there was actually a bug with the software.

the problem was with the midi controller (see below)

I recently "discovered" the newish (as of max 8) xctlin object, which is a welcome change over manually parsing 14 bit CCs, and a more general solution than the "assign midi map" feature, so this is more of a PSA for others who might benefit from it because I didn't find much about it while researching the topic.

That said, I did find a weird bug where it doesn't respond to the first message arriving on a different channel after a standard 7 bit message is received. More details in the attached patch.

comment

number

message

midiin

button

xctlin

ctlin

EDIT... AGAIN:
i forgot to come back to update this post, but the folks at cycling confirmed that there was actually a bug with the software.

EDIT: [SOLVED]
the problem was with the midi controller (see below)

~~~~~~

I recently "discovered" the newish (as of max 8) xctlin object, which is a welcome change over manually parsing 14 bit CCs, and a more general solution than the "assign midi map" feature, so this is more of a PSA for others who might benefit from it because I didn't find much about it while researching the topic.

That said, I did find a weird bug where it doesn't respond to the first message arriving on a different channel after a standard 7 bit message is received.  More details in the attached patch.

14-bit-midi-xctlin

Interesting. I tested it quickly with another controller (other CC numbers and other channel numbers) and cannot reproduce. It's tough to send just one value with faders, so I added [print] and a counter to make sure I received the same amount of messages from xctlin and ctlin.

From what I see here, it's working. I will try again later if I can have more time.

Interesting. I tested it quickly with another controller (other CC numbers and other channel numbers) and cannot reproduce. It's tough to send just one value with faders, so I added [print] and a counter to make sure I received the same amount of messages from xctlin and ctlin.
From what I see here, it's working. I will try again later if I can have more time.

You're right, Jean-Francois. Cycling 74 support suggested testing the problem using the IAC driver and everything worked fine, so it seems to be an issue with the midi controller i'm using. Thanks for looking into it.

You're right, Jean-Francois.  Cycling 74 support suggested testing the problem using the IAC driver and everything worked fine, so it seems to be an issue with the midi controller i'm using.  Thanks for looking into it.

If you're on Mac, also try MIDI Monitor ( snoize.com ), a great little open source app to observe MIDI traffic. That might help you find out what's going on.

With different CC numbers and other channel numbers, I quickly tested it with another controller and was unable to duplicate it. With faders, it can be challenging to convey a single value, so I added [print] and a counter to make sure I received the same number of messages from xctlin and ctlin

With different CC numbers and other channel numbers, I quickly tested it with another controller and was unable to duplicate it. With faders, it can be challenging to convey a single value, so I added [print] and a counter to make sure I received the same number of messages from xctlin and ctlin. 

14 bit midi / xctlin