Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Question:

Question: Newbie advice: avoiding beach ball after every action

I am using the FC trial version, and this is the first thing I'm making. So both my terminology and my process are probably wrong.


I have 43 short film clips that i want to show simultaneously in such a fashion that the clips slide from the middle of the screen to their own location in a 8 x 5 (-ish) grid.


Each clip has been cropped to a square format and transformed. The transformation scales the clips to 15% size, and assigns a location for the clip in the "grid". All clips are preceded by the Slide effect that lasts about 2 seconds. After the completed Slide, I need to show 5-10 seconds of the clips.


To get to this, I:

- imported each clip "on top of" each other

- selected all clips and applied a Crop on them

- selected each clip individually and set the Transformation parameters

- added one Slide effect before one clip, set its parameters, and copied it to the beginning of the other clips


I noticed that if I have more than 5 clips active (as in I press V on a clip to toggle it on/off), I get the beach ball. So I did what I described above by toggling the clips so that I had about 5 active clips at any given moment when cropping/transforming.


OK, so now I have them set up as described above, and I want to render them to one clip, but I'm not doing too well. Most of my clips are now deactivated, and when I activate them (one at a time or all simutaneously), I get a beach ball that doesn't go away. So this seems like Mission Impossible.


So is this thing that I'm doing simply too much for my MacBook Pro 2015? Am I doing this the wrong way? I have disabled background rendering, but otherwise the settings are defaults.


As a workaround, I have thought I could make the first frame of the clips to an image file, and apply the Slide effect to images as opposed to the movie clips, but that gives the wrong end result. Another approach might be to render just 5 clips at a time, and then mix the resulting clips together two at a time using green screen or some unknown-to-me mixing method.


So, as you can see, I'm completely lost, and any and all tips are greatly appreciated! Also, I need to get this done...


Cheers,


Kim Johnsson

MacBook Pro (Retina, 15-inch, Mid 2015), macOS High Sierra (10.13.4)

Posted on

Reply
Question marked as Solved
Answer:
Answer:

I wouldn't do this project in FCP X. I'd dot it in Motion. It would be a breeze. It's $49. Good luck.

Posted on

Question marked as Helpful

Apr 21, 2018 1:59 PM in response to johnssonkim In response to johnssonkim

That is a pretty complex timeline. FCP X has to fetch and decode frames for all the 43 clips, and do all the math calculations for each frame. The beachball usually means the program is waiting on IO, which is not surprising.


It is a sound option to work with several of the clips disabled.

Once you enable all of them, you probably should weather the beachball, then render the timeline.

There’s more to the conversation

Read all replies

Page content loaded

Question marked as Helpful

Apr 21, 2018 1:59 PM in response to johnssonkim In response to johnssonkim

That is a pretty complex timeline. FCP X has to fetch and decode frames for all the 43 clips, and do all the math calculations for each frame. The beachball usually means the program is waiting on IO, which is not surprising.


It is a sound option to work with several of the clips disabled.

Once you enable all of them, you probably should weather the beachball, then render the timeline.

Apr 21, 2018 1:59 PM

Reply Helpful (1)

Apr 25, 2018 10:30 AM in response to johnssonkim In response to johnssonkim

OK, so I made the clips 20% of the originals, but still no luck. What happens is that if I start will all clips disabled, each new clip that I enable appears to NOT use a linear amount of memory, but way, way more. The first about twelve clips turn on nicely, but after that each new clip brings up the beach ball, and starts consuming memory and taking longer. This is now on my 2013 i7 iMac with 24GB RAM. So, for example, from clip 11 to clip 12, RAM usage jumps from 10 GB to 24 GB, but from clip 12 to clip 13 it goes to > 100 GB. I'm watching it climb, and now it's at 128 GB and climbing steadily.


I don't think that makes much sense at all.


But now I am in the situation that I can't even open the project, because it immediately starts to eat up all my memory until my machine crashes. Got to post this before that happens. Is there any way to stop this processing from happening, so that I can swap out the clips for even smaller ones?

Apr 25, 2018 10:30 AM

Reply Helpful

Apr 25, 2018 12:55 PM in response to johnssonkim In response to johnssonkim

BTW, I don't think I read the whole thread. Have you tried transcoding the footage to ProRes? For whatever reason, that Sony AVCS codec makes my Final Cut Pro X turn into mud, if that's the codec used in your footage.

Apr 25, 2018 12:55 PM

Reply Helpful
User profile for user: johnssonkim

Question: Newbie advice: avoiding beach ball after every action