Function Keys not working as shortcuts

[MPoczynek]

I am running Windows 11 with a Logitech K350 Keyboard.  

I can configure F5 to Transmit to Monitor, but it does not work in the program. Although Alt-Shift-T does.

In other words, F5 will configure and show up on the keyboard configuration layout.

None of the function keys other than F1 - Help work.

[MyerPj]

Do you have to run a logitech keyboard software with that? If so, make sure the function keys are setup as you expect inside it. I have to do that with a Steelseries keyboard.

[MPoczynek]

I tried it with and without the Logitech Software package with the same results.

I can assign the F5 in keyboard shortcuts, it just doesn't do anything.

So it sees the keyboard and F5.

[MyerPj]

My rather 'dumb' Steelseries kb, has function keys on the top like almost all modern pc  keyboards. However, it has a set of 14 (10+4) keys on the left, like our best oldschool keyboards. However, our oldschool keyboards duplicated the keys on the left as normal function keys (to the top ones), then we could customize then from there. This dumb one, just left those keys blank. So, there is not default action on them (they don't do anything) w/out the SS software and setting them to something. I'm just wondering over there.

Have you tried the DEFAULT set of keystrokes in PP, you'd have to assign something to F5, but maybe there is a problem with the KB short file that is affecting it.

[Stan Jones]

@MPoczynek,

I suspect this is like the Alt key, which invokes the Windows functionality despite mapping it various ways in the PR shortcuts.

So probably, plain F6 does some Windows function and is not passed on in actual use.

I was able to assign F6, and, as you say it doesn't work. But Ctrl+F6 does. (I was assigning them both to "Fit" in the Program Monitor). So try Ctl+. That's all I tested.

Stan

[MPoczynek]

Thanks, Stan.

[MPoczynek]

The thing is, Premier Pro sees the F5 in the setup; it just does not work when called for as a function.  Otherwise, I would think it was a driver or Windows.  It is good to see I am not the only one with the issue.  I hope I did not miss your point.

[Stan Jones]

@MPoczynek,

I do think Windows function has something to do with it. But I also agree that the shortcuts should not allow assignment of a key that won't work. The Alt+ issue is, for me, an example of such a problem. The Alt+ option is used in some default shortcuts, and works, but also pops up a menu command, because the Alt key in windows does that!

See my post here:

https://community.adobe.com/t5/premiere-pro-beta-discussions/caption-and-text-based-editing-keyboard...

The part that is relevant to our discussion:

"But there are now Text Panel commands "Merge Segments" (assigned by default to Alt+M) and "Split Segment" (assigned to Alt+S). The problem, since I am on Windows, is that these do work correctly. They DO merge or split, but they also bring up the Markers and Sequence menus respectively. In the current Beta default assignments, they are the only Alt+ letter combinations. Shft+Alt works no better; some letters that do not have Alt menu commands work okay. For now, I just assigned the same keystrokes I have assigned to the "Merge selected caption segments" [Ctrl+Alt+U] and "Split caption segment under CTI [Ctrl+Alt+Y]." These work correctly."

There are only 15 Alt+ and Alt+Shift uses in the current default shortcut.

Stan

[ThioJoe]

I might have figured it out - I just noticed something strange with the F5 and F6 shortcuts specifically. By chance, to test I had set F5 to be a shortcut to the "Change label color to [whatever color]" command, which happens to be one that show up in the history panel. And I noticed that when using it, F5 triggers the command twice. (Perhaps someone can test confirm this happens on their computer too.)

I tried this in a fresh virtual machine with and Premiere installation, and it does the same thing. It seems the only F keys this happens with is F5 and F6. It does not seem to happen when a modifier is used with it like Ctrl+F5. Just like @Stan Jones noticed.

I suspect what's happening, is that since the "Enable Transmit" command is actually a toggle (it will disable if it's already enabled, and vice-versa), the apparent double-action bug of F5 and F6 means their shortcut is actually working, but it's triggering it twice therefore instantly toggling it back off.

[MPoczynek]

Thank you.  All good points.  I have had issues with ALT shortcuts as well.  

[MPoczynek]

Interesting.   I will do some further testing and check out the other post mentioned.  Thank you.

[MyerPj]

Yes, I just tried F5, and indeed it shows two entries in the history window. I haven't been using f5, but it is set to set label color.

[MyerPj]

I  just tried a bunch of things, and I can't get F5 to do anything other than assing a clip color with the two instances in the history panel.  I couldn't change tools with it, get properties, set marker, etc. 

strange thing.

[jamieclarke]

Hi @MPoczynek - 
Thanks for submitting your bug report. We need a few more details to try to help with the issue.
Please see, How do I write a bug report?

What OS and Premiere Pro version are you using?

Sorry for the frustration.

[MPoczynek]

I am using:

Windows 11 PRO 23H2

Adobe Premiere Pro 2025 25.1.0 Build 73

Thanks.

[ThioJoe]

Ok I believe I found the actual cause and the solution to this. Apparently behind the scenes, the F5 and F6 keys are already assigned to apparently no-longer-existing commands. 

Solution:

1. Go into your keyboard shortcut file which ends with .kys -- For example mine is located at:
D:\Users\Joe\Documents\Adobe\Premiere Pro\25.0\Profile-Joe\Win\My Premiere Shortcuts.kys

2. Search for these two entries and delete them. The "item" number might be different, so search for "cmd.file.batchcapture" and "cmd.file.capture".

Note: Apparently the virtual key values of 11 and 12 correspond to F5 and F6, so you could search that too. Theoretically you may have assigned these commands to something else in the past, in which case a different key would be blocked. But I guess F5 and F6 were the default.

			<item.174 Version="1">
				<virtualkey>12</virtualkey>
				<modifier.ctrl>false</modifier.ctrl>
				<modifier.alt>false</modifier.alt>
				<modifier.shift>false</modifier.shift>
				<commandname>cmd.file.batchcapture</commandname>
			</item.174>
			<item.175 Version="1">
				<virtualkey>11</virtualkey>
				<modifier.ctrl>false</modifier.ctrl>
				<modifier.alt>false</modifier.alt>
				<modifier.shift>false</modifier.shift>
				<commandname>cmd.file.capture</commandname>
			</item.175>

3. Restart premiere, and now the F5 / F6 key assignments you have in the hotkey GUI should actually work.

I don't take credit for discovering this, I just happened to stumble upon a post on a different site with the solution. 

Though I will point out that this appears to be the exact same problem I came across with my hotkey for the Transform Selection tool, which changed between PP 2024 and PP 2025. The leftover old command name in the .kys was 'blocking' any assignments from working. Not sure I didn't make that connection myself before. Though I'm not sure about the weird behavior I noticed before with it double-triggering, that seems to maybe not happen anymore and could have been a separate bug.

@jamieclarke Perhaps the keyboard shortcut assignment GUI in Premiere could show some kind of indication if a particular key is assigned to a no-longer-existing command?

[Kent_SLA]

Thank you!

This was driving me absolutely bonkers.

I did NOT want change the KB shortcut I've been using for 25 years!