I suspect you have a different issue. The issue reported in this discussion does not affect startup. If you were experiencing this issue, it would always be triggered by selecting "Use system setting". And always resolved by selecting "Custom resolution". As for your situation, I share your frustration. InDesign can take minutes to startup after restarting the system, and Illustrator is also a slowpoke. Photoshop isn't quite as slow. However, quitting and restarting those apps (without restarting the system) is usually pretty quick. Opposite of your experience, Acrobat always starts up pretty quick for me. Go figure, right? ... View more

Thanks for your reply, Akanchha. I have emailed an example PDF file and a screen capture video to the email address provided separately (outside of the forum). The files are 22MB and 151 MB, so Dropbox links were provided. Oddly, the screen capture movie only shows a normal cursor during the 20-30 second delay after any operation (such as going from page 1 to page 2, switching to the Finder and back, etc.). In reality, after every operation a spinning beachball icon appears 3-10 seconds into the delay, and no other operation is possible until the beachball goes away. I attempted each operation (moving from page 1 to page 2 and back, switching to the Finder and back) as quickly as possible! Each time you see the cursor hanging around on the page, I am waiting for the beachball to go away. You should be able to reproduce the slowdown by changing the Page Display preference to "Use system setting" then opening the PDF file. (The value for the system setting probably should not be allowed to match the value for "Custom resolution". Operations are nearly instantaneous when the Page Display preference is set to "Custom resolution".) Finally, my installation is at version 19.010.20098. ... View more

Refreshing this thread, Acrobat Pro DC (CC 2019) does not behave as Adobe describes in their online user guide (link below), which says "To turn off automatic OCR: In the right pane, clear the Recognize text check box. From next time [sic], Acrobat won't automatically run OCR and convert a scanned document to editable text." Acrobat honors that setting for each subsequent file opened, but only until quitting Acrobat. Upon reopening Acrobat, the setting is lost and when going to the Edit PDF pane in the first opened PDF file, Acrobat always recognizes text on the first page and turns on the "Recognize Text" check box. This needs to either be fixed or an option provided to make it stick. https://helpx.adobe.com/acrobat/using/edit-scanned-pdfs.html ... View more

I don't have Reader installed, but if it has a page display preference similar to Acrobat Pro (which I would think it does) you can try selecting Custom Resolution (at whatever pixels/inch it defaults to) instead of Use System Setting. If that doesn't help, the problem you are experiencing is something else. Good luck! ... View more

When I first reported this problem, my installation of Acrobat DC was stuck on version 18.11.20040.280397. The Creative Cloud app thought it was fully updated, and it generated an error message when trying to delete Acrobat DC. (Even after managing to delete Acrobat DC, the CC app still though it was installed and updated.) Acrobat DC is finally installed and updated to version 19.10.20069.311970, thanks to some brilliant troubleshooting from Adobe’s online chat service. (It took 3 reps to forward me to the 4th rep, who actually got it done, and it took about a half hour of time in a computer sharing session to resolve. But I was very impressed. And I was left shaking my head at the inscrutable convolutions of the Creative Cloud installation, activation, uninstallation, etc.) I relate all of this because I can now state that the current version of Acrobat DC is identical to the 18.x version in that using the “System resolution” preference for “Page Display” still causes an extreme slowdown of Acrobat operations. The problem still disappears completely when using “Custom resolution” instead. If any of the Adobe staff who tried to address this problem are still receptive, I can provide a PDF file that should let them reproduce the problem for themselves. I can also provide a screen capture movie of it. (I get the feeling that the version problem derailed them.) ... View more

When I first reported this problem, my installation of Acrobat DC was stuck on version 18.11.20040.280397. The Creative Cloud app thought it was fully updated, and it generated an error message when trying to delete Acrobat DC. (Even after managing to delete Acrobat DC, the CC app still though it was installed and updated.) Acrobat DC is finally installed and updated to version 19.10.20069.311970, thanks to some brilliant troubleshooting from Adobe’s online chat service. (It took 3 reps to forward me to the 4th rep, who actually got it done, and it took about a half hour of time in a computer sharing session to resolve. But I was very impressed. And I was left shaking my head at the inscrutable convolutions of the Creative Cloud installation, activation, uninstallation, etc.) I relate all of this because I can now state that the current version of Acrobat DC is identical to the 18.x version in that using the “System resolution” preference for “Page Display” still causes an extreme slowdown of Acrobat operations. The problem still disappears completely when using “Custom resolution” instead. If any of the Adobe staff who tried to address this problem are still receptive, I can provide a PDF file that should let them reproduce the problem for themselves. I can also provide a screen capture movie of it. (I get the feeling that the version problem derailed them.) ... View more

