-
“(plug-in) failed to render”: Update
This topic recently got revived over on apple.com.
Applying some filters in FCP, especially blurs, will produce a red screen “effect failed to render.”After re-reading the posts, searching for and re-reading some related threads, I realized I had not followed the same tests as the other victims. So I re-ran the tests. This is clearly a graphics card issue, in the case of my two Intel machines.
I have four dual-head nvidia geforce 7300 gt cards in each of our Intels. This is enough display power to run 8-30″ Cinema displays. (It was an early Intel config, the cards are supposed to be linked together to improve performance. It was total Apple/Nvidia marketing BS and we fell for it.)
If I use one card (two connectors) to run two monitors the filters work in FCP and in Motion.
If I use one card to run two monitors and add a third display to any of the other 6 connectors, the filters fail to render in FCP but they work in Motion.
If I use any two graphics cards to run any two monitors, the filters fail in FCPbut will work in Motion.
If I use any three cards to run my three displays, the filters fail in FCP but work in Motion.This totally blows but now I know. If I want to use about twenty obscure filters, I have to go back to working on two displays. The horror.
bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”