BLOGS: My COW Blog Adobe Blog Editing Technology After Effects Final Cut Entertainment

Final Cut Server - Genesis

COW Blogs : Jeff Handy's Blog : Final Cut Server - Genesis
In the beginning, there was chaos and confusion. We have so many variables that I find myself referring back to my original workflow diagram, circa 1999. The basic high-level concepts of post-production are virtually the same anywhere you go. The devil, of course, is in the details. That's where things can easily get convoluted very quickly - especially in a team environment. In all, we have five (sometimes six) editors including myself. (I'm a working supervisor.)

The trick right now is to focus on the limitations and construction of Final Cut Server, XSAN and Windows network. Two weeks ago I attended a three day course on Final Cut Server called "FCSvr 201" at MacSpecialist in Chicago. The first day was 25% on end user experience and 75% on what not to do and the major bugs were present. Some of the bugs were fixed in FCSvr 1.5, the help menu to start. But what I really learned about implementing FCSvr was that you can't have too many details on your own workflow needs. Luckily, for me, I have already done much of the legwork required to get the proper metadata set up.

The basics of FCSvr break down to metadata, both how it is related and what kind is present. At the highest level of the food chain, we have the Metadata Set. The set consists of many groupings of fields. That grouping, the level just below a Set, is called a Group. The Group houses the final level, the granular level of the metadata - fields. In order to get this all constructed correctly, you have to first look at all of the bits of info you need to have and track. Then you have to think of how to group that info and finally in which set that group belongs. In essence, you have to look at the big picture, then cut it with a jigsaw, then piece it all back together again. I have done database work before, with Filemaker and Access, but nothing to this granular level that is afforded by Final Cut Server.

The one thing I can say about the beginning of implementing such a powerful and vast installation is that you can't plan too much. Accounting for unknowable variables can't be done well. Thus, the most effective approach is to get as much feedback as you can to uncover all contingencies anyone can think of to date. One thing you can count on is that the details will change down the line. So, knowledge of production changes down the road would help tremendously.

I learned in my class that Final Cut Server comes stock with over 1200 fields. Before we started designing our case-study solution in class, I thought that was way more than anyone would need. Once involved, I discovered that there were key bits of info missing for our particular needs for Pretend Co. Even with all those fields, we still needed more than the stock 1200-odd fields. Most of our needed fields were already in FCSvr, though. Caveat: only the ones labeled as custom fields could be manipulated for our use. Some fields are populated by file-embedded metadata and cannot be made to store other data types. More on custom fields later.

Final Cut Server, as a custom solution, requires custom configuration. I am compelled to offer an analogy here about custom car tuning. You can buy a stock Mini Cooper for under $20k USD and it will drive and ride just fine. If you want that car to perform really well under harsh driving conditions, you want it customized. It'll cost you another $10k, but it will perform better, look sharper and handle corners tighter. Installing the server only nets you a stock car. If you want that car to drive and look certain ways, you must customize. With that, I'm going to be rolling up my sleeves and getting my hands dirty. I'll write about it here for others to learn from my mistakes and successes.


Posted by: Jeff Handy on Jan 25, 2010 at 9:14:39 amComments (2) final cut server, post production workflow

Comments

Thanks, Ron
by Jeff Handy
Thanks so much for the welcoming words and levity. I should be careful with my analogies, eh? Yes, I never stop loving geekdom; and putting Final Cut Server into use is certainly no exception. I always knew I'd "come home" to the COW eventually. I've been in the trenches of post production for so long it was difficult to poke my head out of the cave. I have truly missed R&D work; but I'm back, baby! :D

HandyGeek

A Tale of Granular Levels and Database Tables
by Ron Lindeboom
Jeff Handy: "I have done database work before, with Filemaker and Access, but nothing to this granular level that is afforded by Final Cut Server."

Granular levels and database tables. Man, you have to love it when people are fully conversant as they speak Geek. ;o)

But on a side note, Jeff...can I borrow your Mini-Cooper for a weekend? I promise I won't drive it fast. Well, not very fast anyway...well, mostly...okay, I admit it... I'll drive the hell out of it and will even pay for the new body work and the repaint. ;o)

Good to see you out and about, Jeff. Kathlyn and I are happy to see your new adventures and that you have indeed attained new powers of Geekedness over the years.

Best always,

The Boomies


Editing, managing and innovating media for higher education.
© 2020 CreativeCOW.net All Rights Reserved
[TOP]