Re: FC and problems getting/setting point parameter values
Re: FC and problems getting/setting point parameter values
- Subject: Re: FC and problems getting/setting point parameter values
- From: Emile Tobenfeld <email@hidden>
- Date: Thu, 28 Feb 2008 13:30:22 -0500
Title: Re: FC and problems getting/setting point parameter
values
At 11:32 AM -0500 2/28/08, Paul Schneider wrote:
Hi, Steve,
it looks like this is a bug in Final Cut. When your plugin
changes a point parameter, if you change the X value *but not the Y
value*, the change won't stick.
This is something we'll need to fix on
our end. In the meantime, you should be able to work around it
by changing the point parameter twice - first to a dummy value, then
to the value you want - so that both the X and Y components
change.
or change the Y value by .000001, which is how we hacked around the
issue..
Thanks for bringing this to my attention! Sorry for the
inconvenience.
- Paul
On Feb 27, 2008, at 8:08 PM, Steve Christensen wrote:
I have a plugin that has a popup
parameter to specify presets. When the user changes the value, the
plugin sets the values of a number of other parameters based on a set
of values associated with the particular preset. What I'm finding is
that with a point parameter, the x- and y-value are not always updated
correctly, but only in FCP/FCE, not Motion. Also, other types of
parameters seem to behave correctly in all three applications.
All of the parameters are added with flags set to
kFxParameterFlag_NOT_ANIMATABLE, so the values should be constant
across an entire timeframe of the effect.
Hoping to narrow down the problem, I wrote a small test generator
plugin that just has a popup parameter and a point parameter. I dumped
out the values in -parameterChanged: and -renderOutput: and found that
the values had changed along the way. I also noticed that the UI was
not reflecting the updated values either, in this case.
Final Cut Express[6339] ### parameterChanged @ 0.000000: x was
0.500000, should be 1.000000, is 1.000000
Final Cut Express[6339] ### parameterChanged @ 0.000000: y was
0.500000, should be 0.500000, is 0.500000
Final Cut Express[6339] -----------------
Final Cut Express[6339] ### renderOutput @ 0.000000: x should be
1.000000, is 0.000000
Final Cut Express[6339] ### renderOutput @ 0.000000: y should be
0.500000, is 0.500000
I can accept that I'm doing something weird, but I don't know where to
look. Does anybody have some ideas?
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:
>e.com
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:
>com
This email sent to email@hidden
--
"Now, here, you see, it takes all the
running you can do, to keep in the same place. If you want to get
somewhere else, you must run at least twice as fast as that!" --
The Red Queen
Emile Tobenfeld, Ph. D.
Video Producer
Image Processing Specialist
Video for your HEAD!
Boris FX
http://www.foryourhead.com
http://www.borisfx.com
_______________________________________________
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