I have revised the post I just made, deleting the original. In the original I was talking about color profiles along with color temperature and display gamma. All of those, along with a calibrated display, are essential to soft proofing print jobs. However, only the color profile is what matters in the current discussion. Only PDF files with an embedded sRGB profile will display correctly in the current versions of Acrobat and Reader. If a PDF file has a different profile such as Adobe RGB or US Web Coated (SWOP) v2, which is CMYK, it will NOT be displayed correctly by Acrobat or Reader. On my screen, the colors are darker, a bit drab, and shifted slightly toward blue. The color values are correct and will print correctly, but they are displayed incorrectly because Acrobat and Reader assume the profile is sRGB. They have lost the capability of looking for an embedded color profile and rendering colors according to that profile. (Even as I type those words, I can't believe such a basic and essential capability has been lost by any publishing program from Adobe, the champion of color management.) The solution should be straightforward: restore the capability of honoring and using embedded color profiles. It sounds like this arcane world of color management may be somewhat unfamiliar to you, so I strongly encourage you to seek input from the people at Adobe who know it cold. They are probably part of the Photoshop group. Chris Cox might be a good starting point. Thanks for chasing this down, Sandeep! ... View more

Come on, guys! (And I'm addressing this to all of us.) Is this really a hill to die on? Chris may not be as forthcoming as we would like, or probably even as he would like, but his credentials are rock solid. Take a look at the names on the Photoshop splash screen. (He has been there for decades, and he has been participating in user forums the whole time.) It seems fairly clear that Chris is constrained by various Adobe policies regarding what he can say or do. He has said as much himself, and it shows in his responses to straightforward reasoning, which have curiously verged on the non sequitur. (For example, "We don't know exactly why Apple's code crashes with CS6 files" in response to the reasoning that borrowing from CS5.5 would solve the problem. We are left to infer that Adobe does not know what to borrow from CS5.5, which may or may not be correct.) It's also a pretty safe bet that the policy makers do not want to deal with a few cranky users about an obscure technical issue. I'm not happy about it either, but let's keep it civil and constructive, and recognize when an impasse has been reached. ... View more

Thanks, Chris. These tend to become circular arguments, but giving you the benefit of the doubt, it sounds like you are more or less acknowledging that it is indeed a haystack and don't know what CS5.5 is doing differently to get the desired result, in spite of Apple's bug. In other words, Adobe has been unable to identify which change or set of changes in CS6 ended up with a result different from CS5.5. (This has been going around long enough that I don't recall whether we know if anyone at Adobe has experienced or recreated the problem.) ... View more

I meant go back to whatever it is that CS5.5 did that worked, and still works. ("Handling file icons" is simply a term for what users see as a result, not necessarily the cause of that result.) I am assuming that restoring a process used in the previous version of Photoshop isn't asking Adobe to search for a needle in a haystack. (Of course, if the problem is known by Adobe to come up in earlier versions, this is moot. But that is not information available to this forum, and we have not seen evidence of it ourselves.) ... View more

Not sure that Cocktail is deleting the DS_Store file. My recommendation was to run Cocktail in its default "Pilot" mode. The DS_Store file is not part of the Pilot mode unless it is buried in the functions that are listed for Pilot. (Cocktail does have a separate function for deleting the DS_Store file, which I have not used. The Pilot mode has been sufficient in itself.) However, some users have reported that Cocktail doesn't solve the problem for them, which might be attributable to configuration differences (such as network vs. single user, etc.). I've only had the problem come up twice in many months, and both times Cocktail resolved it. Some users are clearly more affected by the problem, which leaves me wondering if Adobe could choose to go back to the way CS5.5 and earlier handled icons, while telling Apple "we'll do it the way you say when you fix it." Seems like common sense, but there's sure to be much more to the story, both technical and political, than we'll ever hear about in this forum. ... View more

Hi, Sandeep. Thank you for stepping up! My posts provide what I've determined about the problem, but I'll be happy to help anyway I can. It sounds like this problem does not occur for some or many users, which surprises me. It suggests a configuration problem or conflict. For you to reproduce it in your lab, you need to creating PDF files that do not use a Windows sRGB color profile. (For example, use Adobe RGB or SWOP CMYK profiles.) The problem is even more apparent if you are working at 5000K and a 1.8 gamma ("legacy" Mac, which is still the standard for print). If you can set your system to those values (and calibrate your display), that might be a good experimental base. Rick Meikle Meikle Communications LLC Tigard, Oregon Phone 503-430-8430 ... View more

I haven't checked CMYK values in InDesign CS6, as all colors I use in it are from Photoshop or Illustrator. The CMYK values reported in Acrobat X 10.1.4 Output Preview actually do match the CMYK values in Photoshop CS6 13.0. (The test: a CMYK image created in Photoshop is placed in Illustrator CS6 16.0, and a PDF/X-1a file is generated from there.) Acrobat simply displays colors incorrectly, but does not alter them. (My guess being that it treats all files as Windows sRGB, regardless of the embedded profile.) If an Adobe staffer is monitoring this topic, it sure would be nice if he or she could at least confirm that Adobe is aware of the problem. ... View more

That's a thorough and clever solution, but I'm not sure it addresses the problem described in this topic, and it may introduce a new problem. I use a color managed workflow based on Adobe RGB. Files that I proof in Acrobat Pro X (10.x) have been converted to CMYK (and have the North American Prepress 2 profile). Acrobat appears to ignore the profile. Colors on screen appear relatively darker and muted than they actually are, which might indicate that Acrobat is displaying CMYK values as if they were Windows sRGB values (6500K color temp, 2.2 gamma). The same CMYK colors are displayed correctly within the originating application, such as Photoshop or InDesign. In short, the Acrobat problem has nothing to do with actual sRGB files or files missing a profile, other than apparently treating every file as Windows sRGB. The problem you describe is evident in Dock icons, which are relatively bright and oversaturated in Mountain Lion, just as one would expect when a monitor calibrated for prepress (5000K color temp, 1.8 gamma) is presented with an sRGB file that was generated for 6500K color temp and 2.2 gamma and has no color profile. It may be that Color Faker addresses that problem, but based on your description (any automatic "Convert to sRGB" or "Assign sRGB Profile" commands in applications will no longer work) it may also add a new problem by interfering with preparing profiled sRGB files for web use in Photoshop (Save for Web function). Unless Apple is somehow implicated, which may be the case, the problem in Acrobat is something that should be easy and quick for Adobe to fix. Except they haven't done it, and there is no indication they even acknowledge the problem. ... View more

The PDF/X-1a format is so bulletproof for print jobs that viewing it in Acrobat Pro after coming from InDesign or Illustrator was the final word before sending the job off. It still is, of course, for catching things like white set to overprint in Illustrator (another infuriating dropped ball), for making sure effects have ripped correctly, for viewing color separations (especially whether any spot colors have slipped through), and so on and so forth, except now color accuracy has to be disregarded. That's the supreme irony of the whole situation. After a couple of decades getting there, Adobe finally achieves preflight nirvana, then sabotages it. Users spin their wheels posting on user forums (hoping someone from Adobe will sit up and take notice) and filing bug reports that seem like pushing the Close Door button in an elevator, all the while scrambling to see if there's some way to trick the software into doing its job. I know Adobe has a lot of chaff to sort through to find any wheat, but it has always seemed like they should have a hotline for obvious, easy-to-fix screwups in their products. And that hotline would lead to a patch in the next update, which could be a pretty quick process in their new subscription approach to pushing software out the door. (Yeah, and pigs will fly soon, too. 😉 ... View more

Yup, it's an abomination. This is a perfect example of Adobe dropping the ball that drives me crazy. Even Lion was imperfect, as Acrobat did not sync with the rest of the Creative Suite. It had to be manually set to the correct color management settings. But at least it worked. So well, in fact, that it was more trustworthy for proofing than the originating app. Now it is unusable. This is not a small thing, which makes the failure, especially the fact that it continues, all the more stunning. ... View more

Thanks, Chris. Looks like those who have workarounds will have to stick with them until something gives in a place that this forum can't touch. ... View more

I, for one, truly appreciate your participation in this forum, Chris. You take a lot of heat from frustrated users who may not realize this is just a place where users talk to users. Over the years of my (very) sporadic participation, I've seen you go the extra mile, even though once in awhile I disagreed with your position on an issue. At this point in this topic, it seems to be boiling down to whether this is or isn't a Photoshop CS6 only problem. How do you know it isn't? I haven't seen any other app, including earlier versions of Photoshop, fingered. But you have vastly greater input than us users. Are you constrained from naming names? (Even one? Like another Adobe app?) ... View more

I believe (hope) that creds get you taken seriously by developers! On that level, creds are priceless. My creds are taking a beating, though. I mistakenly associated your long post about the "file has changed" problem with the missing icon problem. ("I then installed one of the CS items mentioned above and any of its updates. Immediately afterwards, icons would not be created for all files; a QuickTime function." Plus a couple other references to creating or not creating icons.) It may all be related, which I presume is why you brought it to this topic. I too experience the irritating "file has changed" message from time to time, but as a standalone user I just ignore and dismiss it. I visited that topic to learn about it but don't recall posting to it. That illustrates my point about how many users with a given problem may not make it known to the developer. At no time was I trying to say that all or most users have or don't have the missing icon problem. Only that it is affecting a sizable number of users, of which it is reasonable to assume that only a portion, probably a small portion, are participating in the forum. At the same time, if the problem only comes up in column view, for example, users who don't use column view won't discover the problem. There are lots of ways to argue for and against populations with or without the problem, but that is beside the point when there are enough users with it. I'm still curious to know whether any other application has verifiably demonstrated the same icon creation problem that affects many users of Photoshop CS6. To my way of thinking, this is a key step in pinpointing the problem. ... View more

I just did a quick search on Google for "Apple missing icons," "Apple missing icons open save," "Mac missing icons," and a couple other variations. Maybe I need to try other keywords, but I only found the Photoshop CS6 problem (a single result) and some issues with iPad and Final Cut Pro which appear unrelated, plus other "oddball" icon problems at the system level (Dock, Preferences, iTunes, AirPlay, etc.) that also appear unrelated. In fact, the most striking thing about the searches was the absence of issues, especially during 2012, and how what is there has nothing to do with the problem being discussed in this topic (except for the Photoshop CS6 results, of course). Anyone else finding evidence of other apps having the same problem? While we're at it, why don't Illustrator and InDesign (among other CS apps) have the same problem? ... View more

This has become such a rambling topic that I don't recall (might have missed) a post about other apps with the same problem. Can anyone specifically identify such apps? (And can we rule out that the users in such cases don't have some other problem?) Finally, even if "most" users do not see the Photoshop CS6 icon problem, how many of them have simply not noticed it, don't care, or aren't saying anything? If there is a percentage of users, possibly a very large percentage, who don't have the problem, that would suggest there is conflict in the system configuration of the users who do have the problem. Except that Kurt ruled it out with his exhaustive testing of virgin system installations. A question that occurs to me is: How is it that no one at Adobe is encountering the problem? (And is that really true?) ... View more

The missing icon problem finally popped up again on my system last week, after a 2 month absence. It sounds like you are on to something, Kurt. (And if I recall correctly, you are also a color display/color management guru non pareil, which means tons of cred.) Running Disk Warrior, then Cocktail (on Pilot) again corrected the problem for me. (The latter being the probable "fixer," though both repair permissions. I don't have the opportunity to invest more time.) Upgraded to Mountain Lion subsquently without problem (other than a font smoothing issue resolved by turning it off in General System Prefs and restarting). Sheer logic would point the finger at something Adobe did in CS6, even if Apple is also implicated, as CS5 and no other apps have a problem with icons. (I skipped 5.5.) So far, Chris has not explained how that logic might be faulty, but hopefully your tests have Adobe looking at new possibilities. Thanks for the intensive effort! ... View more

FWIW my "fix" using Cocktail (default Pilot mode) was on the startup drive. (Same with Disk Warrior.) And mine is a standalone Mac Pro 2010 (not part of a local network). There are two other 1TB drives identical to the startup drive in the Mac Pro. One is for Time Machine, the other is a Super Duper clone (from which I run DW). I use the Finder and Open/Save in column view extensively every day, and the icon problem has not returned (over a month now). I also use Default Folder for most navigation in Open/Save, which is probably not relevant but does interact a great deal with Open/Save. ... View more

I have not upgraded to Mountain Lion yet--I usually wait for the first update to a new cat before installing it--but the icon problem has not returned since running Cocktail on Pilot per my earlier post. That specifically includes column view, which I use nearly 100% of the time. If Cocktail didn't do it for you, I suggest rebuilding your disk directory using Disk Utility (or Disk Warrior, if you have it), then running Cocktail on Pilot, then restarting your Mac. If that doesn't get it done, you'll need to look for some other solution. ... View more

A true techy can answer this better than I can. All Disk Warrior does is repair any errors in the hard drive directory, essentially the filing system for the computer, so it knows what files are stored where (among other things). It's like Apple's Disk Utility app, but historically has been more thorough. Directory errors can lead to various odd behavior by the system or apps at different times. You may or may not have directory errors, or at least any that matter much, and most users never repair or rebuild their directory (and most will use Disk Utility if they do), but that's a separate topic from this one. Just run Cocktail on Pilot and see if the icon problem is fixed. I recommend restarting the system immediately after running Cocktail. (I only mentioned Disk Warrior because I ran both it and Cocktail as part of my standard troubleshooting routine. Better would have been to see if anyone said Cocktail didn't fix the problem before mentioning Disk Warrior.) ... View more

You do not need to mess with the DS STORE files or any other settings. Just go to Pilot and click run. (I should add that I did run Disk Warrior before Cocktail when I solved the problem. I doubt that rebuilding the hard drive directory was the solution--the problems fixed were too few and more-or-less routine. What Cocktail does is more relevant to what the earlier posts were saying.) ... View more

I'm not that techy, either, Marc. Cocktail is a 3rd party utility that does much of the same stuff that Onyx and others do. It handles a number of "housekeeping" chores. To digress, I periodically run Disk Warrior (rebuilds disk directory) followed by Cocktail, usually before updating system software, and that seems to keep things running smoothly. (Little errors and problems gradually crop over time, especially if you create lots of files and are a robust filer, unlike most consumers who leave it to the system.) Anyway, Cocktail has a Pilot mode that by default runs what most of us will ever need done. It's simpler than the more involved ways to get to the same end. (I have no connection with Cocktail other than being a satisfied user.) You'll find it easily in a search. Don't remember if there's a free version, or how much the paid version costs, but it isn't much. The Pilot function is easy to find, and you just click run. ... View more

FWIW, running Cocktail in its default Pilot mode (which includes emptying caches) corrected the problem on my system. On a purely logical level, even if the fault is with Apple, there must be something Photoshop CS6 is doing differently than CS5 (or any other app), or it wouldn't be the only app with the problem. ... View more

FWIW, Daring Fireball (John Gruber) provided a link to this article by Pierre Igot that points the finger at dubious decisions by Apple in their new autosave scheme, which indicts Lion's file version management: http://www.betalogue.com/2012/03/27/lion-autosave-2/ ... View more

(A side comment first that these forums would benefit from being able to make a general reply, rather than to a specific post...unless I'm missing it somewhere.) Since my earlier post confirming that the "Suitcase fix" resolved the problem, it has cropped up again, but only rarely. Given the widespread nature of the problem affecting different users with different configurations, it appears that the Photoshop behavior described by Chris can be triggered by any number of scenarios. Adobe may not consider it to be a problem, and in fact may view it as a feature, even though for many users it is nothing but a nuisance. It appears to be something we have to live with until such time that Adobe either improves or fixes the "feature" and/or makes it something you can turn off. That's my pragmatic take on it at this point, with the real purpose of this post being to confirm that the Suitcase fix is not a complete fix, nor apparently even close to being one. It just removes one of the more common triggers. ... View more

Just now decided to see what might be causing this warning (after recently upgrading to Lion). The solution posted on Aug 30 by lem0nayde nailed it for me. I did not thoroughly read all the posts, but many thanks to "lem" and to all who contributed, especially Chris, who took a lot of heat, mostly unwarranted. Adobe cannot check for everything, especially 3rd party software, though you would expect that they would be using Suitcase themselves or at least make it part of their testing because so many of their customers use it. Also, I am a single user on a single system, and there are probably a fair number of us, so if this "feature" is to warn that changes have been made to a file by a different user on the same network, I would hope that Adobe would either be able to detect when the warning is not relevant or allow a single user to opt out. ... View more

Now that's pretty cool, Peter (and Dave)! For those using CS5, the Scripts panel is located at Window > Utilities > Scripts (or Option-Command-F11). Another way to arrive at the number to use in the script is to divide the pixels/inch value shown for "Use system setting"  in Acrobat Pro's Page Display preference by 72. (Then multiply by 100 to get the needed percentage. Or both steps can be reduced to dividing by .72 as a single step.) In my case, I needed to fudge the result slightly upward. Don't know why it wasn't exact, but it was very close to start with. However, despite this clever workaround, the feature request remains valid. In fact, the clunkiness of the script solution, and the time that has passed without building the capability into InDesign, underscores the need to just do it. ... View more

Hi, John. Your exercise carried you to the gist of this feature request. There isn't a way to do what you want in InDesign, so all you can do is add your voice to the request. In the meantime, you can make a PDF file from your InDesign document and view it at 100% in Acrobat Pro. The "Page Display" pref in Acrobat Pro needs to be set to "Use system setting". (This should also show you the ppi you calculated, but without having to calculate it yourself. If for some reason it doesn't show what you calculated--or at least something very close to it--you can enter the number yourself.) Of course, it would be far superior to be able to view your InDesign file at "true" actual size as you work on it. Hence, the feature request. ... View more

Thanks, Peter. I was unaware of this avenue. I will put it to good (and judicious) use! Rick ... View more

I'm finally checking in a few months after posting this request. As the "OP", I can say that this "question"--a curious description for a feature request--has NOT been "answered." "Jongware" is correct. Unfortunately, the lack of visible support for the feature request leaves little hope that the InDesign team will seriously consider it. Even experienced designers often struggle with the concepts of resolution and dimension and "actual size." Perhaps that includes members of the InDesign team. (I wonder how many users who can nod their head with what I've suggested even visit this forum in the first place. Once upon a time, the Adobe user forums were frequented by gurus and even the occasional Adobe participant.) The merits of this particular request are inarguable, but if it comes down to "popular demand," its prospects are dim. What is amazing is that someone on the Acrobat team not only appreciates the concept, but actually managed to get it implemented. Well, if anyone who reads this request "gets it," now would be a good time to chip in with "I agree." ... View more