Ronny Courtens
Forum Replies Created
-
Welcome to the club, Lawrence. Hope you will enjoy working with FCPX.
Great to hear you have found the solution to your problem yourself. That’s a good way to learn.
– Ronny
-
Our facility is all FCPX, but we are still an exception. Larger post houses I know in France and Germany have been with Avid and/or legacy FCP for years and apparently they are not going to change soon. But large pure post houses are slowly disappearing in our parts of Europe as well. Small shops seem to be taking over most of the work. And here’s where it gets interesting.
What I see is that the smaller shops as well as the audiovisual depts of some big agencies and corporations over here are really embracing FCPX. I get a lot of interest from people asking about our workflow lately (-: Some of our bigger corporate clients and agencies, but also small production houses and one-man-band shooter/editors, are already bringing in logged or even pre-edited FCPX projects to our shop. We do the fine tweaking of the edit (FCPX), the finishing (Smoke/Flame, Resolve, ProTools…) and the conforming for broadcast, DCP or digital platforms for them. It’s a workflow I encourage because they do the bulk of the lower-end work and we can charge good money for our experienced people to polish, finish and deliver the projects.
– Ronny
-
Thank you for correcting me. I really thought this was something new with 10.0.9. I have bladed CCs in 10.0.8 as well but I could swear I haven’t noticed the dotted lines then. Must be getting old (-:
– Ronny
-
What is the language of your keyboard?
– Ronny
-
No problem, I hope everything turns out all right.
– Ronny
-
Nope, no going back once you have opened the project using a new version and your Project and Event has been updated. Too much has changed under the hood since 10.0.5.
If trashing prefs didn’t work I would try restoring the black clips one by one. To check what really is causing that error message could take a very long time because so many things can make it appear.
– Ronny
-
Okay, now I get it.
First thing you should do is refresh your FCPX preferences. If you don’t know how to do this: https://support.apple.com/kb/TS3893
Or use Preference Manager to refresh your prefs, this is much easier: https://www.digitalrebellion.com/prefman/
Then restart FCPX and see if this has solved your issue. If not the only solution to get out of this problematic project seems to be re-encoding the black clips.
If you are able to optimize one clip at a time I think you should do this one by one and shut down and restart your computer after every clip to clear your memory and caches.
I know it’s a drag, but it will be very hard to pinpoint the cause of your memory leak at this time and you need to get this project out. So if trashing your prefs does not help try transcoding clip by clip and if this still does not work post back.
– Ronny
-
Oops I think I missed something in your original post.
Just to be clear: all the original clips in your Event Browser are OK, only some of your clips in the timeline show as black clips, is that right?
– Ronny
-
Yep. Remember the golden rule of editing: never, EVER update anything while you are in the middle of a project.
But you only seem to get the issue (which often indicates a memory leak) while trying to restore your “black clips”, so let’s try and find a workaround:
R-click of the black clips in the Event Browser and select Reveal in Finder. Double-click the clip in the Finder window. Does it play in your QT player?
If it plays OK in QT player drag the clip from the Finder window onto the FCPX Event Browser. Does it still show as black in the Event Browser?
– Ronny
-
This can be a either a very complex problem, or a simple one. Let’s eliminate.
Check your RAM to make sure. Click the Apple icon and select About This Mac. Is all your RAM OK?
If it is OK: do you have any processes running that would take up a lot of resources? Such as Spotlight Indexing running, Time Machine running, any other backup processes, a virus program…?
– Ronny