Uploaded December 2017 | Updated September 2026, 1 week ago
DO NOT USE THIS FOOTAGE TO IMPLY JON'S ENDORSEMENT OF YOUR OWN ILLICIT BEHAVIOUR.
DO NOT NOTICE THAT YOU COULD PUT ANY TEXT YOU LIKE.
Source: youtu.be/oTydZBIGAuk?t=3m5s
DO NOT USE THIS FOOTAGE TO IMPLY JON'S ENDORSEMENT OF YOUR OWN ILLICIT BEHAVIOUR.
DO NOT NOTICE THAT YOU COULD PUT ANY TEXT YOU LIKE.
Source: youtu.be/oTydZBIGAuk?t=3m5s
![Captain forever any% [PB] 14:11](https://i.ytimg.com/vi/re_pq7KbRNc/mqdefault.jpg "Captain forever any% [PB] 14:11
PLAY HERE: http://www.captainforever.com/captainforever.php
edit: DANG IT looks like Ive already been BEATEN to the tune of 8:01: https://www.youtube.com/watch?v=YQyJaOd5wXg
This was the only prior world record that I could find: https://www.youtube.com/watch?v oA7dHdKk9U")
![[SOLVED] HELP TARAN with AHKs controlSend command](https://i.ytimg.com/vi/sC2SeGCTX4U/mqdefault.jpg "[SOLVED] HELP TARAN with AHKs controlSend command
EDIT: Solution was found, please look at the pinned comment.
https://autohotkey.com/docs/commands/ControlSend.htm")
![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.")
