I haven’t posted many updates lately so sorry for that. I’ve been working on a project involving a lot of two camera interviews using my Canon C100 and C300. This has been a good test for the profiles I created to match the camera and so far it’s going really well, the images from each camera are really close and I’m finding that with careful setup of exposure the results cut together well with the same grade applied.

The one thing that seems to let the the C100 down slightly is of course it’s internal 4:2:0 codec writing at 24MB/s, this doesn’t hold up as well as the C300‘s 4:2:2 codec at 50 MB/s. Below are some frame grabs showing one of the interviews I’ve shot and you will notice that although the C100 close up looks very similar to the wider C300 shot, closer inspection reveals compression artefacts that become more apparent when the footage is graded.

Both cameras were shooting in log with a minimal grade applied as an adjustment layer in Premiere CS6. I used Premieres RGB curves effect to add a shallow S curve and added some saturation using the fast color corrector tool. I’ll need to spend more time on the grade later in production but for now this gives a rough idea of how it effects the compression artefacts. Both the ungraded and graded screen grabs are shown below.

The wider shot was recorded with the C300 fitted with a Canon 50mm f/1.2 lens with the closeup recorded on the C100 with the Canon 70-200 f2.8 L. Both lenses were at f/2.8.

I’m going to be reviewing the Atomos Ninja-2 external recorder over the next few weeks to see how that improves the images from the C100. Because the camera outputs 4:2:2 over the HDMI port that should in theory produce results much closer to the C300. Watch this space for more on that very soon.

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.

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