• Hi and welcome to the Studio One & Studio Pro User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by Fender. Learn more in the Welcome thread!

Keyboard shortcuts trigger while typing in preset search / plugin text fields (worked before)

tom3k

New member
Since updating to Fender Studio Pro 8.2 on Windows 11, my keyboard shortcuts fire whenever I type in a preset search field or a text box inside a plugin. Letters that should appear in the field trigger DAW commands instead. It used to work fine, and it happens in every plugin I’ve tried, not just one. Caps Lock and Scroll Lock are both off, and the cursor is clearly blinking in the field when it happens. [Add what you’ve already tried, e.g. restarting the DAW or checking the shortcut list.]


Does anyone know if there’s a setting that controls whether the computer keyboard sends input to the DAW while a plugin or search field has focus? I’m also wondering whether a recent update changed how keyboard focus or computer keyboard MIDI input works. If so, is there a way to reset the shortcuts or preferences without losing my other settings?


Thanks in advance for any help.
 
I experienced this a couple days ago. I forget which VST it was, but it was exactly as you described. I then tried plugins from a couple other vendors and those worked fine.
 
I saw the very same thing yesterday when trying to rename a macro control button. Every time I pressed the T key, the new track dialog opened up. Also, the context menu was entirely disabled. The original text never changed.

I just now tested it again and had the same problem. Let's see if I can duplicate it in a simple example. Later...
 
Here's how you can replicate the problem:
  1. Download the attached .txt file and change it's extension to a .song file. I did this to circumvent the upload filter.
  2. Double click the song file.
  3. Try to change this button's text to "test" to see the result:
1794777205458.png

Someone please give it a try. If you would also please submit it to Fender support, I would appreciate it. Thx - s
 

Attachments

Since updating to Fender Studio Pro 8.2 on Windows 11, my keyboard shortcuts fire whenever I type in a preset search field or a text box inside a plugin. Letters that should appear in the field trigger DAW commands instead. It used to work fine, and it happens in every plugin I’ve tried, not just one. Caps Lock and Scroll Lock are both off, and the cursor is clearly blinking in the field when it happens. [Add what you’ve already tried, e.g. restarting the DAW or checking the shortcut list.]


Does anyone know if there’s a setting that controls whether the computer keyboard sends input to the DAW while a plugin or search field has focus? I’m also wondering whether a recent update changed how keyboard focus or computer keyboard MIDI input works. If so, is there a way to reset the shortcuts or preferences without losing my other settings?


Thanks in advance for any help.
Not that it helps you much, but this is a focus issue. Normally, the os passes the focus to the appliation in foreground. However, since plugin windows are created by the DAW, it still has the focus. It is the DAW's job to pass the keyboard input to the plugin. Other DAWs solved the worst issues by simply handing the full control over to the user. You can click a switch that passes the full focus to the plugin window. During that time, the DAW can't be controlled by keys anymore, but it makes sure the plugin recieves the keystrokes. Studio Pro never had such a functionality. It always tried to do its best, but obviously can't handle all situations, esp. if the pugin itself handles the system api wrong or not at all.
Such a switchable focus state has been suggested many times, but Fender did not (yet?) realize it.
Unfortunately, there is no real solution or workaround to it (other than preparing the text in another app and copy/paste in the plugin's preset browser). Unless I missed some last minute development.
 
Not that it helps you much, but this is a focus issue.
Keyboard focus is also the problem in my case. However, there is no way to paste the text into the label. Nothing happens when I press CTRL-V. Also, the context menu is all disabled:
1794779599441.png
 
Has anyone ever lost functionality in Windows Explorer due to running FSP? Often, Windows will not allow me to rename files (either via the F2 shortcut key or right clicking and choosing 'rename').

The only way to remedy the problem is to reboot.

I think this is related to certain plugins because it doesn't happen every time, but some of my more complex projects cause it as soon as I load up the song.
 
Keyboard focus is also the problem in my case. However, there is no way to paste the text into the label. Nothing happens when I press CTRL-V. Also, the context menu is all disabled:
View attachment 4281
There's a separate thread regarding this. Definitely a bug. I'm back on v8.1.2.

 
Has anyone ever lost functionality in Windows Explorer due to running FSP? Often, Windows will not allow me to rename files (either via the F2 shortcut key or right clicking and choosing 'rename').

The only way to remedy the problem is to reboot.

I think this is related to certain plugins because it doesn't happen every time, but some of my more complex projects cause it as soon as I load up the song.
Try this: with only FSP running and the problem is exhibiting, go to task manager and look for multiple instances of Explorer, then restart each and test again. This should whittle it down so that there is only one instance of Explorer running. Report back.
 
I'm also not able to rename FX Chain Macro controls from the control panel. They can be edited only by open the Macro Controls panel, and entering the name on the control itself that's being assigned to a particular parameter. This seems related.
 
Has anyone ever lost functionality in Windows Explorer due to running FSP? Often, Windows will not allow me to rename files (either via the F2 shortcut key or right clicking and choosing 'rename').

The only way to remedy the problem is to reboot.

I think this is related to certain plugins because it doesn't happen every time, but some of my more complex projects cause it as soon as I load up the song.
I noticed that as well, it started to happen ever since v8 was introduced.
 
Back
Top