Interface is Slow and Laggy

Well that's a lot of posts for a weekend. 😊

A few responses:

* The AE team are on these forums, responding as we can. We moved off uservoice over to the forums to be able to do a better job of engaging with our community. Hopefully that's being felt. Sorry if we didn't move everything over, if you have specific things for us to look at, please let us know. 

* We are definitely working on the UI. A new release of AE is coming out very soon and we have incorporated the UI fixes that have been in Beta of late. If you're on Windows, the timeline should be more performant. We haven't solved every case, but we are actively working on it. MacOS timeline has some decent perf (90fps on my Mac arm system) but we will keep pushing on both Win and Mac. 
* While we can't officially talk about future work, please hear me when I say we are taking the UI design, usability and performance as a very high priority. 
* The majority of features we've worked on the past 2-3 years are a direct result of feedback from the community. We've had to take them in some order, and I know it's not fast enough, but we are systematically working through the backlog. Yes, 30 year old code can be slow to update, but we are updating it, focusing on rewriting pieces, trying to make AE more stable and make AE what our community needs it to be.  

Keep letting us know what doesn't work and we'll keep you updated as we make progress. 

Thanks,

Sean

Group Engineering Manager for AE

@Warren Heaton10841144 @Scott.C. 

https://imgur.com/a/jP6OPa8 
let's just say, I wouldn't be complaining here if it was in a "usable" state. 
I was only on uservoice originally, but then they decided critical bugs and program-breaking errors didn't warrant a direct line to the devs. Enjoy no more crowdsourced bugchecking, idiots. (I'm still salty about having a bunch of my posts deleted for not being in the top 2.85% in popularity I made those so your devs would know what errors were occuring when.)
that I paid $600 a year to be treated like dirt is pretty much a scam, except even scammers have the decency to pretend you're getting a good deal, I've gotten my fees reduced twice, because I was being overcharged by a team that didn't think I'd have the guts to speak up- there have been no performance improvements or updates that didn't add something significant that already used to exist in a previous version, let alone the price scheme is a hard upsell because the 3 apps video editors need come in at more than the entire suite, and every. one. is. cumbling, ancient nonsense.

Don't get me wrong- I started in CS3- I know what the programs are like, and what they used to be like. You might be able to say "this is industry standard" to a college kid getting their first programs, but I had the experience of owning them, they were mine, and they worked well, and they didn't need updates once. It's an unspoken truth that pirating protection was soft in the beginning to allow a wider audience to get hooked on it. Now you have a huge collection of editors who know for a fact that the still available pirated 2008 software was vastly superior to a suite that will run you thousands over a couple years.

The programs are now filled with little gimmicks that mean nothing, while things like clicking the play button on a video, and zooming in are buggy and barely functional. I'm convinced that it's all the dev teams can do, and at some point, I just wish they'd... stop. it would be painful. for everyone. but maybe then, someone up top would notice that something is wrong.

These poor dev teams. I feel for them. they watch the company looming over them suck up billions in revenue, while they, in relaive comfort I hear, are not given a team sufficient to even maintain a software, let alone write the new one we need. They serve a purpose of providing essential life support to adobe, but are given no medicine to even ease the behemoth's pain as those at the top ride it into the ground.

if CS6 was made available again, and all updates were halted as the team made a new After Effects using what they've learned from this one, but with modern hardware and code at its base... I think it would be wonderfully successful.
but that won't happen because
adobe's programs aren't even legal half the time 
and covers up lawsuits by passing the costs onto their clients 
and delete the files they're afraid of being exposed for 
and threaten their users for remaining loyal instead of switching 
and refuse to provide reliable long term support, so they can bury their tracks every fiscal year. 

and you guys still owe me 2 seats of Adobe CS6 that you deleted from my account or the $1040 that's worth.

Hello to all. I've experienced terrible performance in AE2023. Ae 2022 works as expected, while 2023 turns out as a nightmare, unusable. Well, here is my discover, i'll post here my reply in this thread https://community.adobe.com/t5/after-effects-bugs/ae-2023-2-1-3d-is-unusable/idc-p/13665866#M2992

