Re: Getting 32 bit float image format instead of 16 bit
site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Hi Brad, - Paul On Aug 8, 2008, at 12:11 PM, Brad Wright wrote: Hi ProApps: Brad Wright _______________________________________________ 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/pschneider%40apple.com _______________________________________________ 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... Final Cut will never give you 16-bit images. Motion will only send you 16-bit textures, never 16-bit bitmaps. Is there any way to avoid getting 16 bit float the input image format for renderOutput. I'm having to write image processing loops for 32 bit, 16 bit, and 8 bit, for both RGB and YUV. This comes out to 6 different loops for all the formats, as I'm trying to avoid extra processing inside each loop for speed. That's a lot of redundant code all doing the same general thing. I'd like to skip supporting 16 bit and just support 32 bit, if I could prevent Final Cut from sending me 16 bit images. Is this at all possible? I just want 8 bit integer or 32 bit float. This email sent to pschneider@apple.com This email sent to site_archiver@lists.apple.com
participants (1)
-
Paul Schneider