Tuesday, 5 October 2010

What's Wrong with Final Cut Server

It's been over a year since Apple released version 1.5 of Final Cut Server and I have to admit I like many are disappointed with the Apple Product. Apple themselves are wondering where they are going wrong and I though I'd take a moment to look at why.

First of all I think we should look at the fact the training book has only just been released and in fact my copy only arrived this morning. The old course was informative but not on par with other Pro Apps courses. I'm hoping the new training will start to rectify this but I have a feeling the program itself is where the problems lie.

Apple did not build Final Cut Server from scratch it was based on Proximity's artbox package. This means from the start it is very unApple. That is fine but when you start using it you start finding the problems. Yes its price point is great and it does meet some of my needs but the truth is there are products like CatDV that do the same thing better though with a larger price tag.

First thing I'd say is the problem of set up, everything takes too long to set up correctly. Its great it meets so many needs but there are no basic work flows to start you off. I need to see how it works before I can imagine how I want it to work for me. There are so few real world examples of Final Cut Server in use, it makes me wonder if it's used at all.

Set up is also awkward there are two places to setup, on the server or through the client application. I'll be honest I spent weeks trying both until I struck gold and got the thing working, this will turn away most users of apple products.

My biggest problem with Final Cut Server is it's integration with Final Cut Pro, it does it really badly. You have the client application but no integrated function in FCP. I can't share my final sequence with my FCS system. In turn I can't access video files within FCP and bring them into my project, I have to leave the program for the FCS app.

If I send assets or projects to other programs in Final Cut Studio, such as Motion it's done on that computer, I cant send it to Motion via Final Cut Server. My graphics editor is not going to be working on my computer, he will be on his the other side of the room.

This programs not all bad, when I get it working. Things do what their supposed to. I can create video archives of all my assets, though I can't look at proxy's for anything but video and audio. I can however put practically anything into it. I'm just waiting to be able to view any file.

I can set my own search parameters and meta data set, again these could be a lot better improved but do an ok job currently.

The big thing I can't see working well is how multiple editors can work on the same project. Either by checking in and out a project, or by working on it simultaneously on an Xsan.  The truth is this is partly down to your operation but more to do with FCP integration again.

I think lots of the output and management functions found in FCP need to also migrate to FCS so to take full advantage of it's potential and abilities found in the FCS app need to be integrated into FCP.

I like Final Cut Server, don't get me wrong its a powerful and handy tool. The problem is it doesn't work as well with Final Cut Pro as it should. I expect it to develop and grow very quickly over the next few years if it's to survive. I'd also like to see its potential integrated with news management systems. In the end FCS will hopefully bring ways of getting footage direct from the field into it's system, this could see future iPads with SD card slots and FCS apps in the app store.

What ever happens Final Cut Server is just at the start. The future could be amazing, only if Apple throw more weight behind its development.