Re: FxPlug using CIImage with CIFilter behave differently between Motion and Final Cut
Re: FxPlug using CIImage with CIFilter behave differently between Motion and Final Cut
- Subject: Re: FxPlug using CIImage with CIFilter behave differently between Motion and Final Cut
- From: Stonewall Ballard <email@hidden>
- Date: Thu, 2 Oct 2008 18:06:00 -0400
Darrin,
I've been using an autorelease pool set up at the beginning of
renderOutput: and autoreleasing any bitmaps I fetch during that method
execution. Any reason why that's a bad idea?
- Stoney
On Oct 2, 2008, at 1:13 PM, Darrin Cardani wrote:
Jim,
If you're never releasing the images the host application gives to
you then you are leaking memory and possibly OpenGL textures and you
will eventually crash. You do need to call [myImage release]
explicitly on any images the host app gives to you. I recommend
using them, and then releasing them in your render method, although
you could also get them in your -frameSetup::: method and release
them in -frameCleanup.
--
Stonewall Ballard
email@hidden http://stoney.sb.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden