Premier Pro lagging on 24 and 23 versions.

Thanks for the update! I honestly don't mind moving back to 23 because the features are not really game-changers, nor have they really improved my workflow. I can live with auto-save interrupting me again, if that means the beach ball isn't interrupting me with every click. I'm gonna give it a try and will try to remember to report back.

So an update on my original post: 

Adobe still seem to not be able to fix .24 issues on Premiere Pro across Mac and Windows. I'm still using a mid year version of .23 and it runs really solidly! Obiously I am missing some features but for my work I'm not missing out too much. About the comments on RAM 16GB on my MAC has been plenty. This may be due to me not using Premiere too intensively. Until I have the patience to try it again I think I'll just stay on .23 for now!

Same problem here. I've tried everything. The app is unusable.

I decided to record the screen as I have a feeling the whole conversation went a bit off-topic.

I don't believe there is a machine power problem because:

• The same project worked normally in the previous version of Premiere Pro.

• After removing music from the timeline, it works normally again.

• There is a significant delay with actions that I don't see as performance-heavy (selecting clips, deleting clips, undoing).

In the recording, I added text titles for my commands and left them on the screen for the duration between input and action happening because the screen recording sometimes does not show the spinning beach ball. You will see that after removing some of the audio clips, the project starts working normally again.

This is a new issue in the 24 version, and it would be really helpful if someone knows what is happening differently in the background compared to the previous version. Thank you for the time and help.

Recommended,  on their list, and to many users, is really a minimum figure for most work. It will work mostly, and for some things pretty decently. Especially on the new Macs with their integrated memory.

Until, of course, it ... doesn't. And    things    slow ... down.

I work for/with/teach pro colorists, mostly Resolve on Macs, and they think a rig with 128GB of RAM like my PC is a middling rig at best.

R Neil Haugen,

"As to the Mac ... I wouldn't expect much pro level work to go well under 32GB of RAM these days."

Note that 32 GB is double the recommended RAM per Adobe documentation.

(Also, anecdotally, I have a Mac with 32GB RAM and have not encountered issues.)

R.

Frustrating, yea. But thanks for posting your playback situations and what you've tried. Definitely a help for others to both troubleshoot and to report similar problems here.

So, after working for an hour or so in the timeline with replaced .pek and .cfa files, I was still having lagg of about 3 seconds performing some of the tasks. So again, I went to the solution of erasing all the music tracks in the sequence and it got me back to realtime editing speed known to me from previous versions of Premiere Pro. I did set Audio Default Input to No Imput earlier and it had no effect. The problem seems to be happening somewhere in the back and is really bizzare, as it happens also if there is a timeline with music opened in the top bar, but I am working on a timeline that has no music. I just got used to the previous version being working the best in 15 years and now this.

For the OP, a six-core AMD CPU with only 16GB of RAM is a pretty minimalist machine for present Premiere needs. Neither enough cores for processing, RAM for cache, and no H.264/5 processing in hardware.

As to the Mac ... again, not a lot of RAM. I wouldn't expect much pro level work to go well under 32GB of RAM these days.

For Macs in general, I've seen a number of posts on the pro Premiere Facebook user page that they had to sort out permissions and security issues, and suddenly, Premiere took off great. Prior, it was a dog. Not being a Mac person, I can only report that, not what the specific items were.

As to audio settings ... for many rigs, over the years, the better option has been to set the  Preferences/Audio Hardware option, "default input", to none. No clue why, but it just works better.