Uploaded February 2017 | Updated September 2026, 1 week ago
WATCH THE FOLLOW UP TOO YEAAAAH youtube.com/watch?v=sgpYKus32tg
NOTE that these ARE listed as "experimental features," so the lag should be fixed eventually. But there are a lot of customization options I want that simply don't exist right now.
Stuff like this is why I say the Palette Gear is only at 10% of its potential. My AHK scripts can do the same things, but faster, easier, and more accurately, while being significantly more customizable: github.com/TaranVH/2nd-keyboard/blob/master/Taran's%20Premiere%20Mods/PREMIERE%20MOD%20-%20Instant%20RESCALE%20button.ahk
WATCH THE FOLLOW UP TOO YEAAAAH youtube.com/watch?v=sgpYKus32tg
NOTE that these ARE listed as "experimental features," so the lag should be fixed eventually. But there are a lot of customization options I want that simply don't exist right now.
Stuff like this is why I say the Palette Gear is only at 10% of its potential. My AHK scripts can do the same things, but faster, easier, and more accurately, while being significantly more customizable: github.com/TaranVH/2nd-keyboard/blob/master/Taran's%20Premiere%20Mods/PREMIERE%20MOD%20-%20Instant%20RESCALE%20button.ahk
![Premiere 2017.1.2 BUG - Timeline is ignoring keyboard and mouse input - [Public version]](https://i.ytimg.com/vi/t_Swd8Yv55Y/mqdefault.jpg "Premiere 2017.1.2 BUG - Timeline is ignoring keyboard and mouse input - [Public version]
This is a very serious bug, where Premiere simply does not respond to some commands, while the video is playing... and sometimes even if the video is NOT playing.
This bug can vary in severity. For some projects, Premiere becomes nearly unusable, with hardly any keyboard or mouse input getting though.
THE SOLUTION (which I found later) is to switch to another program, and then switch back to Premiere. (I now have a macro that will do this as quickly as possible.) Then, Premiere becomes responsive to the keyboard and mouse again. However, it will soon become unresponsive again, sometimes on the very next keystroke. So this is definitely not a complete solution.
This was NOT a problem in 2017.0.2... and I deliberately waited several months before upgrading to 2017.1.2, in order to avoid the smorgasbord of bugs that are common in new releases of Premiere. Unfortunately, this bug persists.
I first reported this bug on Aug 2, 2017 with an unlisted video, but it has yet to be watched at the time of this writing.")
