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

Search modules keyboard input produces duplicate of input key #54

Closed
jp-gorman opened this issue Dec 1, 2021 · 5 comments
Closed

Search modules keyboard input produces duplicate of input key #54

jp-gorman opened this issue Dec 1, 2021 · 5 comments

Comments

@jp-gorman
Copy link

Version Tested: SHA builld - 4a85fc8

Expected:
Rick click to open dialog for adding module
Type "a" to see all modules starting with "a"

Actual:
Type "a" and get "aa".

Just FYI - I confirmed double lettering was not happening on Rack2 official release.

@falkTX
Copy link
Contributor

falkTX commented Dec 2, 2021

This is on Windows, correct?

@jp-gorman
Copy link
Author

OSX 10.15.6 - Reaper 6.19 64bit vst and vsti versions.

@AriaSalvatrice
Copy link

Keyboard input in Windows is host-dependent with a variety of weird behaviors.

So far:

  • Reason 11: Behaves as if the Shift key were stuck, only uppercase and no spaces
  • Renoise: Won't accept keyboard input even after the keyboard is explicitly enabled in renoise's ui
  • VSTHost: Text fields add a letter on key down and on key up both

@falkTX
Copy link
Contributor

falkTX commented Dec 5, 2021

To explain, this is because VST2 defines a method for hosts to notify plugins of keyboard events.
But typical of things in VST, exactly how to implement is not documented well so every host does it a bit differently.

Some hosts do not send the special VST2 keycodes at all, only relying on native OS events.
Others send both.
And finally a few ones only send VST2 keycodes, never OS events.

The whole thing is quite silly and PITA to implement and get right...

@garygeeg
Copy link

Can happens in Reaper on Windows for me but Ableton is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants