I put a sustain pedal widget in with cc64 going to it from my pedal, it’s getting it to control sustain within Kontakt on Chamber Strings that seems to be a problem. In stand alone mode it just recognises the incoming controller but within GP there doesn’t seem to be anywhere to map it.
I’m travelling for a few days but will look at global midi monitor as soon as I can.
Thanks for replying.
Don’t do that. That’s why it’s not working. When you associate a widget with a physical control, the control is blocked by default. It’s beyond the scope of this conversation to explain why that’s a good thing (it is😀) but for your purpose, get rid of that widget and it will work
Bedtime here now. Travel the next few days. I’ll be back on it on the 26th and will try to post things then.
Appreciate the help . . I’m just starting with this program, although not new to programming midi/editing.
Just got home [late]
Here is a screenshot of wiring and midi.
Expression and mod get through but no sustain. Shows in midi window.
I think it must be a problem from Spitfire [when hosted in GP]
OK – so you have a block that is just named “MIDI In” — what’s the actual device?
Also, could you please play a couple of notes as well as pressing the Sustain so we can see ALL the events coming in, not just the Sustain events.
Yep, the problem is that your notes are coming in from one device (irig keys), which you have connected to Kontakt but the CC64 events are coming from a different device (MIDI Expression Black, whatever that is)
Right that sorted it. Thanks
I had mapped the expression pedal [via the midi expression box] to a widget which is why that was working.
FYI Audiofront midi expression . . very handy https://www.audiofront.net/MIDIExpression.php
Thanks for the help.