Aperture 2.1 slow in RAW adjustments

When Aperture 2 came out, I felt like I had a rand new computer. Everything was so quick!
When I upgraded to 2.1, every adjustment I make in RAW takes longer now. For example, moving the exposure slider is delayed. the little slider ball is always behind where my cursor is.
With hundreds upon hundreds of images to go thru, this is now longer than my old Quad G5.
Any ideas?
Also, I have 8 libraries, and it does this in all the libraries.

I've found most of the adjustments quicker in 2.1, provided as always you don't throw Straighten or Edge Sharpen into the mix too early. I've started using Ap again as a result of that and the other improvements in 2.1, and am doing final trials on a new library.
Edge Sharpen itself, though, is painfully slow and can only be used via presets, in reality.
best
Paul
Paul Ingram FRSA
[email protected]

Similar Messages

Aperture 2.0-slow loading RAW

I got the trial version of Aperture 2.0 and was having a great time with my jpeg projects. The internet is down at my home so I'm on my MBP 2.4. Everything was working great until I imported a project that came from Aperture 1.5 on my home machine. I've always got the Activity Monitor running in the lower left of my screen and noticed problems:
Importing this 8Gb RAW project took twice as long to import into Aperture 2.0 than Aperture 1.5.
The Activity Monitor showed both processors were maxed out when importing into 2.0 and were barely active during the import into 1.5. With the processors maxed out I couldn't do anything but wait for the import to complete.
I converted the RAW files to 2.0 after I imported them into Aperture 2.0 and all 341 came out lighter with whites now blown after they were perfect in 1.5.
Advancing from photo to photo at the rate of 1 sec (in the imported RAW project) caused Aperture 2.0 to max out the processors and stall. No such problem in Aperture 1.5.
I'm curious if this would be different in Leopard or if someone knows what is happening.

Within just an hour ago:
I was at Aperture, just a simple image, and then it basically locks up making a simple adjustment. The processor maxed.
Frustrated, as to final kindling point of solder, the fan is doing it's best at 149/f.
So I minimize the view of Aperture and expose the window for the Activity Monitor to see what's up.
Now this is weird, I just restarted the laptop fresh a few minutes ago with nothing running but Aperture.
I then notice in the column %-CPU a value of 82% for Speech something.
I didn't take note of the full process. Perhaps there is a log report, but I'm not that proficient.
I've seen it listed (speech) before, but didn't pay much attention.
Not sure what this was about or why it was running.
Extremely Hesitant, I select and Squashed it, like a Bug.
I admit, I was a bit worried as to what was going to happen.
Suddenly, the processor load and furnace blower settled down to idle.
Bring up Aperture to finish image and things actually work.
Did I just fix my biggest pain of the year? The splinter finally pulled free.
I'm like ready to put on my Spider-Man outfit, and go fight some crime.
A simple adjustment later, and the processor maxed out for a couple seconds and back to idle.
What The H*LL,,, I can deal with that real easy.
Now, who out there is a 'Guru of Scrip' that can make a window pop up if any process goes
beyond a certain value? This is a critical featured tool to have. I'm back to 110/F from 149/F.
I have to assume this anomaly has plagued me a long time. The Mystery baffles me.
I truly wish I could explain this. No dought, I'm sure this process even sounds insane.
Cheers

Aperture 3.1.3 Very slow importing raw files

Aperture 3.1.3 Very slow importing raw files please help
Pro Photographer. I have a Mac Pro Quad core 1 yr old with 12GB Ram. I import via 2 Firewire 800 card readers - A Lexar & a UDMR Reader.Only using them singly. System has 4 1TB hard drives 1. Applications, 2. Aperture Library, 3. Aperture Vault, 4 Time Machine
On a photo shoot, first CF card may download and complete in less than a minute but the next card with a similar number of images may take 10 minutes.
Sometimes if I swap card readers, this can speed up download but then everything slowly grinds to a halt.
I have closed down all other programmes, switched off Faces and Enable Gestures - switched off Look up places.
Situation driving me nuts as we shoot and view images with customers immediately after the session and download time effecting the amount of time we have to do this. Nothing seems logical as such a high spec machine should theoretically fly through this.

