Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reversing Clip - Draw Mask Keyframe Control Points overwritten/clobbered by first keyframe #384

Open
belisoful opened this issue Jul 11, 2024 · 0 comments

Comments

@belisoful
Copy link

belisoful commented Jul 11, 2024

Apple Feedback Assistant ID: MISSING

DESCRIBE THE BUG:
With a set of keyframes in the Draw Mask Effect on a reversed clip, resetting the clip or RE-reversing the clip causes all the keyframe data to be set to the first frame data. All but the first keyframe mask data is gone.

The keyframe time sequences do look properly reversed, but all the mask points are all set to the first keyframe of data.


TO REPRODUCE:

Make a new compound clip. Make a basic clip in the compound clip and reverse it, Put on a Draw Mask effect on the reversed clip within the compound clip. Make a few keyframes with different mask points. Un-Reverse the clip. The keyframe timing is reversed but the first keyframe control point data is in all the keyframes.

Not sure if this happens outside the compound clip. Other effect plugins may have the same problem with custom data being clobbered by reversing the clip. I tested with the Transform > Scale on two data points, the keyframe data was retained on reversing the clip.


EXPECTED BEHAVIOUR:
When reversing, or unreversing the Draw Mask keyframe control Points should be preserved


SPECS:

  • 2021 16-inch MacBook Pro (M1 Max, 32GB RAM, 2TB SSD)
  • macOS Sonoma 14.5
  • Final Cut Pro 10.8

ADDITIONAL COMMENTS:
I tested the clip reversal on the Shape Mask Keyframes. They work as expected. It may just be the "custom data" aspect of the Control Points is the Draw Mask Effect. This may be a bug in other effects with similar custom data fields.

Please implement a built-in Apple Dvorak keyboard layout for iOS. Accessibility is important. Without it, Apple is saying accessibility is not a priority, not even important enough for something that simple and cheap. It's basically just a file configuration at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants