Motion - weird handling of large images
Motion - weird handling of large images
- Subject: Motion - weird handling of large images
- From: Steve Christensen <email@hidden>
- Date: Mon, 4 Feb 2008 22:18:47 -0800
I have been testing some effects on both 8-bit and 32-bit (float)
channel images and ran across some weird (to me) behavior.
After launching Motion, I dragged a large (2276x2649) Photoshop file
into the middle of the workspace and applied a filter. This worked
fine with an 8-bit depth. I then opened the project properties window
and changed to 32-bit float depth, then clicked the OK button. Motion
popped up a sheet saying that the object is too large to render and
that it would be cropped to 2048x2048. My filter was called to
render, and then the final image looks like the edge pixels were
repeated to fill out the original image size. (I didn't do this since
the filter was passed a 2048x2048 image.
Why am I seeing the difference, especially given that the original
image is larger than 2048x2048? I'd expect the same message for the 8-
bit case. Here are the numbers Motion is passing to my plugin:
rendering at kFxDepth_UINT8:
rowCount = 2648
columnCount = 2276
inputRowBytes = 9104
outputRowBytes = 9104
rendering at kFxDepth_FLOAT32:
rowCount = 2048
columnCount = 2048
inputRowBytes = 32768
outputRowBytes = 32768
_______________________________________________
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