Larry Jordan Blog



Category: Software

Three items of note

Posted by on July 14, 2011

Some interesting news this morning.

FIRST

Apple has quietly notified developers that it is preparing to offer volume purchases for business customers via the App Store.

MacNN has more about this.

The significance of this is that volume purchases of Final Cut Pro will no longer be tied to individual iTunes accounts. This might also presage the arrival of volume pricing and distribution for educational customers.

SECOND

I’ve had emails or phone calls from three different resellers telling me that Apple has notified resellers that it is offering them a one-time, two-day opportunity to buy as many copies of Final Cut Studio (3) as they want.

While this is not the same as putting FCS (3) on the open market, it does mean that the product will be available from selected retailers for a while longer. If you need licenses, contact your favorite, non-Apple store reseller.

THIRD

A large number of Final Cut Pro editors are thinking about switching platforms. Last week, my podcast – the Digital Production Buzz – had a series of discussions on switching to Avid. (Details here.)

This week, we have the product manager for Premiere Pro on the show, along with a recent Final Cut Pro post house that switched to Premiere. (Details here.) If you are thinking about switching, listen to this show first.

Larry

Changes Coming to Final Cut Pro x

Posted by on July 07, 2011

Long-time newsletter reader and Final Cut Pro developer Alex Gollner (Alex4D) posted a blog late yesterday about a secret meeting between Apple and some of its enterprise customers in London.

You can read the entire blog here.

Here’s a summary of the key points that Alex listed in his blog, covering tweets from Sam Johnson, who attended the event:

1. FCP XML in/out is coming via 3rd party soon…no FCP 6/7 support project support coming ever it seems…

2. Ability to buy FCP7 licenses for enterprise deployments coming in the next few weeks…

3. FCPX EDL import/export coming soon…

4. FCPX AJA plugins coming soon for tape capture and layback…capture straight into FCPX bins.

5. XSAN support for FCPX coming in the next few weeks…

6. FCPX Broadcast video output via #Blackmagic & @AJAVideo coming soon…

7. Additional codec support for FCPX via 3rd Parties coming soon…

8. Customizable sequence TC in FCPX for master exports coming soon…

9. Some FCPX updates will be free some will cost…

So far, there is no official word from Apple about this.

What I find most interesting about these statements is the degree to which Apple is counting on third-party developers, rather than Apple itself, to provide missing features in Final Cut Pro X.

Next week, both AJA and Blackmagic Design are doing stage presentations at my Final Cut Pro X Event – we should learn a lot more about this latest news then.

Click here to learn more about our Final Cut Pro X event.

Thanks,

Larry

The Sound of 1,700 Jaws Dropping

Posted by on April 13, 2011

Final Cut Pro X - Main Interface
[Image courtesy Apple Inc. Click for enlarged view.]

Apple this evening provided a “sneak peek” at the next version of Final Cut Pro – now called “Final Cut Pro X” at the NAB SuperMeet in Las Vegas, Nevada.

The new Final Cut Pro is a bold move – a totally redesigned interface, 64-bit memory addressing, multi-processor support, tight integration of metadata in the project file with metadata stored in the clip not just in the project, heavy use of automation to simplify tedious tasks, and a rethinking of the entire concept of what it means to edit.

I can’t think of any other company that could so totally redefine what a non-linear video editor is than Apple. Since the release of Final Cut Pro 1, each version of FCP has contained incremental improvements. This is a complete restatement at every possible level.

As Phil Schiller, senior VP for world-wide marketing for Apple told me after the presentation, “This is a total rethinking of how we tell stories visually.”

Love it or hate it, our editing life won’t be the same again.

Oh, and did I mention — it has a ship date of June, with a suggested retail price of $299, and will be sold through the App Store (more on that in a bit).

TAKING A STEP BACK

But to look at Final Cut Pro in terms of its features or spec list misses a much bigger point that I want to reflect on for a bit. And it all revolves around a term I used in my first line – this was a “sneak peek.”

This is why you won’t see anything about the new Final Cut on Apple’s website – this is a preview, not the launch. There is still much work that needs to be done on the software.

Understanding an Apple event is like understanding a meeting of the Federal Reserve Bank. It is essential to concentrate on both what was said, and what was not said.

After the presentation, I spoke with Richard Townhill, Director of Pro Video Product Marketing for Apple (who served as the host for Apple’s presentation) who told me that “the purpose of today is to focus exclusively on Final Cut Pro, highlight some of the new features, and give people a chance to see and comment on the new interface. We will have much more to say about both Final Cut and our other applications in the future.”

Final Cut has been rewritten from the ground up and borrows a lot from other siblings in the suite. The audio cleanup and processing borrows heavily from Soundtrack Pro, primary and secondary color correction tools are taken from Color (see the screen shot below), and some of the motion effects techniques are taken from Motion.

However, this does not mean these other applications are dead – simply that Apple is not talking about them… yet.

I was reading posts this evening on IMUG and Twitter, where users were saying: “is it iMovie on Steroids?” I think this is a premature question.

Final Cut Pro X - Main Interface
[Image courtesy Apple Inc. Click for enlarged view.]

THIS IS A PRO APP APPLE DESIGNED FOR PROS

After the presentation, I went down front to talk with the folks from Apple about what I saw. And I asked Richard directly: “Explain to me why this isn’t a big version of iMovie?”

Richard replied: “We designed this to have professional features for the professional user. The reason we chose to present it here at the Supermeet was that we wanted the professional user to see it and understand what we are doing.”

As one attendee said to me after the event: “Both a Ford and a Ferrari have an accelerator, but that doesn’t make them the same car.”

Also, what viewers in the audience did NOT see was who from Apple was attending the presentation that did not appear on stage.

Somehow, I managed to sit in the Apple executive section of the hall. In front of me was Phil Schiller, Senior VP for Worldwide Marketing. The head of PR was sitting to his right. The two lead engineering directors, or VPs, were sitting on either side of me. I was surrounded by top-level executives from engineering, PR, marketing, product management — literally a dozen extremely senior executives were sitting in the front two rows.

Apple would not send this level of executive talent simply to watch the roll-out of a product that they did not care about.

SIDE NOTE: I was sandwiched between two senior engineering executives who had as much fun as anyone in the audience watching the demo and applauding. I suspect it was because they were finally seeing the public result of years of behind-the-scenes work.

Another interesting data point. This presentation was almost exactly the same one that I saw six weeks ago in Cupertino. Apple used it then to get feedback from a small group; I suspect they are using this exact presentation tonight for the same reason — to get reactions from a much larger group.

LOOKING AT THE NUTS AND BOLTS

Based on tonight’s presentation several long-standing irritants with Final Cut Pro disappear:

* Rendering is now in the background and much faster because it harnesses the power of the GPU.
* The 4 GB memory limit is gone – FCP will use as much RAM as you have installed on your system.
* FCP X now uses all the processors on your system, not just one and a half.

In addition, a flock of new features were added:
* It supports editing video image sizes from standard definition up to 4K.
* It uses fewer tools from the Tool palette (which is no longer there, by the way) by making the cursor smarter. WHERE you click something determines WHAT you can do with it.
* A lot of existing features are jazzed up (linking and grouping are replaced by the much more elegant Clip Connection and Compound Clips)
* While new features like the magnetic timeline, permanent audio sync and auto-metadata generation are flat-out stunning.

NOTE: Nothing said, or implied tonight, indicated that you would need any special hardware. My guess is that any Mac you buy now will run FCP perfectly. Also, contrary to some rumors, I spoke with Apple engineering about Thunderbolt. This is a system level I/O connection. If your Mac has it, ANY version of FCP – or any other Mac application – will take advantage of it.

Final Cut Pro X - Main Interface
[Image courtesy Apple Inc. Click for enlarged view.]

THINGS I WAS STRUCK BY

While the slide show was identical to the February meeting, the demo was not. Randy Ubillos, who did the demo, added more features and additional explanations on effects (see the screen shot above). However, I was told later that the build that was demoed was the same build that was shown in February – and that the application has moved significantly forward since that time.

In other words, what we saw tonight was nowhere near the final form of the application.

I was also very impressed that audio was not treated as an unwelcome step-child. First, the demo paid a lot of attention to setting and maintaining audio sync, however lots of little details were also obvious:

* Sample rate precision in scrolling an audio clip
* Pitch corrected audio scrolling in slow motion
* Displaying waveforms at a size big enough to see what they look like
* Displaying audio levels within the waveform that are approaching clipping (as one engineer near me remarked, “And THAT took us a LONG while to figure out.”)
* Displaying audio peaks for the entire mix that are approaching clipping
* Improved audio cleanup controls, which can be applied or ignored by the user (these look to be borrowed from Soundtrack Pro)
* Adding fades with a keystroke, or by pulling in the top corners of a clip, with four different fade shapes, rather than the limit of two inside FCP 7; these, too, borrow interface ideas from Soundtrack Pro.

THE CROWD’S REACTIONS

In brief, the crowd was loving it. Granted, many of them got well-lubricated at the no-host bar before the event, but nonetheless, everyone seemed to have a good time.

The new interface drew applause, 64-bit support and background rendering had people drooling and the new price of $299 received a standing ovation.

MY REACTIONS

I’ve been thinking hard about this since I first saw the software six weeks ago.

And, truthfully, I’m very torn. There are some features here that I really like a LOT. There are a few that I don’t like at all. But there is a great deal that has not yet been said.

And that, I think, is the key point. The devil is ALWAYS in the details.

Apple has done its usual magnificent job of previewing a new product. But this is only the preview.

I met Randy Ubillos, Chief Architect for Video Applications at Apple, after he presented the demo of the software. I told him that parts of what I saw I liked a lot and parts had me quite concerned. And I asked if Apple was interested in our feedback. He immediately said that Apple is VERY interested in our feedback, that they are listening and want to make this application something that all of us can be proud of using.

I believe him. And I also believe that it is way too early to make any final decisions about this version. There are too many unanswered questions. For example, here are some questions the answers to which are still unknown:

* The retail price for FCP is $299 – but what is the retail price of the other software parts of the Suite? Are we back to ala carte pricing?

* The application will be sold through the Mac App store. What happens to all the great data files that were available with the suite in earlier versions?

* How does FCP X work with existing FCP 7 projects?

* What other applications ship with Final Cut and how do they integrate?

* How many of our existing plug-ins, peripherals, hardware, and other gear need to be updated to work with the new software?

* Editing does not exist in a vacuum, how do we share files, clips, metadata, and project information with other software tools?

* How does it handle media?

* How has QuickTime changed to support what Final Cut Pro X can do?

* Real-time, native video processing is great for editing – however, we still need to encode to get files on the web. How?

As of tonight, Apple hasn’t provided answers to these, or many other questions. As they do, or as I’m able to find them out, I’ll share them with you in this blog and my newsletter.

As one engineer told me at the Cupertino meeting in February, Final Cut Pro is still a work in progress. We’ve seen the outline of the work – the rough cut, if you will. Now we need to give the engineers time to listen to our feedback, polish it up, and deliver the final cut of Final Cut.

ONE LAST THOUGHT

I’ve made a promise to myself to provide training on the new version of Final Cut Pro as soon as possible after the release date.

If you are interested in getting up to speed quickly on the new version – please sign up for my free monthly Final Cut Studio newsletter. As I learn more, I’ll be sharing it with you there.

And as I make new training available, I’ll announce it there first.

For now, I’m going back to the drawing boards. I’ve got a lot of new work to do.

Larry

UPDATE – April 13, 2011

I just posted an eight minute audio review and commentary on the new version of Final Cut Pro X, with Michael Kammes. You can hear it here.

Refreshing Hard Drives Revisited

Posted by on January 02, 2011

A year or so ago, I wrote about a problem of digital media slowly "evaporating" when a hard drive is powered down and stored on a shelf.

You can read the first article here.

The solution is to refresh the hard drive. You can read that solution here.

Bill Lauer now asks:

A couple of years ago you wrote an article on how to refresh a hard drive using the "sudo cat /dev/rdisk0> /dev/null" or "sudo badblocks -b 4096 -p 1 -c 32768 /dev/rdisk0". I was wondering if there is a better way yet?

I never was able to get the bad block method to work. I tried 10.4, 10.5 and 10.6. Does TECH TOOL PRO’s "scan drive" command do the same thing? I really want a safe way to do this. Fast would be good also.

Larry replies: At the time the article came out a number of developers contacted me saying they were going to work on an easier solution. As of today, I don’t know of any.

However, if any reader does, please let me know and I’ll share the information.

UPDATE – JAN. 2, 2011

Bob Gobeille, who originally provided the terminal script to fix this problem, wrote again in answer to Bill Lauer’s wish.

