Skip to main content
Participating Frequently
November 2, 2022
Question

CREATING MERGED CLIPS HANGS MAC M1 Mini

  • November 2, 2022
  • 1 reply
  • 289 views

Hi ! 

So this is super weird. 

Today, an entire computer lab that I was teaching in experienced the same problem for every single student but one and also myself. When merging and audio and a RED clip from within a bin every merge option caused every M1 mini to hang (Spinning beach ball of no return). Only way out was to force quite. Every time, 9 of 10 students. Merging with timecode, markers, IN points, and Waveform audio. There was no way out. 

REDRAW picture footage
.wav audio
Select both clips in an otherwise empty bin, right click MERGE
choose parameters 
Press OK and ....HANG

OS 12.5.1 
Premiere Pro 22.3
Mac M1 Mini 9,1

Any clues ? 



This topic has been closed for replies.

1 reply

R Neil Haugen
Legend
November 2, 2022

Weird!

 

But then the better and recommended option is to join video and audio with the Multicam process.

 

Merge clips has a number of issues because it was designed for quick timeline joins really.

 

Their big pdf file on recommended long-form and episodic workflows stresses this, especially for anything where you may be sending audio out or files for color/vfx.

 

Neil

Everyone's mileage always varies ...
Participating Frequently
November 2, 2022

Thanks Neil, 

I appreciate your response. 

Merging clips from a temp bin is the standard practice, at least in Post on the East coast here, although usually with AVID. Maybe that looks a little old school now ?  And it has worked quite well for the last 6 years, even with proxies and round tripping to Resolve for grading. 

I have read about the multi-cam workaround for merging on the timeline and have used multi-cam for...well multiple cameras. 

Is that document you mention easy to find. I would like to read it. And thank you very uch for pointing it out to me. 

CSL

Participating Frequently
November 3, 2022

As to the Hanging ... who knows? They change parts of the underlying code constantly as part of the general work of updating the underlying code. And that can have intriguinging effects at times ... totally unexpected. Could be something like that, or ... something in a program on your computer interacting with Premiere's audio stuff ... hurts the brain to figure all that out.

 

Neil


I've been told that upgrading to Premiere Pro 23 (October update) seems to have fixed the proble. It could also be that the cache or the prefs need to be cleared to move on from the issue.