That's exactly why it took me some time to understand what was going on at first. The reason for that is that when you first press alt, the focus changes to the context menu (the root of the problem), if you press it again the focus goes back to where it was earlier. Basically ALT works like a toggle.
-
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!
Fender Studio Pro 8.1 - Discussion Thread
- Thread starter Lukas
- Start date
freddiphin
Active member
For what it's worth I find all the the FSP stock ALT... keyboard shortcuts (the ones listed at Help - Keyboard Shortcuts, or Ctrl+Shift+K) to work exactly as intended (on Windows 11, on previous ver. of FSP and the current 8.1.2) whenever the context is appropriate and otherwise, or if not assigned, they default to the Windows ALT combos invoking the menu bar items (File, Edit, View, Help, etc.), which is what I assume you mean by "Context menu" (which is more accurately the Right-Click popup menu) .
In other words, if the action you are trying to invoke with the shortcut, for example ALT+T (Transform Range) is not appropriate to your context (because there is no automation range to transform), then you will get the Windows default of Menu bar>T-letter item (i.e. "Track").
In this video
you see me using first the ALT+X (for a Split action), then awkwardly choosing a selection and an ALT+S (for Zoom to Selection Horizontally), then toggling between that and ALT+Z (full Zoom), and then "inappropriately" choosing ALT+T and getting the menu bar item, then correcting that to create an envelope, choosing a range and then ALT+T again and getting the appropriate action (Transform Range).
These and all other FSP stock shortcuts and those that I create work every time as long as the contextual conditions are met.
I wish it was just a matter of context, but I can confirm that all this time I've been performing those actions in the right context, and they do not work as intended. Just to give one example again, I recorded the screen and pressed alt+t to transform range. The menu 'Track' opens up. Hopefully you can see the video here
freddiphin
Active member
Nuts! Sorry about that. I guess it working as intended for me just means it's probably not a bug.
Do you have any kind of mouse or keystroke overlays (AutoHotKey, etc.) that might confuse it ?
Nope, never had any of those. I tested this on my second computer, and other friends (and users here) have the same issue. I wish someone from Presonus could chip in and tell us what's going on.
I experience it with and without alt, depending onwether I used alt before. It seems that alt (unintentionally) now triggers the menu, as in the golden days of Win XP. I had it several times that I copied a note with the alt modifier, and then, with alt released, tried to duplicate a fewselected notes, but instead the file menu opens. Which makes sense, because in my language, the file menu starts with a D, and alt + d was the Windows mnemonic to open the menu.
And I can repeat this error and provoke it. Just hit alt while moving a note. let go off alt and then hit a letter that used to open the menu, the file menu with d, the edit menu with b, the session menu with s, and so on. @Kisnou is right. It's a bug.
And I can repeat this error and provoke it. Just hit alt while moving a note. let go off alt and then hit a letter that used to open the menu, the file menu with d, the edit menu with b, the session menu with s, and so on. @Kisnou is right. It's a bug.
freddiphin
Active member
I feel ya. I wish I could replicate any of youse guyses issues here in order to confirm its universal bugginess, but it always works as expected and desired in my setup, which I have not altered in any known way, i.e. Windows 11 25H2 ; Studio Pro 8.1.2 standard install ; no mouse/keyboard overlay scripts running with FSP
AAV
Active member
The only way to properly test this would be to use a standard (supplied with FSP) ALT-Key combination command in a specific context (to freddiphin's point) that should execute the command (e.g. on a selected event) but instead executes a main menu command. It would not be sufficient to just point to earlier versions as different, because it is likely Fender fixed (or broke) this specifically in FSP. Any ideas for a specific Key combination and an agreed to context that always fails. that we could all try? freddiphin's point is that context matters. Just pressing ALT-key might do 2 different things depending on when and where the key combination is executed. (Debatable so would need to be demonstrated).
Last edited:
Hey AAV, you should probably read previous posts. Default Alt+Key commands (a key that corresponds to a context menu word such as F for Files) will open the context menu list instead of triggering the supposed shortcut. We have already tested this earlier, it's not a matter of context or which windows is focused, as you can see by my video as well.
AAV
Active member
That's kind of the point - ALT-F is not a default key command for Fender Studio Pro 8.1 as far as I can see. If you have ALT-F assigned to something else it is either a key command you have added or it is a holdover from a previous version where it was. If you re-read the previous posts, you will see that I actually agree that it is a bug. But in reality it may be just Fender making changes that might not be desired or desirable for all users. I am trying to get to the bottom of whether there is actually a bug, or if it is just a change that not all of us like.
Gemini says:
Gemini says:
AAV
Active member
And FWIW, I have also upgraded through multiple generations of S1 (every version from 3). My keyboard mapping scheme in FSP 8.1.2 shows up as "Studio Pro (modified)". Alt-F is assigned to "Audio - Open Event FX Editor", ALT-E is assigned to "Zoom - Redo Zoom" (which according to Gemini (above) is a standard second use of this key command, depending on context (Focus), ALT-S is assigned to "Zoom - Zoom to Selection Horizontally", ALT-T is assigned to "Automation - Transform Range", ALT-A is assigned to "Automation - Show Current Parameter", ALT-V is assigned to "Event - Copy Ranges to Track", and ALT-H is assigned to "Event - Replace Event With Next Layer". I can't say whether all of these have been standard key commands in previous versions, but at least some of these certainly have.
AAV
Active member
And to the point of all of this. This is only a bug IMO if FSP lets you assign (or carryover) an ALT command and fails to execute that command reliably when you have the correct focus/context for the command to happen. If you press (for example) ALT-T that is supposed to Transpose Notes in an event, but there is no event highlighted, FSP bringing up the Track menu would not be a "bug" although it might not match what happened in earlier versions. I was trying to see if we could find a basis to test this in a way that would actually illustrate whether or not a bug exists. (Peace)
All the ALT+key command should work, otherwise studio one wouldn't allow for that, as it would be quite a contradiction if it lets me use any Alt+ shortcut only to trigger context menu actions.
Alt+T is a native shortcut, yet for me it opens the Track menu in ANY context, and like I said, that's just an example.
This is only a bug IMO if FSP lets you assign (or carryover) an ALT command and fails to execute that command reliably when you have the correct focus/context for the command to happen
That's exactly what we are talking about here. All the alt+[insert key] should work, whether they are custom or native, and when the focus is correct. Yet for me and other users here, even when the focus is correct, the context menu tabs get priority over everything. I've been making music for around 20 years, and all the alt+ shortcuts have been working perfectly until a while ago, something has changed and we were not informed.
freddiphin
Active member
For sure it's frustrating for those experiencing this issue. It seems clear in Kisnou's video that the pressing and holding of Alt+T (for example) is not performing the "Transform Range" function as it does correctly in my video example and does for me consistently.
The question, then would be what is the difference between that setup/system and mine. Something hidden obviously, but perhaps not in the purview of Studio Pro? But I certainly wouldn't know. I'm just offering up my experience as a "control" part of the tests/experiments.
I can confirm that the following consolidated list (culled from Help>Keyboard Shortcuts) of just the ALT+letter combos (the default ones from FSP) work for me as intended/expected every time (as do any others) given their appropriate context conditions are being met and that (of course) ALT is held down as the letter key is then pressed
The question, then would be what is the difference between that setup/system and mine. Something hidden obviously, but perhaps not in the purview of Studio Pro? But I certainly wouldn't know. I'm just offering up my experience as a "control" part of the tests/experiments.
I can confirm that the following consolidated list (culled from Help>Keyboard Shortcuts) of just the ALT+letter combos (the default ones from FSP) work for me as intended/expected every time (as do any others) given their appropriate context conditions are being met and that (of course) ALT is held down as the letter key is then pressed
Last edited:
Yes, there is something that causes it. It is not up to us to find out what exactly, as it is bound to the code base and how it deals with the Windows message system. Don't forget, there's more going on, than just the shortcuts. Remember my example, where alt is used as a modifier for a mouse action (for example, drag a note while holding alt to duplicate). This may not activate access keys, as it is another action entirely. But it does. The next letter you press after above mentioned mouse action with modifier activates a menu item. But only in 8.1.2, not in version 6!
I am honestly running out of options, I can't seem to find out why this is happening. I can't check in Studio One 6 but it happens in Studio One 7 as well (the latest version), that's why I thought of a windows update that probably messed things up.
Without the help of Fender/Presonus, I think we'll never find out the cause of this. I informed their support team a couple of months ago but we still have no news. It's honestly frustrating, I had to change almost all of my alt+[key] shortcuts because of this.