Skip to main content
Participant
May 9, 2022
Question

Permiere hangs (crashes) when selecting specific merged clips

  • May 9, 2022
  • 4 replies
  • 2557 views

I’m working on a documentary. I have several merged clips (created from separate audio and video assets), that when selected, crash premiere (endless beachball).

 

I’m on a new 16” Mac book pro with updated OS. The project is stored on the internal SSD. Any timeline that is associated with these problematic clips play and scrub without any issues (from multiple bins). Original media also plays without issue. It’s only when I try to select these specific clips directly, does the issue occur.  I can’t even select the problematic clips. I just try to select them and Premiere freezes with the beach ball. I discovered this when trying to view the end of the clip to make sure all the footage was in a timeline.

 

Things I’ve done to try to fix the issue: Updated all software with restarts. Reset preferences. Cleared all media caches. Created new project and imported old project into it. The issue still persists only with these specific clips. The clips are in several separate bins, and other clips within the bins select and play without issue. The original un-merged camera video also selects and plays without issue.

 

One thing that happened just before this issue: in an editing session, the project had a few momentary glitches when trying to save. Any thoughts?!

 

 

Specs

Macbook Pro M1 2021 16 inch

Monterey 12.3.1

Premiere Pro 22.3.1 build 2

This topic has been closed for replies.

4 replies

Participating Frequently
November 3, 2022

I also am having this exact problem. Copletely different computer. Merged clisp were working mostly perfectly a few updates ago. This is crazy. 
Premiere 22.6.2
OS 12.6.1

iMac 18,2  32 GB Ram 3.6 Quad i7 Rad Pro 560 4 GB

Legend
November 3, 2022

If it was working ok in a previous version of Premiere 22, revert to that version...    To reinstall a previous version, open creative cloud and click on the ellipsis (the 3 dots) to the far right of Premiere 22 and choose "other versions"

 

And what are the properties of your source clips?  Might give us a clue to the cause of the problem.

Participating Frequently
November 3, 2022

RedRaw and .wav were the source files. I've used the same files for 6 years to test process and this weas the first time this happenned.

Participant
July 22, 2022

I am having a similar problem. I merged clips from my video camera with the higher quality audio from my lav mic (the "merge clips" function is set to remove the original audio and replace it with the better audio), the clips work fine and play just fine in the preview window, but as soon as I try to drag the clip onto the timeline I get the endless beachball and I have to force quit Premiere. Is there anything to be done about this? I already tried uninstalling and reinstalling Premiere. This is a huge issue as it is making it impossible for me to edit my project unless I want to manually realign the audio every time I add a new clip to my timeline.

Kevin-Monahan
Community Manager
Community Manager
July 25, 2022

Hi nataliea,

Sorry about that. Is this a standard project or a team project? Let me know.

 

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participant
July 25, 2022

Hi Kevin,

 

Thanks for the reply! It is a standard project. I appreciate any help you can offer.

 

Best,

Natalie

Participant
May 21, 2022

I've just encountered this same problem. It's all the clips I've merged whether it has glitches or not. The most recent update seems to have triggered this for some reason.

Community Manager
May 21, 2022

Hi kendrad57257741,

 

We're sorry about the poor experience. For testing purposes, would you mind running the app in Rosetta mode & check if it's working properly?

 

Thanks,

Sumeet

Community Expert
May 10, 2022

If the video has glitches in it it can cause an error in Premiere. You may want trim the video and create a new video where there are no glitches in the file and see if that helps.