some (!) keyboard shortcuts do not work as expected in CLAP in REAPER

[Rundraster]

Hello there,
this is my first contribution here.
Of course i've used the search function here, and was surprised that this seems to be no issue already.

By using the CLAP version of Surge XT, some (!) keyboard shortcuts do not work directly. Not until i activate "Send all keyboard input to plug-in" in plug-in options as a workaround.
Is that the recommended way to work with the CLAP version in Reaper?
In the VST3 version they work instantly, without that workaround.

In CLAP, these shortcuts DO work also instantly here:
Ctrl+F
Alt+F
Alt+A
Alt+O
Alt+K
"+"
"-"
Shift+"+"
Shift+"-"
Shift+Left
Shift+Right
F1
F12

The reason could be that these are not bound by Reaper itself here, so no override appears, EXCEPT for the keys "+" and "-". They ARE bound with Reaper actions. Hm...

Version: Surge XT 1.3.4.f7b97c6
Build Info: 2024-08-11 @ 16:02:24 on 'fv-az292-728/pipeline' with 'MSVC-19.40.33813.0' using JUCE 7.0.12
System Info: Windows 64-bit CLAP on Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz, 8 GB RAM
Host: Reaper @ 48000 Hz
Processing Block: 32 samples

Windows 10
Reaper 7.33
Bitness: 64

[baconpaul]

I wonder if we need to apply surge-synthesizer/sst-clap-helpers@d4e0fbe to the clap juce helpers

I’m traveling with Mac only right now but can look at that this week sometime

[mkruselj]

CLAP doesn't have keyboard handling the way VST3 does. So it is going to behave differently.

[baconpaul]

yeah but that juce hack/trick basically gets around al the keyboard handling.

reaper doesn't implement the vst3 keyboard handling logic at all - it seems only cubase live and s1 do - and so the difference between reaper vst3 and reaper clap is almost definitely the application of that juce trick which basically snags the windows event loop, and which in surge will be on in the vst3

[mkruselj]

Noted!

[baconpaul]

Another “would haven’t have found without six sines” gem!

[Rundraster]

Oh cool. Thanks for noting and caring!