December version is unusually sluggish.

[DamianBericat-SAE]

Hi, friends, I wish you all a nice 2025!

I've noticed two somewhat annoying things in PrPro 2025.1.0(b73)

- After an hour or so of editing, it becomes unusually sluggish, with lags as long as half a second to playback. Restarting the program seems to fix it... only for another hour or so. This is a performance issue new to me with my hardware.

- It stopped autosaving. It's configured to do so, but it won't, not for love, not for money. Simply put, this version does not autosave. I am being forced of saving copies at regular intervals. Are any of you experiencing this nonsense?

Other than that, it works fine, at least the features I got to test in such short time.
I'm on an oldie but goldie PC AMD R3700X, 64GB RAM DDR4, Radeon RX6700 XT 12 GB VRAM DDR5, which had no problems until now and does not slug around in any other video app. Win10 up to date, CC up to date. No unusual resource consumption, 46% memory, 6% CPU used when lagging on Premiere.

[Kartika Rawat]

HI Damian223357108vrz!

Sorry to hear that. Could you try deleting cache files and resetting preferences? Check if the GPU Acceleration is enabled (File > Project Settings > General), as it can sometimes cause issues with specific hardware.

For the Auto save issue: Double-check your Autosave settings (Edit > Preferences > Auto Save) to ensure everything is configured properly.

Could you verify if your scratch disk location is accessible and has enough space? A lack of space can prevent autosaving. 

Let us know.

Thanks,
KR

[DamianBericat-SAE]

Hi Kartika. Thank you very much for your response.
Yes, GPU acceleration is fine, cache has been purged and preferences as well. In fact, it's an on again off again problem, it does it most sessions after a couple of hours editing, but not all sessions... Auto save is, of course, enabled. For some reason, four projects won't autosave no matter what, while opening an old project resumes it's autosaving features. Cleaning preferences didn't help with that matter.

Regarding disk space, I have a dedicated SSD for projects, cache and templates, currently 65% free.
I am reinstalling everything to see if autosave comes back; it's really a PITA having to save as every hour.

Another weird thing that never happened before is that some shots lose sync with their audio (not the original audio, but the external recorder one) long after being edited. See, I have camera shots with reference audio and four tracks of audio being recorded separately; Everything is properly synced, I edit, everything works, a couple hours later I playback a scene, and some clips are out of sync. They are exactly seven frames late. Not a track issue, since not every clip is late, but some are. Not many. Just the necessary amount to make me waste a good hour of my life checking the sync of the entire timeline. Gear hasn't changed, workflow hasn't changed, media files are consistent, it just does it. Never done it with former versions.
On a brighter note, really annoying problems from previous packages look corrected: no issues with DL or with quality loss just because.

I'll keep you posted.

[DamianBericat-SAE]

Update: reinstalling the whole CC did the job for the autosave feature. Slug temperament comes and goes, sadly.

[Luke2984491936f6]

I have the same issue; I'm not sure why it's happening either. I rolled back to Premiere 2024 and it helped some, but there is still some lag for me. Try rolling back to Premiere 2024 and see if it helps.

[DamianBericat-SAE]

Unfortunately, I rely a great deal on Dynamic Link, and 2024 versions cannot be linked to 2025 AE projects

[MyerPj]

Can you not install the matching (v25.x) AE? You can run/have them both (installed) at the same time.

[DamianBericat-SAE]

Yes, Myer, but I already have the projects on a newer version, and 2024 will be unable to open them. In the long run, with all my ongoing projects, it'll be better to fix this, or wait until Adobe fixes it, than rolling back.
If I had to start something new right now, yes, I'd go with your workaround. But, honestly, I do workarounds only when I run out of proper solutions.

[MyerPj]

Understood, thanks for your comments. @Kartika Rawat has responded here already, hopefully the staffers will follow up with you.  🙂

[Luke2984491936f6]

Just so you're aware, there are tutorials on how to roll back projects. If you have something you need to finish now, I would recommend finding a youtube video on how to roll back projects.

[MyerPj]

You could roll back, but do take note of what @Kartika Rawat said about deleting cache. It's a real good idea to do that with every update, (or roll back). 

Hold down shift as you start PP from the normal icon.

[DamianBericat-SAE]

That's solid advice. Everyone reading your answer would do good following it.
I do it every time, at the end of every project and after updates (I never allow PrPro to update mid project, not changing horses in the middle of the river and all that...)
And you're right, it's a healthy thing to do.

Thank you.

[MyerPj]

Great point, after a project is finished, no need for the cache of those files. Actually, I've never seen a downside to deleting a cache. Also, not changing horses in the middle of the river! Ha, ha... 🙂