This is a perfect example of someone who does not have the correct Final Cut Pro configuration or the proper workflow.
http://ace-filmeditors.blogspot.com/2010/05/end-of-final-cut-for-me.html
Notice he’s an ACE editor so this shows that even the professional editors don’t always get it right for whatever reason. My feeling is that his system is simply not configured properly for the huge projects he’s undertaking. You simply cannot have a system crashing 5 times a day, let alone 5 times a week and expect to get any work done.
It appears this person is an Avid editor and made the switch over to Final Cut Pro for these projects and tried to apply all his Avid workflows to FCP. Can’t do that. You need to adjust your workflow to match the tool.
As for the crashing, I can only assume this was a badly underpowered system or poorly configured. Currently we’re managing almost 400 hours of material on our systems for three documentaries. One documentary has been in Post 14 months. In addition we have three broadcast series going along with a myriad of other projects. Final Cut Pro is not crashing here. Maybe once a month, once every two months on one of our 5 workstations.
Unfortunately this editor got set up in a perfect storm. Trying to force a tool into a workflow he was familiar with, but that the tool is not optimized for. Poor system configuration and / or poor media management.
A shame because now he blames the tool instead of realizing that the tool works, it just has to be configured and used correctly. A lesson for all of us.
Sorry, the comment form is closed at this time.