site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Feb 4, 2008, at 8:21 AM, Darrin Cardani wrote: On Feb 3, 2008, at 12:02 PM, Steve Christensen wrote: In FCP, I think it's this: In Motion: 1) From the "Edit" menu, select "Project Properties" 2) Change the "Bit Depth" popup from "8 Bit" to "32 Bit". 1. So the input bitmaps are advertised with the correct channel order? _______________________________________________ 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... I don't remember seeing these specifically addressed so I figured I'd ask so I can make sure I'm doing everything correctly. I'm currently interested in the software rendering case, but if there some differences in the hardware case, that'd be nice to know as well. 1. So far all the images or video I load into a project for testing use 32-bit ARGB/RGBA for the pixel format. If I've read the docs correctly, I should also expect to see 128-bit floating point ARGB/RGBA pixels in some circumstances. If that's so, what can I do to get that to happen so I can test that I'm handling that case correctly? 1) select your sequence in the browser, or click on the timeline window 2) From the "Sequence" menu, select "Settings..." 3) Click on the "Video Processing" tab 4) Click on the "Render all YUV material in high-precision YUV" Thanks. I've already started testing in Motion, and the FCP info will come in handy since I wouldn't necessarily associated that with floating-point pixels. 2. Can I assume that the input and output images will always have the same sized pixels, i.e., I shouldn't expect to see a 32-bit pixel in the input image(s) and a 128-bit pixel in the output image? Correct. Input and output should always be the same bit depth and channel order. Note that there is a bug in Motion in which the output bitmap will claim to be RGBA, when it's really ARGB, just like the input (when working in software). It's safe to ignore it and output ARGB. 2. Is this separate from what the formatsFloatRGBABitmapsAsARGB selector in FxHostCapabilities returns? 3. Or in the Motion case are all bitmaps ARGB, independent of the pixel depth? This email sent to site_archiver@lists.apple.com