-
Lots of crashes
Working in a proxy timeline.
If I have a still image (jpeg) as a connected clip with dip to colour dissolves either end of the clip, if I start messing about with Ken Burns crops too much it crashes.
Time and time again.
Run repair disk permissions and trashed preferences (again).
Corrupted render files? I hope not as I have already thrown them away once and had to do all those moves and redone all my crops and transforms.
Only 8 gig RAM on a iMac.
Am I too lightweight?
-
23 Replies
-
Thanks
But it only happens when I am doing that particular thing?
-
I have 32gigs and certain things in X (templates for example) can suck it all up. I’ve watched the ram monitor when it gets sluggish and watch the available ram drop from 10gigs to a few hundred Megs and then crash soon after. It’s like its memory management is non existent
-
Sounds buggy to me – anything interesting in your system logs in your console.app?
————-
OutOfFocus.TV – Original series, music videos, mini-docs. -
I feel like I remember some talk about one thing or another causing problems with ken burns, I just can’t recall.
On the other hand, I’ve somewhat retrained my command-s save instinct to be command-q. Yes, suddenly quit FCPX after working for a while. My trigger being any slight hang or hiccup, after it becomes responsive again I quit then reopen. Maybe a reboot, if its necessary. Seems pretty effective in avoiding unexpected quits in general.
-
James, try removing the transitions from the clip before working with the ken burns effect. It seems that transitions on a secondary storyline could be the main culprit of the Ken Burns crash bug.
-
I have trashed preferences and render files and logged in as a different user. No difference.
It crashes with Ken Burns only when there are dissolves both ends of the clip.
If I add dissolves afterwards no problem.
I will try reinstalling but think that is unlikely to help.
It is such a specific problem it feels more buggy to me. -
James says “Corrupted render files? I hope not as I have already thrown them away once and had to do all those moves and redone all my crops and transforms.”
How did deleting render files make you have to redo moves/crops etc? That’s not right.
-
I wondered about that…it was late so pilot error probably the cause of that one.
Thanks for confirming my suspicions about Ken Burns and dissolves….bit of a pain having to delete the dissolves before making changes but I can see how a dissolve could be a bit confusing for a key frame . -
Actually the behaviour of connected clips when dissolves are added somewhat puzzles me – they automatically become Secondary Storylines (with a “shelf”) and if I select the clip and delete it leaves the dissolves there as connected dissolves.
If I lasso the clip and the dissolves obviously it deletes the lot but strange that it thinks I might have use for a dissolve sitting there on its own.
A bit odd?
-
It is a bit strange to leave behind two transitions with no media between them, but I guess fcpx treats the transitions as something you put there, so you have to delete it if you want it gone. Just for the integrity of “not doing something I didn’t say to do”, you know?
I’d use cut to remove the transitions, then paste them back on after finishing with Ken Burns.
You can also click the “shelf” to highlight and delete all of a secondary storyline same as lassoing.
Reply to this Discussion! Login or Sign Up