Skip navigation

Camera Raw 7 CS6 adjustments slow to operate.

Jul 14, 2012 2:04 AM

  Latest reply: CanJam, Oct 19, 2012 7:36 AM
Replies 1 2 Previous Next
  • Currently Being Moderated
    Sep 20, 2012 5:18 AM   in reply to tobylong

    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.

     
    |
    Mark as:
  • Noel Carboni
    21,003 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 20, 2012 8:02 AM   in reply to AlexOzerov

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 27, 2012 11:10 PM   in reply to tobylong

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Sep 28, 2012 3:43 PM   in reply to tobylong

    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...

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 28, 2012 9:41 PM   in reply to elliot-n

    elliot-n wrote:

     

    Is ACR 7.1 usable on any current Mac? ...

     

     

    Ironically, ACR 7.1 and 7.2RC1 work well in my ill-equipped, dedicated Photoshop 13.0.1 Mac-Intel system, a 2007 MacBook laptop, literally rescued from the trash, with 4 GB of RAM and an external FireWire scratch disk drive.  Go figure.  The only other application I run on that machine is Text Edit.  Spotlight and Dashboard are permanently disabled.

     

    I do run Snow Leopard 10.6.8 and have stayed away from Lion and Mountain Poop. 

     
    |
    Mark as:
  • Noel Carboni
    21,003 posts
    Dec 23, 2006
    Currently Being Moderated
    Sep 29, 2012 8:48 AM   in reply to tobylong

    tobylong wrote:

     

    Nehalem Mac Pro with 33 gb RAM

     

    Do you get that with 3 x 11 GB DIMMs?    I assume it's a typo.

     

    In all seriousness, Adobe:  Why haven't you continued to address this issue? 

     

    Adriana commented early on, but then....   Nothing. 

     

    A "we've reproduced it" would be great, but even a "we hear you and we're continuing to look into it" would be welcome, I'm sure, to the folks who are unable to use the software until you fix it..

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 29, 2012 9:36 AM   in reply to Noel Carboni

    I assume Adobe has allocated more resources to their subscription license (i.e., more/new features, more income), and don't have enough time to address existing problems with the software that people already paid for.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 2, 2012 5:33 AM   in reply to Noel Carboni

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 4, 2012 9:42 AM   in reply to tobylong

    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

     
    |
    Mark as:
  • Noel Carboni
    21,003 posts
    Dec 23, 2006
    Currently Being Moderated
    Oct 4, 2012 12:41 PM   in reply to CanJam

    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:

     

     

         EverSlower.png

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    21,003 posts
    Dec 23, 2006
    Currently Being Moderated
    Oct 4, 2012 12:48 PM   in reply to Noel Carboni

    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).

     

    CR5.7.png

     

    CR6.6.png

     

    CR6.7.png

     

    CR7.0.png

     

    CR7.1.png

     

    CR7.2.png

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 4, 2012 1:11 PM   in reply to Noel Carboni

    Hi Noel, So what you are saying is that ACR 7.*** is not supposed to process more than one image at a time, it is however using all the accessible cores to process each image individually? (Based on your screen shots and my test)

     

    If we were to step back to the 2010 process as opposed to the new 2012 process we would have our process times return to what we are used to?

     

    Geoff

     
    |
    Mark as:
  • Noel Carboni
    21,003 posts
    Dec 23, 2006
    Currently Being Moderated
    Oct 4, 2012 2:53 PM   in reply to CanJam

    Well...  Not exactly.  In my case 7.1 and 7.2 clearly are busying a lot of logical processors, but not all  - as 7.0 did.  Look carefully at all the little graphs - something like 7 of them have gone unused in 7.2. 

     

    But just to complicate things, if I open one image, interactively, the doggone thing DOES seem to use all logical processors!  This is just weird.

     

    I haven't timed opening the files through the 2010 process, but conceivably it's possible it will execute fewer instructions to get the job done.  It would be worth a try.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 7, 2012 12:25 PM   in reply to Noel Carboni

    I started a new thread regarding a 7.2 issue, but perhaps it belongs in this discussion?....

     

    I've noticed that working in 7.0, 7.1 has been slow, but 7.2 is now painfully slow after clicking "done" -- there is a new "Camera Raw | Updating Settings" modal dialog that freezes progress and seems to last 7-10 seconds for each image edited! Has anyone else noticed this?

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 19, 2012 7:14 AM   in reply to Noel Carboni

    For the first time ever I have rolled-back to a previous version of Camera Raw. I'm now using 7.1, as 7.2 was proving painfully slow in Bridge batch operations, as well as rendering to Photoshop. Quality seems good enough, but it's just too slow to get things done.

     

    Windows 7 64b, Intel Core2 Duo @ 3.55GHz, 4GB RAM @ 1066GHz, P45Express/ICH10 RAID. Not cutting edge, but not past it neither.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 19, 2012 7:36 AM   in reply to Yammer P

    Fortunately 7.2 is working okay for me except for the saving of the images. It's particularly slow.

    My work around is to use Lightroom 4 to do the export and by breaking up the export into several simultaneous saves, that seems to get things done.

    Geoff

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points