site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Micah On Jul 5, 2007, at 2:29 PM, Dave Howell wrote: Dave On Jul 5, 2007, at 2:23 PM, Micah Sharp wrote: RESULT: Very dim results, compared to 32 bit float. Please let me know if there is anything we should be doing. Thanks, Micah _______________________________________________ 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 figured I wouldn't have to do anything there. How do I file a bug again? Sorry...I'm sure I've been told a million times... Very interesting! Thank you, Micah. Would you mind filing a bug about that? By the way, you're fine not doing any "half precision float messing about" because in software rendering you'll never have to render in 16-bit mode. Hey guys, just got a bug that I think might be in Motion. Our output is very dim and generally in-correct when a user switches to 16 bit float in their project settings (and has the float preview turned on). However, I noticed the same thing occurs with the Broadcast Safe plug-in. As far as I know, we don't actually process the incoming float buffer any differently (we don't do any half precision float messing about). Here are the steps: 1) Make a text layer, very red saturated 2) Apply Broadcast Safe plug-in and reduce saturation (just to see it work) 3) Switch project settings to 16 bit float _______________________________________________ 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/dhowell% 40apple.com This email sent to dhowell@apple.com This email sent to site_archiver@lists.apple.com