Skip to main content
Known Participant
July 14, 2012
Answered

Camera Raw 7 CS6 adjustments slow to operate.

  • July 14, 2012
  • 5 replies
  • 27616 views

I have updated to Photoshop CS6 and I'm having a problem with camera raw adjustments.

When loading a batch of images into camera raw all is fine then after a few images have been adjusted everything slows down. Adjustment controls take 1-3 seconds to activate when clicked on.

Using MacPro 2.66 Nehalem 8 core, 32GB RAM, OS 10.6.8, ATI Radeon HD 4870

Any suggestions welcomed.

Have tried:

disabling all plug-ins

Launching Camera Raw from Photoshop and Bridge

Closing all other programs

Adjusting Camera Raw Cache(currently 10gb)

    This topic has been closed for replies.
    Correct answer tahoelight

    Just as a follow up. Do you see slowdowns when working with a single image? You said it is more prominent  when using local adjustments and also while saving, correct? If you can send me exactly the controls you are using it would be very helpful. For example, when using adjusment brush, do you feel it is slower when using the exposure slider, or the noise reduction slider? What controls and values used cause this to slowdown? Do you have masks on or off? Any detailed information will help us reproduce and narrow down the issues reported. If you could share an image with the adjusments and the xmp file will be very helpful. Thank you!!


    Hi Adriana,

    I get slowdowns in the multiple seconds category, sometimes with as little as one image, but always with 10 or more. For example, load 10 nikon d800 raw files, start going down the line adjusting WB, shadow, highlight, blacks, etc, and by the 3rd image, I guarantee you will be having to wait a second or two before you see your adjustments redraw on the main preview image. After that, I usually use the adjustment brush for simple burning,dodging, mostly of faces, or darkening distracting areas. Then the slowdowns really increase. I almost can't use the brush because I have to wait so long for the adjustment to show up on the preview. I have automasking on almost always. But really, just fine tuning your image by nothing more than adjusting WB, Shadows, Highlights, etc and after a few images you will see slowdown. My system specs are above. I agree that the quality is better, but currently I use cs5.1 for all my work except for a couple images that I really wanted but over exposed, then I crank up cs6 and have been able to save them, otherwise I don't use my expensive new software at all because it takes forever! I haven't returned it yet because I hope you will fix it, and also, one image it saved for me was worth the cost of the update, so on that I guess we're even.

    5 replies

    Participating Frequently
    October 4, 2012

    Looks like ACR 7.2 hasn't helped our problem.

    I posted in the photoshop feedback forum here. Screen shots included.

    http://gsfn.us/t/360sq

    Please chime in to make your issue heard.

    Geoff

    Noel Carboni
    Legend
    October 4, 2012

    Seems to me there are two or more aspects to this issue that should be clarified...  Are we talking about one or all of these?

    1. Interactive performance (i.e., how quickly the dialog opens, how well the controls respond). 
       
      For some people apparently the controls operate instantaneously, and for others they see multi-second delays.  Some say the size of Camera Raw dialog clearly affects the interactivity, while others are able to use it interactively at nearly the full size of their monitor.
         
    2. How quickly Camera Raw actually converts (multiple) raw files to images.

      Based on my measurements on a multi-core machine, some aspects of interactive performance have been improved in version 7.2.  But for doing blocks of multiple raw conversions this is pretty much the slowest version yet.  But that's somewhat understandable - people always want more functionality, and assuming that takes extra code (not a bad assumption, as past versions were already heavily optimized) then that will come at a cost in speed.  But is it reasonable?

      Here are my results of doing blocks of conversions with multiple different versions of Camera Raw to test the throughput.  I converted the same set of 50 raw files to 6144 x 4096 pixel .PSD files, striving to keep the output as much the same as possible between versions of Camera Raw.  All tests were done with 64 bit Camera Raw on Windows 7 x64 with the same reasonably modern 12 core machine.  You can easily see the progression of ever slower performance:

        

    -Noel

    Noel Carboni
    Legend
    October 4, 2012

    These will give you a visual idea how the various versions multi-thread (yeah, I know, quite likely more detail than you wanted to know).

    -Noel

    Participating Frequently
    September 28, 2012

    The main reason I use camera raw is for speed, it more closely meets my needs for ease of use when working in a production environment. I find though that 7.1 is slower in a few areas but does seem better in others.

    Creating selective adjustments seems to be offering slightly less lag.  I have although found that if I jump to another image too quickly the adjustment I have just made on the first image has now been added to the new image. In the worse case I am selecting all images the change is made to all images.

    Multicore processing seems to be what is affected here not memory, at least when saving images. Using Activity monitor I am noticing that 7.1 briefly jumps to using over 500% cpu and then quickly drops to 103% and varies very little until all the images has been saved. CS5.1 used to be very efficient in this. I can't tell you how much because I removed it thinking everything would be peachy... It's not.

    While doing adjustments in 7.1, activity monitor is showing over 600% usage GREAT that's what it should be doing.

    This MBP is no slouch, it used to be fast but 7.1 is defineatly slower at saving images so much so that I may have to go back to 5.1

      Model Name:          MacBook Pro

      Model Identifier:          MacBookPro8,3

      Processor Name:          Intel Core i7

      Processor Speed:          2.5 GHz

      Number of Processors:          1

      Total Number of Cores:          4

      L2 Cache (per Core):          256 KB

      L3 Cache:          8 MB

      Memory:          16 GB

    tobylongAuthor
    Known Participant
    September 28, 2012

    I have reverted to Photoshop CS5.1 and have not used CS6 since due to the slow operating of the new camera raw and quite a few other annoyances within Photoshop CS6. I find CS5.1 is altogether a better and quicker program to operate day to day so I would recommend reverting for now.

    Inspiring
    September 28, 2012

    Is ACR 7.1 usable on any current Mac? - It's dog slow on my Mac mini (2.7 i7, AMD graphics, 16Gb ram). Maybe Jeff Schewe is right and we'll have to wait until computer technology catches up with the software...

    Participant
    September 20, 2012

    New ACR still have very very very slow and ineffective engine. My PC have 32 Gb of RAM and when I open 2000 RAW files - I see that 15% of ram used 85% is free. There is lags when make exposure or sharpness tweaks. And red eye remove is bold and unpredictable - and still there is no manual mode for it. And missed manual mode for chromatic aberration - auto is not 100% adequate. And saving is very slow too - and I can even play WorldofTank during it - because it takes only 40 - 60% of my 3770K CPU. ACR 6 saving was much faster - it used 98 99% of CPU and made 4 files in row

    P.S. http://ozerovpaparacci.photofile.ru/ - my galleries if somebody whant to ask why so many foto in time.

    Noel Carboni
    Legend
    September 20, 2012

    Alex, it sounds as if your supercomputer may be waiting on I/O...  What kind of disk subsystem do you have?

    AlexOzerov wrote:


    And missed manual mode for chromatic aberration - auto is not 100% adequate. 

    Agreed.  it's often very good, but there are some times when you can see that a slightly different correction is needed - or you have such an extreme correction that it has confused the algorithm.  Someone has started making unilateral decisions on feature changes and they're leaving functions behind without adequately replacing them.  There is an unspoken expectation that software must always get more functional, not less.

    -Noel

    Participant
    October 2, 2012

    For me its UpSystem not sub -  Transcend SSD SLC 64 Gb just for Win and Program Files. WD 10K rpm 600 Gb for cache and saving foto and games. RAW files on WD 2 TB 7200 RE4. 2 x 3 Tb 5400 for data inside + 1 + 2 Tb WD RE4 in external enclosure for backup - mostly offline. + 4 x 500 Gb NAS. MB Asus on Z77 with native SATA600 support.

    And main problem imho sometthing wrong with multithreading - in CS5 foto saved 4-in-row - now just 1. And it LONGER than 4 files on CS5. At the same system.

    P.S. Im work in IT selling 16 years so own PC is refreshing often.

    Noel Carboni
    Legend
    July 14, 2012

    I just tested the scenario you described (I have a PC, but with similar compute power) and even when I'm adjusting controls with 50 raw files selected the preview is updated virtually instantaneously.  I even went through all 50 individually and adjusted controls specific to them.  It was fast to the last.  Your hardware should definitely be providing you better performance than what you're seeing.

    I have a friend who has told me he has the exact same issue you're reporting (he said "2-3 seconds for control responses" and "worse when working on groups of images"), but with Lightroom on an i7-based PC (Windows 7).  I created a thread some time back about it.  He ended up buying a new high-end video card (switching from nVidia to ATI in the process) and while it the more powerful GPU made a little difference for most everything across the board it specifically did NOT solve this problem.  He said the very latest Lightroom release (just weeks ago) helped a lot, but it still slows down some after a while or under some conditions he can't nail down.  Perhaps this is something Adobe has found and fixed, and we will see it in Camera Raw 7.2.

    I have not yet seen a fix or workaround that directly addresses this for the people who are experiencing it.

    Some additional questions about things that might be pertinent on your system:

    • Are you using a lot of spot adjustments in the images?
    • Do you have lens corrections enabled by default?
    • What camera do you have, specifically?
    • Are there power-saving (vs. performance) settings on your computer (I'm not familiar with Mac) and if so how are they set?

    I think there's a basic problem somewhere in the software that is triggered only under some conditions or on some systems.

    Station_two, I take it your control response in Camera Raw is fluid?

    -Noel

    Participating Frequently
    July 15, 2012

    I have found the same thing. When processing my d800 files the slowdown becomes so severe that I can no longer use ACR 7.1 and fire up photoshop 5.1 to work. Another thing I notice even with my d3s files, is that processing and saving batches of images is much slower. In PS5.1 I can watch as ACR saves 4 images simultaneously. You can see the processing indicator on 4 images at a time and file saving (I usually process to large JPG for client delivery and reprints of weddings)  Yet with the new ACR, it works on one image at a time while processing and saving and according to my stopwatch, is almost 4x slower to process and save a batch of raw images to jpg than ACR 6.7 (or whatever the last update was with cs5.5)

    This is in addition to finding all the slowdowns described above during the adjustment process itself. I can not use this version.

    System info, mac pro, 12 core 3.2 gz 32 mb ram 512 gb ssd drive as scratch disc. I usually process 50-80 images at a go and it is a mix of global adjustments and some spot adjustments in ACR. Using 7.1 and quite unhappy with it. The quality is a bit better, but not as a trade for several extra hours of computer time per wedding.

    station_two
    Inspiring
    July 16, 2012

    With that powerful a system, it's indeed unfortunate you are seeing performance issues. 

    The one thing you might want to try is disabling the intrusive and useless Spotlight.  Above all, make sure it's not trying to index your SSD scratch disk drive and/or your image-file storage drive. 

    OFF TOPIC:

    Is there an industry-wide standard size (in pixels) at which wedding photographers deliver JPEGs that are represented to clients as being "full resolution JPEGs"?  I'm asking because the pro that covered my daughter's wedding a couple of years ago did a super fantastic job but the large-group-pictures JPEGs are a wee bit too small to be printed.  They're only 1280 by 1920 pixels from a Canon EOS 5D.  There were several thousand shots, and I can see why that shoot would have been tough to handle at a larger resolution. Thanks in advance.

    station_two
    Inspiring
    July 14, 2012

    .

    Have you updated the ACR plug-in to version 7.1?

    I'm not familiar with your video card.  How much VRAM is there on it?  Just mentioning this in case that is the bottleneck.  I do not know, obviously.

    tobylongAuthor
    Known Participant
    July 14, 2012

    Yes, it's the latest version.

    The card has 512 MB VRAM.

    station_two
    Inspiring
    July 14, 2012

    I noticed that in neither of your two threads have you mentioned trashing your Photoshop's preferences, which is normally the very first thing to try.

    Hold Down Command+Option+Shift as you launch Photoshop until you see a dialog box allowing you to delete and re-set all your Photoshop's preferences.

    One more thing:  Do you have a dedicated, physically separate (preferably internal) hard drive set up as your primary Photoshop scratch disk?  Is it sufficiently large?  Figure on up to 100 times or more the size of your largest file multiplied by the number of files you have open.

    Even with 32 GB or 64 GB of installed RAM, Photoshop always creates a scratch disk the instant you open an image file or create a new document.