Possible bindings bug

I just discovered a possible bug in bindings in build 3189. I was trying to set up two bindings triggered on song state load, to send a MIDI Note On to a plugin, and then 1000ms later a corresponding MIDI Note Off. I set up bindings as follows:

If I manually trigger the Note On binding, the note starts, and then if I trigger the Note Off binding, the note stops, as you’d expect. However, if I try to trigger these bindings off Song State load, I actually get two Note Off messages, one after the other with the 1000ms delay. So for some reason the first one is coming through as a Note Off instead of a Note On.

Curious!

Neil

Hi Neil,

Yep, this is a bug. It’s actually sending a note on but with velocity zero. I’ve changed the way this works a little - you used to be able to specify a velocity for note on events but that ability is not showing atm and it’s defaulting to zero. Basically there’s a mapping/UI/display issue.

I’ll fix it. In the meantime a work around would be to set the Action column to Note/Mapped and enter the note number in the value column.

I know… not very intuitive but should get you going for the moment.

Brad

1 Like