Widget link with special note properties

Is it possible to link a widget to a keyboard note that only triggers when the velocity is, for example, over 100? I can’t set such a value in the widget properties.

There is no such property
What do you want to achieve?

In my specific case: I play a note with a velocity greater than 100. Then, a widget should be triggered that initiates a fade-out of a channel strip from the audio mixer (I already have this routine in my template). However, I also play this note several times during the song – but at a velocity of 100. In that case, the fade-out shouldn’t be triggered. Therefore, my only option is to trigger the fade-out with a hard keystroke. I only need the fade-out when I’m playing a hard keystroke.

Use scripting to trigger the fadeout

You can accomplish this by setting the velocity minimum in a MIDI IN block from your controller, routing the signal to a MIDI Out (Local GP Port) block, and then mapping the widget via the Local GP Port. Just make sure you aren’t using any Omni blocks.

OK, clever solution.
But a 2nd MIDI In Block is needed for playing the regular note

Yes, that is true.

I am a dedicated script user, but unfortunately not a programmer.

I started using GB in September. I used to have several local port blocks. GB was crashing a lot. I wasn’t sure if I had created a MIDI loop, so I deleted all local ports from the gigfile. The crashes stopped. Now I’m afraid of using local ports.

For me, the most appealing solution would still be the ability to differentiate NoteON based on velocity. Before GP, I used Logic – that’s how I was used to it.

Ok, but this is literally the stated purpose of the MIDI Out (Local GP Port) block.

It just occurred to me: The fade-out is already started by a script. But it’s triggered by a note. And that note should only be triggered at a velocity higher than 100.

I can try it again, but if crashes result (because I might be programming poorly), then I’ll remove local port again.

You were probably using MIDI Omni blocks…those blocks are intended for beginners to get up to speed with GP but eventually one should switch to MIDI In blocks explicitly associated with ports

I can’t say for sure whether I used Omni blocks in my initial programming attempts. I don’t think so, though. Now all inputs are correctly and explicitly assigned to my MIDI patchbay.

I’ve now implemented the suggested solution. However, I only have one MIDI In block. One cable goes to the instrument. A second cable goes to the Local Out. The MIDI In block only sends notes louder than 100. And the widget works exactly as I envisioned, always for notes louder than 100. I hope my fears about the Local GP Port were unfounded.