Re: Colorsync-users Digest, Vol 13, Issue 116
Andrew, Can you explain what Adobe did that excluded Adobe 1998 as a profile when you choose Photoshop Manages Colors? i think this has been true since CS5. thanks in advance! Best Wishes, Mark Nelson Welcome to the Precision Digital Negatives Home! <http://www.precisiondigitalnegatives.com/> PDNPrint Forum at Yahoo Groups <https://groups.yahoo.com/neo/groups/PDNPrint/info> Mark I. Nelson Photography - Welcome <http://www.markinelsonphoto.com/> CURVE CALCULATOR III FOR THE MAC NOW AVAILABLE!!!!
On May 23, 2016, at 2:00 PM, colorsync-users-request@lists.apple.com wrote:
Message: 1 Date: Mon, 23 May 2016 10:55:58 -0600 From: Andrew Rodney <andrew@digitaldog.net <mailto:andrew@digitaldog.net>> To: ColorSync List <colorsync-users@lists.apple.com <mailto:colorsync-users@lists.apple.com>> Subject: Re: Custom profiles not showing up in Photoshop's Print Dialog Message-ID: <FC44D2F5-BED0-4BEB-AD77-9BE8C7C96689@digitaldog.net <mailto:FC44D2F5-BED0-4BEB-AD77-9BE8C7C96689@digitaldog.net>> Content-Type: text/plain; charset=us-ascii
All Photoshop did (through engineer Dave P.) was filter the ICC profiles such that the manufacturers profiles (say Epson) would appear at the top of the dropdown once a printer was selected. I don't think Adobe did anything further to allow or disallow illegal characters to be used.
IMHO, the best approach it to use accepted characters for naming ICC profiles that are accepted for multiple operating systems.
Andrew Rodney http://www.digitaldog.net/ <http://www.digitaldog.net/>
I see sRGB, ROMM RGB, Wide Gamut RGB etc. I moved Adobe RGB (1998) from the 'recommended' folder Adobe creates to my user folder, I don't see it. ProPhoto RGB doesn't show up either. So what I did in Photoshop's Color Settings is load Adobe RGB (1998) as the working space, then I clicked on that dropdown and used 'Save RGB...' and gave it a new name (ARAdobe RGB (1998)) and made sure in the ColorSync Utility that all three naming fields (ASCII, UniCode, Mac Script) had this new name. By default, PS doesn't do this. Save. NOW ARAdobe RGB (1998) shows up in Print! My suspicion is some of the RGB working spaces are filtered out by name. Andrew Rodney http://www.digitaldog.net/
On May 23, 2016, at 2:18 PM, Nelson Mark <ender100@aol.com> wrote:
Andrew,
Can you explain what Adobe did that excluded Adobe 1998 as a profile when you choose Photoshop Manages Colors? i think this has been true since CS5.
That’s interesting! Can you confirm if the null transform trick works with this? Scott Martin www.on-sight.com
On May 23, 2016, at 3:38 PM, Andrew Rodney <andrew@digitaldog.net> wrote:
So what I did in Photoshop's Color Settings is load Adobe RGB (1998) as the working space, then I clicked on that dropdown and used 'Save RGB...' and gave it a new name (ARAdobe RGB (1998)) and made sure in the ColorSync Utility that all three naming fields (ASCII, UniCode, Mac Script) had this new name. By default, PS doesn't do this. Save.
NOW ARAdobe RGB (1998) shows up in Print!
Yes, it works. Andrew Rodney http://www.digitaldog.net/
On May 23, 2016, at 2:58 PM, Scott Martin <scott@on-sight.com> wrote:
That’s interesting! Can you confirm if the null transform trick works with this?
Scott Martin www.on-sight.com
On May 23, 2016, at 3:38 PM, Andrew Rodney <andrew@digitaldog.net> wrote:
So what I did in Photoshop's Color Settings is load Adobe RGB (1998) as the working space, then I clicked on that dropdown and used 'Save RGB...' and gave it a new name (ARAdobe RGB (1998)) and made sure in the ColorSync Utility that all three naming fields (ASCII, UniCode, Mac Script) had this new name. By default, PS doesn't do this. Save.
NOW ARAdobe RGB (1998) shows up in Print!
Too cool! And does your ColorSync Utility crash as often as mine does? I use the heck out of it and it crashes several times a day curiously… Scott Martin www.on-sight.com
On May 23, 2016, at 4:59 PM, Andrew Rodney <andrew@digitaldog.net> wrote:
Yes, it works.
Andrew Rodney http://www.digitaldog.net/
On May 23, 2016, at 2:58 PM, Scott Martin <scott@on-sight.com> wrote:
That’s interesting! Can you confirm if the null transform trick works with this?
Scott Martin www.on-sight.com
On May 23, 2016, at 3:38 PM, Andrew Rodney <andrew@digitaldog.net> wrote:
So what I did in Photoshop's Color Settings is load Adobe RGB (1998) as the working space, then I clicked on that dropdown and used 'Save RGB...' and gave it a new name (ARAdobe RGB (1998)) and made sure in the ColorSync Utility that all three naming fields (ASCII, UniCode, Mac Script) had this new name. By default, PS doesn't do this. Save.
NOW ARAdobe RGB (1998) shows up in Print!
It does not crash. I do recall this happening awhile ago when moving from 'pane to pane'. Andrew Rodney http://www.digitaldog.net/
On May 23, 2016, at 4:24 PM, scott@on-sight.com wrote:
Too cool! And does your ColorSync Utility crash as often as mine does? I use the heck out of it and it crashes several times a day curiously…
Scott Martin www.on-sight.com
Digest users, please change your subject lines when replying.
It’s been true since CS6. I know a number of people that keep CS5 around for this reason. They exclude AdobeRGB so that people don’t try to continue using the null transform trick that so many of us relied upon in CS5. Scott Martin www.on-sight.com
Can you explain what Adobe did that excluded Adobe 1998 as a profile when you choose Photoshop Manages Colors? i think this has been true since CS5.
participants (5)
-
Andrew Rodney
-
Nelson Mark
-
Pylant, Brian
-
Scott Martin
-
scott＠on-sight.com