many vst plugin windows won't pass the spacebar/start stop key to tracktion 7 while tweaking

[kvruserr]

Hi,

win10 x64 , tracktion 7 64bit, plugin (e.g. boz plus 10) 64 bit
I noticed that Tracktion is very peculiar with many plugins and their windows active. After having touched a vst parameter the spacebar has no function anymore ... until I click on the vst windows top area.
The same plugin and the Spacebar function will work in other Daws alright (fyi).
So Tracktion seems to be blocking those keycommands while in an active vst plugin window.


I hope the description is good enough to follow.

regards

[dRowAudio]

This is specific to the plugins I'm afraid. Once the plugin UI has focus, they control what keys get passed on to Tracktion. You'll see some plugins correctly pass unused keypresses (like space bar when no text fields are active) to us but not every plugin.

Other hosts may add additional keyboard hooks to capture all key events sent to a plugin but this can cause problems as it will for example trigger play/stop when you try to type a space into a text field.

This may be one for the plugin developers to fix.

[kvruserr]

This is specific to the plugins I'm afraid. Once the plugin UI has focus, they control what keys get passed on to Tracktion. You'll see some plugins correctly pass unused keypresses (like space bar when no text fields are active) to us but not every plugin.

Other hosts may add additional keyboard hooks to capture all key events sent to a plugin but this can cause problems as it will for example trigger play/stop when you try to type a space into a text field.

This may be one for the plugin developers to fix.

Thanks for your fantastic support and swift responses!

I know too well what you are pointing at and another Daws will steal the 'blank' space bar from a vst 'search field'.
Why is Tracktion less dominant compared to Samplitude and Studio one and Mixbus where e.g. BOZ doesn't seem to get the Spacbar? Just asking...
Imho, correct me if I'm wrong, the Spacebar is of such an importance to start and stop Tracktion and other Daws while tweaking the plugin that I would rather have Tracktion just cling on to that one shortcut.
I hope this makes any sense to you. : -)
I'm not sure but does not Reaper have an option/tick box: direct keyboard activity to plugin or daw?

thanks and regards

[gigazaga]

This is specific to the plugins I'm afraid. Once the plugin UI has focus, they control what keys get passed on to Tracktion. You'll see some plugins correctly pass unused keypresses (like space bar when no text fields are active) to us but not every plugin.

Other hosts may add additional keyboard hooks to capture all key events sent to a plugin but this can cause problems as it will for example trigger play/stop when you try to type a space into a text field.

This may be one for the plugin developers to fix.

I've seen other DAWs implement a "keyboard focus off" button on the plugin header. This allows you keep sending all keyboard input to the host while allowing mouse input for keyboard robbing plugins. I'm not saying this is a good idea necessarily but I have seen this done as a workaround.

[klangbastler]

i also think, some thought about a workaround would be good. it is one big inconvenience of tracktion, that start/stop via spacebar is interrupted when working in pluginwindows.
the only workaround at the moment is, to use some kind of controlsurface for this.

i don't know if the solution is, to move the responsibility to plugindevelopers. it might be the case from a programming standpoint.
but reality is different i guess and almost all daws circumvent this in some way.

[magicmusic]

you can write to the plugin developer and post the link to this thread, what easy to add code the plugin developers can add so that it work.
http://www.kvraudio.com/forum/viewtopic ... 0#p6793760

i test waveform with MUX plugin(which contain the code) and the space bar work on all windows MUX opens. so from waveform side is all ok.

tracktion 5 i test too, on this do space not work, when a 2. window is open from MUX and active

[aMUSEd]

But if it passes spacebar to the DAW even when you have the plugin window in focus, how do you type preset names when you save them? I would not want to be typing something and accidentally activate something in the DAW (happened to me a lot in Bitwig before I deleted all keyboard shortcuts). I don't know why all hosts don't implement a toggle, leaving it to something based on the plugin dev to implement is unlikely to work as there is not much commonality in how plugins are developed, it has to be at the host end.

[fromwithin]

This is one of the main reasons that I bought a Korg nanoKontrol Studio. External controller data comes in via MIDI data, so window focus is irrelevant. I highly recommend getting a little controller with transport controls and a jog wheel.

[zzz00m]

This is one of the main reasons that I bought a Korg nanoKontrol Studio. External controller data comes in via MIDI data, so window focus is irrelevant. I highly recommend getting a little controller with transport controls and a jog wheel.

[midi-man]

I've seen other DAWs implement a "keyboard focus off" button on the plugin header. This allows you keep sending all keyboard input to the host while allowing mouse input for keyboard robbing plugins. I'm not saying this is a good idea necessarily but I have seen this done as a workaround.

This would make a good FR I think...
And maybe a filter setting which keys goes to the host?