Migrating FCP to Avid

[Dom Silverio]

Uhm… he asked specific questions not relating to Avid vs FCP. The others pulled that one from him – and he is a troll? Mark – let us be fair. He did say he is no expert and he is very clear (line by line) on his needs/wants. Relax Mark.

[Dom Silverio]

Media? Best is to recapture it. But that would take a lot of time. Either hire an night shift AP or swallow the jagged little pill and finish it in FCP.

IF you want FCP to fly – turn off RT Extreme. Yep – you read that right. This is the biggest hinderance to FCP GUI speed.

Good luck

[Andy Mees]

[MPE] “IF you want FCP to fly – turn off RT Extreme. Yep – you read that right. This is the biggest hinderance to FCP GUI speed”

RT Extreme ? are we talking FCP’s “Unlimited RT” vs “Safe RT” or OS X’s Quartz Extreme ? … please feel free to share your insights! 🙂

thanks
Andy

[Steve Connor]

In response to your original question, you will not be able to migrate the media, use Automatic Duck and recapture the footage and use the whole experience as a lesson, don’t start a huge project on an NLE you are not familiar with or that doesn’t fit your style of working.

There are thousands of professional editors editing on FCP every day, it has its shortcomings like most NLE’s but you find out what they are and work around them.

Talking about shortcomings, what is the “dupe detection bug?”

Steve Connor
Cardinal HD

[D.z.gilad]

The whole idea of migrating to Avid only occurred to me because that’s exactly what a friend of mine found herself forced to do recently. She told me about the “dupe detection bug”. It is the main reason I am considering doing the migration now, rather than later.

Here is what she told me:

“The timecode issue we had was that FC kept randomly changing TCs on us. For example, we would batch digitize something in and once captured, FC would just change the TC and assign different numbers to the clip. If you captured on the fly, it would use random code instead of the correct one (and we even had a rosetta stone and ext. TC feeds, not only firewire). FC would also do this randomly once the media was captured. For example, I would work with a sequence one day, shut down and call it a night. On the next startup the morning after, the same exact sequence would all a sudden show all these duplicate frames. Yet, all the content of the footage and the cut remained intact When we investigated, we found that FC had somehow changed our TCs and now was showing the same TC for different clips of the same tape. So the bin of tape X had 3 or 4 clips with a TC of 00:04:00:00

[Steve Connor]

I’ve always had dupe detection switched on and I ‘ve never had an issue like this.

Steve Connor
Cardinal HD

[Dom Silverio]

[Andy Mees] “are we talking FCP’s “Unlimited RT” vs “Safe RT””

Yes. FCP’s RT Extreme engine is resource intensive at any setting. Disabling it actually increases UI responsivenes – especially for long form projects. It works well for long, mostly straight cuts/dissolve type stuff. For everything else, I would not recommend it.

[Juan Salvo]

What are your OS X, and QT version numbers and how were they installed?

[Kim Rowley]

Thanks Shane. I hadn’t come across the TTTT tool. Very handy indeed. It brought me back to the FCP quick reference guide that lead me to a few more enlightenments.

Dual 2.7 GHz G5, 4GB RAM, ATI Radeon 9650, Xserve RAID, AJA IO, 2 20″ Cinema Display, FCP 5.02, OS X10.4.2

[Shane Ross]

I like TTTT so much. I really miss that ability in the Avid.

Hows THAT for turnabout?