It’s been quite a while since I’ve used Tech Tool Pro, but anything that reads the entire disk (like drive scanning) should work fine.

I use Terminal windows all the time and forget that the commands I sent you can be intimidating to those that don’t.

Since Bill wanted an easier way, I’ve attached an AppleScript that will refresh a disk with two clicks (one to select the disk, the other to run the scan). Here is a sample screen shot from the script.

Once you select the disk you want to scan, click OK. The only feedback you will get is that your disk drive activity light should go on and stay on until the refresh is done. When it is finished — and it will take a LONG time — another dialog box will come up and let you know. Here’s a sample screenshot:

This is a sample screen shot of the message you get when scanning is complete.

If you aren’t familiar with installing AppleScript, copy this script to your Library > Scripts directory. Then when you click on the script icon in the OSX menu bar, you should see it. Like this:

If the script icon is not in your menu bar, add it by running: Applications > Utilities > AppleScript Editor.app

Then open the AppleScript preferences and click Show Script menu in menu bar.

BOB’S NOTES
I’ve never tried this on RAIDed drives (I don’t have any). This reads at almost 60 MB/s on my internal MacPro drives, which works out to about 200 GB / hour. This means a scan of a 500GB disk will take roughly 2.5 hours. Different computers will scan at different speeds.

My script will only scan one drive at a time at this point.

I was tempted to have this script also check for other types of disk errors (and attempt to fix them), but you can use Disk Utility to do the same thing, using the Verify Disk and Repair Disk buttons.

As with all software, test this on a drive you have backed up first. We believe this to be reliable, but do not guarantee it.

Larry replies: Bob, this is GREAT! Thanks for taking the time to create, explain, and share it with us.

Here’s the link to the AppleScript file. This is stored as a Zip file, double-click it to decompress it, then install it as Bob outlined above.

Larry

Oops, I made a mistake

Posted by on October 14, 2010

Sigh…

In my webinar yesterday on Automating Compressor, I provided a link to an open-source X.264 codec which can be used with Compressor.

The problem is I was linking to an older version.

The current version of the codec is 1.2.16 and you can find the file here:

http://www.macupdate.com/info.php/id/24173/x264encoder

PLEASE read the instructions on the MacUpdate website, installing this codec can be a bit tricky.

Sorry for the error, I’ll correct this in the posted version of the webinar, which will be available tomorrow.

larry

More “Death of Final Cut” Rumors

Posted by on October 01, 2010

Yesterday, MacRumors posted that “Final Cut Studio Update Scaled Back and Delayed.”

Naturally, this sent seismic tremors throughout the Final Cut community. (Personally, I’ve lost count of how many times one rumor site or another has cried that Final Cut is dying. This is, apparently, good for ratings.)

First, the blog post takes Apple to task for missing a rumored release date. This is like being blamed for not accomplishing something you never said you would do in the first place.

Second, it rehashes old rumors about layoffs on the development team. As we have discussed here in the past, the staff layoffs did occur, but they were not in development.

Third, it rehashes old rumors that Apple is turning FCP into a “prosumer” application. These were rebutted by Apple, no less, within days.

So, while it is exciting, I’m sure, to imagine that the sky is falling, more informed speculation leads us to entirely different conclusions.

Apple does not preannounce products. Apple does not, in almost all cases, comment on rumors. Apple has on several occasions reiterated its support for Final Cut Studio. Apple recently updated four of the applications in the suite — which, to me, indicates on-going development. You don’t update programs you are looking to kill.

Philip Hodgetts has written a detailed, and I think, essentially accurate account of what’s going on behind the scenes with Final Cut Studio.

Neither he, nor I, are privy to any Apple secrets. Philip is just very, very good at reading tea leaves.

You can read it here.

Larry

Apple Updates Final Cut Studio

Posted by on September 16, 2010

Apple today announced a series of minor updates to fix a variety of bugs in Final Cut Studio (3).

These improvements do NOT include full support for Snow Leopard, but do fix a variety of problems in Final Cut Pro 7, Motion 4, Color 1.5, Compressor 3.5, and Apple QMaster.

My philosophy on bug fix updates is to wait a few days to make sure these didn’t break anything, then update.

You can view Apple’s announcement here: support.apple.com/kb/DL949

AppleInsider published a full list of the bug fixes here: www.appleinsider.com/articles/10/09/15/apple_updates_quicktime_for_windows_pro_applications.html

There are a variety of FCP fixes that I’m pleased to see, including the improved support for AVCHD, fixing the XML carriage return bug, and fixes to QMaster — a program that needs a LOT of improvements.

The easiest way to update – after waiting a bit, just to be “sure” – is using Software Update.

Larry

Solution to FCP XML Export Problem.

Posted by on August 16, 2010

UPDATE – Sept. 16, 2010

Yesterday, Apple updated Final Cut Pro to 7.0.3 which, among other things, fixes this problem. You can get the latest version via Software Update. If you are running an earlier version of Final Cut Pro, please read on.

- – -

Andreas Kiel, of Spherico, brought this to my attention yesterday.

There’s a problem with the XML Export function in Final Cut Pro 7.0.2. As Andreas writes:

Over the last few weeks I got more and more mails from people who complained about missing line breaks in XML metadata text entries — and they asked for a workaround.

The issue is very simple and probably won’t affect too many of your readers, but I got more than hundred mails about that issue.

So it’s simple. Enter a text with line breaks into any metadata field which allows that — like with text generators, markers or comments.
They could look like this in FCP:
line 1
line 2
line 3

The XML exported will give you a value:

line 1 line 2 line 3

with any app which tries to interpret the XML — this includes FCP itself.

This is a real disaster, if you working with subtitles which are are sent forth and back between systems using XML. I got a customer who had a documentation with 7 languages each about more than 2000 subtitles which were fine tuned within FCP — all in all there were around 15,000 subtitles screwed up for release on DVD, film, YouTube etc.

It was solved by the workaround described below – the customer was more than happy. Imagine, if you need about 1 minute to control each title, it would take about 250 hours to fix this one movie.

Andreas went on to detail the solution:

This is a known bug of FCP 7.0.2 and will affect all XML exports and there is no workaround within FCP. This is more than annoying if you work with subtitles, but it can/will be the same little disaster if you want to ‘downgrade’ to a lower version of FCP or collaborate using XML as interchange format.

So if you already updated to 7.0.2 here a tip how you can create ‘clean’ XMLs.

1. Move your ‘Final Cut Pro.app’ from the Applications folder to the Desktop
2. Insert your FCP installation DVD and install FCP 7.0 only
3. After installation is done, rename the freshly installed ‘Final Cut Pro.app’ to ‘Final Cut Pro 7.app’ – this way it won’t be touched by any automatic updates
4. Ctrl-click the ‘Final Cut Pro 7.app’ and select “Show Package Contents”
5. Navigate to Contents/MacOS/Final Cut Pro
6. Create an Alias of the ‘Final Cut Pro’ either on the Desktop or in the Dock.
7. Close the Folder
8. Move your current ‘Final Cut Pro.app’ back to the Applications folder

Procedure:
If you want to export an XML from your current FCP 7.0.2 then
1. Save your project
2. Double-Click your Alias ‘Final Cut Pro.app’ executable which you have created earlier. ‘Terminal.app’ will start and maybe give some error messages which might be interesting, but can be ignored.
3. An instance of FCP 7 will launch beside your FCP 7.0.2
4. Open your current project with FCP 7
5. Export XML without saving the project
6. Close the project or keep it open when you know you have to export more changed XMLs from that project — use the “Revert” menu to update from your 7.0.2 project
7. Never save the second instance of your project

Notes
1. If you know that you have to do a lot of XML exports, keep the FCP 7 instance open – it will share all the settings with the FCP 7.0.2
2. To quit the FCP 7 instance, close the ‘Terminal.app’ window related to your FCP 7 instance – this is cleaner than quitting the FCP 7 instance
3. Once you have created the FCP 7 version on one machine, you can copy it to other machines where you need it without using the Installer, you only have to create or fix the Alias

Larry adds: As you can probably tell, this workaround is not for the new user. But for those people that have experienced the problem, now you have a solution.

Thanks,

Larry

Favorite iPhone Apps

Posted by on June 03, 2010

In a recent newsletter, I invited readers to send in their favorite iPhone apps for production or post. I thought you might be interested in some of their replies:

Ian Hart

I find Movie*Slate very handy as I often need a clapper to sync multi-cams and/or digital audio recorded on my Zoom. I work on my own or with a very small team and I can operate Movie*Slate with one hand (shake to iPhone to cause the slate to clap).

