Copy link to clipboard
Copied
You will only see this if the clip is a different resolution than the sequence. (higher or lower) On a Mac Studio, but this also does this on iMac. Has been this way for years. Only solution is to next the clip, but we should not be nesting to fix bugs.
Put the clip in a matching 4K/uhd sequence.
Animate the transform effect.
Then nest into HD timeline.
@Michael7G this issue should be resolved in 25.0 beta 14. If you still encounter the issue please let us know, and apolgies for the disruption to your workflow.
Copy link to clipboard
Copied
I can confirm this is once again an issue for me... This has been going since 2017 and noone fixed this, I'm furios 🤬
Copy link to clipboard
Copied
@creative_Lionheart5C13 a fix is available in the current 25.0 beta. If you can, please give it a try and let us know if you still have issues.
Copy link to clipboard
Copied
Put the clip in a matching 4K/uhd sequence.
Animate the transform effect.
Then nest into HD timeline.
Copy link to clipboard
Copied
Yes nesting - the solution to everything. Not because you need to nest for the project, but to fix the fact that Adobe has a problem with the internal structure of resolution handling in Premiere Pro (and others). It is all locked to legacy resolutions and aspect ratios that are ingrained in the architecture of Adobe products. Built in an era of SD and HD and 16x9 and 4x3.
Just look at the color pickers that are spread across all the applications. How is anti-aliasing handling of type working between AI, PS, AE and PP?
One day they all might get on the same page, but for now it seems to be, "Hey you, get off of my cloud!"
Copy link to clipboard
Copied
@Michael7G this issue should be resolved in 25.0 beta 14. If you still encounter the issue please let us know, and apolgies for the disruption to your workflow.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now