Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLAP and Reaper text input issue. #7382

Closed
JoeMegalos opened this issue Dec 10, 2023 · 1 comment
Closed

CLAP and Reaper text input issue. #7382

JoeMegalos opened this issue Dec 10, 2023 · 1 comment
Labels
Bug Report Item submitted using the Bug Report template

Comments

@JoeMegalos
Copy link

Bug Description:
When using the CLAPi in Reaper and renaming a preset the space bar is captured and toggles playback instead of being used for naming. Normally handled by enabling a Reaper option "pass all keyboard input to plugin" but that is greyed out with the CLAPi version. This doesn't happen with the VST3i version or a CLAPi I tried from Full Bucket which implies this is specific to the CLAPi of Surge.

Oddly, I've found that I can enable the Reaper keyboard input option when I first load the CLAPi but haven't tried to edit anything. If I don't enable it and try to rename the preset it captures the space key as I described and the input option is greyed out in the FX container menu.

Surge XT Version
1.3.0

  • Version:
  • Plugin Type: CLAPi
  • Bitness: 64

Computer Information (please complete the following!):

  • OS: Windows 10
  • Host: Reaper
  • Version: 7.06

I hope that's enough to go on. Let me know if you need more info or if it's something better brought up with the Reaper folks. Thanks.

@JoeMegalos JoeMegalos added the Bug Report Item submitted using the Bug Report template label Dec 10, 2023
@mkruselj
Copy link
Collaborator

mkruselj commented Dec 10, 2023

This is just how it is with JUCE CLAP extension produced CLAPs in REAPER, AFAIK. Not much we can do here. Full Bucket is using iPlug so that's the discerning factor here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Item submitted using the Bug Report template
Projects
None yet
Development

No branches or pull requests

2 participants