Show Cue System

I am using a Yamaha PM5D with my SCS rig. I have enabled 4 user defined keys on the console to send a "note on" message. When I am on the midi test page of SCS Editor I can hit those keys and see activity. I get 2 entries for each key press. 1 entry for the midi note at velocity 127 and another at velocity 0. I can't seem to set what velocity I want to be the trigger velocity. So what happens is I hit the key I've assigned to trigger the "Next" command and it triggers twice, once on the 127 and once on the 0. Any ideas what I am doing wrong?

What the PM5D seems to be sending is "Note On Velocity 127" for "Note On", and "Note On Velocity 0" for "Note Off". I'll make a change to SCS to treat "Note On Velocity 0" as "Note Off", which will prevent it being treated as "Note On". ("Note On Velocity 0" is an accepted alternative for "Note Off" in MIDI standards.)

I should be able to get this change into 10.4.1, which I am planning to release soon.

One curious fact is that this only seems to affect "go back" and "go to next" commands. It does not do a double "Go" command. Is there a setting that requires a minimum time between "GO" commands to eliminate double triggering a "GO" command?

newrob1 wrote:Is there a setting that requires a minimum time between "GO" commands to eliminate double triggering a "GO" command?

Yes - see General Options / Permanent Options. The 'Double-Click' Timeout field contains this setting. The default is 0.4 second.

That fixed the midi triggering issue, thanks. Now I have a new problem, I have been using SCS 9 instead of 10 because with my RME Fireface 800 the clips hiccup when playing. Not so with SCS 9. Any ideas?

Hi Mike,

We've just run into exactly the same problem (PM5D sending two Note On messages, one with Vel=0 when the button is raised) causing double-triggering on one of our running shows that we've just upgraded from an earlier version of SCS 9, to SCS 10.4.0. We'll update it to 10.4.1 when we get a chance (the crew reverted to SCS 9 as they were under pressure), but we are curious as to why the problem didn't occur on SCS 9 - when the PM5D was presumably sending the same double-message. Did SCS 9 not recognise a note on with velocity 0, or was the default double-click time longer, perhaps?

Cheers,
nick

Hmmm - you're right that it was in SCS 9. The MIDI processing in SCS 10 was optimised and this special case somehow got left out. However, the change I have now made in SCS 10 to convert a "Note On velocity 0" to a "Note Off velocity 0" is slightly better than SCS 9, which completely ignored "Note On velocity 0", ie threw it away.