I'm the originator of this topic. The problem very much remains some 2 years later. I'm running CC 2019 (Acrobat build 18.11.20040.280397) and Mojave 10.14 on a Mac Pro (mid 2010). Trashing the pref files noted in Rahul's post made no difference (quitting Acrobat before and restarting after). In fact, there was no "Adobe WebCapture Cookies" or distiller prefs or Acrobat folder. Just the plist and three plist "lockfiles" were trashed. The problem was quite obvious with a 2 page PDF file from a 3rd party data sheet (for a thermal imaging product). It was sluggish to scroll, moving in herky jerk jumps after briefly stalling. Using "Custom resolution" is still the way to avoid it. It is disappointing that Adobe could not resolve this easily reproducible problem given so much time. Apparently, there are very few users who are bothered by this, or it would have received more attention. I have given up on being able to see PDF files at actual size on my screen (same size as when printed). C'est la vie! ... View more

A follow up note: Single page files don't suffer much from "Use system setting", but multipage files choke, especially if there are a lot of pages (e.g., dozens). It makes me wonder if Acrobat is rendering every object on every page at "Use system setting", instead of just the current page. ... View more

This will also be posted as a new discussion. Found the specific cause of the slowdown (spinning beach ball for about 15 seconds on EVERY click, including accessing Preferences menu and settings within it): Choosing "Page Display > Resoution > Use system setting", causes the problem. Choosing "Custom resolution" solves the problem. Perhaps there are other causes, but this is clearly a defect in the code. (Incidentally, "Use system setting" is important because it allows pages viewed at 100% to also match the printed size...or in other words, 8.5" x 11" on screen matches an 8.5" x 11" paper page.) In case this problem only affects certain systems and configurations, I am running a mid-2010 Mac Pro (quad core, 48GB RAM, 2TB SSD startup in PCIe slot), High Sierra 10.13 (though the problem was present in previous system releases), Adobe CC 2017 (including current version Acrobat DC), NEC PA271W display. ... View more

Nice! Colors now display correctly in Adobe Acrobat XI 11.0.06 (including Print Production>Output Preview) and Adobe Reader X 10.1.9. Thanks, Deepak, for seeing this through. (Some users may have technical issues that extend beyond this specific problem of corrrectly using the the display profile.) ... View more

