[Tom Fuldner]

Today at last, the Quadro 4000 works in PP and AE! I found a new driver dated 9 Sep 11 on the NVIDIA Web site, “cudadriver-4-1.0.50.” Good news/bad news: the issues I had with opacity on existing PP/AE projects remains. I started a new test project from scratch: no opacity problems, no aliasing. When and if I have to work on older projects started with the ATI card, I’ll have to switch back to the old card.

I can live with this. Keeping my fingers crossed.

Tom

Tom F.
Raleigh, NC

[Tom Fuldner]

David,

I must confess I don’t know if exporting AE projects we do/did in FCP7 will resolve opacity issues. I’ve resisted experimenting because I so much prefer being able to move quickly between PP and AE. As to the tearing/aliasing I’ve experienced using AE with the Quadro 4000 card, it’s evident even before leaving AE.

Tom

Tom F.
Raleigh, NC

[Tom Fuldner]

David,

I made the same transitions from FCP7/X to Premiere Pro CS5/Production Premium a few months ago. I too am very pleased with PP, though I may be more fortunate in not having experienced the frequency of crashes you describe. I’m running the application suite on a MacPro 3.1 with 32GB RAM.

More recently, I also installed the NVIDIA Quadro 4000 card to replace my ATI 4870. It’s been a mixed blessing. The Quadro card makes Premiere Pro sing on the MacPro. No ifs and or buts — until you add After Effects to the mix. When adding AE segments to a PP timeline, the opacity of AE segments gets hanky. Basic opacity transitions and the head and tail of a lower third super created in AE an inserted in PP lose their opacity and take on a white-color background instead. Also, diagonal shapes created in AE manifest jagged edges.

After making these discoveries, I replaced the ATI card and the issues went away. I’m using the latest NVIDA drivers and running Lion. I may reinstall the Quadro in a few months if new drivers provide a cure. In the mean time, the joy of real speed in PP is utterly compromised by problems encountered in AE. I realize the Quadro card doesn’t provide a speed edge for AE as it does in PP, but it should at least work properly.

Tom

Tom F.
Raleigh, NC

[Tom Fuldner]

I agree with Oliver. I really, really wanted to like FCP-X. I’m already into a project and I’ve made the same discovery: no keyframe editor for color correction. Ugh! This has got to change!

Tom F.
Raleigh, NC

[Tom Fuldner]

Just tried ClipWrap after encountering the same problem from StreamClip. It works! That’s what counts. Thanks for the tip.

Tom F.
Raleigh, NC

[Tom Fuldner]

David,

You have the goods on me!

I’ve been postponing the inevitable: a clean reinstall of the OS every application on my system drive.

Today seems like a good day to start.

Tom

Tom F.
Raleigh, NC

[Tom Fuldner]

I’m having the same experience with FCS3 and SL. FCP7 crashes by itself; when round-tripping to Color and Soundtrack Pro.

It’s like owning a PC two years ago and upgrading to Vista: uggh.

The 10.6.1 update hasn’t contributed any greater degree of stability. In the mean time, I’m saving my FCP sequences much more frequently.

Deleting preference files in Adobe Soundbooth and Office 2008 for Mac has improved their stability. Tempted to do the same with FCP, except I’m leery of making things worse while I’ve got projects due.

Tom

Tom F.
Raleigh, NC

[Tom Fuldner]

Same thing is happening with me in FCP7. Immediate impact: SMOOTHCAM won’t function on a file designated as a text file rather than a “mov.” file. Will likely implement Jeremy’s suggestion of renaming files via automator. Hope this gets fixed.

Tom F.
Raleigh, NC