• 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
Re: Colorsync Utility Source vs Destination
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Colorsync Utility Source vs Destination


  • Subject: Re: Colorsync Utility Source vs Destination
  • From: Glenn Kowalski <email@hidden>
  • Date: Thu, 15 Apr 2004 17:46:53 -0400

John,

Thanks for your response. I have followup.

> creates filters which can be used when printing

For example in Preview, hit Print, go to the ColorSync section, you'll
see a popup titled "Quartz Filter". That's where you select a filter
you've created using ColorSync Utility.

Yes, I understand how to apply it. The question is, what is the difference between applying a filter that is using an icc profile and printing to a "device" defined to use the same profile? Possibly nothing in the end result, maybe it's just a different way to get to same thing and a matter of convenience.

> How does the system know what the source profile is?

Either the file has an embedded profile, or default profiles are chosen
depending on the color model (rgb, cmyk, lab). Preview, Safari, Mail,
and any Cocoa app using NSImage behaves that way.

Ok, so the default profiles act as source profiles if there is nothing embedded. Good to know.

> In other words, if I want to color manage an application, say Quark 6
for example, but don't want to use Quark's built-in CMS (mostly
because it only handles tiffs and built-in colors)

Depends on how the app handles color so this will vary from app to app.
The behavior I described above applies to the standard behavior of
Cocoa apps.

I take this to mean that there must be specific spec/code built in the outgoing data in order for the "filter" and the "device" defined in the Colorsync Utility to work. Not just a matter of outputting color data. Sadly, this translates to me as it's all useless until/if developers get on the wagon.

> Ok, now... so what is the difference between all of this and creating
a "filter" in the ColorSync utility?

The ColorSync Filter section of CSU creates filters which can be used
when printing. Filters aren't profiles. Profiles describe the
behavior of a device and/or tweak a device to behave a certain way,
they're tied conceptually to devices. A filter is more like collection
of manipulations you want to save and use again, not necessarily tied
to a certain device.

I realize filters aren't profiles, but they can be used to apply a profile. I was asking if there is a difference in the end result of applying a profile in a filter vs applying at the "device" as defined in the ColorSync Utility.

Thanks John.

--

Glenn Kowalski
Macintosh Systems Consultant
MacLab; a Division of Studio 405, Inc.
http://www.studio405.com
301-270-8445 x26
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: Colorsync Utility Source vs Destination
      • From: John Gnaegy <email@hidden>
    • Re: Colorsync Utility Source vs Destination
      • From: Chris Murphy <email@hidden>
  • Prev by Date: Soft proofing?
  • Next by Date: Re: Soft proofing?
  • Previous by thread: Re: Colorsync Utility Source vs Destination
  • Next by thread: Re: Colorsync Utility Source vs Destination
  • Index(es):
    • Date
    • Thread