[David Bogie]

Since it worked in FCP3, bBroken” at this point suggests the feature was deliberately sabotaged by Apple. One can only wonder Why.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

“Extrude?”

Run that by me again. What would you do with an extruded alpha?

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

And another thing, there are dozens (hundreds) of ex-Avid suers here and on the apple.com FCP forums. Be sure to check them all out and lurk for a few weeks. Also lafcpug.org.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

1. Apple offers education discounts. You’ve got to look harder. Your bookshop probably sells Apple hardware, even Boise State has an Apple dealership!
2. Why do you think you need RAID? I ask because, after we’ve examined the issues, most folks end up realizing they don’t need a RAID at all.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

This is how FCP works and, yah, I hate it, too. It treats all speed adjustments as Insert Edits. Some folks like it that way, go figure.

Open an empty sequence and do your time remapping there, copy and paste back into your main sequence. It’s not as tedious as you think but it’s still lame in my opinion.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

It also depends on where the nest originated. As silly as it sounds, the 4.5 manual contains a good explanation of how to create and use nests. Not all of us do it properly.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

that’s as much operating style as it is protocol. Much will be dictated by your boss’s previous experience and demands for maintaining a workflow that no longer applies. The hardest part is likely to be learning Apple’s new terminology. It won’t help her to complain that Avid’s way is better. No one using an FCP system really cares (What’s an Avid?) and that’s tough for a long-time Avid expert to deal with: Change.

Invest in two books today, spend your own money if you must, but you might be able to find used copies at Powells or Amazon.

“Behind the Seen” Murch edits “Cold Mountain” on FCP

“FCP for Avid Editors” a reasonable attempt to justify Apple’s way of doing things. A good cross reference along the lines of “If Avid says THIS then FCP says THAT.”

Others will have better advice for you soon. Welcome to the family. You’re going to love FCP, you’re going to hate FCP. You get over both of these feelings soon.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Thanks very much for closing the thread and including your solution. Hardly anyone does that around here. Good kow-karma.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

Not any direct help, sorry. But since the AJA box is actually doing the talking to the deck, you might try posting over on the AJA forum.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

[David Bogie]

I’ve opened all of the documentation for the clustering apps and I’ll be danged if I can figure any of it out. The recent software updates included qmaster pieces. There aer no index entries or Help system entries in FCP5 on these topics.

Please let us know if you get it figured out.

bogiesan

This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”