Mulab keyboard input12/12/2022 ![]() Note that for our solution with, it is not necessary to tick the Send all Keyboard Input to Plugin option in Reaper. Yes, there is something like this in Sonar, too: It seems that other hosts like Cakewalk Sonar has this option too… Its not user friendly and i think most users do not know about that feature, but its there and maybe a useful work around. Otherwise a right click on the plugin name on the left. In the floating window mode: a right click on the top of the plugin window shows the context menu. I just figured out that there is a Send all Keyboard Input to Plugin option in reaper. If the host has added a keyboard hook to catch all key events, there’s no way we can tell it when we’re using the keypresses and when we’re not. Reaper does its default behavior instead and starts playing the song.Īlmost certainly impossible to do anything about that from the plugin’s side. The SPACE key does not work in Windows Reaper (other keys work). Mulab keyboard input license#It seems to work on almost all hosts, as people need this to insert their license keys, and we rarely get complaints (I think it still does not work in some host from Magix and in MuLab). Just checked a 64bit plugin from us in 64bit Reaper on Windows 7 and we get the Space key, based on the latest JUCE 1.x release (was it JUCE 1.4?) But we do a dirty trick, using when our text editor gains the focus - see also my old post on this in this thread. OSX VST works and its possible to enter SPACE’s into the TextEditor. ![]() The same happens with the AU version in Reaper OSX. Reaper does its default behavior instead and starts playing the song. I’m having following issues (above fix not included): I do not know much about that keystroke issue, but i’m not sure if this is something that should be fixed for specific hosts. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |