Bug with getting images over time within Motion?
Bug with getting images over time within Motion?
- Subject: Bug with getting images over time within Motion?
- From: Peter Litwinowicz <email@hidden>
- Date: Thu, 11 Mar 2010 18:17:52 -0800
- Thread-topic: Bug with getting images over time within Motion?
Title: Bug with getting images over time within Motion?
Hey all,
I’m creating a software-only FxPlug.
Is it a known bug in Motion that FxTemporalImageAPI returns bogus frames if the render resolution is set to half, quarter, etc.?
Let’s say I have a 320x240 movie, and I set Motion to render at 50% resolution. The inputImage to my FxPlug is at 160x120. Cool enough. Then I do something like:
parmsMultipleInputFramesApi = [_apiManager apiForProtocol:@protocol(FxTemporalImageAPI)];
isSuccessful= [parmsMultipleInputFramesApi getInputBitmap:¤tMap withInfo:renderInfo atTime:renderInfo.frame];
Well currentMap then tells me its width and height are 320x240. So I shrink the image to160x120 before using it. Well it appears Motion shrinks the 320x240 buffer to 160x120, but then puts that in a 320x240 buffer to pass to me. So when I shrink it, it effectively gets shrunk twice.
Argh.
Does this ring a bell?
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