Re: Viewer Window and Display preprocessing
Re: Viewer Window and Display preprocessing
- Subject: Re: Viewer Window and Display preprocessing
- From: Brian Gardner <email@hidden>
- Date: Thu, 19 Mar 2009 15:55:45 -0700
Hmmm....
1. Is there any way an FxPlugin could read a Global
variable? I'm thinking, perhaps, a user settable toggle
whose state all instances of a FxPlug could access?
2. Thanks for the link to the FxPlug API page.
Would you happen to know if there is a tutorial
available for FxPlug programming? Maybe even
one that teaches writing hardware accellerated FxPlugins?
The nesting idea sounds interesting.
Programming it to be realtime sounds puzzling.
Though, that might be overcome, if I could find
a way to learn GPU FxPlug programming quickly enough.
Any suggestions?
-- Brian
On Mar 19, 2009, at 1:47 PM, Paul Schneider wrote:
Hi Brian,
You can make an image processing filter and apply it to your project
(using groups in Motion, or nesting in FCP). But the filter is part
of the project, not attached to a particular viewer. The user will
need to remember to switch it off when viewing your project on a
different display, or when you render / export to a file on disk.
And there isn't any FxPlug API to detect when you are being called
for display in the viewer, versus the canvas, versus exporting to
disk. So, you can't do that automatically in your plugin.
So, you can get close, but there aren't any "display LUT" hooks.
If you're interested, the FxPlug SDK is here:
http://developer.apple.com/appleapplications/fxplugsdk.html
- Paul
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden