Re: Bug with FxParameterRetrievalAPI in Motion
Re: Bug with FxParameterRetrievalAPI in Motion
- Subject: Re: Bug with FxParameterRetrievalAPI in Motion
- From: Emile Tobenfeld <email@hidden>
- Date: Fri, 20 Jul 2007 15:56:05 -0400
Title: Re: Bug with FxParameterRetrievalAPI in
Motion
I aslo consider it a bug, and had to do a fair amount of hacking
to get around it.
At 12:47 PM -0700 7/20/07, 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.
Actually, I found these to differ by one pixel each way,
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:
>com
This email sent to email@hidden
--
"Now, here, you see, it takes all the
running you can do, to keep in the same place. If you want to get
somewhere else, you must run at least twice as fast as that!" --
The Red Queen
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