site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10 Dynamic down-ressing is a feature of FCP's RT engine. There are certain features that aren't available in the RT engine, and if your plugin uses one of those features, we'll run it in another, "non-RT" codepath that doesn't do dynamic quality adjustment. If you use the FxTemporalAPI (and set the mayRemapTime flag in your poperties dict), you'll find yourself in this state. You'll also find yourself here if you have any non-empty image well parameters. AHA! I guess I'm guilty of two of those things, but in this case, they aren't used all the time. We have an image well that CAN be used to reference another clip, but it's used rarely. And, the first time the effect is applied, it references the first frame of the clip, and then ignores it after that. Is there any way to say "99% of the time I'm RT", and switch on the non-RT code path only when needed? (I'm guessing not, but worth a shot!) _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... This email sent to site_archiver@lists.apple.com