plugdata-team
[bug] - plugdata-fx vst3 keyboard focus - space bar
Encountering issues here, varying from DAW to DAW on macos 13.6.7 with the keyboard focus of the plugin window.
Logic is often not usable due to various errors, so i gave up on it for now.
Reaper only has one big problem, and that is, that the space bar is assigned to play/stop. When the plugin in window is open, then hitting space while typing objects
- example: sendspace{variable} triggers Reaper play/stop instead of typing a space into the object container.
A workaround here is typing shift-space instead of just space, just mentioning.
Thank you for all you do.
Can you try changing the shortcut to alt-space or something other than space to see if this fixes this for you?
Can you try changing the shortcut to alt-space or something other than space to see if this fixes this for you?
@alcomposer Did so now (sorry took some time to evaluate). Turns out, that taking out the spacebar from the shortcuts solves it for empty object boxes.
However the error still occurs, when typing text into into comment boxes.
I might be wrong, but I think the issue in REAPER is fixed by enabling the "Send all keyboard input to plugin" option!
As for Logic, I use Logic myself so I'm very familiar of this problem. I've been trying to fix it for a while, but I still have no idea why it happens :(
@timothyschoen Thank you, i needed that hint, so for Reaper this is solved. As that doesn't tackle the general issue I'll try testing with sthg. other than Logic as well, and will report back then. It seems obvious, that there must be sthg. buggy in the vst3 export somehow, as any other plugins i use do not have a keyboard focus problem. Now i wonder: What do Reaper's devs might know about this?
Do you know of a way to consistently recreate this problem in Logic? For me it only happens some of the time, pretty randomly. That makes it hard for me to find out where it goes wrong
@timothyschoen @alcomposer Logic behaves erratic here, too. Using it very rarely myself - and hey it's AU.
I've now checked on Cubase 12 under macos 13.6.8: No problems with keyboard focus.
I suspect, that Nuendo will also work, but still will have to test.
I still wish, that there was a 2-track only version of plugdata, so that WaveLab would work, as indicated in #1724. Besides Sequioa Wavelab is the best there is for Mastering, and being able to write our own mastering plugs in PlugData sounds like a possible major gain.
If there was an AAX version (commercial) for Pro Tools i could check here, too. However, i do not think, that this will be necessary, as customer groups differ too much from Puredata users - and creating the plug requires a commercial license. So let's not.
I just encountered this issue in Bitwig (v5.2.1) using the VST3 plugin. I tried creating [param<space>1] but am unable to enter the space, which toggles playback.
The shift-space workaround works for me, but removing the spacebar binding (mentioned above) seems to have no effect.
Other bindings are affected as well, (such as ctrl+z, ctrl+n, ctrl+s) which seem to be sent to both the plugin and the DAW. In the case of ctrl+z, however, often the last item in the DAW's undo history is the creation of the plugin instance, so undoing causes the plugin to be removed from the project.
The shift+ctrl+z shortcut also appears to have no effect within the plugin.
And to add further context, Bitwig also just started recording undo history for VSTs in v5.2, so that may or may not be complicating the issue.
Looks like the problem in Logic is really a bug in either Logic or macOS:
https://forum.juce.com/t/bug-m1-apple-silicon-keyboard-focus-lost-permanently-in-logic-when-plugin-is-resized/51292/26
@timothyschoen @alcomposer Logic behaves erratic here, too. Using it very rarely myself - and hey it's AU.
I've now checked on Cubase 12 under macos 13.6.8: No problems with keyboard focus.
I suspect, that Nuendo will also work, but still will have to test.
I still wish, that there was a 2-track only version of plugdata, so that WaveLab would work, as indicated in #1724. Besides Sequioa Wavelab is the best there is for Mastering, and being able to write our own mastering plugs in PlugData sounds like a possible major gain.
If there was an AAX version (commercial) for Pro Tools i could check here, too. However, i do not think, that this will be necessary, as customer groups differ too much from Puredata users - and creating the plug requires a commercial license. So let's not.
I think this vst host incompatibility is partly related to my own issues currently where internally plugdata says it exposes 32 inputs and 32 outputs iwhen probed for vstinfo, but to the host itself says it only supports 2 chanels of i/o. Usually if a plugin tells the host it supports 2 channels, it won't have a vstinfo of anything above 2 channels, so I think this is gonna cause lots of issues in vst hosts. I justs tried in Cubase, Nuendo, Studio One, DAvinci REsolve and plugdata will not work correctly as an fx insert there. The DAW will simply bypass plugdata entirely above 2 channels as plugdata told it to by reporting 2 channel support only. However internally the plugin is still 32 channels i/o it seems.
However, when placed in a host following vst3 specs t othe letter, plugdat.vst3 is only telling it about 2/2 i/o and this causes many VST hosts issues. e.g. I've not been able to run plugdata.vst3 on anything Steinberg > 2 channels. Neither Cubase or Nuendo will work correctly if e.g. you place plugdata.vst3 on a track with > 2 channels. It breaks the DAWs internal routing it seems. Same in Davinci Resolve and many other hosts too.
