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 09:21:16 -0700
On Jul 20, 2007, at 12:47 PM, 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.
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, Please file a bug if you feel this is incorrect behavior. We do this with textures because it means that no data has to be sent from the CPU to the GPU if the texture is already on the GPU and you can simply adjust the texture coordinates so that it matches your other inputs. This saves bus bandwidth and time as nothing is sent over the bus and no rescaling needs to be done. We should probably not do the same thing for bitmaps, since it will mean you'll have to resample something in software, which is usually expensive. I'll see if there was any other reason we were doing this with bitmaps and let you know.
Darrin
|
_______________________________________________
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