Hi guys.
As you know, the spacebar starts and stops the transport.
However, If I am adjusting a plugin and the plugin is the active window, then pressing space does nothing. you have to click somewhere to make Sonar the active window first which is quite frustrating after a while.
Anyone know of any changes I can make to rectify this??
Cheers.

That's one of the reasons I picked up a cheap korg nanokontrol for $50 so I can use it's transport controls without having to do click elsewhere to stop it with the mouse.

That's windows for you. You have to give a Window focus to use any controls in that window.

Which plugin?   I think the delivered plugins (or at least most) do allow the transport keys to work while the plugin is in focus.
 

That should only be a problem with the GUIs of Bitbridged 32-bit plugins. That's one of the reasons the 3rd-party JBridge is preferred to Bitbridge; it doesn't have this issue and is worth the $20 if only for this one feature.

Hi. please post the plugins in question. I have had no problem with using the spacebar while plugins have focus.

R3V3RB,
 
not quite the same but similar, I sometimes am recording in a loop for a long time and find I need to hit the space bar twice to stop recording. I don't know why. It's one of the reasons I stopped using a wireless keyboard.
 
When I use my AlphaTrack interface, the stop button always works.

Rebel007 some plug-ins will "stay on top" if you have menus for them open meaning the spacebar won't start playback even if they're 64 bit. One that I can list is the KORG Monopoly which is 64 bit, but when the patch browser window is open, I have to click elsewhere to start Sonar.
 
 

It's not really a Windows limitation, nor is it SONAR's fault. Windows does always dispatch keystrokes to the window that has focus (imagine the chaos if it didn't!), and it's up to the plugin to pass keystrokes back to the host application. Some do it well, others do not do it at all. Some (e.g. Ozone) have an option to pass all keystrokes to the host. Check with the plugin vendor or the plugin's documentation for a solution.