Premiere 2025 is an embarrassment

Report · Jan 07, 2026

Anybody on the premiere development team should be truly embarrased with premiere 2025.

I have spent the better part of an hour trying to import a sequence from one project into another and save...that's it and premiere simply will not save without crashing and forcing me to start over again. This is a new issue, aside from the absurd interface lag that makes this version completely unusable on all levels.

It is 2026 and version 2025 is still not usable. When I look at the known bug list I see many unsolved bugs from april of last year, nearly a year ago. You should not be releaseing any new "features" until the software is at least usable, which in it's current state it is not.

Report · Jan 07, 2026

I've been doing that without any issues ever ... and if it was wide-spread, there'd be a ton of complaints about it. So ... my guess is something in your system is off, somehow. Which is easy enough to have happen.

Have you dumped the cache files? If not, close, launch while holding the Shift key down, select the option to dump all cach files.

Report · Jan 07, 2026

That behaviour usually points to a project that’s become unstable.

To narrow this down, a couple of key questions:

How large is the project file?
How long are the sequences you’re working with?

Report

It turned out the issue was premiere building waveforms in the background (I have very large/long files). Once I turned off "build waveforms in the background", everything worked normal. Background processes should be that, in the background and not effecting what I am doing in the foreground.

And to Neil, I researched this before I posted to try and find a solution and come across quite a few people with this same problem, here is one such example of exactly what I was experiencing

https://www.youtube.com/watch?v=5sqxLC0t54M&t=308s

Just because YOU are not experiencing it, doesn't mean it is not an issue, I hope you understand that.

Report

Your latest post was an excellent stating of the issue, well done. And showing something that needs to be addressed ... that is exactly what people would hopefully do when reporting issues, as then it can become clear right quickly if they are simply doing one or more steps wrong (wrong really only to what Premiere expects) or something, as well as when there is clearly an issue.

And in this specific case, yes, Premiere can be well off in dealing with several of the cameras that record many audio channels. And it is often an "intermittent" thing for some users, where even cameras set the same are treated differently in Premiere, and that is really a pain.

In my comments, I tried to be as clear as possible that no one should expect their experience with Premiere to be "universal" ... I clearly gave my lack of this behavior as one data point. While noting that if it were a huge issue this forum would be swamped.

You do understand that say a hundred users having an issue is still a tiny percentage of the user base? Again, with several million daily users, the only guarantee is some subset of them will be having a variety of issues.

Some of those will be entirely based on things within their system, such as hardware or media or a combination of the two, and some will be hinks in Premiere that may be an actual bug. And there will always be some bugs out there. Annoying as that is.