Copy link to clipboard
Copied
I haven't had any problems stabilizing hyperlapse footage in After Effects.
Well, nothing works at a resolution of 5K (5120 x 2880). AE doesn't even begin to analyze.
I've only been working on 5K since I got a new computer with an i9-13000KF, ASUS RTX 4090, and DDR5 64GB, Windows 11 Pro
That should work.
What could be the problem?
Greetings
Jurgen
Copy link to clipboard
Copied
Hi Jurgen,
What happens when you try to use Stabilizer? Do you see any error messages? Does it happen with all the media files or a particular one? Have you used Time Remapping to create the hyperlapse and try trying to stabilize the same footage? In that case, You might need to Precompos the footage as the Stabilizer doesn't work with the Time Remap.
Let us know.
Note: Moving this thread from Bugs to Discussions for troubleshooting.
Thanks,
Nishu
Copy link to clipboard
Copied
Hello Nishu,
thanks for the quick reply.
No, the images were previously only edited in LRTimelapse and Lightroom Classic and then imported into After Effects as JPG.
The blue bar appears when stabilizing, no error message and the analysis begins, but stops at frame 1 of 293 during initialization.
This doesn't happen at the size of 1920 x 1080, nothing works at 5120 x 2880.
Greetings
Jurgen
Copy link to clipboard
Copied
I have now managed to stabilize the hyperlapse with AE.
However, not as I would have liked.
As a precaution, I made more cache available in the settings, but unfortunately that didn't help.
I tried to reduce the resolution in AE by downscaling. No success, it started to analyze but stopped at frame 77.
Only when I imported the photos as 4K - 3840 x 2160 was I able to stabilize them.
So After Effects cannot stabilize above 4K.
My new computer is a monster for this work.
CPU, RAM and graphics card, the best available in the consumer sector.
Are there any settings in AE that I haven't taken into account?
Greetings
Jurgen
Copy link to clipboard
Copied
Hello,
Now it doesn't work at 3840 x 2160 either!
Does anyone have any advice?
Greetings
Jürgen
Copy link to clipboard
Copied
The Adobe supporter connected to my computer, but unfortunately that couldn't solve the problem. Ultimately, the new BETA version provided a solution. I assume that this was a bug that has now been fixed.
Greetings
Jürgen