Skip to main content
A
aa120
Participant
December 12, 2022
Question

[NEED HELP RQ] MBP13 M1 (8GB/512) SUPER SLOW AE & ME

  • December 12, 2022
  • 1 reply
  • 291 views

MBP13 M1 (8GB/512)
Problem: SUPER SLOW AE (18.4) & ME (15.4)
Cached files and everything (all version, all adobe programs, absolutely evthing) - DELETED (deleting cache files sometimes when i see a little lags)
Cached files in Media Encoder folder - DELETED (.cfa .pek) (method)

Good AE settings:
- Save 5 copies every 2 min, max project versions 100 (doing motion a lot thats why)
- Disk cache 250-300GB
- Intalled RAM 8GB - for other apps 1,5GB - for Ae&Me 7GB (MAX)

Using some technics:
- "quarter" preview and then just waiting until each frame is loaded into RAM
- i can also use every quality starting from quarter and then ending with full quality preview just to make sure every frame is loaded into RAM and then Me can render evthing faster, rarely using auto quality
- turning off mbp completely, then after half an hour i turn evthing on from the very beginning and continue to work in projects

I think that reducing all these problems to the fact that this program is not official is not worth it now, it feels like something happened at some point with the laptop, maybe I have accumulated too many projects with animation that weigh a lot mb..

I know I'm not alone with dealing this s***, need help rq guys, thanks!

This topic has been closed for replies.

1 reply

A
aa120Author
Participant
December 12, 2022

using Ae 18.4 through rosetta on macos big sur (still not updated)
evthing was cool bbut when I started getting a bunch of projects evthing started to function a little slower, sometimes Ae used to work quickly, Me rendered evthing fast but sometimes Ae & Me just stopped and didn’t want to render, as it is now and still, I can’t even view simplest animation I made from last week to tweak a couple of things in this project and render later. 12 second video with super light animation, there are quite a lot of layers from Ps. Just imagine 12sec30fps animation but even quarter is not showing frame in preview window, this windows was empty... I think it is also connected with these layers, the layers have a bunch of adjustments maybe thats why its really slow. I remember when I used Ps text layer, then converted it to the Ae text layer, render was slow af omfg (this text layer had a few effects inside after coverting from Ps text layer to Ae text layer).

 

 

 

nubnubbud
nubnubbud
Inspiring
December 13, 2022
  • do you have them both open at once? ME is spectacularily inefficient as an external encoder- you may as well have the program open twice, and I just export an intermediate format then encode in premiere. If you haven't tried it, I would suggest just exporting straight out of AE whenever possible. I think ME's team just wants a reason to exist- but they'd have to do something better than the other programs for that.
  • You only have 8Gb of RAM. that's downright anemic for these unoptimized, bloated programs. one at a time is more than enough to fill 8Gb of RAM https://helpx.adobe.com/after-effects/system-requirements.html < and the devs tell you. if someone sold you that computer, and told you it could run these programs, that's false advertising. It doesn't even meet minimum requirements. (shame on apple for selling something with lower specs than my $1400 2017 budget workstation and advertising it doing things it's not rated for.)
  • avoid switching preview quality. if you preview 50% and 25%, both will be stored in RAM, shunted to disk, or both. Adobe is super naive and has a super inefficient, uncompressed storage.
  • there's a reason edit>purge>all memory can be bound to a shortcut. adobe's naive memory handling needs to be cleaned up manually and often, so here's the broom. get purging.
  • you seem to be working on a Mac of some sort. Macs, in my experience, love to swap. if you run out of RAM, it'll start using your drive as RAM... and that's so slow it'll look like it just stopped.
  • if you preview at 100%, anything previewed in RAM or cache gets just thrown into the render to speed it up. consider purging and doing that when you're getting ready to export.

 

complain at adobe. they're complacent and haven't updated the core code since ever perhaps. it's a 30 year old program and we're all sure that if it used the GPU or multithreading, or had an actual acceleration to its previews beyond "stick it in RAM" it would run fine.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices