So Much Going On Lately…

Not many posts lately because we’ve been in the thick of it for a few weeks.  Here’s a quick recap:

I spent the last 2 weeks working with Hit Entertainment, transitioning them to HD.  They’ve had HD cameras for a couple of years now, but their post production workflow hadn’t been upgraded to allow for it yet.  So - they went all out with HDCam SR decks (6 of them) and new Media Composer Nitris DX systems.  I worked alongside James Johnson building cables and getting the decks setup.  Barney in HD!

We’ve also been getting ready for the upcoming Varsity Wired season. We had our annual meeting yesterday and it went well; we’ll be handling a few more events this year and we also have a couple of cool apps in the works to make things a bit easier on everyone.

I leave for Anaheim, CA for a shoot for an optical pharma company on Friday. I plan on stopping by the San Diego zoo while I’m out there (and the lego store!).

Just picked up the CS4 Production Premium bundle and so far I’m impressed - I’m looking forward to using OnLocation. Photoshop and After Effects seem like minor upgrades but Flash is rocking - I finally feel comfortable animating in Flash!

Avid vs. Final Cut Pro

Had to jump back into an Avid for a gig this morning and man is it a rough transition.

I grew up editing on an Avid and I have to say, aside from a few tools, I absolutely despise them…
I hate the idea of ‘modal editing’ - let me drag clips around without having to hit an extra hot key…
And I absolutely hate the way that Avid forces you to import footage… “No rendering” they say… but I’d rather grab a cup of coffee when I’m almost done with a project than wait until all of my animation codec files import and get wrapped in a proprietary format…

All that being said, Avid’s are still everywhere and they still have their uses.

So - in case anyone wants a crash course on either system:

Compressor Virtual Clusters

Anyone out there using Final Cut Studio 2 needs to read this post.

If you have any of the Intel based Mac products and want to get a little bit more oomph out of Compressor all you have to do is setup a virtual cluster.

Compressor setup on a solid network is a really cool way to encode and transcode alot of footage quickly. The problem is that sometimes you don’t have any other macs on your network (or a shared storage setup).

A virtual cluster allows you to run an instance of compressor that acts like all of the processors on your machine are machines that it can use to distribute its work to. All of those dual core and quad core and dual quade core systems out there don’t really use more than one processor during an encode (generally compressor distributes the encode to one processor and then to another and then to another in a multi-core tease that drives anyone that knows what’s going on under the hood insane).

QMaster Panel - Setting up a QMaster Virtual Cluster

QMaster Panel - Setting up a QMaster Virtual Cluster

To set up a virtual cluster go System Preferences > Apple QMaster

QMaster is the distributed rendering/compressing app that ships with Final Cut Studio. It’s basically your network traffic controller. The easiest way to get up and going is to use a QuickCluster with services.

Check the Share and Managed boxes for Compressor and set your instances to how ever many processors you have - my laptop is a dual core so I set it to two - if you’re lucky enough “gishcluster” and click on start sharing.

Now - next time you’re in Compressor and you want to take advantage of your virtual cluster just submit a batch and instead of using the “This Computer” option send it to the cluster you just created.

There are a few caveats about this whole process:

  • You must have the machine connected to the network protocal that you had it connected to when you installed compressor - this is beating of an issue but one that sort of makes sense - compressor was meant to be an application that lived on a stable network so it wants to know what ports are being used and how everything is connected.  If you installed compressor on a laptop and you had the ethernet port setup for your network connection then you always have to use an ethernet connection to use compressor and its virtual cluster (it will hang/freeze if you try it with wireless).
  • Sometimes things just freak out - I used a setup like this for a lot of very intensive encoding for 3 months straight and only had a couple of issues - generally they were resolved by following this procedure exactly
  1. quitting compressor and batch monitor
  2. turning off the QMaster sharing
  3. restarting the machine
  4. opening compressor and clicking on Compressor > Reset Background Processing
  5. quitting compressor
  6. turning QMaster sharing back on
  7. opening compressor and submitting my batch
  • Keep your Final Cut Studio install discs and serial numbers handy - if the above steps don’t work and you’ve checked your network connection then you may have to reinstall.  It sucks but that’s part of the risk you take with using something in a slightly different way than it was intended.