Skip to main content
Participant
January 20, 2022
Question

Productions - Certain clips causing copy and paste crash

  • January 20, 2022
  • 2 replies
  • 652 views

I am working in Adobe Productions on a long form documentary. The editors move sequences across projects within the production. We have found that copy and pasting sequences from one timeline to another whether it is in the same project or another causes infiinite beach balling/hanging and crashes. This happens with copy and pasting, but also with bringing in media through the source monitor or media browser, or importing sequences. 

We recently have been able to narrow it down and realized that this issue is specifically prevalent when copy and pasting clips that were digitized from super 8 film. I tried re-encoding the clips to a slightly different custom Prores codec but it did not help the issue. 

 

Here is the information on the clips: 

720x486

Codecs: Timecode, Linear PCM, Apple ProRes 422 Proxy 

Color profile: SD (6-1-6)

 

If anyone has been able to sucessfully solve a similar issue I would appreciate any suggestions. 

This topic has been closed for replies.

2 replies

Participating Frequently
November 26, 2024

I am in exactly the same boat. Same size/type of production. Longform Documentary in Productions.  Same crash. Certain very specific clips crash upon paste. This is true whether JUST the clip, or the clip amongst others, or the clip embedded in a sequence or nest. Infinite beachball. 

I have tried to RE-RENDER the clip in Davinci Resolve to create an alternate ProRes copy and Replace Footage: No improvement. The CRASH appears to be due to the pointer files surrounding the clip rather than the codec or footage corruption. Same test was run via Quicktime and an MP4 copy. No dice.

Still investigating.

Participant
January 30, 2022

Does the sequence you are copying from have any sequence markers? If so, try removing these and then try to copy again.
We had a beach ball issue earlier this week, and after trying to copy several times we removed the sequence markers, and voilla it worked

Participating Frequently
November 26, 2024

That is the craziest programming error I've ever heard of. I'm trying it.