Aperture Challenge

I've got kind of a challenge for Nikon shooters who use Capture NX and Aperture. I love Aperture and would love to be able to use it for RAW, (NEF for Nikon), files. For most photos I would rather bypass Capture NX and go straight to Aperture.
I'm aware that Aperture cannot read my in-camera settings for NEF files after import, and therefore strips my images of my camera settings. This would be ok if I could somehow replicate those camera settings manually in Aperture and get the same look that Capture NX gives me without having to use Capture NX.
My problem is I've tried for months with my RAW files imported into Aperture and cannot get Aperture to come close to the quality and look that Capture NX gives me right out of the camera and then right out of Capture NX with no adjustments made whatsoever. I open the NEF in Capture NX, it looks great, and I do a batch save as JPG, and I'm done.
I'm thinking Aperture is a powerful app, I should be able to at least come close to what Capture NX gives me right off the bat. Has anyone been able to save a collection of image settings in Aperture that they can them stamp onto their Nikon RAW files?
I've attached a link to a gallery that shows a NEF in Aperture and that same NEF saved as a JPG in Capture NX then imported to Aperture. I cut off the bottom half of my niece's head for privacy reasons if your wondering. I'm shooting with a Nikon D80 by the way. My goal of course is to make that NEF in Aperture look like the JPG that comes from Capture NX.
http://gallery.me.com/joshuagarrett#100255
Thanks
Joshua

Joshua,
For what you are looking for, this link may be of interest. I haven't tried it, but it looks like it could solve your problem. I'll probably give it a try myself at some point.
http://brushedpixel.com/
Regards,
Simon

Similar Messages

  • Public workflow challenge for Appleture? A Shootout: Aperture vs. CS2/ACR

    How about it?
    A start to finish shootout from CF cards to sorted finished files ready for proofing.
    Two equal G5 powermacs
    - DC 2.3 Ghz
    - 4 GB RAM
    - separate 7200 RPM SATA drives for library/scatch
    - NVIDIA GeForce 6600 with 256MB GDDR SDRAM
    - 23" Cinema display
    - FW CF card reader
    On each machine is a seasoned power user of both Aperture and CS2.
    Each has eight 2GB CF cards full of D2X shots from a wedding, 400-600 NEFS.
    Points are given for:
    -SPEED (obviously)
    -Quality of output
    -Praise spouted by user(i.e. "Sweet!" "Yeah!" "Nice!" and "Beeaauutiful!!")
    Points are deducted for:
    -Number of pauses
    -Spinning beach ball of death sightings
    -Curse words spouted off by user
    After CS2/ACR wins, we could try it with the Aperture machine as a fully loaded Quad Mac with 16 GB RAM against the above CS2/ACR machine.

    Thanks for the movie link. I don't know where you found the index page for that on the Adobe website (I couldn't), but I just flat out guessed the URL for the second one, which is here.
    I took my time getting back to this, but I now have a fully informed opinion on Bridge versus Aperture. I guess I'm an oddball going from Aperture to Bridge, since almost everyone else will be doing the opposite.
    I did find Bridge to be way stronger than the previous CS browser, but two silly little features (or lack thereof) really got to me, as did one potential trap.
    First, note how in that second movie Brown points out that you can use the cursor key to go between images in the RAW dialog. I consider that very important for workflow. I hate having to mouse between. What he didn't point out is that once you mouse into the adjustments are of the RAW dialog, your cursor no longer works for navigation; rather, it will just move the insertion point around inside the adjustments box. I found that very annoying. If anyone knows a quick key for getting back to navigation, please let me know. The quickest way I found was to click in a gray area below the preview image to get the focus back out of the adjustments panel, at which point navigation on the cursor keys resumed... While you may not consider this as important as I do, this is a big advantage to Aperture, which definitely can go shot-to-shot faster than Bridge for this one simple reason.
    Secondly, the Bridge demos focus on studio shoots that are arbitrarily uniform. When you're dealing with more live non-uniform material, there's more of a need to quickly grab the "last shot" settings as fast as possible.... In Aperture, I would say that the lift/stamp way of doing this is way faster (because of keyboard shortcuts) than using the Syncrhonize button in Bridge. In fact, I would say that the CS way of doing this was faster (though less versatile/configurable), because you could just select "previous conversion" faster than you can Option-click the Synchronize button in the new one (the Previous Conversion method does not work when multiple images are open in the new/improved RAW dialog, apparently because a "conversion" has not actually taken place until you click, at minimum, the Done button; therefore the "previous conversion" you get might be from a prior shoot; thus what ACR should to is have a "previous image" choice added).
    Now to the big trap that I fell into.... In an attempt to work in the "all files always open" mode that Aperture pulls off, I opened my entire wedding of approx 600 files in the RAW dialog all at once, and I worked them all that way for over 4 hours. Then right at the end when I was ready to save, I had the bright idea to use the Finder to verify the existence of my XMP files... at this point I learned that the XMP are not created until you click Done, and thus that my entire effort had been highly at risk during 4 hours of editing. I did a Select All with intention of saving them all out at once, then accidentally bumped something (I still don't know what), resulting in a global adjustment to all the 600 hundred which blew away all the other adjustments I'd spent 4 hours making... Mind you that this is ultimately user error, and I consider such par for the course on the first day of new software, so I had no anger (my girlfriend witnessed this moment and said it was "very Zen" of me, but I figure it's just experience in the digital photo world). Three hours later (having gotten faster at it) I had it all redone again... The lesson here is to click Done more often to write out your XMPs, which in the new RAW is equivalent to doing a save of your work. That way if you accidentally bump your whole shoot out of adjustment, you can Cancel back to your last "save." In this respect Aperture is safer for going Shot-to-Shot, since the lift-stamp design makes it more difficult to whack your entire shoot than the more free-wheeling design of ACR does (I realize this is a tradeoff and that there are appropriate moments for free wheeling, too). The secondary lesson is to open your photos in smaller groups. I ended up settling on groups ranging from 25 to 100 as appropriate based on lighting environments. However, if you break into smaller groups, it's no longer quite as slick as Aperture in terms of shot to shot... BTW, with the massive support that Photoshop usually has for Undo and History, I was surprised that ACR did not support an Undo of my accidental mass edit (that that yourself).
    Obviously Bridge is a more mature program overall (which other threads have covered, so I won't bother repeating any of that), but I think Aperture shows some clear advantage for fast shot-to-shot editing. I'm not convinced that the new Bridge/ACR combo is faster for this (temporarily discounting the white balance thing, of course). I could not figure how the new Synchronize dialog in ACR (which I much enjoyed) could do anything in excess of what the lift/stamp engine in Aperture can do in that it also allows you to select just what you want to transfer (ignoring the known cropping issue for now on this point).
    In the end, I'm definitely glad I upgraded to CS2/Bridge, because I was having a hard time relating to how much love there is for it here, and I do like it a lot (especially that I can easily change the RAW Defaults for my camera to make them "pop" more by default like in Aperture). It's safe to say that I will do some things in Aperture and other things in Bridge/ACR as appropriate. Though I've already delivered jobs converted in Aperture, I think I've settled into a workflow that uses Aperture's superior sort and compare features to make my "cut," then export the selects to Finder for use in ACR, then optionally imported back into Aperture later as finished JPEGs. This is a very simple workflow, so I don't get all the bitterness expressed over it by some here in other threads... I will certainly do this until the shadow noise and parquet things get worked out.
    G5 dual 2.0    

  • I have a 3 year old MacBook Pro with MAC OSX 10.6.8, iPhoto '09 version 8.1.2 and have downloaded two software programs: one is Aperture 3.2 and the other is Photoshop Elements 9 (which I got from a friend who didn't need it). I am totally happy with the

    I have a 3 year old MacBook Pro with MAC OSX 10.6.8, iPhoto ’09 version 8.1.2 and have downloaded two software programs: one is Aperture 3.2 and the other is Photoshop Elements 9 (which I got from a friend who didn’t need it).
    I am totally happy with the way iPhoto organizes my photos and how I can work with iMovie to create slide shows with music from iTunes, etc.
    I have been shooting mostly high resolution jpegs and I continue to learn more and more about photography, post processing etc. I realize that the small adjustments I can make in iPhoto are good, and are adequate most of the time. However, a have started to experiment with shooting RAW images and would like to go the next step, ie. post processing.I am totally technically challenged and need SIMPLE, INTUITIVE programs and am certainly NOT anywhere ready for Photoshop CS whatever!
    After having these programs sit on my computer, I decided to try to see if I could figure them out. When I opened Aperture, this is what first comes up.
    “Welcome to Aperture 3.2
    Your library needs to be upgraded to work with this version of Aperture. Once upgraded, you will not be able to use this library with previous versions of Aperture.
    Upgrading a library from previous versions of Aperture 3 generally takes a few minutes or less, though larger libraries will take longer. After that, Aperture 3.2 will upgrade your library's thumbnails, but you can use the application during that time.
    Tip: To open a different library, quit Aperture and hold the Option key down while starting Aperture
    Current Library Location:
    Jadzia (home)   -----Pictures------Aperture Library
                                                      QUIT             UPGRADE”
    I have heard horror stories  about moving your entire library to Aperture, ending up with 2 libraries, etc. etc. hence my previous reluctance in attempting Aperture. In addition, many of my photography friends are saying: Go with Lightroom 3.....you’ll love it!
    So here is my dilemma.  I don’t want to mess around with my iPhoto library. All I want to be able to do, is to isolate a few photos, export them to Aperture, Elements, and work on them there, then bring them back into iPhoto.
    Can I do this? Should I forget about Aperture and Elements and look at purchasing yet another program like Lightroom?

    Export those few photos via the File ➙ Export ➙ File Export menu option with Kind = Original to the Desktop.  Then import them into the Aperture library. That would keep one copy in your iPhoto library and another in your Aperture library to edit, etc.
    You can use Photoshop Elements 9 from within iPhoto as your editor of choice. However, if you edit a raw file in iPhoto with PSE9 the resulting edited version must be saved outside the iPhoto Library and imported back in as a new file.  For editing jpegs just do a Save (not a Save As) and it all will be kept within iPhoto. 
    Using Photoshop or Photoshop Elements as Your Editor of Choice in iPhoto.
    1 - select Photoshop or Photoshop Elememts as your editor of choice in iPhoto's General Preference Section's under the "Edit photo:" menu.
    2 - double click on the thumbnail in iPhoto to open it in Photoshop.  When you're finished editing click on the Save button. If you immediately get the JPEG Options window make your selection (Baseline standard seems to be the most compatible jpeg format) and click on the OK button. Your done. 
    3 - however, if you get the navigation window
    that indicates that  PS wants to save it as a PS formatted file.  You'll need to either select JPEG from the menu and save (top image) or click on the desktop in the Navigation window (bottom image) and save it to the desktop for importing as a new photo.
    This method will let iPhoto know that the photo has been editied and will update the thumbnail file to reflect the edit..
    NOTE: With Photoshop Elements  the Saving File preferences should be configured as shown:
    I also suggest the Maximize PSD File Compatabilty be set to Always.  In PSE’s General preference pane set the Color Picker to Apple as shown:
    Note:  to switch between iPhoto and PS or PSE as the editor of choice Control (right)-click on the thumbnail and select either Edit in iPhoto or Edit in External Editor from the contextual menu. If you use iPhoto to edit more than PSE re-select iPhoto in the iPhoto General preference pane. Then iPhoto will be the default editor and you can use the contextual menu to select PSE for your editor when desired.
    OT

  • Performance and Usability Problems-Aperture 3.1.3 and 10.7.1

    Late 2009 iMac
    Quad Core i7
    8 GB RAM
    512 ATI GPU
    Nik Software Complete Collection Plugins—all updated
    I’m guessing this is due to memory leaks, but Aperture is crippled with 10.7.1. On my great iMac, Aperture now runs like it did when I ran Aperture 2 on a 2004 PowerBook G4.
    With Snow Leopard, I had none of these issues.
    With Aperture idle, it uses up to 2 GB real memory and 3 GB virtual memory. With it idle, it generates MBs of page outs and swap used. If I start to use it for adjustments, even minor ones, page outs and swap used increase dramatically. For example, last night after editing and adjusting a project of images, page outs were just under 5 GB. I’ve reverted to the old habit of rebooting to clear page outs and swaps. Last time I had to do this was with the 2004 PowerBook.
    While actually using Aperture for edits and adjustments, response to almost any input is slow, with conspicuous delays. Even checking and unchecking an adjustment brick causes a considerable delay between the click and when the change is visible.
    Again, with Snow Leopard, Aperture was a bullet with current configuration. I just ordered 8 more GBs of RAM in hopes that this will help until Apple fixes Aperture.
    Anyone else having such considerable performance issues with Aperture 3.1.3 and 10.7.1?
    Thanks

    jcrosby wrote:The "individual setup" argument is an oversimplification. With relatively current hardware, I can reproduce very poor performance when running Aperture in Lion in either 32-bit or 63-bit mode (though the patterns change a bit), and so can many others.
    John-
    Actually I do think it is about individual setups. The kinds of complaints expressed in this thread have been going on literally for decades.
    Starting with early-days Photoshop then later Aperture I have observed the challenges of heavy graphics apps with hardware/RAM/OSs/app versions. We have always been able to reproduce poor performance, because apps/OSs generally do evolve to be more demanding.
    IMO our goal is to help individual setups tweak to achieve non-poor performance while we wait for stronger hardware, or an OS improvement, or an app improvement, or money to buy more RAM, or whatever. IMO it really is an ongoing individual-setup (e.g. last year I was running a 2006 C2D MBP with a max of 3 GB RAM requiring constant tweaking) issue.
    Today I run Aperture under 10.6.8 on a 2011 MBP with SSD and 8 GB RAM and it rocks. I would consider 10.6.8 to be one of the tweaks that folks might do if all the other tweaks (like add RAM and run 32-bit) fail to achieve non-poor performance.
    -Allen

  • Consolidate multiple iPhoto libraries to Aperture

    I recently purchased Aperture 3.2.2 in order to perform a consolidation of my various iPhoto libraries. I primarily have two libraries, one on my MacBook Pro which contains photos from about the last 2 years (and is about 220GB), and one on my old PowerMac G5 which contains a few more years worth of photos, and size is difficult to determine as that one is partially managed (at about 130GB) and partially referenced (most of the older photos are referenced).
    To add to the complexity, I find it very difficult to tell exactly where the referenced photos are in iPhoto. When I go to open a referenced photo that is unavailable, iPhoto gives me the equivalent of a blank stare. If it would at least tell me the expected drive (of the few external Firewire or USB drives I have), I'd be able to connect and point to it.
    As I have keywords and stars for quite a few of my photos, I'd prefer to avoid going the route of pulling in the original photos rather than trying to import the iPhoto libraries.
    The more recent library (on the MacBook Pro) seems to have imported to a fresh Aperture library successfully. The library from my PowerMac (connected in Fireware target disk mode to the MacBook Pro) got about half way through the import process, and then proceeded to hang in limbo doing nothing but spin.
    Ok so
    a) Best way to bring in the remainder of this other iPhoto library? (just trying to import and not import duplicates does not seem to work, it looks like it's trying to bring in the whole thing again)
    b) Best way to resolve the challenge of finding and importing all referenced images, even if they are residing on unattached drives? Quite honestly I'd be happy to export a spreadsheet of the metadata with photo names, dates, and filepath references, if that was possible, just to know where things are supposed to be as far as iPhoto is concerned.
    Thanks :-)

    Referenced Libraries on iPhoto are a bug bear. Referenced Libraries on iPhoto where the library is on one volume and the original files on another are a disaster waiting to happen - or in your case, happening rght now. iPhoto 09 and earlier uses aliases to track the location of the actual file, and these break if you move the file after importing, when the file is on another volume.
    iPhoto has no tools to fix this problem.
    You're not going to be able to get this material into Aperture until you do.
    No point in hoping that iPhoto will magically provide the missing information, you're just going to have to make all the drives available to it. If it still can't find the images then you'll need to use an app like  FileBuddy to fix the aliases.
    iPhoto has no ability to export a spreadsheet with the data you require.

  • Best Practice for Installation of Both Leopard and Aperture 2 upgrade.

    I've finally bought the bullet and purchased both Leopard and Aperture 2.0 upgrade. I've tried searching for a best practice to install both, but haven't been able to find one--only trouble shooting type stuff. Any suggestions, things to avoid, etc would be greatly appreciated. Even a gentle shove to a prior thread would be helpful. . . .
    Thanks for pointing me in the right direction.
    Steve

    steve hutchcraft wrote:
    I've tried searching for a best practice to install...
    • First be really sure that all your apps work well with 10.5.3 before you leave 10.4.11, which is extraordinarily stable.
    • Immediately prior to and immediately after every installation of any kind (OS, apps, drivers, etc.) got to Utilities/Disk Utility/First Aid, and Repair Permissions. Repairing Permissions is not a problem fixer per se, but anecdotally many folks with heavy graphics installations (including me) who follow that protocol seem to maintain better operating environments under the challenge of heavy graphics than folks who do not diligently do so.
    • When you upgrade the OS do a "clean install."
    • RAM is relatively inexpensive and 2 GB RAM is limiting. I recommend adding 4x2 GB RAM. One good source is OWC: http://www.owcomputing.com/.
    • After you do your installations check for updates to the OS and/or Aperture, and perform any upgrades. Remember to Repair Permissions immediately prior to and immediately after the upgrade installations.
    • If you are looking for further Aperture performance improvement, consider the Radeon HD 3870. Reviews at http://www.barefeats.com/harper16.html and at http://www.barefeats.com/harper17.html.
    Good luck!
    -Allen Wicks

  • Question about setting up a workstation with Aperture 2

    hello, I hope I will get some help from here.
    I guess first I should list the things I have, this will make it easier. I have a Macbook Pro with 10.5.6, a Samsung 24" monitor, Aperture 2, Photoshop CS4, CANON Pro9000 Printer, and Pantone Huey Screen calibrator.
    So I already have both my screen (macbook Pro's and Samsung's) calibrated. My question is about how to correctly set up my printer.
    I went on Canon's website and try to download the driver for the CANON printer, But I see there is 3 different version for the driver, i am not sure which one to choose. One is for 10.3.9 and above, one is for OSX CUP (which i donno what it means).
    and do I need to install any of the canon software or plug-ins? I thought the printer color profile is in the driver as well. and aperture should pick that up fine. but for max quality printing, am i better off with the canon software? if so which one should i USE? Easy Photo Printing EX or Easy Photo Printing PRO?
    last... I guess it will be nice if someone can point me the right steps to make a print after I have done everything I want to in Aperture. if you guys can give me a step by step guides for printing from Aperture 2 to Canon Pro9000 with Canon Photo Paper Pro II. and is photoshop is must have in the printing process? I really would love to stick with Aperture as much as possible. but again, quality go first...
    Thank you for reading my post, and thank you even more for replying.

    Challenging, yes, here is a link to a podcast on the O'Reilly website, hope this helps, I found it very useful. I actually subscribe to the podcast (via itunes) and find that there are some great topics.
    http://digitalmedia.oreilly.com/pub/a/oreilly/digitalmedia/2007/02/13/insideaperturepodcast-9.html?page=last&x-maxdepth=0
    Joe Schorr on Color Management in Aperture
    Inside Aperture Podcast 9
    by Derrick Story
    02/13/2007
    Joe Schorr, Apple Senior Product Manager for Aperture, covers color management in Aperture 1.5.2. He discusses the three basic areas that photographers must address in order to have consistent color throughout the workflow: Screen calibration, correct settings in the print dialog box, and adding profiles to exported images. There are some nice tips in this chat, including how to use on-screen proofing in Aperture. Derrick Story interviews Joe in this exclusive O'Reilly Media podcast. (Inside Aperture, Feb. 13, 2007: 18 minutes, 18 seconds).

  • Best way to start with Aperture, importing thousands of images at once?

    I'm evaluating Aperture 2 on my MacBook for my DAM workflow going forward - right now I'm using the Bridge application paired with Photoshop and Adobe Camera RAW on my PC. I find the DAM and sorting functionality to be challenging/lacking/not intuitive for me under Bridge and I've been using it for years at work and home.
    In taking a look at the trial of Aperture, I've tried the obvious thing of trying to import all images on my system under the Pictures directly, but it really doesn't like to do that. I know there are a few thousand in the JPEG directory and a few thousand in the RAW directory, but it still doesn't add up to the 10,000 limit (or was that 100,000?) that it complained about when I pulled up the program for the first time and simply tried to have it import the media on my entire hard drive.
    I really don't like using Picassa, but I do like the fact that it found all the images on my hard drive for me, and allows me to do basic searches and image tweaks. There really should be a simple way for a photographer to set Aperture up with the existing (legacy? pre-Aperture?) image base which he's already collected. I have almost ten years worth of images that I want to go through and I seriously do not want to go through each and every day's worth of images (folder by folder) for ten years without some sort of automated process to go through them and pull them in.
    Any ideas? Any plugins? I realize that, going forward, if I choose Aperture as my primary DAM and initial tweaker, as opposed to say Lightroom, I'll have the Automator tools to pull down images from my various cameras and place them into projects automatically.
    Also, just wanted to mention that Aperture has crashed a few times on me and even, once, deleted my entire Picture library (even though it claimed in the message it would only delete the links to the images, not the images themselves). Luckily, I'm insane with my backups, and was able to restore to a point prior to the Aperture "catastrophe" in a few minutes...but still. I want to be able to trust my programs and it lost a few points there....
    Any tips would be much appreciated. Thanks!

    I think what you're looking for is File >> Import >> Folders into a Project. The top level folder will be imported as a project, and sub folders will create albums within that Project.
    With that many images, I would choose the option to keep the images in their current location. (Unless that location is a hard drive formatted FAT32.)
    If you have side car files, most of the IPTC metadata will come along, but not ratings.
    I don't recommend placing the whole thing into one big project. You can keep the organizational structure you have in the finder in your Aperture Library if you do a little planning.
    All that being said, do it in chunks not all at once.
    DLS

  • Prints Managed By Aperture Too Dark/Red; Printer Managed Match Display

    I did a Startpage.com search and found this archived discussion: https://discussions.apple.com/thread/1378192?start=0&tstart=0. It has lots of suggestions but before I tried any I did a little experiment: I told Aperture 3 to allow the printer software to manage the color.
    The result: the print essentially matches my display. The Aperture-managed print is too red and dark. Go Figure...
    I'm trying to understand why Aperture is botching the print job while the HP software gets it spot-on. Theoretically the Aperture color-managed prints should be better than the HP software-managed prints.
    My hardware: Mac Mini and 10.8.3. HP Photosmart 8450 printer. NEC 2490WUXi2 display. I am using the stock NEC display profile because it is so darn good. My option is software calibration but nothing I have created has come close to the NEC profile. I have checked the NEC profile against various online display checkers and it looks good, so I see no reason to invest in hardware calibration. sRGB images exported from Aperture for Web use look good too.
    When using Aperture 3 "Printer Managed" color management is automatically disabled. I select the proper HP paper profile. The image looks good on the display. The print looks not so good...
    When using "Printer Managed" the only automatic setting that I had missed in the HP software was automatic sharpening; I'm going to disable it and see what happens. The only thing I change is the color setting from sRGB to Adobe RGB 1998. Otherwise I stick with the correct paper profile, select "Best" or "Maximum DPI" and hit print.
    I would say that my test image is challenging to reproduce: skintones, light blonde hair, deep red/purple color in the clothes.
    It's been a while since I printed from Photoshop CS3 but prints managed by that application look fine. I also use Nikon Capture NX2 but I don't recall using it to print. I'm going to test it later.
    Any thoughts/feedback? At this point it looks like I should just stick with using the HP printer software. But the question remains: Why are the Aperture prints sub-par? Is it me or is it Aperture?

    Honestly, it's probably your calibration.  Saying it "looks good" with the software profile is completely subjective.  If you don't measure the display, it's all guesswork.
    Aperture can print fine, with its drivers.  You do have to ensure you're not double color correcting (i.e. Aperture AND the printer drivers, which will double down the adjustments and make things look bad), but if you have stuff set up right and colors are bad, then you really can't go to step 2 without doing a hardware calibration.

  • Aperture Crashing

    I posted this a few days ago, but I am coming to my wits end. In the last 3 days, Aperture has crashed over 20 times. Originally the crashes seem to coincide with Time Machine backing up, but this is not always the case. Aperture has crashed when I have been away from the computer (with or without other programs open), when exporting JPEGs from Aperture to a Finder folder, and when editing RAW files in Aperture. I am not using plug-ins and am running Aperture 2.1.1. on an iMac with OS X 10.5.5. and 108GB of available memory (total 300GB). I have not had this problem before with Aperture and it only started last weekend. I have not loaded any new programs between installing Aperture 2 and last weekend. However, I have started to store my photos on an external hard drive rather than in the Aperture library. Any help much appreciated.

    You have not described your setup, but first thing would be to fully upgrade the OS to 10.4.11.
    • Immediately prior to and immediately after every installation of any kind (OS, apps, drivers, etc.) go to Utilities/Disk Utility/First Aid, select the boot drive and then Repair Permissions. Repairing Permissions is not a problem fixer per se, but anecdotally many folks with heavy graphics installations (including me) who follow that protocol seem to maintain better operating environments under the challenge of heavy graphics than folks who do not diligently do so.
    • When you upgrade the OS do a "clean install."
    • RAM is relatively inexpensive. IMO folks with laptops and iMacs should have max RAM on board. One good source is OWC: http://www.owcomputing.com/.
    • After you do your installations check for updates to the OS and/or Aperture, and perform any upgrades. Remember to Repair Permissions immediately prior to and immediately after the upgrade installations.
    Good luck!
    -Allen Wicks

  • How can i use aperture 3 from my macbook on my macbook pro?

    i had a macbook with aperture 3 on it and tried to reinstall the disk on my new macbook from but when i click to open the program is doesnt work. i am a photography student and NEED this to work PLEASE HELP ME thank you!

    im kind of mac challenged aha - i shouldve mentioned that - but this is the error that keeps coming up "Check with the developer to make sure Aperture works with this version of Mac OS X. You may need to reinstall the application. Be sure to install any availbale updates for the application and Mac OS X."
    would your suggestion still work you think?

  • DxO Optics Pro - Aperture plug-in?

    Hi,
    The Apple list of plug-ins includes DXO Optics Pro.  I've got a trial version of v9.0 & have it running fine as a image editor.  Anyone know how to install it as a plug-in?
    Have searched several places & mostly found that it does not work as a plug-in.  Also found a plug-in called Catapult that's used to shuffle finles back & forth between Aperture & DxO.  Tried dropping the application into Liobrary>Application Support>Aperture>Plug-ins but no luck.  Now I can't remove the alias out of the Library folder.
    So can it really be used as a plug-in?
    Thanks much!

    Here's a follow up for anyone who finds this thread in the future.  I may have answered my own question but since I'm still learning OP9, there may be another feature yet to be discovered.  Optics Pro 9 has a new feature, Export to Application, that might be stretched to consider it a plug-in.  You don't install it as a plug-in or even select it as an external editor from Aperture- it seems designed to be a stand alone preprocessor for your RAW files.
    If you wish to continue using Aperture for DAM, you'd launch OP9 after importing your RAW files into Aperture.  The OP9 Organize tab shows the complete folder structure on your storage drive including all the folders w/in the Aperture container.  Folder names are the cryptic number system used by Aperture so navigating could be a challenge in a large library.  Anyway, this gives you complete access to all your original files so they can be opened in OP9 using its RAW converter for further processing.  Several of OP9 tools such as Prime noise reduction can only be applied to the original RAW file.  After processing is complete, you Export to Application & choose Aperture.  After you've chosen a file format, OP9 will place the file back into the Aperture container as an untitled project & the file will have "_openwith" at the end of the name.  Within Aperture, you can then move the file to any project or folder you wish.
    This certainly makes round tripping easier but not as convent as say NIK plugins or what the plug-in Catapult apparently does - put the file back into a stack w/ the parent file.

  • Aperture crashes

    I'm running a first generation mac pro with 5GB of RAM as well as Parallels and Windows 7. When I run Win 7 I think it takes up about 2 - 3 GB of RAM here or there.
    I keep getting Aperture crashes even though Activity Monitor seems to show available RAM. Page outs show up right now as 3 GB.
    I'm no expert, new to mac and aperture and getting more ram here shortly.
    however, is there a way to see if I have too much stuff in one Aperture Library or otherwise a way to troubleshoot this?
    Right now I am creating slideshows and the crashing seems to be pretty regular - every 20 min or so.
    thanks

    I cannot speak to that specific machine, but after a restart, without Parallels or other apps running, you (generally) should not be getting page outs with 8 GB RAM.
    • Look under About this Mac and make sure that all 8 GB RAM are shown.
    • Switch to 32-bit operation if page outs continue.
    • In your case the CPU and especially the GPU are limiting to Aperture.
    [Page outs is found under System Memory under the Activity Monitor application.]
    HTH
    -Allen Wicks
    Some general guidelines for operation of heavy graphics applications (specifically Aperture):
    • Only the strongest Macs will provide the strongest operation. Owners of weaker boxes (CPU, GPU, i/o, RAM) or older boxes will experience lesser performance.
    • There is a huge difference in hardware needs among workflows. A heavy pro workflow will only work best on a top well-equipped modern box.
    • As RAM prices continually fall RAM needs will continually grow. This has been true since the beginning of computing.
    OS X has enabled Photoshop, for instance, to take advantage of at least 32 GB RAM for many years even though 32-bit operation limited direct RAM access to ~3 GB RAM.
    • All computers/OSs/workflows are different. Each individual user needs to carefully evaluate (meaning see what the early adopters report) workflow and hardware operation BEFORE upgrading any application or OS.
    • SSDs rock.  All users, all apps will benefit from using a solid state drive as the boot/apps drive. Strongly recommended. RAM-challenged setups will additionally benefit from 10x faster page outs.

  • Aperture performance on MBP 17" 2.16GHz Core Duo

    Hi everyone,
    I've been happily using Aperture for a couple of years and apart from a few niggles I love it.
    I'm using a Macbook Pro 17" 2.16GHz (Core Duo) with 2GB RAM (the maximum) and an after-market 320GB 4200rpm internal hard drive. Running OS X 10.5.8 and Aperture 2.1.4. My hard drive is quite full, about 25GB free space. My Aperture library is about 60GB.
    However I recently upgraded from a 6MP dslr to a 15Mp dslr and at approximately the same time Aperture performance began to take a nosedive. Now opening an image will sometimes beachball for 10 seconds (at other times they open normally in about 2 seconds). Cloning has become a nightmare of sluggishness, just clicking the retouch tool will beachball for 10 or more seconds and every edit will take a few seconds to appear.
    Apart from buying a new Mac, what are my best options to improve performance? Its got so bad I'm starting to think about switching to Lightroom! (I read somewhere that Aperture is limited by the video card RAM, and my card only has 256MB I think. Apparently Lightroom doesn't do this?)
    Thanks!
    Edit: Don't know if it has any relevance, but I have never used Aperture's Vault feature. I don't even really understand it to be honest . I backup my photos online to Mozy.
    Message was edited by: Timothy Houghton

    The file sizes on the 15 MP files are 2.5x larger than on the 6 MP camera. So by nature it's going to be slower.
    What's causing it? Probably a mix of all 3. That machine is 2.5 years old now; things have gotten faster and with larger RAW file sizes it will be taxed.
    You could always see if you could get to an Apple Store and load up a card with a few of your images and see how it goes. Challenge being, new machines are running 10.6 and there have been reports here that Aperture on 10.6 is slower than it is on 10.5 (seems better with 10.6.2 than 10.6.1 but still not sure if it's 100% as fast) so there are a lot of variables going on there.

  • When will Aperture provide RAW support for the Nikon D4s?

    Just got my D4s and can't work with the RAW files in Aperture 3 ... It says 'incompatible file format'...

    Wait and see, the currently available raw support is here.
    http://www.apple.com/aperture/specs/raw.html
    iMac, Mac OS X (10.7.5)
    But even, when the raw supoort for your new camera will have been released, it will probably only be available for you, if you upgrade to OS X Mountain Lion 10.8.5 and at least Aperture 3.4.5. The most recent Digital Camera Raw Support releases have all been released for these versions only:  http://support.apple.com/kb/DL1734
    Give Apple a little time to do a decent job with the raw support. Your new camera is particularly challenging with the high ISO sensor and the excellent low light sensitivity (ISO 409,600). You will want that the raw support can deal with these new features properly. Last year we have seen quite a few threads with complaints about strange blueish or pink colors on raw images taken in low light for new Nikon and Canon cameras.

Maybe you are looking for

  • Report on received goods

    Hello everyone, The issue is about finding a report, which tells which purchase order is completed or not. It shall give the following datas: - PO number - Order date - Purchase Requestor - Vendor Number - Total PO (qty and net price) - Received to d

  • Calling RFC with webdynpro java (in NetWaver Dev.Studio)

    Hi, I have a RFC like below FUNCTION ZSAP_X. *""Local interface:* *"  IMPORTING *"     VALUE(USNAM) TYPE  USERNAME *"  EXPORTING *"      VALUE(PWD) TYPE  CHAR8 1-I want to write webdynpro java application to call RFC 2-Call RFC with USNAM parameter 3

  • After reset can't use as iPod without sim

    I upgraded to a 3g iPhone a while ago and have been using my original iPhone as an iPod without a sim card. I was planning to lend my old iPhone to a friend and thought that I would reset it before giving it to him - so I "reset all data" , which too

  • APPLE PLEASE HELP! Mail hangs after start, address book never launches!

    I've been reviewing postings since friday last week about issues with mail/address book after 10.5.2 and here's a summary: • Symptom 1: Mail launches slow • symptom 2: mail hangs while downloading new mail (in my case from 1 particular account accord

  • Best Practices for Organizational Change Management

    Hooray!  Finally an opportunity to take this forum back to its proper direction of Organizational Change Management topics as we begin to engage with some subject matter experts in OCM. Those interested in having OCM conversations here are also welco