Re: Bug with FxParameterRetrievalAPI in Motion
Re: Bug with FxParameterRetrievalAPI in Motion
- Subject: Re: Bug with FxParameterRetrievalAPI in Motion
- From: Peter Litwinowicz <email@hidden>
- Date: Fri, 20 Jul 2007 12:47:12 -0700
- Thread-topic: Bug with FxParameterRetrievalAPI in Motion
Title: Re: Bug with FxParameterRetrievalAPI in Motion
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.
However, I’m using multiple frames in the input sequence using FxTemporalImageAPI::getBitmap . That works just fine, but gives me images at my original resolution (720x480).
It seems to me that if I’m called to render an image at 146x100, then all the calls to get images from the sequence should be at the same resolution that I’m currently asked to work at.
Pete
Of course the same thing happens when asking Motion to work at 1/2 or 1/3 , etc. resolution.
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