Nano Control CC MIDI messages trigger twice

Ah, I see.

SoundFlow has built-in support for filtering Note On and Note Off messages to make sure this kind of thing doesn't happen.

If the device is sending CC values, then this issue would be expected, for exactly the reason you specified there.

The only real way to address this would be to either:

• Have your device send Note On/Off messages (as they would be automatically filtered for you, so only velocity>0 goes through for Note On messages)

• Or, add some code to the top of your script to filter out CC messages with a value of 0.

The 2nd step requires no changes to your device, but it does require you to convert your macro into a script.

Once you've converted your macro into a script, you can insert this code at the top to filter out any MIDI message with a value of 0:

if (event.trigger.midiBytes[2] === 0) throw 0;