Did anyone manage to figure out what causes the horrendous memory leak
in Core Image filters when the 'edit filter function' option is used?
I absolutely need to use in several places, but it's eating 4GB of ram
in no time at all :(
I've attached a composition with the filter in question. Open it,
watch it leak. The speed of the leak depends on the image size (I'm
using HD video streams, in 32bit colour - total worst case scenario
unfortunately!)
Is there any way around this bug? Or is it fixed in 10.6? (This is a
potential show-stopper - that's a critical filter I really can't do
without, so if necessary I'll make my app 10.6 only). Alternatively,
is there a way to set ROI without going through the javascript? Maybe
set the CI Filter up outside of QC and get it loaded as a plugin?
Thanks
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
