Stop changing value of Lumetri Curve when manually adding keyframe

[Pierre Louis B.]

When manually adding keyframes to the Hue vs Sat curve, for example, the act of adding a keyframe sometimes bumps the curve up or down by a small amount rather than just adding a keyframe to the cursor's location. This should never happen by mistake.

[Kevin-Monahan]

Hello @Pierre Louis B.,

Thanks for the message. It’s been a long time since you filed this bug, and I apologize for the lack of a response. Are you still having this issue? If so, the team will need more information from you to reproduce the bug. Can you provide the information required here? How do I write a bug report?

I'll move your post to the Discussions board while we await your information.

Thanks,


Kevin

[Pierre Louis B.]

Hi Kevin,

Yes, the issue still happens.  The only steps for reproducing this issue is to add keyframes to the Lumetri Hue Saturation Curves.  It doesn't happen every time.  Maybe once out of every 20 clicks.  Haven't you or others on the Adobe team noticed this quirk?

This issue is currently happening on my M3 16" MacBook Pro, Premiere 24.1.0. 

Thanks

[Kevin-Monahan]

HI @Pierre Louis B.,

I have seen a similar bug in another part of the UI as a user. I moved this back into the Bugs forum. I'll make sure it is filed internally, too.

Thanks,
Kevin

[Kevin-Monahan]

HI @Pierre Louis B.,

I have seen a similar bug in another part of the UI as a user. I moved this back into the Bugs forum. I'll make sure it is filed internally, too.

Thanks,
Kevin

[Kevin-Monahan]

Hi @Pierre Louis B..

Any improvement with this issue? I have heard that engineers are working on it. Let me know.

Thanks,
Kevin

[Pierre Louis B.]

Hi Kevin,

In my latest use of Pr, the issue happened once but seemingly less than in the past.

What I'd really like to see addressed is the complete lack of respect that the Pr team seems to have for established workflows that most if not all other software companies use, and even Adobe itself uses in its other programs, such as:

1. Alt-stretching a shape's side to stretch the opposite side at the same time (the lack of this makes Essential Graphics worse than the Titler was)
2. Shift-selecting to select a range of items and Ctrl-selecting to select individual items, in every part of Pr, not just certain parts of the program while arbitrarily ignoring this convention in other parts

I could add a lot more examples, but I'll keep it at 2.  For the Pr team to disrespect established conventions isn't just confusing and frustrating for users, but it comes across as out of sync, crass and disrespectful to users and their time.

Hopefully the Pr team can promptly fix these issues that never should have been programmed into Pr in the first place.  Whenever an established convention is changed, it should only be done if there's an actual, concrete advantage for the end user.

[Kevin-Monahan]

Hi Pierre,
I'm still able to reproduce this issue. Sorry for the frustration.

You can request features and behaviors of those features in the Ideas forum. Create one post for each "idea." I apologize if the design of certain features comes off as abusive; that is never intended.

Thanks,
Kevin

[Kevin-Monahan]

@Ron Rigler - can you comment on the issue?

[Kevin-Monahan]

Updating the status of this bug report.