Re: Point parameters when applied to shape layers
Re: Point parameters when applied to shape layers
- Subject: Re: Point parameters when applied to shape layers
- From: Garrick Meeker <email@hidden>
- Date: Wed, 27 Aug 2008 21:54:11 -0700
I finally tracked it down. Apparently setting
kFxPropertyKey_PixelIndependent = YES in properties will cause point
values to go haywire when applied to a shape layer.
On Aug 27, 2008, at 5:21 PM, Darrin Cardani wrote:
Garrick,
That doesn't make a whole lot of sense to me. The .39... scale is
because it's drawing a preview either in the timeline, the layer
list, or the inspector window. But I don't see any reason why the
point parameter would change its value. Looking at the filters that
ship with Motion, Fisheye and Droplet have point parameters that
seem to work as expected.
Are you getting back a valid value for the FxParameterRetrievalAPI
object?
Darrin
On Aug 27, 2008, at 5:01 PM, Garrick Meeker wrote:
Here's my printf's showing x and y from getXValue, x and y scale,
width, and height. The odd lines are from renderOutput and the
even lines (that around about 0.5) are from inside frameCleanup.
It's applied to a simple rectangle shape that covers about half of
a DV frame. Does this make any sense?
get point: -0.567039 1.398438 1.000000 1.000000 358 256
get point: 0.500000 0.500000 1.000000 1.000000 358 256
get point: 0.013514 0.981308 0.395413 0.395413 361 257
get point: 0.500000 0.500000 0.395413 0.395413 361 257
get point: -0.297297 1.172414 0.077779 0.077779 475 372
get point: 0.500000 0.500000 0.077779 0.077779 475 372
get point: 0.031250 0.958333 0.158203 0.158203 379 271
get point: 0.500000 0.500000 0.158203 0.158203 379 271
get point: -0.567039 1.398437 1.000000 1.000000 358 256
get point: 0.500000 0.500000 1.000000 1.000000 358 256
get point: -0.567039 1.398437 1.000000 1.000000 358 256
get point: 0.500000 0.500000 1.000000 1.000000 358 256
get point: -0.567039 1.398437 1.000000 1.000000 358 256
get point: 0.500000 0.500000 1.000000 1.000000 358 256
get point: -0.567039 1.398437 1.000000 1.000000 358 256
get point: 0.500000 0.500000 1.000000 1.000000 358 256
get point: -0.567039 1.398437 1.000000 1.000000 358 256
get point: 0.500000 0.500000 1.000000 1.000000 358 256
get point: -0.533141 1.398438 1.000000 1.000000 358 256
get point: 0.533898 0.500000 1.000000 1.000000 358 256
get point: -0.533141 1.398438 1.000000 1.000000 358 256
get point: 0.533898 0.500000 1.000000 1.000000 358 256
get point: -0.530316 1.398437 1.000000 1.000000 358 256
get point: 0.536723 0.500000 1.000000 1.000000 358 256
get point: -0.530316 1.398437 1.000000 1.000000 358 256
get point: 0.536723 0.500000 1.000000 1.000000 358 256
get point: -0.533141 1.398438 1.000000 1.000000 358 256
get point: 0.533898 0.500000 1.000000 1.000000 358 256
get point: -0.533141 1.398438 1.000000 1.000000 358 256
get point: 0.533898 0.500000 1.000000 1.000000 358 256
get point: -0.263399 1.172414 0.077779 0.077779 475 372
get point: 0.533898 0.500000 0.077779 0.077779 475 372
get point: 0.065148 0.958333 0.158203 0.158203 379 271
get point: 0.533898 0.500000 0.158203 0.158203 379 271
On Aug 27, 2008, at 4:35 PM, Darrin Cardani wrote:
On Aug 27, 2008, at 4:05 PM, Garrick Meeker wrote:
I seem to be getting inconsistent and bogus values from getXValue
when my FxPlug filter is applied to a shape layer in Motion 3.
Has anyone seen this? I don't have time to make a simpler test
case right now.
Can you elaborate on how they are "inconsistent and bogus?" In
what way are they different from what you expect?
Thanks,
Darrin
--
Darrin Cardani
email@hidden
--
Darrin Cardani
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