Hello again, Sandeep. I think I may have encountered this same problem (ignoring the user's display profile) in the Photoshop CC and CS6 print preview. If so, it may be a helpful clue. This is my post in the Photoshop forum... http://forums.adobe.com/thread/1272047?tstart=0 ... View more

Well, the plot gets thicker. I reported that the fix worked for me, but I didn't go far enough in testing it. I can now report that PDF files saved as "High Quality" display correctly in Acrobat 11.0.03 until viewed in Output Preview, at which point they darken considerably. Exiting Output Preview (file remains open) restores correct display of colors. However, PDF files saved as "PDF/X-1a" are dispayed with the darker colors at all times, regardless of Output Preview. (I should add that I tested files originating in InDesign CS6 & CC, as well as Illustrator CS6 & CC. The same result was obtained in all cases, including files containing only RGB graphics or only CMYK graphics.) At this point, the problem appears to be a coding error, perhaps as a result of switching from Carbon to Cocoa. Hopefully, Adobe will provide Sandeep, et al, with the priority and resources needed to unravel it before too much longer. ... View more

Hi, Dave. I'm using 11.0.03. How do you execute a "major nudge"? I've tried the usual modifier keys with the arrows to no effect. (And, oddly, it's not turning up in a search.) Personally, I would rather default to paste in place with NO offset. If it lands on top of something else, it can be major nudged at that point, then major nudged back. Oh well. ... View more

The fix absolutely works for me (and others). The problem in this topic is limited to this one thing: Acrobat was failing to use the correct display profile (apparently defaulting to a generic profile based on sRGB/6500K/2.2gamma). The question now is whether that is still true for some users (11.0.03 only). I have noticed that sometimes Acrobat is very sluggish about using the correct profile, taking several seconds to switch to it (for example, after syncing to web/internet from print or back again). But that is probably just muddying the water. If the fix is in fact failing for some users, there's not much those users can do but report it. Otherwise, color management troubleshooting is in order, which can be a nasty piece of business. Questions include: What is your display and how is it calibrated? If you're on a Mac is that custom display profile selected in System Prefs>Displays>Color? Does Bridge show that your suite is synced? And so on. If you provide detailed information of that sort, perhaps another user can spot an error, or at the very least it may help Sandeep figure out what's going on. ... View more

The fix appears to work only with 11.0.03 at this time. For those using that version who still report a problem, either the fix fails for some users or they have some other problem in their color management setup (display not accurately calibrated, system not set to use calibrated display profile, CS suite not color synced, etc.). Not sure how the fix would work for some and not others. ... View more

Hi, Sandeep. Acrobat 11.0.3 appears to have fixed the problem! (Thank you!) However, Adobe Reader 10.1.7 still has the problem. Given that, I would guess the browser plug-in remains unfixed as well. I did not check Acrobat 10.x, as I do not have it installed. Hopefully, the fix will migrate to whatever still needs it. ... View more

Thanks for getting back to us, Sandeep. I hope the fix will include the PDF viewer plugin for Safari (and other browsers). I'm sure your guys are on top of this, but I mention it just in case. ... View more

It would seem to me that the best way to get a handle on it would be for someone from Adobe/Apple to go look at a problem system. (Or have it come to them.) This whole topic is like the joke about the blind men each describing the part of the elephant they have hold of. Adobe/Apple can't recreate the problem on their own systems, so that's where it stops. Imagine if that's how auto mechanics worked? (OK, maybe some do, but you get the point.) I suspect the bigger problem is that there just aren't enough affected users to warrant doing more. The best policy for a user caught in this predicament is to find a workaround (or simply put up with it) and be patient while the Mac OS and Adobe CS both evolve through time. That approach pisses off some users who only see their own point of view. What's interesting is that no one workaround works for everyone--perhaps with the exception of reinstalling the OS, which I have not needed to do. (It's only come up twice for me and Cocktail as part of my standard troubleshooting routine resolved both instances.) I don't recall a problem that was so elusive and hard to pin down in over 25 years of making my living on a Mac. (Well, maybe color management before Adobe allowed CMYK values to be preserved.) Still seems very odd that Adobe can't make Photoshop CS6 do the same thing that CS5 or other CS apps do. (Chris Cox's assertions about other apps having the problem notwithstanding. It needs some substantiation, especially with respect to other or older CS apps.) ... View more

Versions 10.1.5 and 11.0.01 do not fix the problem. (It would have been surprising to see the fix this soon.) As Ian noted, the problem is that the current version of Acrobat (and Reader) fail to use the display profile set in System Preferences > Displays > Color to correctly display the colors in a PDF file. (There's probably a similar scenario for Windows users.) Fortunately, the problem does not affect CMYK print output. (Don't know if Acrobat also ignores printer profiles for outputting RGB colors.) The more your display profile deviates from whatever Acrobat is using to display colors--my guess is it's the default color workflow settings for Windows and recent Macs (sRGB/6500K/2.2 gamma)--the greater difference you will see between your PDF files and the originating files. My guess is that most users who stick with a system's default display settings (e.g., an iMac out of the box) won't see much or any difference. Whether or not the display profile problem affects you, color management problems may also be in play. If so, the two most obvious things to do are 1) calibrate your display and/or 2) synchronize your Creative Suite on the appropriate color workflow. In my experience, the only effective way to calibrate a display is with a display calibration system that measures what your display puts out (with some kind of sensor that hangs on the screen) and builds a custom display profile that adjusts the display output to be more accurate. Anything short of that is unlikely to get the job done. Ironically, until the display profile problem is fixed, calibrating your display may amplify the on screen color differences between your PDFs and originating files, especially if you calibrate for traditional print settings (Adobe RGB/5000K/1.8 gamma). That's because the display profile will be ignored by Acrobat. ... View more

Nice job, Sandeep! I'm glad you (or someone at Adobe) saw this discussion and recognized it had some merit. And I'm grateful for your diligence in seeing it through! ... View more

I'm going to shut up now. (Really.) But I just looked back at all my lengthy posts this morning and realized that I should summarize by saying I think I was wrong initially, when I thought Acrobat was ignoring embedded color profiles. That may still need to be verified, but more experimentation on my part now suggests it is the display profile that is being ignored. Also, Mountain Lion has a defect that may underly the problem. My earliest posts amounted to red herrings. ... View more

Yes it is a head banger. Color has become much more consistent out of the box since the early days, but it isn't good enough if you want your screen to show you what will come off the printing press with any real accuracy. My office has north facing windows, neutral walls, and 5000K lighting, plus my display sits on the east wall and has a hood, all in support of getting color right. The problem is that there are so many settings and variables in so many places that when something goes wrong it can be very difficult to isolate, especially when it involves an application that is out of your control. Ironically, as you note, people who should know better are more clueless than ever. With the web taking over from print, a lot of them don't even know that color management exists and why it matters, much less what to do about it. I have studied and applied it for many years, and I'm still banging my head at times. Like this one. The trend is painfully obvious, though. The world has become an sRGB, 6500K, 2.2 gamma place, which does not work very well for soft proofing in print, but meets the masses' needs without them having to deal with it. Or even be aware of it. For now I am optimistic that with Sandeep's help we might be able to forestall color management entropy, at least in Acrobat! ... View more

One more thing...Mountain Lion has a defect that renders some things without regard to display profile. (This is documented in various forums online.) For example, the Dock icons are bright, vivid, almost garish on my screen. It's what web files I prepare look like when a 3rd party resaves them, which strips out the embedded color profile. (I always have to go back to them and tell them it's OK to rename the file, but not to resave it.) Those files look fine on a Windows machine (and also Macs) running sRGB at 6500K and 2.2 gamma, but without the profile they are bright, vivid, almost garish on a Mac at 5000K and 1.8 gamma. This is more or less the inverse of what is happening in Acrobat and Reader, which is why my first thought was that color profiles were being ignored. But per my last posting it may be that the display profile is being ignored. Anyway, Acrobat and Reader might be hitching a ride on Mountain Lion's defect. Or it may be unrelated, but I thought it was worth mentioning. ... View more

If you are using a calibrated display, the calibration software should set your Displays>Color profile for you. Mine is set to "PA271W 0610738UA 2012-11-14 14-57", which is the name of the profile created by the calibration software. This is where color temperature, gamma, and color corrections are stored (in my case for prepress work at 5000K and 1.8 gamma). Sorry about this long-winded posting, but I think the last few paragraphs may help make some progress, and I must first digress to get to them... Control of color profiles embedded in my PDF files is done in Adobe Creative Suite (verson 6 at this time). I use Bridge to synchronize the suite. North American Web/Internet is for files going to the web and I apply sRGB to those files when opening them (if they aren't already sRGB). North American Prepress 2 is for files going to a printing press, and I apply Adobe RGB to files when opening them (if they aren't already Adobe RGB). Files for the web are saved using Photoshop's "Save for Web..." command, which is set to sRGB and uses the Document Profile for a preview. Files for print are converted to CMYK and placed in InDesign or Illustrator, where they are saved as PDF/X-1a files, which are CMYK and those values are preserved (not color managed). I should note that before that point, during client proofs, the files are placed as Adobe RGB. They are replaced by CMYK images before making a PDF/X-1a file for the printing press. Either way, the files display correctly and identically (except for any color gamut differences) regardless of color mode or application. (This is color management working correctly.) Except for Acrobat and Reader. Until CS6, all PDF files would be displayed by Acrobat identically to how they appeared in the originating application (Photoshop, Illustrator, InDesign). Now all PDF files are darker, more drab, and shifted slightly toward blue. Here's the weird thing. No matter what I do, even if I start with an sRGB file and save it as a Photoshop PDF using the Save for Web command, so it has been sRGB throughout the process, when the PDF file is viewed in Acrobat or Reader it is darker, more drab, and shifted slightly toward blue. My first hypothesis was that Acrobat and Reader were applying sRGB to everything. But that appears to be wrong. Now I'm thinking that it's my calibrated display profile that is being ignored. And since it is calibrated for 5000K and 1.8 gamma, that is what explains the big shift in darkness, vividness, and color. It may be that the display profile, not the embedded color profile, is all that matters! If so, a good experiment would be to calibrate one of your displays for 5000K and 1.8 gamma. If Acrobat and Reader are ignoring the display profile, you should see a very obvious difference in displayed PDF files compared to displays using 6500K and 2.2 gamma (which is just about everyone these days, except for publishing professionals who do exacting print work). Sheesh! ... View more

As a follow up, the results of your experiments so far have been consistent with a failure to use embedded color profiles. Color temperature and display gamma should only make a difference if you take the file to another computer or display, or change your display settings. So for the purpose of experimentation, you can probably ignore color temp and gamma as long as you are staying on the same system without making changes to its display. If you just change the embedded color profile, sRGB files show look "right." Other profiles should deviate to some degree, but they shouldn't if Acrobat and Reader are displaying them correctly. In all cases the actual color values in the file will remain unchanged. Only how they are displayed will vary. Also please see the next post regarding how profiles are set. ... View more

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