I bought Storyboard (Cinemek) with which you use the iPhone camera to construct a storyboard, then perform pans, tilts, zooms etc, rearrange your shots, add dialogue (as subtitles) etc, play in "real time" and then export to a PDF document. Very impressive app, but until now it’s been more like a party trick than a serious part of my workflow.

Voice Memos is a really convenient tool for research. With a 30GB iPhone you can do very many hours of recording.

And the camera, of course. Just about an indispensable tool these days.

Gary Wales

My current favourite iPhone App is Movie*Slate. A simple yet multifunctional digital clapperboard that allows you to export/import XML files into Final Cut. A real time-saver on a shoot and can be blue tooth synced with another iPhone for multi-cam use.

Steve Schumacher

Time calculator is great if you need to add minutes and seconds, etc. Works just like a stand alone time calculator.

For pre-production and planning of shoots, Sunrise & Set Lite is fantastic. It tells you when the sun rises and sets, not just for today’s date, but for any day you choose. Perfect for knowing in 5 months when the sun is setting.

Kit Lammers

Convert – convert any units, use for time (no time code though)

OS X Ref – Quick reminder for key commands

DipSwitch – Calculate DipSwitches

Keith Marshall

ProPrompter
This is a very cool app where I can upload/download scripts and use my iPhone as a teleprompter. If you have another iPhone/iPod available, you can use it to control the other as well.

Storyboard
This will allow you to build a storyboard, animate camera movements and export as a pdf. I was working on a project as a teaching experience to a group of teens and we used this to educate them the process of planning.

And my most favorite…

iProRecorder
I can dock my iPhone into my Alesis ProTrack and record 16/44.1k stereo or mono to my device. This acts just like a field recorder and the ProTrack allows me to plug in XLR or Phono audio source or use the built in X-Y stereo microphones

Norman Hollyn

AJA DataCalc
DVDBudget
Both of Moviola’s guides: FCP Guide and Pro Video
Diana Weynand’s iKeysTo Go is also a good alternative
And I also like NEDi (which is macPro Video’s online tutorial guide

Pat DeFilippo

P D Post has used DJay software (Mac only, $50) for years to live- and auto-mix walk-in/walk-out music at corporate events, dance music at parties, etc. Today, DJay released DJay Remote, a $5 app for iPhone/iPod Touch. You still need the full version of DJay installed on your Mac, however DJay Remote lets you completely control all of your songs with DJay’s powerful functions remotely via the same Wi-Fi network that your Mac is on!

Tore Jonssen

I use CodecCalc and AutoCue all the time, works like a charm.

John Warner

I use Focalware on each and every location shoot to accurately predict sun and moon positions globally from sunrise through sunset anytime of the year.

All interesting choices. Let me know what your’s are and I’ll add them to the list.
Larry

Tech Note: Sending Files to Soundtrack Pro

Posted by on May 27, 2010

Michael Cowan sent me a note earlier today that I wanted to share with you.

He was having problems sending sequences from Final Cut Pro to Soundtrack Pro (STP). Since I do this all the time with my own projects, without problems, I couldn’t figure out why he was having difficulty.

First, I suggested that he send his sequences from the Browser, rather than selecting all the clips in the Timeline. I find sending Browser files to STP to be more reliable.

That didn’t work.

Second, I suggested that he trash both his FCP and STP preference files. I have found that corrupted FCP preference files can mess with sending files to STP.

That didn’t work.

Hmmm… time to think. However, while I was thinking, Michael did some research. What he didn’t mention when we were first talking about this was that the sequence he wanted to send contained other sequences in it (what Apple calls “nesting.”) Ah-HAH! Using nests causes problems. As Michael wrote:

“Alas this issue lies with the well-documented nested sequence/XML problem that prevents “Send To” of nested sequences to Soundtrack Pro. I’ll need to change my workflow. There was some guy [Jeremy Hughes] who said he had success by Sending To Apple Color, back to FCP and then on to STP (perhaps Color generates cleaner XML), but it didn’t work for me.”

For those that need more information, here is the link to Apple’s support site:

http://support.apple.com/kb/TS2155

And here’s the link to Jeremy Hughes‘ Color workflow workaround:

http://filmvideostuff.blogspot.com/2010/01/how-to-get-audio-from-nested-fcp.html

Thanks, Michael, for sharing this!