Constant beachball and crashing in Premiere 23.4
Not sure if this is an issue with the new 23.4 update, but for the past 2 days I've been having a lot of issues with Premiere having a constant beachball every time I make any change, to the point that it stops responding and I need to relaunch it. It's very random, sometimes I can work for 15 minutes, and other times I can't even move the mouse once it's opened. It goes directly to "not responding". Even if I have Auto Saves every 10 mins, I've lost a lot of progress and time having to deal with this.
After going back to previous Auto Saves and trying those projects to see if they weren't "corrupted", I resetted all the Preferences in Premiere, cleared all Media Cache. I opened a new project and imported the one that was giving me problems to see if it would help. It got stuck on the beachball again while trying to import it, maybe 30 mins... (I have to say it's a big documentary with a lot of footage) but seconds before I gave up and Force Quit again, the new project opened and started working fine.
I hesitated before activating my Keyboard shortcuts again, and my Window layout, just in case those were the ones causing the problem, so I created a new Window layout from scratch and waited before adding Keyboard shortcuts. I added the Keyboard Shortcuts and it worked well (it weirdly changed my "Paste to Targetted Track" setting though). Now, when I decided to update my Default Audio Transition duration to 3 frames as I like to have it, it started acting weird again.
I've never had a constant issue like this in Premiere happen to me before. It's really frustrating cause it looks like there's something corrupt inside the project but at the same time, it doesn't make sense that the settings I choose are making the program become corrupt? It's very frustrating as I've lost 2 days of work trying to fix this.
I've been working on the same project, with the same amount of footage, and the same setup for the past 7 weeks and only started getting these weird glitches yesterday, so I'm guessing it might have something to do with the new update? Has anyone experienced something like this before?
Here are my specs:
2017 iMac Pro
Processor: 3.2 GHz 8-Core Intel Xeon W
Graphics: Radeon Pro Vega 56 8 GB
Memory: 32 GB 2666 MHz DDR4
mac0S: Ventura 13.0
Thank you
