CRITICAL Bug Report - Premiere 14.0 Timeline Keyframe handles change behavior frustration, mistakes.
Premiere 14.0 scenario. Working in the timeline, I add a keyframe from the box at the left of the track, on the keyboard, I shift-arrow right 6 clicks. I click the add keyframe again.
****INSTEAD OF ADDING ANOTHER KEYFRAME, IT DELETES THE ONE YOU JUST ADDEDUNLESS*YOU MOVE THE CURSOR OFF THE KEYFRAME BUTTON, THEN BACK ON, BEFORE YOU CLICK15 YEARS OF HIGH VOLUME PRODUCTIONMUSCLE MEMORY****I NOW HAVE TO REVIEW EVERY VIDEO AND I USUALLY HAVE TO REDO IT. NOW I HAVE TO THINK ABOUT THINGS THAT WERE AUTOMATIC FOR OVER A DECADE????? You might want to look into that one people.
Michael Tierno commented
I fixed it by have the timeiine be only on TIME RULER NUMBERS. Right click on timeline, uncheck all but this.
The issue has NOT disappeared. I have v14.2.0 build 47 on Mac, Creative Cloud offers no newer version, and I have just seen that the Add keyframe button removes the previous keyframe (on the remapping value of a video) most of the time, apparently not only depending on whether the mouse was moved off the button before each click, but also if the playhead is changed with the arrow keys instead of using the mouse. Using the mouse the bug disappears. This is the second bug I'm finding in only a dozen minutes of usage. Back to FCPX it seems…
Mark McKee commented
Update, this bug has been correct with the latest Premiere Pro update. Nice job engineers! Thanks.
Mark McKee commented
Thank you Matt. Yes, it is happening in the video tracks as well. The problem is that I'm used to adding a keyframe, and leaving the cursor over the add keyframe, while moving the playhead(?) in the timeline using shift+arrow, then just clicking again on the add keyframe button, but now, it deletes the keyframe I just added, unless I move the cursor off the button, then back on.
I thought I was going crazy, and so I have dubbed it the Great Premiere Gaslight Bug of 2020. I'm sure the good folks will undo the error. But someone needs to prioritize it. I've never seen anything like this in Premiere, ever. I'm just saying it must be accelerated to the very top. If you don't fix it immediately and I'm forced to slow way down and re-learn the sequence, to get by, and our workload just increased 10X this week... I need to know that you can undo this unforced error. I love Adobe and I'm just trying to help. Everyone makes errors. How you fix them is key to keeping your well deserved stranglehold on the market. It's a bad bug, at a very bad time. I so don't want this to be your Final Cut X moment. Best of luck hunting it down. pesky bugs!
Matt Stegner commented
This is a known issue (DVAAU-4202460) that is logged against audio only right now. Is it happening elsewhere also? Your report above doesn't specify.