Skip to main content
Participant
January 2, 2024
Question

Ease in, Ease Out Shortcuts not Working

  • January 2, 2024
  • 7 replies
  • 1524 views

1. Premier Pro v.24.1

2. Windows

3. Set Ease-in & Ease-out keybindings to any binding.

4. Need help fixing this bug.

 

I have used the Ease-in and Ease-out keybindings as ctrl,- and ctrl,= for a long time. I recently changed computers and now no key binding works as a shortcut to easily apply the Ease-in and Ease-out temporal interpolation effect on the Effect Controls Panel.

I've tried using different bindings, restarting computer. Downloading older versions of Premiere Pro. Nothing has seem to work. I've seen this issue a lot online with no fixes.

7 replies

hsaaash
Participant
May 14, 2025

update to say it's still not working. using a Mac shortcut CTRL+OPT+I & O respectively

Participant
November 6, 2025

same here

Ann Bens
Community Expert
Community Expert
November 6, 2025

Did you set the kbsc for the correct panel?

MyerPj
Community Expert
Community Expert
April 24, 2024

It's seems to be working for me. 

Win11-23H2 / PP24.3

Participant
April 24, 2024

That's the problem. The shortcuts do not work when applied. Other shortcuts work for other actions but not ease in or out for any bindings. I use F9 because I use after effects as well. Worked in previous versions. Reinsltled previous versions and not doing the trick

Diego5C3AAuthor
Participant
April 21, 2024

They told me a whole lot of nothing. Just lots of back and forth about it not working. What i did find out is that deleting Photoshop Beta fixed half of the issue. It made it so when i used a shortcut to ease in or ease out it would ease in & out. BUT the symbol remained unchanged as if i didnt apply the effect. That was a good enough fix for me.

Community Expert
April 21, 2024

You could try the following:

(Easy In): Ctrl+[ (Windows) or Cmd+[ (Mac)

(Easy Out): Ctrl+\] (Windows) or Cmd+\] (Mac)

Byron.
Participant
April 21, 2024

I am having the exact same problem

Participant
April 21, 2024

wow, not a single word on this problem from Adobe. Were you able to find a resolution?