Re: inconsistent FxPlug color parameter behavior
Re: inconsistent FxPlug color parameter behavior
- Subject: Re: inconsistent FxPlug color parameter behavior
- From: Steve Christensen <email@hidden>
- Date: Tue, 2 Oct 2007 08:23:01 -0700
For now I've just decided to use a RGBA parameter with Motion and a
RGB/slider pair for FCP. I may revisit this at some point in the
future if FCP catches up and/or the SDK is updated so I know what's
going on.
steve
On Oct 2, 2007, at 7:37 AM, Dave Howell wrote:
Yeah good point. So you'd need to add the slider regardless, and
just hide it if it is not needed. And you'd need to save (in a
hidden custom parameter) an indicator of whether the correct alpha
value is found in the RGBA parameter or in the slider. I guess this
is not such a simple workaround!
Dave
On Oct 2, 2007, at 6:45 AM, Steve Christensen wrote:
If I understand the documentation, parameter settings are saved in
the project, tied to a parameter ID. If a user created a project
using a version of FCP that doesn't support RGBA, later updated to
one that did and opened the project under the new version,
wouldn't the alpha value get lost if it was tied to a slider that
is no longer added?
On Oct 1, 2007, at 9:57 PM, Dave Howell wrote:
Hi Steve,
Unlike Motion, FCP does not currently support RGBA color
parameters. As a workaround, as you said, you could add a
separate float alpha slider, but you would only want to do this
in a host that doesn't support RGBA parameters. Unfortunately
there's no flag in FxHostCapabilities.h that would tell you
whether or not the host supports RGBA colors. If you assume that
FCP doesn't support alpha, and you add a separate alpha slider to
your plug-in, and then a new FCP adds alpha to its RGBA colors,
you suddenly have two conflicting alphas and your users are
confused. So, what to do?
Here's an idea. I'm not sure if it will work though. In your
addParameters method, you could add an RGBA parameter, and set
its value to something with an interesting alpha. Then retrieve
the value to see if the alpha value is correct. If it's right,
then the host supports RGBA; if not, then only RGB (in which case
you would add the alpha slider). Looking at FCP's FxPlug code, it
appears that this may work, but I haven't tried it.
There are some other things we could try, but this is most
straightforward, if it works.
Dave
On Oct 1, 2007, at 9:33 PM, Steve Christensen wrote:
In my plug-in, I have a color parameter that I added using -
addColorParameterWithName:parmId:defaultRed:defaultGreen:defaultBlu
e:defaultAlpha:parmFlags:.
In Motion, the parameter shows up, as expected, with all four
channels (RGBA) in the UI and clicking on the color swatch
brings up a color panel that includes an alpha slider. In FCP,
the parameter shows up as HSB and clicking on the color swatch
brings up a color panel with only grays/RGB/CMYK/HSB selectable.
This really seems like it's broken, certainly inconsistent.
Can I hope that this will work as expected in the future or
should I just assume that's the way it'll always be and create a
separate alpha parameter?
steve
_______________________________________________
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