(This mobo settings are there from the beginning, and affect only AE2023 performance)

Hello to all. I have an update, probably other people may have the same issue and are just looking in the wrong direction. I've formatted the PC and then i've reset the Bios to the default settings. It seems that the Optimization tool of Asus was running in background. Now the program is 200% faster and doesn't mean if you have hardware acceleration on and gradients on. So, probably the terrible performance of other AE may be related to Bios settings. I think that is in any Asus motherboard with the new Bios.

NOTE: AE 2022 WORKS AS EXPECTED WITH THE OPTIMAL TURNED ON. IT'S ONLY AE 2023 RELATED.

Hope this diecover may help other people in troubles.

https://youtu.be/M_o81UGqjFI

Warren I would say it's time to take off the troubleshooting hat. I would also love to send you some of my project files and have you screen record your interface running at 60fps and then disect your computer for whatever arcane knowledge you've applied to get it to run perfectly. 

This is an Adobe issue, and one that has existed for as long as I've used AE. The UI bogs down any time you add over 10 layers of keyframes etc. At times, I feel that Adobe doesn't really know how its users use its product, because its up to you to send your project files for them to stress test. The bugs I find are fundemental and never attached to some configurartion issue that I'm aware of. I'm always puzzled why it seems like they are not seeing the same thing that I am seeing, becuase you run into it after using the program for more than 20 minutes. 

Additionally, @jenkmeister17177426 has acknowledged in part here and other threads that the UI code is ancient and needs a major re-write. What I find frustrating as a paying customer is that we can't get a commitment from anyone at Adobe that this will ever happen. It's always "under review" "were looking into it" we never hear, "this is our top priority" or "here is some baseline transparancy on how we plan to rectify this issue." It can feel at times like Adobe is stalling for time because they legitimately don't know how to solve the problem becasue the person who wrote the interface code in 1993 retired in 2009 and can't be reached. 

@Marc Trzepla made this request I think back in 2018 on User Voice and I was told a "senior developer" was looking into it then and then literally nothing happened while UI performance actually decreased. (see layer transforms bug etc). Nothing erodes trust more than having the issue acknowledged and then ignored for FIVE YEARS and then basically being gaslit about it. 

I've tried to be more constructive and positive on these forums and will gladly jump in and send project files etc if it means we can move the needle to some modern software code, but I am starting to feel like @nubnubbud where its just not in Adobe's business model anymore to develop software, as absurd as that sounds. When you hear that AEs team is small that does not instill confidence that Adobe is invested in making the best software they can. It sounds like they are letting AE scrape by with the bare minimum while paying out investors with all our subscription money. And this isn't even limited to AE. Photoshop is also creaking under the weight of an ancient single threaded codebase. I don't use it as much anymore but it was always a laugh at how slow filters still run on a single core. 

Adobe is from what I hear, a famously a great place to work as far as company culture and benefits go. I do think the employees want to take pride in their work and deliver a competent product to their users, but without any transparancy into how these products are developed or what the engineering team priorities truly are, the end users are left to speculate on why it takes 5 years to even get basic functionaly moving in the right direction. I will continue to make noise here until a viable competitor takes the AE mo-graph throne down, but until that day...

@Warren Heaton10841144 
looks like we're back to a condescending "community expert" insisting that a program not being able to display UI at 24fps on hundreds of different modern workstation to laptop configurations, means they're all defective-
but not his, oh no- heaven forbid there's something about his live broadcast setup that differs from a heavy VFX setup.

on every computer I've used, from laptops, to mac pros, to gaming desktops, to workstations, it's only ever been tolerable at best. Adobe products run like snails over a bed of salt, and I'm probably inadvertently insulting snails by saying that. Resolve works fine on 3 of them, windows movie maker worked on 3 of them, and blender edited video just fine on every single one. but you put that video in an adobe timeline? Nah, your computer sucks now.

The only time I've been able to consistently get a fast playback on 2k+ video was before CS6.

Sounds like we're back to needing to troubleshoot someone's workstation.

