Archive for the ‘Apple’ Category

New Final Cut Studio Rundown

Release Scope

So, this isn’t the huge rewrite some have been expecting. As noted here, this doesn’t even seem to be Final Cut Studio 3; Apple is just calling it “The new Final Cut Studio” everywhere.

Update: Hmm… except in a couple of the screencasts they do call if FCS3. Which suggests this branding decision may have been last-minute.

That major rewire is undoubtably still coming; when Apple axed 64-bit Carbon they implicitly committed themselves to eventually rewriting Final Cut (their last major mostly-Carbon app, other than iTunes), but it looks like that will have to wait for the next version. The good news is, the fact that Apple isn’t calling this FCS3 might very well mean that we won’t have to wait two full years for that next release. I’d assume that, if this is just an interim update, they’ve been working on the larger release in parallel with it. Perhaps next year?

Notable Features

As I see it, there are basically five features of major significance to Red users here.

ProRes 4444 – A new 320 Mb (40 MB/s) variant of ProRes that supports 4:4:4 chroma sampling and full-resolution alpha channels. You can sort of think of this as being to DPX what ProRes 4:2:2 was to uncompressed HD: a format that makes minor compromises to quality, when compared with uncompressed material, in exchange for footage that’s vastly easier to work with. Testing will, of course, be required, but it’s possible this might be a plausible — and very convenient — finishing format for indie projects, perhaps even indie features.

4K support in Color — Not much explanation required here.

Better R3D Support — Final Cut still can’t (as far as I can tell) edit R3D files natively. But it looks like you can now use CinemaTools to manage the relationship between ProRes proxies and R3D files, and more easily move from a Final Cut timeline using the former to a Color project using the latter.

Generally better Color/Final Cut integration — Not applicable solely to Red workflow, of course, but it looks like a lot of work has been done to make Color smarter about dealing with complex Final Cut timelines. It should no longer get confused with speed changes, stills, and other things that currently confuse the hell out of Color.

Automatic importing of file-based recording media — It looks like Final Cut can now detect when a drive or card is mounted, and start automatically importing media from it. There also seem to be some new features for retaining more metadata from imported file-based media, but it’s not clear if that applies to R3D files.

Cheaper Color control surface options — Again, not Red-specific, but Color now supports the ~$1800 Tangent Wave control surface, among others, lowering the price barrier to using a control surface to about 1/5th of of where it was previously.

Blu-ray & the future

Apparently, DVD Studio Pro still doesn’t support actual Blu-ray authoring. What we have instead is sort of strange and, I think, rather telling. Compressor can encode Blu-ray compatable H.264 now, and create Blu-ray discs using pre-built Apple menu templates. These templates are apparently in some sort of XML format, so anyone comfortable with a bit of XML slinging can build their own. I have a sneaking suspicion that what we’re looking at here is an early version of the file format of a new application that will eventually replace DVD Studio Pro.

More as I discover it.

Red offline/online Final Cut & Color workflow

So, I’ve decided to write up what’s fast becoming Nice Dissolve’s standard Red workflow, after finding about four different occasions on which to describe it over on Red User in the last week alone….

Workflow

  • On your transcoding/conforming machine (needs to be an Intel Mac), transcode R3D files to 720p ProRes SQ with the “quarter res” setting (“Draft” process in Redcine). You can do this from Redcine, Red Alert, Redline, Clipfinder, etc.
  • Edit with 720p files in Final Cut. These files can be pretty easily edited on just about any Mac hardware you’d consider running FCS2 on in the first place, including laptops or those old G5 towers you still have kicking around.
  • Back on your transcoding/conforming machine, export your edited sequence from Final Cut as XML. use Clipfinder to swap references to your ProRes files for references to _H proxies, and let Clipfinder change the resolution settings on your sequence to match. Import the newly generated XML file back into your FCP project. It will come in with the same name as your ProRes sequence, so rename it so you can tell them apart.
  • File -> Send To -> Color in Final Cut with your newly imported sequence.
  • Immediately save your Color project and close. Use the “looping bug” fixer in Clipfinder (in the Tools menu) on the project.
  • Re-open the Color project and grade.
  • Render out of Color to ProRes or Uncompressed HD and send project back to Final Cut for titling, etc. or render to DPX and handle further processing in After Effects, Shake, etc.

Notes

  • We typically use Redcine to export the ProRes files. It lays everything out on a timeline for you and makes it easy to do a quick one-light grade.
  • When transcoding your ProRes files, make sure they have the same names as your R3D files (except, obviously, with a .mov extension rather than a .R3D extension). Redcine might add an extra underscore to the end of file names; use a script or batch renaming utility to get rid of it, or it will cause trouble when you try to conform. (If it’s already too late, then before you process your exported XML sequence though Clipfinder, open it in a text editor and do a search/replace of “_.mov” to “.mov”).
  • If you haven’t used Color before, be sure to read the section of the user guide that discusses its limitations when working with transitions, filters, still images, etc. from Final Cut timelines.

Analysis

This is basically my favorite low-cost Red workflow. It’s the first commodity-software workflow that, in my opinion really has all the essential pieces in place.

