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.
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
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
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. ![]()
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
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.
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?
-Noel
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
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
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?
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.
North America
Europe, Middle East and Africa
Asia Pacific