![]() ![]() With this in mind I didn't touch the timeline in FCPX or import media, until I felt that I fully understood media organisation, and how FCPX wants to be handled, and how it wants to handle my media. A good deal of my time is spent organising media, setting preferences, and thinking ahead of time, a very important question to ask yourself as an Assistant is 'how will this work further down the line?' because a few minutes of planning at the beginning of a project, will save hours if not days of pain at the end of a project. I do however spend more time as an edit assistant mostly for a UK soap but also for feature films on occasion, or as a DIT. ![]() When my role is as a video editor I am typically working solo on my own projects or small projects for other people, and so need to fully understand whatever toolset I am using. The project I was going to edit would be the last of a series of Vlogs I was cutting for my girlfriend as she travelled around Asia for a few months, the previous episodes had all been cut using Premiere CS6 it worked but crashed a lot and I often lost work, and lost a lot of time waiting for Premiere to play catch up. I think my situation is probably similar to many others, who edit occasionally at home and are looking for the most cost effective solution to work with especially as students have just had their Adobe CC subscriptions almost doubled recently. I chose to download the FCPX 30 day trial to edit a project with, and see how I liked it, this blog post is essentially a breakdown of how I worked, what I liked and disliked about FCPX, and if I think I'll move over. I already own and can use Avid but for most projects I do, it isn't an ideal platform. Also I don't edit often enough, to fathom £30 or even £60 a month for Premiere CC, FCPX at £300 for a one off fee looks appealing in that sense. Many of the features added in the lastest version, 10.3, which many have described as more like FCP 11, are totally new to me personally as I jumped ship to Adobe's Premiere when I wanted to move on from FCP7, and have only now started to look back at FCPX as my next step due to the Adobe CS6 package running terribly on my next machine, a 'Late 2015 iMac 5K'. FCP has still seemingly, lost it's place as a premium editor, with Adobe's Premiere quickly snapping up many users and post houses as their main system with Avid often still sat at the head of the table. Users essentially needed to re-train and learn this new way of thinking and find new ways to do things, but over time FCPX has become more accepted, with many additions unique to FCPX, that are better than other NLE's. FCPX was still from day one useable for professionals, it just wasn't a widely praised change, albeit with many seemingly needed features missing: such as multi screen support, lack of XML integration, EDL exports, and one of the biggest - no way to import FCP7 projects. However upon seeing it's new features, and in some cases lack of features, and from reading other user's thoughts I, like many others, became underwhelmed by this 'new way to edit'. From the outrage that came with this is, it appeared the vast majority of users thought Apple were wrong I was one of these users.Īt the time I was 20 years old at University and prior to it's release was extremely excited for this new version with a slicker GUI, and the hope FCPX would make full use of whatever machine I was using: with it's 64-bit architecture, and background rendering. The new version 'Final Cut Pro X' (FCPX) was a huge change from past iterations, and in classic Apple fashion, they pretty much ditched support for old versions and said that FCPX was the way forward, and THE way to edit. In June 2011, Apple released a new version of their popular Non-Linear Editor (NLE), Final Cut Pro. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |