Aperture 2.0 vs Lightroom in respect to raw image adjustment stability

I just downloaded lightroom(demo) in order to compare the stability to Aperture 2.0. It seems that lightroom is highly stable when adjusting images, whereas Aperture wigs out allot when adjusting images. As mentioned in recent post Aperture 2.0 preview wigs out when adjusting images, especially when using the layer or highlights and shadows adjustments. Like everyone is saying they either get a black preview or Unsupported Image Format preview, after adjusting the raw file. This does not happen all the time, but very frequently and too frequently!!
I really like the many features of Aperture, but if it remains too unstable for much longer I'll have to go elsewhere. I hope the Aperture team has been comparing the stability of their product to Lightroom when making image adjustments. This has been an issue forever.

Like everyone is saying they either get a black preview or Unsupported Image Format preview, after adjusting the raw file.
Everyone? Guess I'm not everyone because I'm not seeing this problem at all. And the sluggishness of the 1x versions has all but disappeared with this new update. As culcheth said you might want to define +wigging out+...
For that matter, I never had +stability problems+ during adjustments with 1.5 either - slowness yes, but nothing unstable. I'm using a Nikon D80: what's your camera model? what's your machine specs?
As mentioned in recent post Aperture 2.0 preview wigs out when adjusting images, especially when using the layer or highlights and shadows adjustments.
What's the "layer" adjustment?
We'd love to help, but we need a little more info to determine what your problem is in the first place.

Similar Messages

  • How to get Aperture and iPhoto to use Pentax *ist DL RAW images natively

    Using some techniques that I found in various places in these forums, I am going to give step-by-step instructions to get Aperture and iPhoto to recognize Pentax *ist DL RAW images natively.
    Note: This worked for me using 10.4.6 with the latest iPhoto 06 and Aperture updates. I do NOT know if this will work on older versions of OS X, iPhoto, or Aperture.
    Note: If you also use a Pentax *ist DS camera, these instructions will probably disable support for that particular device due to the modifications made to a system file. Only complete these instructions if you want to use a *ist DL camera.
    ** These instructions involve modifying system level files using a HEX editor. If you are not comfortable with this, do NOT attempt to do this or you could kill your system. Remember, BACKUP BACKUP BACKUP. These steps worked great for me but follow at your own risk!! **
    Ok, lets begin...
    1) Download this great patch by macintosh_tech
    http://idisk.mac.com/macintosh_tech-Public
    This patch contains an updated raw.plist file which includes the RAW information for the *ist DL. This patch also contains an updated libRaw.dylib file and an updated Raw Presets file for Aperture.
    ** Do NOT copy the libRaw.dylib file from this patch to the folder listed in the patch Read_Me. This file did not work on my Intel-based Mac and crashed my system!!
    I was able to modify my original libRaw.dylib file using a HEX editor to get it to work on my system. Instructions for this modification will follow.
    2) Open the .dmg of the patch in a Finder window
    3) Open a new finder window and browse to /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.fra mework/Resources
    *4) Backup the libRaw.dylib and Raw.plist files. Copy them to a safe location. For extra safety, you can just copy the whole Resources folder to a safe location (Make sure that you COPY it and dont MOVE it)*
    5) Right-click the libRaw.dylib file and select "Get Info". Look at the bottom of the info window and expand the "Ownership & Permissions" tab. In this section, expand the "Details" tab. If the lock icon is in the locked position, click it to unlock it. Change "Owner" to your user name. If requested, enter your system password at this point. Close the info window. This step lets you modify the libRaw.dylib file.
    6) Complete step 5 for the Raw.plist file.
    7) Copy the Raw.plist file from the "Place In System Folder" folder from the patch to the Resources folder. It will ask you if you wnt to overwrite the existing file. Click "Replace".
    8) Open a new finder window and browse to the /Users/YOURUSERNAME/Library/Application Support/Aperture/ folder.
    * 9) Backup the "Raw Decode Presets.plist" file *
    10) Copy the "Raw Decode Presets.plist" file from the "Place In Home Directory" folder from the patch to the /Users/YOURUSERNAME/Library/Application Support/Aperture/ folder. Click "replace" if it asks you.
    11) Here's the tricky part. Download a HEX editor if you don't have one. I used 0xED. It is free and can be downloaded from
    http://www.versiontracker.com/dyn/moreinfo/macosx/29521
    12) Open the libRaw.dylib file from the Resources folder in your HEX editor.
    Note: This is your original libRaw.dylib file from your /System/Library/...../Resources/ folder, NOT the file from the patch.
    Use the Find function and search for the string "Pentax *ist DS". Make sure you are using "Search Type: Text" (or equivilent in your editor) and that you use proper case. When you find this string, change the "S" in the "DS" to an "L". The string should now look like "Pentax *ist DL". Use the "Find Next" function to find the next instance of "Pentax *ist DS". Again, change the "S" to an "L". There should be two total instances that you need to change. Save the file and exit the editor.
    13) Open Disk Utility and repair permissions. This will set the raw.plist and libRaw.dylib files back to their original permissions.
    14) Reboot the system.
    15) You should now be able to view .PEF files natively in Aperture and iPhoto. I appologize in advance for any typos. Let me know how this works, as this is my first tutorial of this nature.
    Macbook 2.0   Mac OS X (10.4.6)  

    It would appear that my last post was a moot point as the 10.4.7 update adds support for the *ist DL. It's nice to have it biult into the operating system now.

  • I have a Canon EOS T2i Camera and I want to import the RAW images into Aperture.  How do I import them as RAW images instead of jpeg ?

    How do I import RAW images from my Canon EOS T2i camera into Aperture and have them show up as RAW images and not jpeg images?

    See the list of supported raw formats:
    http://www.apple.com/aperture/specs/raw.html
    The footnote ** for the cameras  EOS Rebel T2i EF-S / 550D / Kiss X4**  says, that the raw format is only supported with Aperture 3. So you will have to upgrade to Aperture 3, to be able to import the raw from from your camera.
    Regards
    Léonie

  • If I upgrade to Lightroom 5, will my raw images from NIkon D800 work?

    I have Lightroom 3 and want to import my NEF (Nikon RAW) files (D700 & 800) and it says not supported.  If I upgrade to the newest version, will it work?

    pinkypunk35 wrote:
    Yes, but.... bear in mind rumours floating around that Lightroom 6 will be announced in the next week so you may wish to hold off for that.
    Best not to go spreading those rumours. No-one with any credibility believes them.

  • Does adobe lightroom open nikon d7100 raw images?

    Does anyone know if any lightroom products can open nikon d7100 raw/nef images?

    Perhaps your confusion stems from the fact that there are a couple of different lists maintained by Adobe which need to be cross-checked against each other.
    List 1
    Starting at http://helpx.adobe.com/creative-suite/kb/camera-raw-plug-supported-cameras.html
    the Nikon D7100 has been supported since Camera Raw 7.4 and Lightroom 4.4.
    So Lightroom 4.4 and later versions support it.
    List 2
    However, according to this list http://helpx.adobe.com/x-productkb/global/camera-raw-compatible-applications.html
    Adobe Camera Raw (ACR) 7.4 is only compatible with CS6 and later.
    So CS5 is only compatible with Camera Raw up to version 6.7: therefore CS5 will never be able to open D7100 Raw files. You'd have to use the DNG converter first then use CS5.
    So your choices:
    Buy Lightroom 5
    Upgrade CS5 to CS6
    Join the Cloud or the Photoshop Photography Program
    Or stay with CS5. Convert the D7100 Raw files to DNGs using the free DNG converter. Then open the DNGs in CS5.

  • RAW images in Lightroom aren't opening in camera raw in Photoshop.  Instead, I have to open the image in Finder before it will open in Camera Raw in Photoshop.  How can I correct that?

    RAW images in Lightroom aren't opening in camera raw in Photoshop.  Instead, I have to open the image in Finder before it will open in Camera Raw in Photoshop.  How can I correct that?

    Your question is a little unclear. In a "normal" Lightroom/Photoshop workflow the raw images do not open from Lightroom into Camera Raw. Lightroom has all of the Camera Raw functionality in the develop module. When you choose to open an image in Photoshop, and Lightroom and Photoshop are synchronized (i.e. referencing the same version of Camera Raw) then Camera Raw is simply used to interpret the Lightroom adjustments as the image is transferred to Photoshop. If Camera Raw is an older version then Lightroom offers you the choice to open the image or create a PSD or TIF file that includes all of the Lightroom adjustments. But in either case, opening in Camera Raw is not part of the workflow. It is possible to open the image as a smart object or convert the image to the smart object in Photoshop and then open it in Camera Raw. That is done from within Photoshop or is one of the open options in Lightroom. If you choose to go the smart object route the image first has to be opened in Photoshop and then from there you can open it in Camera Raw.

  • Printing from Aperture, and printing from Lightroom.

    Hello,
    I have noticed when I print from Aperture using my Canon i9950 and a custom paper Colorsync profile, and if I then print from Adobe's Lightroom using the same Colorsync profile and paper, the print from Lightroom is much sharper. The Aperture print is exact in every respect except it is noticeably softer.
    Anyone else notice this? And if so is this a recognised problem that may be fixed in 1.1?
    Kind regards,
    Anil K Solanki
    G4 Dual 867   Mac OS X (10.4.5)  

    Hi Charles, I totally agree with you. Lightroom's printing features are really excellent. In comparison Aperture almost seems like the printing of photographs was something the Aperture dev team bolted on at the last minute.
    I sincerely hope Apple sort out, what for me is inexcusable in a professional commercial app. A few photographers I know are going to use the next release of Aperture as a turning point, if it can't print as good as the Beta Lightroom then they will become Lightroom users and say good bye to Aperture.
    Apertures sorting and logging tools really are second to none, but if the print quality is poor, what is the point. I know for a large number of photographers, producing prints is not high on their list of needs, especially if they are supplying prints for publication or the web. But if I want to do what my old fashioned enlarger can do, which is create great prints, then hey I am not going to get it with Aperture.
    I know Apple can fix this, I just hope they do.
    Anil.

  • What is the best way to import photos from aperture to my new Lightroom

    What is the best way to import photos from aperture to my new Lightroom ?

    See if this helps
    http://lightroomsolutions.com/articles/migrating-from-aperture-to-lightroom-where-do-i-beg in/

  • Process for exporting out of Aperture to import into Lightroom

    I'm trying to convert a large library of images that is presently cataloged in Aperture 2.0 into a Lightroom 2.0 Catalog.
    Aperture doesn't store the sidecar files with the raw files. Is there a procedure or plugin that will create sidecar files in the same location as the (raw) image files in a nested file structure, so that I can then import the images (where they are now on the disk) into Lightroom and retain all the information that was recorded in Aperture (e.g. star ratings, keywords)? There are many thousands of images, in a fairly complex nested file structure, and recreating the images or manually moving files where they need to be in the file structure would take many hours.
    If there is a FAQ on this topic, can someone simply kindly point me to the FAQ? I tried searching but was unable to find anything useful. I found solutions that exported the master files (duplicating ALL the image files) with xmp sidecars but as noted above this would be problematic given the size and structure of the files currently in Aperture.
    Thanks!

    There are 2 big problems with the export/duplication route:
    1) The files are in a fairly complicated nested structure, and they need to STAY in that nested structure.
    2) The time and disk space required to duplicate the entire library.
    I don't have iView, don't know enough about Applescript to do this myself. (If I did, I would have done it already after reading the threads here that referenced iView.)
    This is *extremely* frustrating. If this is a simple thing (for someone with the appropriate skillset) to write a plugin for, Adobe should have an employee or associate developer do it to ease the transition for new customers coming to Lightroom with a library already cataloged in Aperture.

  • Aperture Library to Adobe Lightroom?

    Hello,
    Does anyone know of a way, or have any ideas, of how to share my Aperture library with Adobe Lightroom? I like both programs for different reasons and was curious if there was a way to at the very least export my Aperture Library in a way that I can import it in Lightroom? I eventually want to move both of these to an external hard drive as well..
    Thanks!

    Well, I just tried this... with one file. What I discovered, makes sense. The original file is not 'syched' because the original is not modified with non-destructive editing. All of the "edits" to the original files seem to reside within the programs, and not with the files. I wouldn't know where to look for this edit data in Lightroom, but I'm pretty sure that in Aperture the edit instructions being stored in the Aperture Library, even if the file is refrenced. This would be an interesting piece of code for someone to work on..... i.e. make a change in Aperture, and Lightroom reads that change from the Aperture library, and vice a versa.
    Not sure that anyone would really want to do this on a long term basis as I sincerely doubt that there is something that on program can do that the other can't. (Except that Lightroom does not make books or have a Lighttable). If for instance you created a bunch of great edits in Lightroom and wanted to used those edits in an Aperture book, you would, at this time, have to export the edited versions and import them into Aperture - at least that seems to me to be the current requirements.
    MacPro 2.66 4 GB   Mac OS X (10.4.8)  

  • Raw images from 1GX are rendering soft in Aperture - crystal clear on Lightroom

    I have just upgraded to a Canon 1Gx MK II as my point & shoot.  RAW images are rendering terribly soft in Aperture - crystal clear in Lightroom.  Any ideas?

    Have you in-camera settings applied, when you take your RAW photos? Aperture will ignore any of the in-camera settings when developing the RAW.
    Have a look at Keith Barkley's User Tip. See this link:
    The Big Three: Setting your camera for the best Aperture RAW results
    Also, you may want to check the RAW Fine Tuning settings in the Adjustments panel. Perhaps these setting have been changed from the default values.

  • Anyway to share original files from Aperture with Capture One & Lightroom

    I would like to use the 10,000 RAW files I have downloaded with Aperture and be able to use them in Capture One and play with Lightroom. I could export the Originals but then I would be doubling or even tripling the space needed to use these 3 programs. All three programs have different advantages and would like to be able to use all three. I'm sure Apple doesn't want anyone to use anything but Aperture but in the real world, Aperture can't do all the things I want to do.
    I have found the originals in Aperture (show package contents) but each picture seems to be in a seperate folder and not altogether in a central folder.
    Any help would be appreciated.
    Thanks,
    Jim

    Best is way is as Jeff says, use referenced files, then to open a raw file with Capture One simply select it in Aperture's browser, ctrl+click (right click) on it and 'show in finder'. From there drag it to Capture One and done.
    To automatically import the result to Apertue you can use a hot folder where the processed file from Capture One should be saved to.
    I also need to process sometimes raw images in Capture One, specially those with coloured tungsten lighting. Capture One's white balance is way much better than Aperture's.

  • Has anyone had trouble manipulating Nikon D750 raw image (NEF) in Aperture version 3.6 on Yosemite?

    Has anyone had trouble manipulating Nikon D750 raw image (NEF) in Aperture (version 3.6 500021000000000.3, Digital Camera RAW 6.0 - Build 761.5, Digital Camera RAW support 6000 - Build 136.1)
    I used to be able to manipuplate Nikon Raw (NEF) images from a Nikon D70 and D3200 using Aperture, until the 70 died and the 3200 was stolen about 18 months ago. Recently I did two things: (1) I upgraded OS X to Yosemite and (2) purchased a Nikon D750.  I have successfully imported NEF files from the camera to Aperture, but the images do not render/ cannot be opened/ manipulated. Instead, I see a black thumbnail for each imported image with a cassette recorder play icon in the center of each image. 
    I can view the NEF image in Finder preview mode, either directly when viewing the images on the camera SD card or after exporting the previously imported NEF image from Aperture to my desktop or user folder.  Previously imported NEF image seem unaffected.
    thanks.
    D.

    The current Apple OSX 10.10 Yosemite and the current Aperture version 3.6 do not have support yet for importing Nikon d750 nef/raw files. It usually takes Apple six to eight weeks to release a new digital camera raw update file for new Nikon dslr models. Once that digital camera raw update file is finally released, update your current version of Aperture and that will allow you to import your d750 raw files. In the meantime, you have many workarounds. In my opinion, the easiest is to save images in duplicate nef/raw and jpeg image files to your SD cards.
    And for now, just import the jpegs to Aperture 3.6 from your d750.  Process your jpegs in Aperture - and hope your clients are happy with the jpegs and can wait for later nef/raw image processing. Be sure to save and do not erase your original SD cards that include the nef/raw and jpeg files - then when Aperture finally releases a new digital camera raw file update that includes the d750 - just insert your original camera SD cards into the computer platform and import the old d750 nef/raw files and edit/process them.
    There are many other ways to proceed in the interim as well. You can always import your d750 nef/raw images into Lightroom (if it has been updated to convert the d750 nef files) and process them there. But for the time being, if you can afford to save and hold onto your original SD cards and wait for the inevitable Aperture digital camera raw update, this is a very easy and simple way to proceed.

  • Curious question about Lightroom previews and Camera Raw Cache

    Posted in the Flickr Lightroom Group as well:
    I have noticed something about the Lightroom (3.6) previews and Camera Raw cache that have me puzzled.
    I create a brand new empty catalog and purge the Camera Raw Cache.
    Then I import ONE Nikon RAW (NEF) file with dimensions 2592 x 3872 (10 megapixels - 10,036,224 pixels).
    Next I export that NEF file to an uncompressed 8-bit TIFF file. You would expect the size of that TIFF file to be roughly 30 megabytes (10 megapixels x 3 bytes per RGB value) and in fact the TIFF file is 30,135,830 bytes in size. If you export the same TIFF file but specify ZIP compression the resulting file size is 10,834,038 bytes. Obviously the compression obtained here is going to be highly specific to the image but so far no surprises.
    During import I specify render 1:1 previews and I go into Loupe mode and view the entire image at 1:1 size. I also visit the develop module and do a bunch of manipulations on the image but no cropping.
    At the conclusion of all of that I exit from Lightroom and examine the size of the Camera Raw Cache folder as well as the Lightroom previews folder. It would be my expectation that the previews folder  should have a rendered full image and that the Camera Raw Cache should also have a rendered form of the raw data. What would you expect the size of those respective folders to be?
    In fact - in my trials the previews folder totals a mere 1,675,264 bytes and the Camera Raw Cache which contains one DAT file corresponding to the one cached image is merely 267,374 bytes. This does not seem like nearly enough bits to preserve the rendered image nor is there a full size image tucked away in the actual catalog either - that file is not large enough to contain that. And yet I can use Loupe mode at 1:1 size and move from image to image with no loading delays (even when importing multiple files).
    I'm wondering if I've missed something obvious in my analysis and if not, whether someone might care to speculate as to what magic Adobe is practicing here. Even if we grant them some special algorithm to compress their previews I don't see how they can achieve a compression so much greater than the ZIP-compressed TIFF file achieves.
    And for those that might think to ask - I've repeated these experiments with multiple raw images and on both the PC and MAC platforms.
    I look forward to some answers or interesting theories or perhaps someone might replicate the experiment and report findings.

    MadMan and Hal - thanks so much.
    So that was my D'Oh moment of what I was missing - the use of re-rendered JPGS as previews. That certainly does fit with the file sizes I am seeing. I had naively assumed that the previews might have tried to preserve the full fidelity of the image - But as you suggest that full fidelity is likely only there in the develop module.
    This perhaps explains another observation from the Develop module - moving from one image to another might display "Loading" either briefly or across a longer duration. My guess is that the length of the loading process might have to do more with what is cached in RAM than cached on disk in the camera raw cache. More of a shame then that 64-bit Lightroom on 64-Bit Windows cannot grab more RAM than it seems to do at present.

  • In Aperture, why do my RAW images momentarily preview well, degrade into extreme colour fringing

    EOS 60D, EF 50mm f/1.4 USM.
    Shot at f/1.4, ISO 3200, Auto white balance
    I've loaded the images into Aperture 3.0, and they preview well while the images are loading (I'm assuming they're JPEG previews) then heavily degrade in quality after the image has fully loaded.
    Is this a camera, lens, or Aperture issue?

    I have no experience with what you are seeing but I can offer, my Mac buddies complain about poor performance with some of the Mac OS's and certain post processing software. I would start troubleshooting there.
    EOS 1Ds Mk III, EOS 1D Mk IV EF 50mm f1.2 L, EF 24-70mm f2.8 L,
    EF 70-200mm f2.8 L IS II, Sigma 120-300mm f2.8 EX APO
    Photoshop CS6, ACR 8.7, Lightroom 5.7

Maybe you are looking for