On 4/26/2013 3:05 PM, Darrin Cardani wrote: On Apr 26, 2013, at 12:56 PM, Paul Miller <paul@fxtech.com> wrote: On 4/26/2013 1:47 PM, Garrick Meeker wrote: Some drivers do have bugs. The AMD driver in 10.6, in particular, may not be worth supporting. It doesn't support OpenCL images (requiring buffers only) and while we did work around that, we found the OpenCL/OpenGL interop so buggy that we disabled FxPlug hardware rendering for these cards/OS (instead transferring from host memory to the card). AMD 6xxx cards in 10.7 had issues (something I found with local memory) but an update seemed to fix that. FOUND IT. In some cases (in this case, D1) the input and output bitmaps are different sizes. The input image was one line taller than the output image. Since I assumed they were the same size, I was doing all the processing at the input size, and when I tried to read it back to the output image, it barfed. Funny, I had solved this problem before, but as this is all new clean code, I didn't incorporate the fix. Need to keep track of all of these little gotchas somewhere. Paul, Glad to hear it's working for you! It sounds like we should be giving you an input and output buffer of the same size in this case. If you want to file a bug with a simple repro case, I'll take a look at it. I seem to recall we've run into this sort of problem before, but I had thought we fixed it. _______________________________________________ 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: https://lists.apple.com/mailman/options/pro-apps-dev/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com Bug #13751398 filed. This one has been around awhile. Funny, I never would have run into it (twice) if I'd just grabbed the output FxBitmap size. Or just asserted() that they were the same size!