Another bug... perhaps a big bug
Another bug... perhaps a big bug
- Subject: Another bug... perhaps a big bug
- From: Peter Litwinowicz <email@hidden>
- Date: Thu, 21 Jul 2011 17:58:13 -0700
- Thread-topic: Another bug... perhaps a big bug
This is in Motion:
So I create a software-only plugin that has an image well. If there is no
clip assigned to the image well I simply copy the image given to me in
renderOutput to the output. If there is an clip assigned to the image
well, I copy that to the output instead of the clip image from the layer
that the effect is applied to.
Note: the project + clip have settings: 720x480 resolution, DV aspect
ratio, lower field first.
So I'm using DV footage (720x480). I've attached the original, scaled
down in order to get this email to fit in the mail-list limit of 50k (any
way to raise that?). FYI: I tried to put the image in the body of the
email and my email client blew the email size to 500k.
In the original image, note the blue dots drawn by Motion around the edge
that define the bounding box where the image is defined. However if I
pass the exact same image sequence into the image well and copy that to
the output, I get the image named "ImageWell.jpg". Note the black bars on
both the right and left sides. This is giving our plugin the same image
sequence, as seen from an image well param using
FxParameterRetrievalAPI::getBitmap (or whatever the nomenclature is for
Objective-C forgive me if this is wrong! :) )
This looks like the image is converted perhaps to suare pixels, but then
reported to me as 720x480. Argh.
Anyone else see this? This makes image wells unusable. I'll be filing a
bug.
Pete
Attachment:
Orig.jpg
Description: JPEG image
Attachment:
ImageWell.jpg
Description: JPEG image
_______________________________________________
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