Aperture access

I can't access my aperture files. When I try i get a message that says 'warning there was an error opening the database for the library...aperture .. ' then it give the only one option, that's to quite.  How do I get to my aperture files ?

Frank,
Have you tried the Aperture Library First Aid Tools?
Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library
I'd try to repair the Aperture Library first, the rebuild, if necessary. Before rebuilding, make sure, you have a backup of the library.
Regards
Léonie

Similar Messages

  • What happens to iPhoto and Aperture access if I do the latest update to iMovie which supports the upcoming Photos app?

    What happens to iPhoto and Aperture access if I do the latest update to iMovie which supports the upcoming Photos app?

    stuckoncc wrote:
    I updated the latest version of iOS software on my Macbook Pro
    iOS is on iPhones and iPads.
    Are you using an iPhone or iPad?

  • Best Practice, Going from iPhoto to Aperture 3

    I'm looking for advice on a best practice of moving from an iPhoto Library to Aperture 3. That is, if I even should do so.
    I know that I can keep the photos in place (in iPhoto) and still access them from Aperture. (Or import just selected photos as needed.) Assuming disk space isn't an issue, would it not be better to import all of the iPhoto library into Aperture and only use Aperture going forward?
    Is there a reason I might want to consider another path?
    Any other setup advice for about to be first time users would be appreciated. Anything from your experiences you'd wish you had done differently etc.
    Thanks

    Welcome to Aperture. The question of whether to use just one photo app be it iPhoto or Aperture or to try and use both has been covered here extensively.
    The short answer is to pick one of the applications and commit to it. Trying to use both in some combination is at best going to make your life miserable and at worst, well whats worst than a miserable life?
    I know that I can keep the photos in place (in iPhoto) and still access them from Aperture. (Or import just selected photos as needed.) Assuming disk space isn't an issue, would it not be better to import all of the iPhoto library into Aperture and only use Aperture going forward?
    Yes you can keep the photos in iPhotos library, you can move them into Aperture library or you could move them to some other place on your disk and have Aperture access them from there. Again if your going to use Aperture then the best advice is to only use it.
    Any other setup advice for about to be first time users would be appreciated. Anything from your experiences you'd wish you had done differently etc.
    Take the time to become familiar with the different possible configurations of the Aperture library. The User manual is a good place to start, they did a good job explaining it all. And of course use this list, there are may good posts if you search for them, and many good people willing to offer advice.

  • Best way to share aperture library over network on two computers?

    I've read several posts about doing this and most recommend using an external HD and just hot swapping. However, is their not a better alternative? Can I not share my library over the network, or just remote connect to the other computer?
    Thanks for the help!

    Hi Terence and Leonie,
    You can run several Aperture on the same computer as long as all Aperture are using distinct libraries.
    What Aperture does is to create a simple lock file in <your Aperture library>.aplibrary/Database/apdb The lock file contains the PID of the process. So not two Aperture could open the same library (although I don't know how good they have manage the concurrent creation, locking, verification of this lock, this is a typical and difficult software engineering problem)
    Anyway, I have not said that Aperture supports concurrent editing. That a file is a database or a simple text file, you have basically the same issues on network or in concurrent environment. So if the folder structure holds simple, flat text file or xml object or databases, it is still a bunch of files (this is a UNIX system by the way ).
    Aperture contains more than one SQLlite file, there are some at the root folder, some under Database/apdb etc. there are also XML files that could be used as database.
    Anyhow, editing a file (SQLlite, XML, txt, doc, etc.) either on a share or locally is plain similar. The drive can fail too, although much less likely than the network.
    Network file edition can have a few shortcomings, but nothing that when known can be blocking.
    Locking files over the network can however be tricky and depends largely on the network protocol used (NFS, SMB/CIFS or AFP just to name a few). In addition, if you import files from /Users/foo/Photos in Aperture (without copying them within Aperture), they might not be visible from another computer or only the previews, as the path /Users/foo/Photos is not "visible" from the other computer.
    What really is a problem when you put a file not locally is the file system type and its features. HFS+ supports extended attributes (metadata), many other file systems support these but the API (how the software, such as Aperture, access this feature) might not be similar, in addition the amount of metadata or their structure might differ from file system to another. And this is where you might lose information.
    A tool like Dropbox is pretty good at maintaining the metadata across different computers, and it has been adapted to do so for OS X specifically (and also for Linux and Windows).
    The second problem is if you would have a Mac and share via SMB (the Windows share network protocol, aka CIFS on recent Windows versions) the library, SMB might not support the reading and writing of HFS+ metadata, thus data loss might occur.
    Apple is just warning us of all these shortcomings, and advise to use local storage formatted as HFS+. Because even a local external disk formatted as NTFS or other file system could be a problem.
    However, power users who understand the risks and limitations of a network share (in general) can create a disk image on a share (even if it is SMB). As for OS X, once the disk image is mounted, it is just like any other local hard disk, it is just "slower" especially latency wise. OS X supports perfectly disk image mounted on a share, it takes care of properly synchronising it.
    Of course, due to the nature of the link between the application data and where they are stored, in case of application or OS crash, the amount of data loss could be greater than when the data are held locally.
    I hope this clarify better my post.
    Note: another shortcoming of having it on the network is: Aperture lock the library by creating a file with a process ID. If the same library is opened from another computer on the network, this other Aperture instance might see the lock file and could perhaps not find the corresponding running process. This Aperture instance might then decide to ignore the lock and proceed with opening the library. This might have some consequences.
    But I haven't developed Aperture so I don't know how it would behave

  • Aperture Facebook Uploader: Both Master and Version

    I've searched the forums and see that others had this problem fixed with 3.1.1; but I'm running 3.1.2 and if I edit, crop and otherwise enhance and make a new version and make that version the stack pick, the uploader insists on uploading both (or multiple) master and versions to Facebook. I have to de-stack the images and delete from facebook, and this then reflects in my project/album.
    What the heck? I should be able to upload one version. And if I choose to delete and unstack, why does it reflect in the master database?

    I don't think Facebook is retaining all the Metadata from images uploaded by any means. However, it's definitely retaining the Version Name - And this is what serves as the caption for the photo in the photo album on Facebook.
    Since updating Aperture to 3.1.1, I no longer get the entire 'stack' or multiple versions of the image uploaded. So the software update for Aperture HAS fixed this issue.
    However, I have now noticed another issue since starting to use the Aperture uploader. I have about 10 albums/galleries on Facebook. All of these were created prior to the Aperture 3.0 release with the integrated Facebook uploader.
    Now when I upload an image and subsequently Aperture accesses my Facebook photo albums, it begins to sync these photos and albums. The Facebook directory that you can see at the bottom of the Library now lists those albums that exist on Facebook and begins to sync those photos. However, when I browse photos by 'date' all those Facebook photos from those albums appear in my Library with the date listed as the date I first viewed them.
    So if I click on one of the Facebook albums in Aperture, let Aperture go through its sync process, then review library "photos" and sort by date, all the Facebook photos I have looked at appear as the most current photos.
    this is not a good thing because I have Albums, Projects etc. that are sync'd with iPhone or Apple TV that include date filters (projects in last month, photos last week etc.) Now all these legacy Facebook photos are appearing on these other devices.

  • Quitting Aperture 2.1.4 trial takes minutes

    Hi, I just installed Aperture 2.1.4 trial over my 2.1.3 trial.
    Basically it works, but quitting Aperture 2.1.4 takes minutes (7 to 8 minutes). During this time, I only see the rotating beach ball.
    It turns out, that the problem is Aperture accessing my Samba share where all the pictures are. If I mount the drive it takes 7 to 8 minutes to quit. If I don't mount the drive, Aperture quits immediately, as expected. Aperture 2.1.3 did quit immediately.
    a) is it possible to uninstall 2.1.4 and re-install 2.1.3? I tried, but it didn't work (2.1.3 does not install after dropping 2.1.4 into trash)
    b) is there a solution to this problem with quitting Aperture 2.1.4 if accessing the samba share?
    I use OSX 10.5.8 on a MacBook Pro.
    Thanks for any hint.

    I have been having the same difficulties since installing Snow Leopard. When I perform a "software update" Aperture updates are not listed. I manually downloaded the 2.1.4 update and was then unable to install it for the same reason as above; the original 2.1 version is not recognized as even existing on the computer.
    Interestingly, I have the same issue with Safari. The program disappeared from my Mac Pro during the upgrade to Snow Leopard and when I downloaded the latest Safari program and tried to install it, the installer informed me that I had to have OS X v10.5.8 or newer in order to install this program; all partitions on the computer were indicated to be unsuitable for installation including the system (10.6.2) partition. This problem persists. So what gives?
    Thanks for any help
    Jon

  • Aperture 3.4.4 crashes with NSRangeException

    My Aperture 3.4.4 crashes all the time a few minutes after startup.
    attached the error message below.
    Someone has any idea to fix this?
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    *** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[NSPathStore2 substringWithRange:]: Range or index out of bounds'
    terminate called throwing an exception
    abort() called
    Application Specific Backtrace 1:
    0   CoreFoundation                      0x00007fff871f6b06 __exceptionPreprocess + 198
    1   libobjc.A.dylib                     0x00007fff8d00f3f0 objc_exception_throw + 43
    2   CoreFoundation                      0x00007fff871f68dc +[NSException raise:format:] + 204
    3   Foundation                          0x00007fff81f3a3ad -[NSString substringWithRange:] + 107
    4   RedRock                             0x000000010a0b693f +[RKFileNamingPolicy fileSafeName:] + 136
    5   RedRock                             0x000000010a261958 -[RKVersion(Imaging) proxyWritePath:] + 141
    6   RedRock                             0x000000010a261edf -[RKVersion(Imaging) absoluteProxyWritePath:] + 28
    7   RedRock                             0x000000010a255b97 -[JPEGFileCacheStore filePathForVersion:key:withWrite:] + 51
    8   RedRock                             0x000000010a329d64 -[IPMiniJPEGFileCacheStore newCachePageLookupForRequest:] + 428
    9   ProXTCore                           0x000000010b88a14e -[XTCachePersistentPolicy newCachePageOnLookupForRequest:] + 136
    10  ProXTCore                           0x000000010b881534 -[XTCacheEvictionPolicy isObjectReadyForRequest:] + 20
    11  ProXTCore                           0x000000010b8872d0 -[XTCacheStore isObjectReadyForRequest:] + 37
    12  ProXTCore                           0x000000010b880b77 -[XTCache isObjectReadyForRequest:] + 28
    13  RedRock                             0x000000010a20b8a2 -[RKImageCache hasThumbnailOnDiskForVersion:style:] + 70
    14  RedRock                             0x000000010a21b12c -[DownsampleFactory cache:cacheStore:onFulfillRequest:intoPageRef:] + 1162
    15  ProXTCore                           0x000000010b882501 -[XTCacheFactory cache:cacheStore:fulfillRequest:intoPageRef:] + 896
    16  ProXTCore                           0x000000010b881388 -[XTCacheBroker cacheStore:fulfillRequest:intoPageRef:] + 51
    17  ProXTCore                           0x000000010b88809f -[XTCacheStore newObjectFulfillRequest:] + 546
    18  ProXTCore                           0x000000010b888657 -[XTCacheStore newObjectForRequest:] + 1034
    19  Geode                               0x000000010b629fc0 -[DGTier2Factory readRequest:intoPageRef:] + 482
    20  Geode                               0x000000010b62a604 -[DGTier2Factory cache:cacheStore:onFulfillRequest:intoPageRef:] + 589
    21  ProXTCore                           0x000000010b881f47 -[XTCacheFactory backgroundFulfillment:] + 532
    22  ProXTCore                           0x000000010b862736 -[XTDistributor distributeMessage:] + 444
    23  ProXTCore                           0x000000010b8620fa -[XTThread handleMessage:] + 342
    24  ProXTCore                           0x000000010b860eb3 -[XTThread run:] + 345
    25  Foundation                          0x00007fff81f5acd2 __NSThread__main__ + 1345
    26  libsystem_c.dylib                   0x00007fff8a28f7a2 _pthread_start + 327
    27  libsystem_c.dylib                   0x00007fff8a27c1e1 thread_start + 13

    Finally, I found both of the cause and the solution.
    The cause :
    (1) in Aperture, upload some photos to Facebook
    (2) in Facebook, update the photos's caption with long foreign characters.
    (3) in Aperture, synchronize the photos with Facebook again.
    This will rename the photo files in Aperture library, and eventually this will corrupt Database/ImageProxies.apdb inside Aperture library folder.
    when Aperture accesses this correupted Database/ImageProxies.apdb file, Aperture just crashes.
    The temporary solution :
    (1) quit Aperture
    (2) delete Database/ImageProxies.apdb file inside Aperture library folder.
    (3) start Aperture
    (4) it will be better rename the master files with only english alphabet to prevent future crash.
        (We can update all the master file names easily by using "Batch Change" menu.)
    Please someone let Aperture developer know this and fix it for next release.
    Regards
    This will help until the next sync, if you do not also fix the captions on Facebook.
    But you never answered my question re the formatting of your drives:
    Are your referenced original master image files on a drive formatted MacOS X extended Journaled?
    Long filenames or ethnic characters in the captions and version names derived from the captions should only matter, if the drive is formatted incorrectly. It would really be good to know, for future similar cases, if all this happened with the library and /or the original files on a correctly formatted drive.

  • Aperture & Facebook Uploader - No Version nor Metadata

    So I'm simply trying to upload a single image to Facebook in Aperture 3.1 via the integrated Facebook uploader. I've edited, cropped and applied metadata (caption, keywords, title etc.) to the photo. Select the version and upload.
    The Master Image AND the Version is uploaded and the default filename is used as the caption. Should be simple enough to select a 'VERSION' and when uploaded only the Version should upload and, of course, the caption should be in place.
    What's up Aperture? Why won't you upload the actual photo I've selected? And please include the metadata!
    Anyone else experiencing this problem. Any ideas?
    Message was edited by: Allan Karl

    I don't think Facebook is retaining all the Metadata from images uploaded by any means. However, it's definitely retaining the Version Name - And this is what serves as the caption for the photo in the photo album on Facebook.
    Since updating Aperture to 3.1.1, I no longer get the entire 'stack' or multiple versions of the image uploaded. So the software update for Aperture HAS fixed this issue.
    However, I have now noticed another issue since starting to use the Aperture uploader. I have about 10 albums/galleries on Facebook. All of these were created prior to the Aperture 3.0 release with the integrated Facebook uploader.
    Now when I upload an image and subsequently Aperture accesses my Facebook photo albums, it begins to sync these photos and albums. The Facebook directory that you can see at the bottom of the Library now lists those albums that exist on Facebook and begins to sync those photos. However, when I browse photos by 'date' all those Facebook photos from those albums appear in my Library with the date listed as the date I first viewed them.
    So if I click on one of the Facebook albums in Aperture, let Aperture go through its sync process, then review library "photos" and sort by date, all the Facebook photos I have looked at appear as the most current photos.
    this is not a good thing because I have Albums, Projects etc. that are sync'd with iPhone or Apple TV that include date filters (projects in last month, photos last week etc.) Now all these legacy Facebook photos are appearing on these other devices.

  • Minimum system requirements for Aperture installation

    I've just downloaded the trial version of Aperture, but it won't install on my G4 desktop running OSX 10.4.8. Looking at this discussion, I'm getting the impression that nothing short of a supercomputer with RAM sufficient for the Cray weather forcasting computer at Bracknell will be sufficient to allow installation of aperture.
    I'll be charitable and assume that Apple wouldn't be so daft as to release consumer software that has more demanding requirements than Photoshop, but I'm ready to be disillusioned. How can I find out precisely what the miminum system requirements are?

    I'll be charitable and assume that Apple wouldn't be
    so daft as to release consumer hardware that has more
    demanding requirements than Photoshop...
    IMO Apple is not daft, and Aperture most definitely is not consumer software. Of course consumers may choose to use and benefit from Aperture so long as they recognize that it is pro software with pro hardware requirements.
    Aperture does have more demanding requirements - referenced to 2006/07 time frame on 2006/07 and earlier hardware - than PS in some ways. E.g., PS fails to take advantage of GPUs for anything other than simple blitting, while Aperture accesses GPU power extensively; hence mediocre graphic cards do not limit PS much but do limit Aperture.
    Aperture is a pro application in a new different graphics space than PS. Unlike decade-old PS, AP evolved recently, with the power of 2008 chips and system architecture and beyond clearly in the sights of design engineers.
    Managing large batches (hundreds per batch) of large (currently in the 10-40 megapixel each range) RAW DSLR image captures fast is a challenge. As of today Aperture clearly is the overall pro workflow speed king in that process. My guess is that with OS 10.5, Aperture v2, and 2007 H2 pro Mac hardware Aperture will start to really show its competence handling heavy pro workflows.
    Pros generally are willing to own the hardware necessary to achieve workflow competency. Consumers have the choice of using a lesser app like Lightroom if they are unwilling to upgrade to strong modern hardware but are willing to tolerate an overall less competent workflow.
    -Allen Wicks
    17" 2.33 GHz 3 GB C2D MBP, 15" 1.67 GHz G4 PB, DP G4 tower; Nikon D2x & D100.   Mac OS X (10.4.8)  

  • Help with Reconnecting Files

    Over this past weekend I was moving, via Relocate Masters, large numbers of images from managed status on my MacBook Pro to referenced status on an external drive (an Air Disk, to be precise). This had gone fine for thousands of images, but Sunday night I returned to the computer to find that it was completely locked up in mid-Relocate, and seemed to have been locked up for a while. I'm not sure what happened, but it seemed bad -- I couldn't get to the Force Quit dialog, or anywhere else. I powered down by holding in the power button.
    Upon resurrecting things, Aperture would not open the library. Long story shorter, I rebuilt the database and was then able to see the library contents again. But then I noticed that many files were "offline." Digging further, and using the Manage Referenced Files box, I discovered that some 3500 files need to be reconnected.
    The Reconnect All button did a little bit of magic for me, but now I've gotten to a point where using Reconnect All only reconnects one file at a time. I was renaming files as I Relocated Masters, and my fear is that this is what has caused the disconnect. *So first,* can anyone tell me that this is what has caused the problem (the problem being my apparent need to now reconnect 3400 files, one-by-one)?
    *Second, and more importantly to me, do I have any recourse beyond reconnecting one-by-one?* Again, the problem seems to me to be that the library file expects a file named image.jpg (or whatever), because the change of the file name to greatimage.jpg that occurred during Relocation did not get written to the library file.
    Many thanks for all help and suggestions.

    Homme dArs wrote:
    I hope someone else can join in with a definitive answer to your problem, but I don't believe you will be happy using the configuration you are attempting to set up.
    Having Aperture access your images via wireless is going to be very very slow, and any connection problems will be very frustrating. I have even abandoned the idea of using wireless backup of image files because it so slow.
    Perhaps someone can help with your immediate problem, but I would strongly suggest you find a way to store your referenced files locally (a firewire drive would be ideal).
    Thanks. I certainly appreciate your thought, and before trying it myself, my instinct was the same as yours. That said, until the present problem cropped up, I have to say it has been quite a good solution. My network is 802.11n, and I've noticed no real lag in accessing the files or otherwise using Aperture with a library stored as this is.
    But yes, I hope someone is able to help me get these 3400-some files reconnected short of one-by-one.
    Thank you for your comments.

  • Referenced and managed files

    I know this is a topic with a wealth of discussions but my search doesn't seem to bring up what I'm looking for.  Can anyone direct me to previous discussions or other web sites that deal with the whole topic of referenced vs. managed files?  Is there a good book to pick up for that?  I want to have Aperture access my photos from an external drive (for freeing up hard drive space) and I need to better understand how to do that.  Yet it sounds like I should be keeping it in Aperture as well via some sort of compressed file (managed?)  Basically assume I know nothing and want to understand the ins and outs of referenced/managed masters.
    Thanks,
    Steve Hadeen

    Hi Steve.
    It's hard to understand -- but not _that_ hard  .  A book is not required.  See if this short description helps.
    Be careful (and specific) with your nomenclature -- it will keep you from getting mired in the bogs of confusion that rim our sun-lit plateau.  Your camera creates files.  You import files into Aperture.  On import, Aperture puts that file somewhere, and thereafter refers to it as a Master.  The Master is never altered.  You control where Aperture puts it (and you can have Aperture move it at any time).  What you see in Aperture is an Image.  Every Image has a Version and a Master.  The Version is a text file containing instructions on how to vary the Master to produce the Image.  The Version of the first Image created by Aperture when it imports a file is essentially null (it contains no information).  When you create a new Version, Aperture names it "Version 2".  (The confusion here is that Aperture encourages the user to call Images "Versions".  This is a bit of a devil's bargain: it helps the casual user, but confuses the careful user.)  You can see the Master of any Image displayed in the Viewer at any time by typing "m" (it triggers the Image/Master toggle).
    All you need to do is have Aperture move some or all of your Masters to your external drive.  Note that you can easily, at any time, convert Masters from Managed to Referenced and vice versa.  Note too that backing up your Library does not back up any Referenced Masters.  You must back up Referenced Masters in addition to backing up your Library.
    Message was edited by: Kirby Krieger -- minor clarification.

  • How can I share a library (or other image files) across computers

    Hi All;
    My wife and I are both freelance photographers. We recently bought aperature ad per the license agreement installed it on my laptop and her mac desktop. We also just bought a 2-Terabyte network RAID storage array.
    I want to be able to pull up the images on the network array from either machine (via aperature)
    What's the best way to do this ?
    Thanks in advance

    First off, even if you are allowed to install it on both computers Aperture will not let you run two copies on the same subnet with the same serial number at the same time.
    Second, Aperture is not designed as a multi-user concurrent access application. The workflows that I have helped people design for multiple photographers do not revolve around accessing the the same library at the same time. They are more like a project check-out/check-in when more than two people contribute to what ends up being a consolidated library. I have monkeyed around and gotten what you ask to work but it is highly inadvisable due to the nature in the way Aperture accesses and modifies the data (a disaster waiting to happen if you access it concurrently). You can share masters but that is pretty much useless if you are working on the same images. If you are not I would suggest something more along the lines of what I have outlined here:
    http://rwboyer.blogdns.com/managing-aperture-2-on-multiple-computers/
    if my new test site is not functioning it is also here:
    http://www.rwboyer.com/RBDesign/Blog/Entries/2008/9/6_Managing_Aperture_On_MultipleComputers.html
    RB

  • Nikon V1 RAW images: strange "unknown image format" message

    Hello,
    I run the latest version of Aperture on my MacBook under 10.7 Lion with a shared iPhoto library. I've purchased a Nikon V1 in late 2012 shooting in RAW (.NEF).
    During the import, Aperture recognized and converted all images correctly. However, a few days later, a strange thing happened: Some of the images display a black  "unknown image format" frame (in German "unbekanntes Bildformat"). This is weird because other pictures from the same series and with the same camera settings are displayed correctly. What I did was to export the broken files and reimported them – everything was okay then.
    Now, the same thing happened again in a different image series. This is what it looks like (first five images are shown correctly, I pixellated them manually before uploading):
    I could surely export and reimport the images like I did before but I'm afraid that this problem might reappear again and again. By the way, I never had this problem with NEFs from my old Nikon D50.
    Thanks for your help
    Christian

    My Camera RAW version is 4.0.3.
    Yes, I am switching between iPhoto and Aperture. The shared library is locally under /Users/Shared where my wife (with iPhoto) and me (mainly with Aperture) access it from our own user accounts. All images are managed on the internal HD, not referenced.
    When I just checked it from my wife's iPhoto account, the images were okay. Only Aperture showed the black frames and interestingly considered the images to be 900x600px.
    I then had to idea to select "Vorschaubild aktualisieren" (presumably "update preview image") from the context menu in Aperture and, to my surprise, it worked Didn't expect that it was a problem with the preview image because the error message suggested something different.
    I will additionally repair the library as LeonieDF suggested. Thanks to you and I hope that this won't happen too often.

  • I have upgraded Apple Aperture from version 2 to version 3 and I'm having a problem with the "Highlights and Shadows" adjustment. According to the user's manual, I should have access to an advanced disclosure triangle which would allow me to adjust mid co

    I have upgraded Apple Aperture from version 2 to version 3 and I'm having a problem with the "Highlights and Shadows" adjustment. According to the user's manual, I should have access to an advanced disclosure triangle which would allow me to adjust mid contrast, colour, radius, high tonal width and low tonal width.
    If anyone has any suggestions as to how to access this advanced section, I'd be most grateful.

    Hi David-
    The advanced adjustments in the Highlights & Shadows tool were combined into the "Mid Contrast" slider in Aperture 3.3 and later. If you have any images in your library that were processed in a version of Aperture before 3.3, there will be an Upgrade button in the Highlights & Shadows tool in the upper right, and the controls you asked about under the Advanced section. Clicking the Upgrade button will re-render the photo using the new version of Highlights & Shadows, and the Advanced section will be replaced with the new Mid Contrast slider. With the new version from 3.3 you probably don't need the Advanced slider, but if you want to use the older version you can download it from this page:
    http://www.apertureexpert.com/tips/2012/6/12/reclaim-the-legacy-highlights-shado ws-adjustment-in-aperture.html

  • How do i consiolidate my photo masters in Aperture 3. I have a vault from Aperture 2 but 3 will not access it.

    I use Aperture for photo editing and management and had been working in Aperture 2. I created a vault on my external HD to store my masters in. I had done something to my computer (not sure what) and ended up wiping my internal HD and reinstalling all of my software. After that I was not able to access my vault so most of my masters are basically gone. I attemped to move them with no luck. Frustrated by this point I upgraded to Aperture 3 thinking it would help me be able to get into the vault only to find out that 3 can not consolidate 2 vaults. I do not know what to do at this point but am really bummed to think that my masters may be gone forever. A hard way to learn that nothing in more secure than just saving the photos to DVD prior to Aperture...
    Can anyone give me a clue on how I can recover my masters?

    I don't have Aperture 2 so that I could check, but Aperture 3 vaults in  Mt. Lion do show the version number in the Finder, like this:
    I will put Aperture 2 on another machine and that work on restoring the vault from there,
    If you did all available upgrades and your vault is recent, it probably will have been created with the latest available Aperture upgrade, AP 2.1.4.
    If you can restore the library this way, back it up, and then rebuild it, before moving it to your SL machine. To rebuild an Aperture library, hold down the Option and Command keys while opening your library in Aperture 1.5 or 2, then click the Rebuild Now button..
    See the Release Notes on upgrading - scroll down all the way to the bottom:  http://support.apple.com/kb/TS2518
    Regards
    Léonie

Maybe you are looking for

  • Backup/save/restore voice memos iPhone 5c and iTunes 11.4

    In the music tab I have it checked to include my voice memos but I can't find them in iTunes.  I search by name; nothing.  No playlist, no section in music.  They are nowhere.  I can use iBrowse to grab them, but they are all just a bunch of numbers

  • When printing PDF file, have FORM TEXT in text fields

    When I print a PDF file, I get { FORMTEXT } in all the text fields (as well as { FORMCHECKBOX } for where the person would circle an answer) and I don't know how to turn it off. Appreciate any help. I also get symbols where there should be a regular

  • Multiple instances of Apache

    We have to default setup. I would like to know if it is possible to run another instanace of Apache (on another port on the same system). Can this be monitored with Server Admin ?

  • Why are calendar subscriptions not up to date?

    When I select Subscriptions from within iCal, the available options are dated 2010 and 2011, even in the Most recent list. Why are more current calendars not available? Also, I have downloaded the US Holiday calendar before.  It updates the holidays

  • Mac app store, can't get rid of an app that I did not buy and it's listed under an unknown Apple ID

    Hello guys, I have a very rare issue with my Mac App Store application. Whenever I want to make an update of a piece of software that I've bought, Angry Birds apears as if I had it, when I haven't. The thing is, I want angry birds to desappear from m