• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
CoreImage problems with very large images
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

CoreImage problems with very large images


  • Subject: CoreImage problems with very large images
  • From: Jim Crate <email@hidden>
  • Date: Fri, 16 Nov 2007 03:07:34 -0500

I'm using CoreImage in an app, but it is unusable with very large images, e.g. a 52-megabyte 18,000 x 14,000 jpg. A 5000 x 4000 jpg image loads and processes with great performance, but trying to process the large image leads to very high memory use and much swapping to disk. I tried to load the large image in the Core Image Fun House example app, and ended up force-quitting after waiting 10-15 minutes.

The old implementation using NSImage could load and process (scale, rotate, watermark, broken grayscale) the large images, and while it wasn't fast, it was at least usable.

Is CoreImage just not meant to handle images this big? Or are there ways to gain acceptable performance with these large images with CoreImage? Will the problem possibly go away on a Mac Pro?

Thanks,

Jim

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • More CoreImage / CGImage questions
      • From: Jim Crate <email@hidden>
    • Re: CoreImage problems with very large images
      • From: Jim Crate <email@hidden>
    • Re: CoreImage problems with very large images
      • From: Chris Blackburn <email@hidden>
    • Leopard print sheet ignoring first page/last page settings
      • From: Jayson Adams <email@hidden>
  • Prev by Date: count how many NSPersistentDocument instances are open, and detect document close
  • Next by Date: Leopard print sheet ignoring first page/last page settings
  • Previous by thread: Re: count how many NSPersistentDocument instances are open, and detect document close
  • Next by thread: Leopard print sheet ignoring first page/last page settings
  • Index(es):
    • Date
    • Thread