• 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: untagged RGB data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: untagged RGB data


  • Subject: Re: untagged RGB data
  • From: bruce fraser <email@hidden>
  • Date: Fri, 19 Dec 2003 16:46:13 -0800

At 3:10 PM -0800 12/19/03, John Zimmerer wrote:

I'm not sure I buy the need for "OS working spaces", since I truly believe all data should be tagged. And ultimately, this is the domain of the user space applications (including AppleScript and sips), since they manipulate color directly. The OS should simply render source color accurately, and have a single definition (across workflows and continents) of how untagged source data is treated, per color space.

John,

There are many reasons for working with untagged data.

RGB profiles are small, certainly, but you need to get off your T1 line and back on dialup to understand the impact of adding 4k to every single JPEG on the web. It's not going to happen anyway, but I'll argue strongly that it makes bugger-all sense to load the web with tons of redundant data in the form of zillions of copies of the sRGB profile.

For CMYK, the same argument applies in spades. Real World Photoshop CS will contain about a thousand images, most of them under a megabyte, the very largest ones maybe 5 megabytes. It will be a cold day in hell before I contemplate adding 1.5MB of profile data to every image.

I think I can fairly claim to be as big an evangelist of color management as anyone else on the planet, but the "all data should be tagged" argument is not one I'll buy. Not only is it simply not going to happen, there are plenty of very good reasons why it shouldn't happen.

If you're going to leave everything to the apps, scrap ColorSync. If you want a system-level OS, it needs to behave in a way that the majority of its users will find useful. Right now just about everyone on this list is telling you that it currently is not doing so, and giving you detailed reasons why it is not doing so.

BTW, re:"The OS should simply render source color accurately, and have a single definition (across workflows and continents) of how untagged source data is treated, per color space."

Tagging it with the local monitor profile BY DEFINITION guarantees a unique definition of untagged color for each workstation, possibly even for each user on a single one...


--
email@hidden
_______________________________________________
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: untagged RGB data
      • From: John Zimmerer <email@hidden>
References: 
 >Re: untagged RGB data (From: Roberto Michelena <email@hidden>)
 >Re: untagged RGB data (From: John Zimmerer <email@hidden>)
 >Re: untagged RGB data (From: Chris Murphy <email@hidden>)
 >Re: untagged RGB data (From: John Zimmerer <email@hidden>)

  • Prev by Date: Re: untagged RGB data
  • Next by Date: Re: Panther drivers-No color correction?, etc..
  • Previous by thread: Re: Tagged RGB data
  • Next by thread: Re: untagged RGB data
  • Index(es):
    • Date
    • Thread