Have you upgraded your OS ans all your Apps to the latest Versions and also rebooted the system?
Turn on the Activity Viewer (Windows ->Show Activity) while importing, to see how Aperture is spending its time.
Also launch some tools from the Application -> Utilities folder:
launch the Console window, to check for diagnostics /error messages
launch the Activity Viewer, to see how much RAM and CPU time Aperture and other processes are using.
How much space is free on your system drive? And on the drive you are importing to?
If you find in the Activity Viewer, that Aperture is slow, but de facto using not much CPU time, then the problem may be a corrupted Aperture Library or corrupted preference files.
Try to import into a new, empty Aperture library and see if the problem persists.
If you have no problems with a new Library, try the Aperture 3: Troubleshooting Basics:
http://support.apple.com/kb/HT3805
Start with repairing permissions and repairing the library.
If none of the measures outlined there, or you need further help, please report back.
Regards
Léonie

I have iMac and need a good photo editing program to use. Reviews say aperture runs really slow with Lion, any suggestions?

I need a program where I can remove objects and touch up dead grass, etc.

Reviews say Aperture runs really slow with Lion, any suggestions?
To add on to Corky02 answer:
The recent Aperture release AP 3.3.x is very efficient, both on Lion and Mountain Lion. But you need a decent hardware to support it. The older Macs will have problems with the storage and CPU requirements. For good performance on large raw images plenty of RAM is important, at least 4GB, but 8GB would be much better, and your library should be on a fast disk, preferably on an internal drive. And don't let the system drive get too full.
Many reports about Aperture being slow are due to putting the Aperture library onto slow disks or acessing the original image files over the network, insufficient RAM, or corrupted or ill-designedAperture databases.
Aperture excels at all kinds of image processing that can be considered image developement - raw processing and color/lighting adjustments, but does not do compositing. If you are shooting raw and want professional image developement I'd recommend to do this in Aperture and not in iPhoto - you will have much more control over this in Aperture (after a steep learning curve). You can also repair and retouch the image to correct minor blamishes. For graphics compositing and inpainting you can set up an external editor and send your images from Aperture to this external editor - any of the editors Corky recommended would be o.k. for this.
To see, if you will want the advanced image processing in Aperture or the easy to use, more basic options in iPhoro will be sufficient to you have a look at the Aperture User manual, or the tutorial on the support page: Aperture Support
But Aperture is a professional apllication, not "plug and play". You should only consider it, if you are willing to spend some time on learning to use it properly and are willing to work your way through the manual.
Regards
Léonie

Lift and Stamp only RAW adjustments by default

I would to be able to lift and stamp my raw adjustments from image to image without having to deselect each of the other metadata properties from the lift and stamp hud each time I restart Aperture. My exclusion of other metadata remains until I close Aperture. The next time I open it I am forced to once again open the hud and deselect unwanted metadata. Is there a way to set my desired lift and stamp method as a default?
Thanks,
Christoph

I would to be able to lift and stamp my raw
adjustments from image to image without having to
deselect each of the other metadata properties from
the lift and stamp hud each time I restart Aperture.
My exclusion of other metadata remains until I close
Aperture. The next time I open it I am forced to once
again open the hud and deselect unwanted metadata. Is
there a way to set my desired lift and stamp method
as a default?
Thanks,
Christoph
Currently not... any time you life you are always going to get the full set of metadata from an image, so even making a template image without the metadata that always gets included would not help much I think.

Bridge does not show my Camera Raw Adjustments in previews or thumbnails.

Bridge CS6 on my Mac is not showing my Camera Raw adjustments in a preview pane or thumbnail.
Here's how it worked until recently:
I open a .CR2
I make some adjustments
I click "Done"
The thumbnail and the preview show the adjustments I made
Now, it works like this:
Open a .CR2
Make adjustments
Click "Done"
The preview and thumbnail don't show all the adjustments. I can't see the results of noise removal, but I can see a drastic change in Exposure
If I double-click the CR2 file, it opens in Camera Raw, and I see all my adjustments, including noise removal.
Here's what I've tried, but saw no difference (I restarted Bridge every time):
Purge Cache
Purge Cache for Selection
Replaced Camera Raw plug-in as described here: Camera Raw 8.4 | No metadata or Camera Raw edit
     (Doing so made Camera Raw disappear in Bridge, so I restored the original file)
