Re: Bug with FxParameterRetrievalAPI in Motion
Re: Bug with FxParameterRetrievalAPI in Motion
- Subject: Re: Bug with FxParameterRetrievalAPI in Motion
- From: Darrin Cardani <email@hidden>
- Date: Mon, 23 Jul 2007 10:21:45 -0700
On Jul 20, 2007, at 1:03 PM, Paul Miller wrote: Peter Litwinowicz wrote: So I discovered this handy little bug within Motion (at least I consider it a bug) When calculating the thumbnail view, Motion states that my InputImage and Output Image (in the –renderOutput call) is 146x100. Cool enough.
Yeah, I "discovered" that little gem a few months ago, but I can't remember if I told anyone about it.
Isn't this behavior similar to After Effects? Looking at the source to one of my old plugins, I see that whenever I do a checkout of a layer parameter, I always have to first allocate a PF_World that's the same size as the output. Then I have to checkout the layer into a PF_ParamDef structure. Then I have to copy from the ParamDef structure into the PF_World I allocated to resize the checked-out layer to the size I actually need. I thought I had to do this because the checkout always occurs at the checked-out layer's original size. Was I doing more work than I needed to? Or does that only occur when you have a layer parameter the user can change, and not when the layer parameter you're checking out is the input layer? (Sorry - it's been a while since I've looked at that stuff, so I could be remembering wrong.)
|
_______________________________________________
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