Skip to main content
Participant
December 4, 2020
Question

Beach ball when trimming and moving clips

  • December 4, 2020
  • 1 reply
  • 343 views

Hi

I already posted about a problem on my Macbook Pro. Premiere Pro won't start on that machine.

 

On my Imac Pro it runs. However, when editing I have a problem.

 

When I split a clip and trim it, the beach ball will appear for a couple of seconds. 

 

If I try to move a clip on the timeline forward or backwards same thing: the beach ball appears for a few seconds.

 

[Typo in title fixed by moderator]

This make the editing ectremely long.

 

Any help?

 

Thanks

1 reply

D Graham Withers
Participating Frequently
September 23, 2025

I'm having the same issue with multiclips using Productions 25.2.3, Lucid Link for the project file and a Mac Studio M2 Ultra - a real pain!  You ever figure it out?

In the past, rebuilding the cache has worked but I'm getting no love.

Kevin J. Monahan Jr.
Community Manager
Community Manager
September 24, 2025

Hi D,

Thanks for the message. What happens if the media is on a local drive? Do you still have the issue? What kind of footage is it? Let the community know. I hope we can assist. 

 

Thanks,
Kevin

 

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
D Graham Withers
Participating Frequently
September 24, 2025

Thanks Kevin!

The media is on an 8 drive RAID 5 connected by TB3 so should be plenty speedy.
I'm not having the issue in other projects and simpler sequences so I started a new sequence with fewer clips and the issue resolves but I'm worried about the timeline gettting longer/more complicated again as I'm on a feature doc.

The media is a mix of DV NTSC 29.97 &  1080P H265 multicam clips but the beachball happens on both types of media.   I've tried flattening the multicam clips & disabling the unused audio tracks in the multicam clips to no avail. 

Of course, I'd usually start with proxies for the H265 material but I wasn't having trouble until the timeline's gotten longer...  Maybe Premiere gets overwhelmed bringing things into RAM when the trim tool is enabled?

As playback is smooth, I hoping not to go through the trouble of proxies if that isn't going to address what's going on.  Thx y'all!