Softube plugins, manual data entry not working

[FSM77]

Hi there
As the title suggests, I cannot edit any of softube's plugin parameters using my laptops number keys or numerical pad, and I cannot name any user edited patches using my laptops keyboard. Is this a global Mulab issue? Or just me?
Steve.

[MuTools]

Is this on Windows or Mac?

[FSM77]

On windows. It been happening for a long time.

[MuTools]

I tried MuLab Plugin in MuLab App and it accepts keyboard input as expected.
Do you have any other plugins, non Softube, that use keyboard input?
Are these accepting keyboard input as expected?

[FSM77]

Yes, no problems with other vsts such as Synapse, Korg, Cherry Audio... these all allow typing of new patch names and data entry where applicable. Its a very strange thing that softube plugins including vst2 and vst3 are ignoring keyboard entry.

[FSM77]

Ive also tried this with Mulab 8 with the same results. Just incase it was a version thing.

[MuTools]

So it seems Softube specific, right?
Did you already contact Softube about this?

[FSM77]

Yes it's softube specific. I could raise a ticket with them.

[FSM77]

I might try Windows' virtual keyboard as a work around. (Windows+ctrl+O)

[MuTools]

I think a plugin editor that needs keyboard input should call GetFocus() on their own plugin window, which is a child window of the host window, when the user clicks inside that plugin window.

[pljones]

(As a developer - although not VSTs, etc - I could understand why someone might think "user clicks inside window" gives the window focus unless the focus event is explicitly rejected - like in normal app windows. But I can also see why in a Host/Plugin context, the host would want to know explicitly that the plugin wanted to take control of the keyboard events.)

Does MuLab just silently drop unused keyboard events when a user has a plugin window selected, if that plugin didn't explicitly request them?

[MuTools]

MuLab uses the standard Windows procedure: Unused (keyboard) messages are returned to the DefWindowProc().

[pljones]

I also notice that Reaper's own JS plugin system doesn't get it right. Click into a text input field and hit Ctrl-A to select all the text in the field... nope, it selects all the plugins in the track (if you've got the channel plugin view open). So this is definitely not a MuLab-specific problem.

[FSM77]

After googling this problem I found a forum where the advice was to use each plugins preset manager pop-out window, in which, you can type in your new preset names