Every time I made a change to a transition effect or title, I would literally just wait for it to render – which it started automatically – because there was no point in moving on to the next edit because it slowed everything down to the point of frustration. The project I was working on was fairly standard corporate video fare – talking heads, b-roll, and some motion graphics from After Effects. It may happen automatically "in the background", but that background activity takes up a lot of processing power, and I found that it ground the performance of the application to an excruciatingly slow speed every time it happened – and I have new machines with SSD and RAM to the hilt. Rendering is still required, just the choice of when to render has been taken away. The highly touted "no more rendering" that the Apple marketing machine has been pushing is a bit misleading. The lack of control in FCPX extends beyond determining how your project assets are organized. They’ll go with me even though some young upstart will charge them half my rate because they know, in the end, things will go more smoothly and they’ll have a better experience. This gives me an edge when bidding for jobs with current clients. That’s because I take the media management aspect of my job very seriously. My client remarked that he liked working with me because he never had any problems getting the projects up and running and knowing where all the assets were, regardless of how complex the project was. As usual with this client, they were going to pick up where I left off – some audio sweetening and color correction, etc. A few weeks ago I was returning a hard drive to a client of mine - a production company that specializes in high-end corporate videos. In fact, it was again a marketable skill. I never saw media management as a problem. Sure, my skills as an editor are not dependent on my tools, but being extremely knowledgeable about the primary tool of my trade is a selling point when I market myself to potential clients.įCP X: Taking The Editor Out of The Driver’s SeatĪpple has decided to take the "hassle" of media management out of the mix by organizing all project assets automatically into Events.
#Avid media composer vs premiere pro#
Right now it seems like it would be far less disruptive to my workflow to switch to Premiere Pro CS6, or even Avid than it would be to continue using Final Cut Pro X. There is a huge cost in terms of both time and energy associated with learning new ways to do things in FCP X. Now, I’m the farthest thing from a Luddite and I don’t fear change, but I spent the last 9 years of my life becoming very proficient at something and now it’s just gone. So why am I turning my back on Final Cut Pro? First is the fact that it is such a completely foreign interface. In fact, FCP X seemed like it was built for the kind of editing I do. The bulk of my business is corporate video, where everything from graphics and audio mixing is done in house. Having said that, the lack of any of the above features (with the exception of XML support) was not much of deal breaker for me. The absence of these features from the new version caused an unprecedented uproar from the post production community, and Apple moved quickly to add these features. Some of the most well documented deficiencies upon the initial release of FCPX were the lack of XML import/export, multi-cam editing, and broadcast monitor support.
#Avid media composer vs premiere professional#
It sure did: for the first time in 9 years as a professional editor I actually didn’t enjoy editing. "Everything just changed in post", is the tagline for FCP X on Apple's website. But I have just delivered my first project cut exclusively on FCP X and must say it was a completely unpleasant experience. And sure enough, until recently, I have been fairly open to the idea of adopting Final Cut Pro X as my NLE of choice. They say don’t knock it before you try it.
0 kommentar(er)
