site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Aug 9, 2008, at 6:29 PM, Brad Wright wrote: [myBitmapImage width] == 720 [myBitmapImage height] == 240 [myBitmapImage rowBytes] = 23040 The image format is Float and 32 bit wide. _______________________________________________ Do not post admin requests to the list. They will be ignored. Pro-apps-dev mailing list (Pro-apps-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.ap... What value did you supply in imageInfo.fieldOrder? If it contains something other than kFxFieldOrder_PROGRESSIVE, the bitmap may actually contain the entire image, but rowBytes is set up so you only see the pixels in every other row. If that's the case, it's not an application bug since it's doing exactly what you told it to do. I'm seeing possibly wrong values for width and height in an FxImage. The problem happens when I export to a DVC Pro 25 NTSC movie from an HD timeline. My sequence is 1440x1080, and the exported image is 720x480. In the rederOutput function I retrieve the actual image using the temporal image API. if ([tempororalImageApi getInputBitmap:(FxBitmap **) &myBitmapImage withInfo:(FxRenderInfo) imageInfo atTime:(double) renderInfo.frame]==NO) { NSLog(@"Failed to retrieve the original Bitmap image\n"); return NO; } Here's the values I get: 23040 is the correct row bytes value for the image if it's at 1440 pixels wide. When I try to process the image using these values in my loop, I get only the first part of the actual image. So it appears that the image is actually 1440 wide instead of being 720 wide. Is this a know bug? Is there a workaround? This email sent to site_archiver@lists.apple.com