Reset Preferences
Reset Standard Workspaces
All the above fixes were inspired by this thread: Re: Bridge CS6 not showing Camera Raw adjustments
Why don't I see the noise removal effect in the previews? I am sure I saw it a few weeks ago. I rely on that, to help me sort and cull photos.
I'm hoping there's a preference toggle that I accidentally changed. It's definitely a puzzle. (Version: Bridge CS6 5.0.1.21 5.0.2.4)
Message was edited by: moonatwork after updating Bridge version. I tried all the above fixes again, after updating Bridge. It actually got worse. I tried replacing the Camera Raw plugin, which failed as before. I then restored the previous plugin, as before, but Bridge now fails to honor the preference, "Double-Click Edits Camera Raw Settings in Bridge" and instead always opens Photoshop.

Thanks, Omke. I tried updating, then applying all the same fixes to the updated version. No change.
I can attach a screenshot, but I must block out names and faces. All you'll see is my Bridge interface, not the faces in the portraits. Hope that helps.
My specs:
Bridge CS6 5.0.2.4
Mac OS X 10.6.8
16 GB RAM
65 GB free disk space
2 monitors, 2 graphics cards:
ATI Radeon HD 4870
Type:    GPU
Bus:    PCIe
Slot:    Slot-1
PCIe Lane Width:    x16
VRAM (Total):    512 MB
Chipset Model:    NVIDIA GeForce GT 120
Type:    GPU
Bus:    PCIe
Slot:    Slot-4
PCIe Lane Width:    x4
VRAM (Total):    512 MB

Why Aperture doesn't send the RAW file to Photoshop