Pros:

  • Fully compressed (except possibly the final output, if you choose to output in an uncompressed format) — you could plausibly finish even a feature with just a couple of terabytes of storage and you don’t even really need a RAID array.
  • Transcoding to 720p files from a 1/4 resolution de-bayer is quick. It can be near real-time on a single 8-core Mac Pro.
  • 720p ProRes files are very lightweight, only a little more than twice the data rate of DV, making it easy to take projects with you. Edit on your laptop, conform on the Mac Pro back at the office.
  • FCP on just about any modern Mac is very responsive while editing 720p, unlike with the comparatively much heavier workload of editing R3D proxies.
  • You can do a quick one-light when creating the 720p files, so your editor can look at nicer footage than R3D proxies with whatever look metadata they happen to have.
  • You’re grading in an environment which provides access to the full range of the R3D data and also provides vastly more powerful color correction tools that Redcine or Red Alert.
  • Only the precise frames used in your final edit ever have to be transcoded at high-quality (happens when you render out of Color).
  • If you have a Mac Pro and set Color to quarter-resolution playback, you can even get real-time playback of R3D in color projects, at least if you don’t get too carried away with secondaries, and it doesn’t look terrible on a client monitor.
  • No messing around with Media Manager or Log & Transfer in Final Cut.
  • This workflow doesn’t require any software other than Red’s software (free), Clipfinder (donationware) and Final Cut Studio.

Cons:

  • Limited to 2K finish or below. (Then again, even most Hollywood features still aren’t finished above 2K.)
  • Footage is fed into Color via the equivalent of a “half res high” decode, not quite as good as decoding full 4K and scaling. (But good enough for almost any HD finish, in my opinion.)
  • Requires up-front transcoding, unlike R3D proxy-based workflow.
  • Because of decoding overhead, Color is not as responsive with R3D files as with uncompressed HD or DPX (if you have a RAID fast enough to handle those formats in real time).

Lots of Apple updates

Nehalem-based Mac Pros and new Mac minis and iMacs. Apple has now totally abandoned Intel integrated graphics in favor of NVIDIA hardware, which should make everyone happy.

The Nehalem Mac Pros are the stars of the show for your Mac-based HD video needs, for obvious reasons. But we’re also pretty excited about the new Minis. With FireWire 800 and NVIDIA graphics, these seem like they’d be perfectly good systems for everyday editing tasks, probably even cutting 1080p ProRes HQ (with external storage, obviously). And the base configuration, bumped up to 2 GB of RAM, is just $650. Not a substitute for a Mac Pro, clearly, but a small video production shop built around three or four of these and one ~$5K Mac Pro seems like a pretty plausible approach.

New Red/Apple FCS workflow

The Pro Applications Update 2008-004 (run Software Update) and the Red Final Cut Studio 2 Installer provide access to two new major features.

The first is rewrapping R3D data into QuickTime files that Final Cut can work with natively, though Final Cut’s Log & Transfer interface. There’s some debate about this, but as far as I can tell it appears to simply create QuickTime movies that are the equivalent of the existing QT proxy files, but self contained. This isn’t actually all that useful. (Why not just use the proxies? Rewrapping all the same data is just going double the amount of disk space your project uses for no good reason.)

The second feature is far more significant. Previously if you did a ‘Send to Color’ in on a Final Cut sequence containing containing Red proxies, you got… nothing. You got a bunch of clips on a timeline in Color that Color couldn’t do anything with. After installing this update, not only do proxies (and the new QT-wrapped files) show up in Color, but Color has access to the full raw data.

This workflow lets you edit immediately without any up-front transcoding, only requires you to transcode the exact frames you use in your final edit (they get transcoded as the footage gets rendered out of Color), allows you to create anything up to a DPX or uncompressed HD final deliverable without any previous step requiring you to work with uncompressed data, and provides access to the full range of the raw image capture by the camera in a grading environment significantly more powerful than RedCine.

While other workflows have offered some of these benefits, this is the first workflow which offers all of them at commodity prices. (Previously only SCRATCH offered all of this, and not at commodity prices.)

Now, there are a few caveats:

  • As is fairly typical for this kind of dual-app edit/conform workflow, Color doesn’t render Final Cut video generators, filters, motion tab settings, or transitions other than dissolves. This isn’t as bad as it might sound, because these things aren’t typically used on feature film projects, and if you’re not editing a feature that’s being rendered to DPX, you can round-trip through Final Cut (do a ‘Send to Final Cut Pro’ in Color) and handle all of this back in Final Cut.

  • Color only supports up to 2K. No 4K finishing from this workflow. 2K comes in as 2K. 3K, rather awkwardly, comes in as 1.5K, which I think Final Cut’s real-time engine has some issues with.

  • I believe 4K footage through this workflow is rendered at the equivalent of the “half high” setting in Red’s other apps. It would be nice to have the option to have 2K scaled from a full 4K debayer as well.

  • This new software hasn’t yet been tested extensively with Build 18 footage, or formats other than 4K 2:1 and 2K 2:1. I’ll be doing some tests with 4KHD this week. 4KHD is going to be important to this workflow because 4K footage comes in at half its native resolution (see above), so if you want to finish in 1080p, shooting 4K HD will make your life easier.

The Red Final Cut Studio 2 Installer linked above comes with a 24 page whitepaper on Red FCS workflow that lays all of this out in much more detail, if you’re interested.

This post is…

…live from my iPhone.

That is all.