Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

Shift + Numpad 5 combination is hardcoded and can not be reused

Community Beginner ,
Mar 18, 2025 Mar 18, 2025

Hello,

I have an issue mapping Shift+Numpad numeric keys (from 3 to 9). They automatically send the corresponding number (3 to 9) into the Timeline Panel's timecode.

 

Even more weird is that is overriding Autohotkey mapping entirly.

Ctrl+Numpad keys work as expected, it is the workaround I am using.

 

These shortcuts seem to be hardcoded outside of the Keyboard Shortcuts panel.

Since Shift+Num 1 and Shift+Num 2 do not behave in the same way, I decided to post this observation as a BUG instead of a discussion.

 

If Anyone has knowledge how this mapping can be undone, please comment along.

Tested the same problem since Premiere 2023 through 2025.

Cheers.

 

 

367
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Mar 21, 2025 Mar 21, 2025

I've just read this post which explains that it might be a keyboard hardware manufacturing behaviour as keyboards might be designed like this - which would explain why autohotkey is never fired-up.
Case closed :))

Translate
Community Expert ,
Mar 18, 2025 Mar 18, 2025

@Av37679217mryu,

 

Interesting. I don't think I tested the Shift+ in this thread:

https://community.adobe.com/t5/premiere-pro-discussions/my-numberpad-is-not-wokrking-in-premiere-and...

 

Are you saying that autohotkey will also not use the Shift+ keypad numbers?

 

Stan

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 21, 2025 Mar 21, 2025

What is interesting is that whatever you setup as shortcode, in premiere, for Shift+Num keys (3-9) does the same thing.
Like I've said, it's not autohotkey problem, with it off, same behavior.
The following is mapped for me in Premiere for Shift+Num5 and Num8, it does not perform this action.
No issues with Alt or Ctrl Numpad mappings in premiere.

Av37679217mryu_0-1742544248258.png



The problem lies elsewhere (prob. windows system), I mentioned Autohotkey because it is interesting that it gets over-rulled.

My understanding is that the way Autohotkey works, is that it intercepts the key combinations and performs the required code. Mapping of Shift+Num5 for example should perform a different premiere combo I set up that helps me edit.
The combo is never fired I tried different workarounds.

+numpad5::
if WinActive("ahk_exe Adobe Premiere Pro.exe"){
    sleep 1000		; whatever else overrides me
					; waiting 1s would allow my further behaviour
	send {Esc}		; normally even if timecode is selected
					; sending esc would take me back to timeline
					
	send +{down} ;my actual desired action
}else {
    send +{5}
}
return 

 

I just experimented without the Premiere wrap to enable map on all the system and the combinations don't work as expected.
I believe the conclusion is that this is simply a Windows environment problem.

+numpad5::
    sleep 1000		; whatever else overrides me
					; waiting 1s would allow my further behaviour
	send {Esc}		; normally even if timecode is selected
					; sending esc would take me back to timeline
	send +{down} ;my actual desired action
return 

+numpad8::
    sleep 1000		; whatever else overrides me
					; waiting 1s would allow my further behaviour
	send {Esc}		; normally even if timecode is selected
					; sending esc would take me back to timeline
	send +{up} ;my actual desired action
return 


Further internet scan shows that other people have issues with shift+Num keys in windows on various atempts to do other things.
On future Premiere updates, Disabling the Shift+Num keys on Premiere keyboard mapper would hint people that it would be an invalid choice (Windows environment wise).

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 21, 2025 Mar 21, 2025
LATEST

I've just read this post which explains that it might be a keyboard hardware manufacturing behaviour as keyboards might be designed like this - which would explain why autohotkey is never fired-up.
Case closed :))

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines