...and I would be so glad, if this could be resolved somehow:
90% of my plugins are blocking the spacebar for transport play/stop...
This is so damn annoying always to have to click onto the header of the plugin window to bring the main app back in focus...
For all other parts I have more or less good workarounds... but this is a timekiller and nerving as hell...
How do you deal with this??? Got used to???
My biggest showstopper with Waveform 9...
-
- KVRist
- 228 posts since 2 Feb, 2015
Some daws have a keyboard symbol on the plugin window that allows toggling of keyboard input to the plugin, but by default the daw receives keyboard input. This would be a good addition to Waveform because sometimes you need to hit the spacebar in an emergency and it doesn't always work! Have deafened myself numerous times because of this so it would be helpful.
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Map play/stop to a different key?
"my gosh it's a friggin hardware"
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
I guess, the keyboard in general is blocked by the plugin...
Years ago, this was a common problem, but luckily most developers have found worarounds for this, that at least the spacebar is let through...
Only a very little DAWs still fighting with this and Waveform is sadly one of them...
Easiest workaround I´ve seen:
The spacebar is in general passed through the main app... to be able to use a it in the plugin is to use Shift+Space...
Simple but does the job... how many times do you need the spacebar in the plugin window...
More complicated, but can live without a different key combination: The Main app recognizes if the plugin is in a text mode or in a normal mode and allows access of the spacebar for the plugin only in this special case...
I don´t need any other keys passing through just the spacebar to start/stop playback...
Years ago, this was a common problem, but luckily most developers have found worarounds for this, that at least the spacebar is let through...
Only a very little DAWs still fighting with this and Waveform is sadly one of them...
Easiest workaround I´ve seen:
The spacebar is in general passed through the main app... to be able to use a it in the plugin is to use Shift+Space...
Simple but does the job... how many times do you need the spacebar in the plugin window...
More complicated, but can live without a different key combination: The Main app recognizes if the plugin is in a text mode or in a normal mode and allows access of the spacebar for the plugin only in this special case...
I don´t need any other keys passing through just the spacebar to start/stop playback...
-
- KVRist
- 473 posts since 1 Feb, 2006
it bothers me like hell, complained about it years ago ...
got a reply from the guru (jules) itself, that this is something the plugin developers have to do (not stealing keyboardfocus or something like that, don't remember the details). end of game.
i did mention, that other daws get it working.
this may very well be true (plugin devs should get it straight), but as it won't ever happen probably, other daws developed their solutions long ago, which work quite well as everybody knows.
to just cling to that statement and let us stand in the rain is beyond me, but well *sigh*
sometimes i use a simple daw controler for play/stop via midi, which circumvents the problem. but i don't always have it with me.
got a reply from the guru (jules) itself, that this is something the plugin developers have to do (not stealing keyboardfocus or something like that, don't remember the details). end of game.
i did mention, that other daws get it working.
this may very well be true (plugin devs should get it straight), but as it won't ever happen probably, other daws developed their solutions long ago, which work quite well as everybody knows.
to just cling to that statement and let us stand in the rain is beyond me, but well *sigh*
sometimes i use a simple daw controler for play/stop via midi, which circumvents the problem. but i don't always have it with me.
-
Robert Randolph Robert Randolph https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=7328 - KVRAF
- 2226 posts since 25 May, 2003 from Saint Petersburg, Florida
The issue is that other DAWs that "work", do this by not sending keyboard events to the plugin in certain circumstances.klangbastler wrote:it bothers me like hell, complained about it years ago ...
got a reply from the guru (jules) itself, that this is something the plugin developers have to do (not stealing keyboardfocus or something like that, don't remember the details). end of game.
i did mention, that other daws get it working.
this may very well be true (plugin devs should get it straight), but as it won't ever happen probably, other daws developed their solutions long ago, which work quite well as everybody knows.
to just cling to that statement and let us stand in the rain is beyond me, but well *sigh*
sometimes i use a simple daw controler for play/stop via midi, which circumvents the problem. but i don't always have it with me.
This leads to another class of bugs, and once again you'd have to click a button to interact with the plugin naturally.
Except AU of course... AU handles this nicely.
-
- KVRist
- 189 posts since 27 Mar, 2014 from Brisbane, Australia
Off point, I know but thank goodness my midi controller (Axiom Air-32) has dedicated play/stop/record buttons. 
Making Bitpop music....
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
Tracktion Waveform 11 under Ubuntu 20.04.
ROC CUbe Ryzen 3400G - 32GB RAM, 2xSSD, Integrated Radeon RC Vega 11 GPU
Yamaha USB Mixing Station, Mackie Reference Monitors & Axiom A.I.R 32 controller.
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
What class of other bugs???Robert Randolph wrote:
The issue is that other DAWs that "work", do this by not sending keyboard events to the plugin in certain circumstances.
This leads to another class of bugs, and once again you'd have to click a button to interact with the plugin naturally.
...
From what I noticed, it works just fine in Studio One, Reaper, Ableton Live and others...
And just blaming the developers is a bit lame... Why should they make any efforts because the developers of 2 DAWs are to lazy to fix that problem, what all other did years ago...
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
Honestly, I cannot understand such point of view...klangbastler wrote:it bothers me like hell, complained about it years ago ...
got a reply from the guru (jules) itself, that this is something the plugin developers have to do (not stealing keyboardfocus or something like that, don't remember the details). end of game.
i did mention, that other daws get it working.
This shouldn´t be neither very difficult nor very time intense...
-
- KVRAF
- 1790 posts since 30 Dec, 2012
I've never heard that before...Trancit wrote:This shouldn´t be neither very difficult nor very time intense...
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Err, they should because that's how it's supposed to work?Trancit wrote:What class of other bugs???
From what I noticed, it works just fine in Studio One, Reaper, Ableton Live and others...
And just blaming the developers is a bit lame... Why should they make any efforts because the developers of 2 DAWs are to lazy to fix that problem, what all other did years ago...
What did the plugin devs tell you, when you asked them about it?
"my gosh it's a friggin hardware"
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
Sometimes things are how they are...chico.co.uk wrote:Err, they should because that's how it's supposed to work?Trancit wrote:What class of other bugs???
From what I noticed, it works just fine in Studio One, Reaper, Ableton Live and others...
And just blaming the developers is a bit lame... Why should they make any efforts because the developers of 2 DAWs are to lazy to fix that problem, what all other did years ago...
What did the plugin devs tell you, when you asked them about it?
What´s easier: to motivate about 1000 developers to touch all their plugins again to implement this correctly or to let 10 daw developers make a workaround (what 8 already did...)
EDIT: and by the way... this doesn´t work neither in Waveform:
I.e. Melda Production has implemented an option an to disable keyboard input... nevertheless this doesn´t work neither in Waveform nor in FL Studio (if you don´t use the internal blocking)
So let do the plugin developers the job isn´t a solution
Last edited by Trancit on Tue Sep 04, 2018 2:50 pm, edited 2 times in total.
-
- KVRAF
- Topic Starter
- 5070 posts since 27 Jul, 2004
I am not a programmer (obviously)... so this was a good guess... but sorry:dRowAudio wrote:I've never heard that before...Trancit wrote:This shouldn´t be neither very difficult nor very time intense...
Is it hard work to i.e. tell your plugin wrapper to block/reserve it for the host the spacebar and translate shift+spacebar for the plugin as spacebar instead???