site_archiver@lists.apple.com Delivered-To: pro-apps-dev@lists.apple.com On Apr 9, 2008, at 3:39 PM, Matt Rhodes wrote: Darrin -- 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... During the -renderOutput call, I grab the pixels from a Bitmap from an image well and apply it as a texture to a 3D object (we create the 3D object and render it). I'm finding that if I put a Group into the image well, the pixels I retrieve aren't quite what I'd expect. Some pixels seem to be missing. If I put in a child of the Group, the resulting image looks correct. That definitely looks and sounds like a bug on our side. Please file a radar. Has anyone seen this problem? I've not seen it, but that's probably just because I didn't think to look for it. Am I simply not accessing the pixels properly? It looks like you are, and it's more likely that the problem is on our end. And why would it not work when applying the Group, but work fine when applying the contents of the Group? Internally to Motion, rendering a group and passing it to a plugin as an image is very different from simply retrieving an existing frame and passing that to a filter. A group can have multiple pieces of footage and even other groups in it, so it has to actually render what's in the group first, then pass the result to the filter. There's a lot that could potentially go wrong during such an action. This email sent to site_archiver@lists.apple.com