site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com Darrin On Nov 5, 2008, at 1:46 PM, Stonewall Ballard wrote: Paul, I'm seeing frames of r408 pixels, all of which are (255, 0, 128, 128). Bug or feature? - Stoney On Nov 3, 2008, at 4:37 PM, Paul Schneider wrote: Hi Stoney, ... - Paul -- Stonewall Ballard stoney@sb.org http://stoney.sb.org/ _______________________________________________ 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/dcardani%40apple.com -- Darrin Cardani dcardani@apple.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... FWIW, you can use the timing API to figure out when the clip ends and just not read frames from then. Maybe make a wrapper which returns either the last frame or an empty frame when appropriate. It's not actually all-zero off the end of the clip in FCP. It's fully opaque and black. Too bad. I believe that one difference between FCP and Motion is that if you request a non-existent frame (a frame that is before the start of the media or after the end), Motion will clamp to the nearest available frame while FCP will return an all-zero bitmap. Are you averaging multiple frames together? That could produce darker frames if some of the images aren't there. This email sent to dcardani@apple.com This email sent to site_archiver@lists.apple.com