• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Bug with FxParameterRetrievalAPI in Motion
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug with FxParameterRetrievalAPI in Motion


  • Subject: Re: Bug with FxParameterRetrievalAPI in Motion
  • From: "Emile Tobenfeld (a. k. a Dr. T)" <email@hidden>
  • Date: Mon, 23 Jul 2007 13:30:26 -0400

Title: Re: Bug with FxParameterRetrievalAPI in Motion
At 10:21 AM -0700 7/23/07, Darrin Cardani wrote:
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?

The issue I have seen mainly involved checking out the input layer. There are numerous circumstances (in both hosts) where the size of the bitmap returned from GetInputBitMap does not match the size of the source passed to render. This would never happen (AFIK) in AE.

(Sorry - it's been a while since I've looked at that stuff, so I could be remembering wrong.)

Darrin
--
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:
>com

This email sent to email@hidden


--

"The test of a first-rate intelligence is the ability to hold two opposed ideas in the mind at the same time, and still retain the ability to function."

F. Scott Fitzgerald

Visit "Before the Fall -- Images of the World Trade Center" at http://www.foryourhead.com

               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

  • Follow-Ups:
    • Re: Bug with FxParameterRetrievalAPI in Motion
      • From: Peter Litwinowicz <email@hidden>
References: 
 >Bug with FxParameterRetrievalAPI in Motion (From: Peter Litwinowicz <email@hidden>)
 >Re: Bug with FxParameterRetrievalAPI in Motion (From: Paul Miller <email@hidden>)
 >Re: Bug with FxParameterRetrievalAPI in Motion (From: Darrin Cardani <email@hidden>)

  • Prev by Date: Re: Bug with FxParameterRetrievalAPI in Motion
  • Next by Date: Re: Bug with FxParameterRetrievalAPI in Motion
  • Previous by thread: Re: Bug with FxParameterRetrievalAPI in Motion
  • Next by thread: Re: Bug with FxParameterRetrievalAPI in Motion
  • Index(es):
    • Date
    • Thread