I've seen the complaint about Aperture not passing the original RAW file to Photoshop in several places in this forum. I think I have a reason for why Aperture doesn't work this way.
The reason has to do with the 1st law of digital RAW photography. "Never, ever, overwrite the original RAW data from a camera's RAW format file."
Because of the above rule, both Aperture and Photoshop do not actually work on the original RAW file. They transform the RAW image data into a usable image using user specified settings (which may be the camera's default setting for that image). The original RAW file is left untouched.
When you open a RAW file in Photoshop and try to save it, you'll be prompted for a new file name. You wouldn't want to overwrite the original RAW file by writing the edited image data back to it.
When you edit an Aperture RAW file using Photoshop as the external editor, Aperture first creates a TIFF or PSD version image file in its library and then passes that file name to Photoshop. Photoshop opens the TIFF or PSD file and directly edits it. Since this version file is already in Aperture's library, when Photoshop is finished editing it, Aperture automatically sees the edited file because its already in the library.
If Aperture were to send the RAW file name to Photoshop, Photoshop would open the RAW file and create a new PSD file. When it came time to save your edits, where would you save it. In order to get it back into Aperture's library, you would need some form of Photoshop to Aperture communication so that Photoshop would know where to save the edited file and Aperture would know to add it to the library. This would require collaboration between both Adobe and Apple and doesn't seem likely.
I have a couple of ideas someone can try. These are only ideas and completely untested. I'd do it myself but I don't own Aperture (see my computer info below for the reason).
1. Create two folders with automator actions. You export your RAW files from Aperture to a "Photoshop-IN" folder. Any new RAW image found in this folder will be automatically opened in Photoshop by the Automator action. Then you save the edited Photoshop file into a 2nd folder "Aperture-IN". Another Automator action imports this into Aperture.
2. In iPhoto, if you try to edit a RAW image with an external editor, iPhoto creates an intermediate image file (JPEG I think) which it passes to Photoshop. But, if you drag the original RAW image thumbnail from iPhotos library window to the Photoshop icon in the dock, the original RAW image file is passed to Photoshop. You only have the problem of getting the saved Photoshop file back into iPhoto's library. Maybe this same thing would work in Aperture by dragging the Master image to the Photoshop icon in the dock.
PowerMac G4 Dual 1.25GHz Mac OS X (10.4.3) FW800, 4 internal HD - 550GB

This is all well and good. I wholeheartedly agree with the idea of keeping the "master" sacrosanct. What I object to is not being able to do the conversion in Photoshop (or elsewhere)
What I want is for Aperture to send the raw over to photoshop when I select "open in external editor", and then follow the current workflow (I do my edits, hit save, and a second master is added to Aperture's db.)
It's totally possible for them to do this, and it wouldn't break anything in the system, or the philosophy. Of course it's a workaround that wouldn't be necessary if Aperture's converter were up to snuff. But it isn't, and I bet it would be easier to implement the workaround than to fix the fundamental defects in the converter itself.

Snow Leopard 10.6.5 makes Aperture 3.1 slower. What gives?

I recently upgraded to Snow Leopard 10.6.5 with Aperture 3.1 1290000.2 in an attempt to make Aperture faster, but instead Aperture is now SLOWER than on Leopard! I am using an iMac 2.66 GHz Intel Core 2 Duo, 2GB SDRAM, with the library located on my internal drive.
I have several thousand photos stored there, and am really, really annoyed that photos take several seconds to "load," and projects can take take 10 seconds to open. It seems to be i nearly constant "Processing" mode.
Is anyone else experiencing this? Is it fixable?
-- pdibello

I would second that, 2GB is not enough to be running Ap.
Also for speeding up the system try some of the following.
Delete your Ap Preferences, I did yesterday for another reason and was blown away at the speed difference I gained without meaning to.
Run some System Maintenance with Disk Utility and an application like Onyx
http://www.apple.com/downloads/macosx/systemdiskutilities/onyx.html
Use the Aperture Library First Aid tools, this will fix any glitches in the library.
http://support.apple.com/kb/HT3805
Let us know if any of these steps helps.
Tony

Some CS4 Raw adjustments lost after save to jpg or tiff

I've been running Photoshop CS4 under Windows XP 64 bit (with 8Gb RAM) with no problems whatsoever (including use of GPU feature) since November 2008.
Very recently, with a difficult event photosession I have a bunch of photos that have are overexposed/blown out highlights which were easily fixed with RAW adjustments in Bridge CS4 with the generous use of the RECOVERY slider as well as EXPOSURE.
After converting to JPEG (quality 12) or Tiff (as a test) the initially overexposed photos which were fixed and look fine in both Bridge and in Photshop show up overexposed -as if the RAW adjustments have never been made. In other words the jpg or tiff version appears with blown highlights right next to the corrected RAW version (Canon CR2 files). I need to emphasize that when the adjusted RAW is opened in Photoshop it looks fine -with all of the adjustments perfect. But once it is saved in Photoshop, the saved file does not look the same, it now has blown out highlights.
In other words something in the workflow whether Photoshop or RAW is simply not working the way it should and the way it used to work.
I have downloaded and installed the latest RAW 5.5. It has not helped at all. I can't pinpoint the time when this problem first showed up because I normally hardly ever have images with blown highlights. This last event shoot was very poorly lit and it took a bit of time to figure out how to correct the exposure setting on the spot.
Have any of you experienced this problem? I can't get Adobe Tech support telephone support without paying for the privilege, in spite of the fact that I suspect that this is a program bug.
Any suggestions will be greatly appreciated and welcome.
Thanks,
Dan

Some additional findings:
When I looked at the JPEGs which had blown highlights in Bridge, with ACDsee, they looked fine! So I also tested with Windows Fax Viewer and they're fine again. Conclusion -Bridge is showing unedited exposure.
Then in response to posting this same problem on Dpreview I got the solution from Walter Wollert:
wwollert wrote:
" Do you have tif and jpg edit options enabled in RAW(ACR)? There was something I ran into that caused the problem like you have. I turned these options off and it cleared up. Why? Ur guess is as good as mine.
Again, I could be in error, since it happened a while ago and I sometimes have rolling blackouts.
Walter
Hey Walter,
Your suggestion solved my problem. Who would have expected that disabling JPEG editing in RAW would solve this problem? I have been told to make sure this feature was enabled and in fact I always had this enabled because on occassion I find it very useful to use RAW tools to fix problems in some old JPGs.
I've been terribly annoyed and depressed about this problem and it just about completely stopped my editing for over 2 weeks, so you can be sure I am extremely thankful for your HEADS ON solution.
Someone at Adobe should have their head dunked in toilet bowl perhaps?
I don't ever remember seeing this problem in the past, even though I had the JPEG & TIFF editing enabled, and therefore I thought this "bug" crept in with one of the program updates.
Thanks a MILLION!!!,
Dan"
So that's the answer to the problem!

Preview is TOO SLOW with RAW images! PLEASE HELP !!!

Hi my name is Dario and I am Photographer.
After upgrading from Mountain Lion to Mavericks on my current iMac preview app is sick slow with RAW images.
On Moutain Lion viewing RAW files from my camera with normal OS Preveiw app was wonderful,fast and now it is disaster...
I can't any more fast pick what I need and delite rest. Now I need hole ethernety until loads next picture.
PLEASE HELP I CAN'T WORK ENY MORE LIKE THIS !!!!

Some things to try - Linc Davis is a good problem solver.
https://discussions.apple.com/message/22128130#22128130

Raw Adjustments - some of them are not showing up?

I have 4 projects that some of the raw adjustments are grey (not active) in; all of my other projects are fine. The adjustments I can't adjust are: sharpening, edges, moire, radius, & de-noise. Camera is canon 5D Mark II. Any help is greatly appreciated.

thanks...at least I know why its like that now...I don't usually shoot sraw, but I did then (unfortunately). appreciate the help!

Bridge CC RAW adjustments

Hi There,
I am using the latest version of Photoshop / Bridge CC. The software has been working perfectly but for some reason today i am having a big problem with my RAW adjustments to DNG files appearing in the bridge browser after i saved them. For example - I open a file from bridge and open in Camera Raw 8.4.1 make adjustments and select done. When i then view the adjusted images in bridge in any of the views ESSENTIALS FILMSTRIP etc the files are not updating. I have tried purging the cache / compacting the cache with no change.
I am using a new 27 inch iMac. The only thing i have changed in my system is that i installed a new workspace in PS but don't think would have any relation to my bridge problems.
Any help would be greatly appreciated as this issue has ruined my workflow.
Thanks

Yes i am am on Mavericks. Embarrassingly it was just a simple selection mistake on my behalf....just a matter of selecting the chequerboard icons, top right.
Thanks for the help.

Aperture Exporting JPEG's from RAW: file size and quality questions?

Hey Everyone,
So, I'm using Aperture 2 and I've got some questions about exporting from RAW to JPEG. I shoot with a Nikon D70 so original RAW files are 5-6mb in size. After doing some basic post processing when I export the pics at "full size" with picture quality of 11 out of 12 then the resulting JPEG is about half the file size of the original RAW file. For example a 5.6mb RAW becomes a 2.6mb JPEG. The resolution in pixels per inch and and the overall image size remain unchanged. Have I lost picture quality due to the exporting JPEG being smaller in file size?
My friend who works with me prefers to edit in Photoshop and when he follows the same workflow his saved JPEG from the identical RAW file in Photoshop is minimally smaller in file size, say 5.6mb to 5.3mb. He's telling me that my Aperture edited photos are losing quality and resolution.
Is he right, are my pics of lesser quality due to being a smaller file size? I've always been told that the quality of a picture is not in the mbs, but the pixel density.
I've bee told that Aperture has a better compression engine and that the resulting files are of the exact same quality because the PPI and image size are the same. Is that what explains the much smaller file sizes in Aperture?
I tried changing the picture quality in the export menu to 12 out of 12, but the resulting JPEG then becomes larger than the original RAW at over 7mbs.
Can someone please help me understand this better? I don't want to lose picture quality if that is indeed what is happening.
Thanks in advance for your help.

mscriv wrote:
So, I'm using Aperture 2 and I've got some questions about exporting from RAW to JPEG. I shoot with a Nikon D70 so original RAW files are 5-6mb in size. After doing some basic post processing when I export the pics at "full size" with picture quality of 11 out of 12 then the resulting JPEG is about half the file size of the original RAW file. For example a 5.6mb RAW becomes a 2.6mb JPEG. The resolution in pixels per inch and and the overall image size remain unchanged. Have I lost picture quality due to the exporting JPEG being smaller in file size?
JPEG is a "lossy" file compression algorithm. Whether Aperture or PS, *every time a JPEG is saved some loss occurs*, albeit minimal at the 11 or 12 level of save, huge losses at low save levels. Some images (sky, straight diagonal lines, etc.) are more vulnerable to showing visible jpeg artifacts.
My friend who works with me prefers to edit in Photoshop and when he follows the same workflow his saved JPEG from the identical RAW file in Photoshop is minimally smaller in file size, say 5.6mb to 5.3mb. He's telling me that my Aperture edited photos are losing quality and resolution.
*Both of you are losing image data when you save to jpeg.* IMO the differences between the apps is probably just how the apps work rather than actually losing significantly more data. The real image data loss is in using JPEG at all!
Is he right, are my pics of lesser quality due to being a smaller file size?
I doubt it.
I've always been told that the quality of a picture is not in the mbs, but the pixel density.
The issue here is not how many pixels (because you are not varying that) but how much data each pixel contains. In this case once you avoid lossy JPEG the quality mostly has to do with different RAW conversion algorithms. Apple and Adobe both guess what Nikon is up to with the proprietary RAW NEF files and the results are different from ACR to Apple to Nikon. For my D2x pix I like Nikon's conversions the best (but Nikon software is hard to use), Aperture second and Adobe ACR (what Photoshop/Bridge uses) third. I 98% use Aperture.
I tried changing the picture quality in the export menu to 12 out of 12, but the resulting JPEG then becomes larger than the original RAW at over 7mbs. Can someone please help me understand this better? I don't want to lose picture quality if that is indeed what is happening.
JPEG is a useful format but lossy. Only use it as a _last step_ when you must save files size for some reason and are willing to accept the by-definition loss of image data to obtain smaller files (such as for web work or other on-screen viewing). Otherwise (especially for printing) save as TIFF or PSD which are non-lossy file types, but larger.
As to the Aperture vs. ACR argument, RAW-convert the same original both ways, save as TIFF and see if your eyes/brain significantly prefer one over the other. Nikon, Canon etc. keep proprietary original image capture data algorithms secret and each individual camera's RAW conversion is different.
HTH
-Allen

"Canon SLR EOS 40D" *Aperture and Canon's CR2 RAW files not supported.*

Hi,
I just started playing with Aperture, and with my brand new *Canon SLR EOS 40D* camera. One problem, Aperture is not recognizing the RAW file format. I am using RAW Fine**-L. Even with that it doesn't even see the JPG shots in Aperture. Went to the Canon site and it shows CR2 format. IPhoto 08 sees the JPG files just fine, It also sees the RAW files just doesn't know what to do with them. I know that RAW files are not supported on IPhoto 08. The camera is only been out a few months, but still lost on why Aperture doesn't support the format. Maybe I am missing something. Anyone have any ideas?
Thanks in advance....

For some reason or another Adobe Photo Shop 7 is no longer supported in Leopard. When you lunch Photo shop 7 in Leopard. You get "An unexpected and unrecoverable problem has occurred because of a Program error. Photo Shop will now exit." even if you reinstall the program, still you get the same error. Photo Shop 7 is Not the latest and greatest, but in most cases, that is all you need. Not sure if they plan on a fix, so for now I put that program on a shelve.
Hope that helps

RAW JPEG PROBLEM I'm new to Aperture and neglected to mark RAW JPEG pairs when I imported (from iPhoto). Now I have two images for each photo. Help!! How can I change this?

I’m new to Aperture and neglected to mark RAW+JPEG pairs when I imported (from iPhoto). Now I have two images for each photo. Help!! How can I change this?

How did you import from iPhoto? If you saw the Import panel with raw -jpeg pairs, then you probably did not import your iPhoto library as library, but as files, and then you will see plenty of duplicates - previews, thumbnails, originls, edited versions. If that should be the case, it would be better to delete the import from iPhoto and to import your iPhoto library again, but this time using "File > Import > Library".
Only that would require compatible versions of iPhoto and Aperture. What are your Aperture and iPhoto version numbers?

Aperture 2.1 slow in RAW adjustments

Similar Messages

Maybe you are looking for