@Warren Heaton10841144 
I've noticed that functionality is terrible, and works poorly for obvious reasons (if edits are slow normally, why would making them while rendering multiple frames while adjusting already taxed and buggy UI be any better?)

I don't even know what downstream or upstream has to do with any of this- It doesn't matter how many comps deep I go, nesting comps has NEVER increased usability.

I've also noticed we've been over this before, and that time too, you sung praises about editing while using playback, for some reason- a canned response?
you've never had any performance issues and the program works perfectly and there's never been a reason for you to compare it with anything else so you'll just sing its praises all day every day. I'm actually providing criticism here because I've had terrible experiences with this program over the course of over a decade, meanwhile you continually misrepresent issues to maintain an air of superiority.

I'm not talking about upstream or downstream editing, I'm not talking about editing while using playback. I'm talking about the UI not acting in a performant manner. the public answer from Adobe is "When we've investigated keyframe or UI lagging, the primary cause has been found to be 3rd-party script panels or plugins that are also trying to interact with the UI causing these delays" 
but it's important to note that they aren't recognizing that many users do not use 3rd party addons, and that many of the 450+ official addons do interact with the UI, too, including several in the tracking workflow, mograph, and corrective effects, meaning it affects nearly every field of work.

so shush and let people criticize a company that charges broke college students a fee for the honor of cancelling recurring fees for not even using that money to keep their service competitive, then sell that service as a product that you can't own.
They live in your head rent free, warren. you buy their product, but you don't own it. Adobe takes from you, and gives you nothing and you love it because without this thing they graciously allow you to use, you couldn't even do that work.

@nubnubbud 

Surely you've noticed that we can make edits while the preview is running?  Or that we can watch the preview run in a downstream Comp while making edits in a upstream Comp?  

I've found that to be extremely helpful for broadcast 2160p work that needs to be deliverd on a tight deadline.

I think that's likely the source of the issue
it's not that they can't get it running on GPU, but they won't.
AE is over 30 years old now. It existed before discrete GPU's and multi-core CPU's, and never had any code to work with one until about 2012, and that code is still a buggy hack that reduces reliability and actually results in often worse performance, because the code simply isn't meant for paralellization at all.

So... now we're here. at a place we wanted to avoid, because, as it turns out, in all the updates, we only ever got features, and we never got a refactor. We never got a true optimization pass, and we never got the maintainence due, from a multi-billion yearly revenue company. Of course, there's a reason for that. 

It's Adobe's business model.

since 2011, Adobe has not been a software development company. They have not developed anything beyond what a solo developer could, even once. their new business model is Autodesk's. buy out the competition, sail on their work with a subscription model, and run it into the ground, call addons "updates"(ever wonder why AE alone has over 450 base addons?) to prolong investment gains rinse and repeat. look at figma, and substance, and mixamo, and aviary, and frame.io! They buy, then let die.
and previous adobe products are not spared this erosion. After all, They didn't develop these programs, and they've given us no real assurance that they even know how. Why would we ever expect them to rewrite a dying program, just so it could compete fairly, when they could just buy the competition using one year of our cash, hard-earned by using their programs?

Adobe, from what I have seen, is no longer capable of developing or updating programs. they develop addons, and lie that it's an update, before overcharging to fund "expensive development" so efficient that it takes 5 years to remove and add h.264 support (a standard output library), and 7 years to copy a one core render process to a second core(after having introduced it in a more performant way in 2011).

@nubnubbud 

Most software I use these days has figured out how to get their GUI code running smoothly on the GPU. Just look at phone apps? No one would use an iPhone if it studdered as badly as an Adobe app, it would be ripped to shreds in the tech press for being laggy. This is considered baseline performace now, and its a long overdue upgrade. Even Adobe Illustrator (by far not my favorite app but I use it when I have to) can scale and update vectors in realtime on the GPU at 60fps. I would say its interface runs pretty well. So it can be done, I'm just not sure what the holdup is with AE, most signs point to ancient codebase from the late 1990s when people were running VooDoo FX cards.