Virtual keyboard loses focus

[nicenoise]

In 3.0.43 the virtual keyboard frequently loses 'keyboard focus'. Clicking on the keyboard still works but pressing A..J doesn't. Reselecting QWERTY from the drop-down box fixes it. It happens about once a minute on this PC and often when switching VSTs or programs.

Also it would look nice if the keys were drawn 'down' when clicked on. Maybe that's in 3.1 - haven't tried that yet.

nn

[MuTools]

The Virtual Keyboard window only receives keystrokes when it is focussed, that's normal. When you start working with another window, then that window looses the focus, that's normal too. When Virtual Keyboard window is not focussed just click on it to activate it. Does this answer/solve the issue?

[pdadda]

Would it be difficult to implement an "always on top" option for the virtual keyboard window? That way one could change VST parameters with the mouse while still being able to play notes on the computer keyboard.

[nicenoise]

Would it be difficult to implement an "always on top" option for the virtual keyboard window? That way one could change VST parameters with the mouse while still being able to play notes on the computer keyboard.

On my (Windows) PC running M3.1.25 you can still play with the A..J keys while another window within MU.LAB has focus, which is very nice. The problem I have is that it periodically stops responding to the A..J keys and only starts again when I click the 'Keys' drop down menu on the virtual keyboard. Oddly I don't need to re-select 'QWERTY' in that menu - just dropping the menu down is enough to bring the keys back.

First I thought it only happened when I switch away from MU.LAB and back again, but it happens within MU.LAB as well, seemingly at random.

[MuTools]

Would it be difficult to implement an "always on top" option for the virtual keyboard window? That way one could change VST parameters with the mouse while still being able to play notes on the computer keyboard.

Ok, i've made a test version 3.1.26 where the Virtual Keyboard keys will also be processed when the Virtual Keyboard window is not focussed. This is done by giving the Virtual Keyboard a special treatment. It's a bit of experiment so please feedback whether it works fine all the time.

You can download the 3.1.26 test patch version (Windows only, if all ok OSX version coming soon) from http://www.mutools.com/mulab/test/mulab ... -patch.zip

How to apply an application patch: http://www.mutools.com/mulab/patch/Read%20Me.Txt

[pdadda]

I only have OSX here, so I can't test it. Any PC users wanna give it a go? Thanks for the speedy reply though.

[sunhome]

First, I have no midi controllers and only run from a lappy, so I am a prime candidate for this fix

1. I loaded AAS Ultra Analog and chose a preset
2. Clicked Show Virtual Midi Keyboard
3. With the VM Keyboard in focus I played the notes fine using my qwerty keyboard
4. Clicked the title bar for AAS Ultra Analog and yes the VM keyboard responded with sounds even though I was focused on AAS Ultra Analog.
5. However when I adjusted a knob on AAS Ultra then my sounds stopped when I pressed the qwerty keys - let me try vanguard ....

Regards, James

[sunhome]

First, I have no midi controllers and only run from a lappy, so I am a prime candidate for this fix

1. I loaded AAS Ultra Analog and chose a preset
2. Clicked Show Virtual Midi Keyboard
3. With the VM Keyboard in focus I played the notes fine using my qwerty keyboard
4. Clicked the title bar for AAS Ultra Analog and yes the VM keyboard responded with sounds even though I was focused on AAS Ultra Analog.
5. However when I adjusted a knob on AAS Ultra then my sounds stopped when I pressed the qwerty keys - let me try vanguard ....

Regards, James

Vanguard works all the way, even when adjusting knobs such as cutoff, I was able to use the qwerty keys to play sounds ... so not sure what is different between the two vsts, AAS Ultra Analog and Vangaurd [using windows vista]

Regards, James

[MuTools]

Can you please try other VSTs too. Maybe it's AAS Ultra Analog specific issue?

[sunhome]

Can you please try other VSTs too. Maybe it's AAS Ultra Analog specific issue?

Three different catagories:
1. Clicking on GUI of vst produces sound
Surge
Blue
Vanguard

2. Clicking on GUI of vst stops sound [even vst gui preset changes]
Rhino
ZebraCM
AAS Ultra Analog

3. Clicking on the MU.LAB titlebar of vst bar stops vst sounds
Z3ta


Regards, James

[pljones]

Sounds like they're stealing the keyboard away from the app.

[MuTools]

Sounds like they're stealing the keyboard away from the app.

Yep that's the reason.

And nothing can be done about that, afaik.

[sunhome]

Sounds like they're stealing the keyboard away from the app.

Yep that's the reason.

And nothing can be done about that, afaik.

A vote of confidence that in due time you will be able to solve this

[MuTools]

To be honnest it's not a top priority at the moment because the only possible workaround is start applying special tricks (hacks) to the keyboard handling on the machine which may result in other quircks. I'm not very wild about such workarounds. The structured solution should be that VST plugin editors that receive certain keystrokes which they don't process, then they should not tag them as processed, and so logically these events should travel further in the GUI system.

[cytone]

You would need some option like this



This is what Renoise has on the plugins window