Part 2: Bug with FxParameterRetrievalAPI in Motion
Part 2: Bug with FxParameterRetrievalAPI in Motion
- Subject: Part 2: Bug with FxParameterRetrievalAPI in Motion
- From: Peter Litwinowicz <email@hidden>
- Date: Mon, 23 Jul 2007 12:54:47 -0700
- Thread-topic: Part 2: Bug with FxParameterRetrievalAPI in Motion
Title: Part 2: Bug with FxParameterRetrievalAPI in Motion
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.
Also, it doesn’t really matter what AE does :-)
Seriously, if the user asks to render at 50% resolution, then all the images I get should be at 50% resolution.
Also, big picture:
InputImage passed to –renderOUtput should NEVER be different than calling:
[ FxTemporalImageAPI::getBitmap:&srcMap withInfo:renderInfo atTime:fenderInfo.frame]
That is, the inputImage should match calling getBitmap from FxTemporalImageAPI at the current frame time. And this goes for pixel dimensions, previous effects on effects stack applied ,etc.
Pete
_______________________________________________
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