Posts Tagged ‘ Final Cut Pro

Editing Canon MXF footage in Final Cut Pro X ( FCPX ) without transcoding

I’ve dabbled with Final Cut Pro X a few times since it was released and although I still struggle to understand apple’s weird naming conventions the application does have quite a few things going for it. Multicam editing is fantastic in FCPX, it automatically syncs clips using audio in the same way the PluralEyes did/does in FCP7. FCPX is also great value and with each new version Apple add’s back in features that were sorely missed by FCP7 users when it first appeared.

The one thing that’s stopped me using FCPX more has been that it couldn’t handle the Canon MXF files from my C300 natively. There were plugins available that would import and transcode / re-wrap the Canon footage into more Apple friendly Pro Res files but after using Adobe Premiere Pro for a couple of years I’ve been spoiled by it’s ability to edit directly from the source footage and no longer dealing with duplicate media..

Read more

Premiere Pro reliability – doing things by halves

I switched from FCP7 to Adobe Premiere Pro CS5 in November 2010, mostly because of the big steps Adobe were making with GPU accelerated effects and the ability to use media without the need to transcode. At that time FCP7 was still the current and trusted solution for Mac users and with no mention of a new version I had become tired of FCP’s lack of advancement and having to transcode DSLR footage.

I’d been using Premiere Pro as my main NLE for six months when Apple dropped the bombshell that was the release Final Cut Pro X. I felt quite lucky at the time because I was by then comfortable with the Premiere workflow and enjoying the benefits it offered. I had a quick look at FCPX when it was released but like many others I thought it seemed little more than a fancy iMovie so didn’t really give it much thought.

Premiere CS5 initially had a few problems running on the mac, I spent a lot of time highlighting issues both on my blog and directly with Adobe who unlike Apple are very happy to interact with their customers about problems and work with them to solve them. It took a long time for CS5 to settle down, many of the problems were not solved until CS5.5. In the mean time Apple released OSX Lion which interestingly helped with some of the UI problems premiere mac users were suffering with.

For me CS5.5 on Lion got to the point of being fairly stable, it’s weakness continued to be handling projects with a lot of media, I found that scrubbing through a timeline with hundreds of short clips would always result in playback problems so learned to not demand too much from it and avoided scrubbing through clip heavy timelines.

Before long CS6 came along offering some great new features, warp stabiliser in the NLE, more GPU based effects, enhanced FCP like timeline control and a lot more. For what seemed like months before it’s release there were numerous beta testers / bloggers who were raving about CS6 so I decided to jump on board.

I ordered CS6 Production Premium on the day of release and upon installation was immediately  impressed with the improvements. Unfortunately though I soon noticed that CS6 came with a whole new slew of stability issues. Many mac users including myself have had problems with system sound becoming unstable effecting the whole system and when working on a large project I would often see the ‘A Serious Error has Occurred and Premiere needs to close’ message many times throughout each day.

The Adobe forums are packed with users complaining of the same issues, one thread has over 250 posts by people with similar issues with over 17,000 views.

I really like using the Adobe software, but having to go through this whole sequence of Mac instability with each release of the suite is a drag, I’m sure once again Adobe will eventually solve the issues and patch up the Mac version to be almost as good as the PC variant but once again that will likely come along as the .5 version.

Because the .5 releases are full paid releases I have to wonder if Mac users would be better of doing things by halves and upgrading on the CS*.5 releases rather than jumping on the Mac problem solving wagon at the release of the new full suite, certainly from the past couple of versions that would have made a lot of sense.

I’ve actually started looking at FCPX  again which seems to have come on a long way since it’s release. It still requires some transcoding but after two days of playing with it I’ve not seen a single crash which is refreshing after using CS6!

Like any software reliability problems there are many factors involved including hardware used, other software installed etc etc so if you’re experience has been different then feel free to post a comment.

 

Final Cut Pro to Premiere Pro – six months in

I switched from Final Cut Pro to Premiere Pro CS5 about six months ago and have been using it as my main NLE ever since. Due to Apples recent launch of the not so pro FCPX there’s a lot of FCP users considering the jump to Premiere Pro so I thought I’d give a quick run down of the things that I’ve missed the most from FCP and the benefits I’ve seen.

Read more

Final Cut Pro X released

Final Cut Pro X released

Apple released it’s totally rewritten version of Final Cut Pro this week and I have to say that I don’t think I’ve seen a release from Apple that has been met with such disappointment and public dismay before.

I’m not going to go in to too many details about the new release here as I simply don’t have enough time today so if you’re not keeping up with the news I highly recommend the following articles which give a really good run-down of the current state of play.

Firstly, have a read through David Pogues post on the New York Times website. Mr Pogue does a great job of highlighting many professional editors complaints about the new software and attempts to answer these complaints, partly in defence of apple.

Unfortunately I don’t think mr Pogue initially grasped the importance of some of these complaints from professional FCP users and I highly recommend reading through the comments below his post.

You may also want to read through the following post by Richard Harrington where I think Mr Harrington does an excellent job of answering Mr Pogue’s comments from a Professional Editors point of view.

David Pogue posted again on the subject today and seems to have taken on board a lot of what his readers have posted and summed up the situation very well indeed.

Having read through hundreds of comments from professionals, both civil and uncivil, I’m now convinced: Final Cut Pro X may indeed be ready for the future. But for professional video editors, it’s not yet ready for the present.

David Pogue – NYT

My thoughts

For now I’m not even going to bother purchasing FCPX. The lack of multicamera support and the iMovie-esque way in which the media and projects are handled are simply not going to work for me. Even if I do enjoy using it I couldn’t make it part of my workflow so for now I’ll stick with the Adobe suite.

The fact that apple have removed the Final Cut Studio suite from their retail list and that this new software doesn’t allow production houses to open projects from previous versions says a lot to me.

The name ‘Final Cut Pro’ has earned an enormous reputation and a lot of respect over the last few years, I expect that alone will convince many an iMovie user to splash out and upgrade to FCPX.

Honestly though, I don’t think this new software really deserves the ‘Pro’ in it’s name, at least not yet!

HDSLR Encoding Wars – Premiere Pro vs Final Cut Pro

Browsing the web reading various reports and reviews about Premiere Pro I keep coming across the statement that because Premiere Pro works without the need to transcode H.264 DSLR files the footage inherently retains more quality.

After using Premiere Pro for a week or so I decided to spend some time investigating this theory and came up with some interesting results that I thought I’d share with you. Firstly let me describe the workflow involved in each process.

Read more