Re: CoreImage: Newbie can't find memory leak
Re: CoreImage: Newbie can't find memory leak
- Subject: Re: CoreImage: Newbie can't find memory leak
- From: Chris Lewis <email@hidden>
- Date: Wed, 15 Feb 2006 09:56:10 +0000
Hi Markus,
Thanks for the heads up. This is for a Masters project, but no-one in
my department runs a Mac (all Linux), so the only time they ever see
the project is running on my 1.5Ghz Powerbook. Which does the
computations pretty fast, much faster than NSImage was doing it (maybe
this points to the slowdown being GPU related?) I'll gloss over any
incompatibilites in the business plan!
The code probably won't ever see a release past my home page, and a
slating by PervisionTracker :)
Chris
On 2/15/06, Markus Hitter <email@hidden> wrote:
>
> Am 14.02.2006 um 21:51 schrieb Chris Lewis:
>
> > I've been using
> > CoreImage to implement a machine vision project, and it's going really
> > well. I'm loving the power/speed I've been getting.
>
> Depending on what machines you expect your software to run on, it
> might be worth a note CoreImage is exceptionally slow on some
> machines. Simple CI filters like "blur" easily take up 30 seconds in
> cases GraphicConverter or Photoshop need 3 seconds only, using their
> own algorithm.
>
> Not sure wether this is bound to the processor (500 MHz G3, 640 MB
> RAM) or to the graphics card (ATI RageM3, 8 MB, "Core Image not
> supported").
>
>
> Markus
>
> - - - - - - - - - - - - - - - - - - -
> Dipl. Ing. Markus Hitter
> http://www.jump-ing.de/
>
>
>
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden