Backup of referenced images

I am new to Aperture. I have my library on my mac and referenced images on an external hard disk. I can backup my library using vault and I can backup my referenced images by copying tmen to another hard disk.
If my fiirst hard disk goes down how do I link the copy of the referenced images back to aperture

Welcome to the forums Jeffrey,
In the Aperture menus you'll find an item called "Manage referenced files".If your drive fails, Aperture will immediately see those files as missing and tag them accordingly. You can then use this interface to relink the photos to your other drive. In fact, you only have to select 1 of the missing files and Aperture will do the rest. You can check it out in the User Manual.

Similar Messages

  • Managing backup systems for referenced image masters

    The manual says:
    +Aperture doesn’t back up the masters of referenced images located outside the Aperture library. *You must maintain your own backup system of referenced image masters.* Aperture does back up the versions, previews, and metadata information associated with referenced images, but not the masters themselves.+ (my bolding)
    So, somehow, I ended up with some images (older, it seems) in the vault but other images (newer) as referenced. An incomplete back up to the vault. I understand how I can move those referenced to the Vault but:
    1) is there a fast way to find and select all the referenced masters for this move? Like a menu item or a button in a dialog box that says "Find and move all referenced Masters to the vault"? Simple eh?
    2) why does Apple not allow you to keep referenced Masters out of the vault but a copy of the Master backed up in it? When it goes to reinstall (hopefully never!), it can just reinstall the whole vault in Aperture - if need be. I could live with this especially if it makes backing up all my Masters easy and recovering all of them assured.
    3) Since #2 is not possible for now - how do people back up referenced files and why do you do referenced over Vaulted or a combination of the two (which is what I have but, not knowing I was doing this)? I would like to be able to look at images on my MacBook Pro but really keep the bulk of the images and editing on a MacPro.
    4) when I imported iPhoto to Aperture, did they all come in as vault Masters or referenced?

    Joseph Coates wrote:
    ...when I imported iPhoto to Aperture, did they all come in as vault Masters or referenced?
    Images are imported according to settings you select. Probably you initially imported using a Managed-Images Library. To import by Reference from within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location."
    ...how do people back up referenced files
    Using any normal data backup method. I like to simply manually Finder-copy to external hard drives.
    and why do you do referenced over Vaulted or a combination of the two (which is what I have but, not knowing I was doing this)?
    Actually the correct syntax is Referenced over Managed. Vault refers to one type of backup routine that does include Managed Masters.
    The primary problem with using a Managed-Masters Library instead of a Referenced-Masters Library is that for almost all modern digital photogs using Aperture their quantity of image files will grow quickly, rapidly taking more and more space on a single internal hard drive if Managed-Masters keeps all image files on a single internal hard drive.
    Hard drives slow as they fill, so unless a multi-drive SATA/eSATA array is used a Managed-Library drive will sooner or later lose performance. Use of Referenced-Masters allows the Library to forever stay small enough not to overfill a single drive.
    Personally I consider separate backup of Masters outside Aperture's Vault protocol a benefit, not a negative.
    Using a Managed-Masters Library works even for for laptop/iMac owners if completed Projects with Masters are constantly purged from Aperture but that is inappropriate workflow for most photogs, and the benefits of using a Managed-Masters workflow are minimal.
    I would like to be able to look at images on my MacBook Pro but really keep the bulk of the images and editing on a MacPro.
    Although various user workarounds exist, the issue of synching your laptop Library with your desktop Library has not (yet) been addressed by Apple. IMO Apple's failure (still) to address this key issue is a travesty; Apple's single-user Filemaker has had that capability since the 1980's.
    I suggest going to "Provide Aperture Feedback" under the Aperture menu and requesting that Apple provide single-user synch capabilities for two Libraries (such as the laptop/desktop setups that you and I both have). Note that it is important to specify single-user, two-Libraries, because multi-user scenarios are entirely different solutions that - unlike single user solutions - are usually very complex and expensive.
    -Allen Wicks

  • Concerns with Dropbox to store/backup referenced images?

    Hi,
    I'm looking for an alternative for my current cloud backup solution (Mozy) since the current scheme requires me to pay 23$ per month for my ca. 260Gb of image data. Since I also pay 10€ per month for 1TB of Dropbox space, I seriously consider to cancel the Mozy subscription and use the available Dropbox space as a cloud-based backup solution for my original images (next to my Time-Machine backups).
    To be clear : I only work with referenced images. I have no originals inside my Aperture library. I do not plan to transfer my Aperture library to my Dropbox. I do not need to work with my originals from multiple computers. I only use Aperture from one single iMac.
    I have read multiple threads about Aperture/Dropbox combinations, but they all cover storing your library on Dropbox. That's not what I intend to do. I just want to transfer the folder structure (where my referenced images are stored when importing into Aperture) to Dropbox.
    Are there any concerns with storing the referenced images on Dropbox?
    Thanks for your help,
    Mitch

    Funky,
    What is the best way to back it up? Just copy the files to another hard drive?
    That will definitely work, but how will you tell what you have backed up and what you have yet to backup? A better solution (if you are using Aperture 3) is to use the backup function when importing.
    I am also using Time machine, I assume that it is backing up attached external drive (I have not "excluded it"), is that correct?
    Well, that's a Time Machine question, but according to the following thread, just because you didn't explicitly exclude it doesn't mean it's not excluded.
    [http://discussions.apple.com/message.jspa?messageID=12222390]
    has anyone had good experiences with on-line backup solutions?
    You should search the forum for a thread with lots of input from the last week or so. There was a lot of talk about some on-line backup.
    nathan

  • Corruption of the Location of Referenced Images

    In other threads we have discussed problems with Aperture becoming confused about which referenced files it is supposed to connect with. Here is my analysis of one aspect of this problem.
    When you have a group of referenced files, if you move some of them to another folder on the same volume or rename them Aperture attempts to find the moved file and change the reference to it. This might be what you want, or it might not, so Aperture ought to ask you whether to change the reference or not. But it does not.
    If the volume on which you have your original files is not mounted, Aperture will mark the files as unavailable but will not change any links. This is clearly the behavior one would expect.
    A problem occurs when your files are missing, but the volume they were on is mounted. This might happen if, for example, if one of your folders had been inadvertently deleted and needed to be reclaimed from a backup disk. In this situation Aperture "reconnects" the references in your Aperture library to what appears to be arbitrary files on the volume. The new references likely bear no relation to the files you really want. This is clearly not the behavior you would expect or want. When this happens it is usually impossible to use the "Manage Referenced Files" command to reconnect the files, because the correct files and the ones now referenced in the database aren't the same size and don't share the characteristics which permit the "Reconnect" button to be enabled when the reference and correct file are selected in the "Referenced File" dialog. Even the "option key" trick which sometimes allows the "Reconnect" button to be forcibly enabled will not work once this happens.
    Obviously, this is a potentially catastrophic issue if a huge number of file references become corrupted in your library. The only way to fix things that I have found is to reimport all of the correct referenced image files, then lift and stamp metadata and image corrections from the corrupt reference entries in the library to the "new" referenced files. This is extraordinarily tedious if the number of files affected is large.
    In any event, this is a serious bug and it should have been found long ago in Apple quality assurance testing and fixed. It ought also to be possible to just hand enter the correct reference to a referenced image in the library if nothing else works.

    Possibly going to settings, general, international, region format, then select the country you are in.

  • Anyone care to write up a workflow solution using referenced images?

    So, I'm having a little bit of a hard time figuring this out, but I think I got something. I'd like others to share their thoughts and opinions about how to get a good referenced workflow going. Maybe we can come up with an efficient method of working on, say, two machines with only one folder of images and a way to archive them efficiently too.
    I'll post what I think I can now do with Aperture 1.5.
    1 - I shoot a bunch of shots, in the field, and download them to my Powerbook
    2 - I rename the raw files in the finder (my preferred choice) and save them out to an external hard drive
    3 - I fire up Aperture on my laptop and import those pix from my external hard drive as referenced images. This does a couple of things: One, it keeps my internal laptop hard drive from filling up and, two, it will allow me, when I get back to my fast killer desktop, to transfer, or work on, the images from this external hard drive.
    4 - I doodle away, in Aperture, on my laptop until I'm happy.
    5 - When finished, I can export a copy of the project I just worked on to the external drive, but make sure that the "consolidate images" option is off (no need to have 2 copies of the RAW file on the same external hard drive). This will give me, on the external drive, a project with all the adjustments (and preview images) along with a folder containing the RAW files. I'll also have a copy of the project on my laptop hard drive as a backup (I suppose I'd have a backup of the raw files on a burned DVD or another hard drive too).
    6 - I get back to my desktop and plug in the external hard drive.
    7 - I import the project from that external hard drive. Since the RAW files are still on the hard drive, there's no problem with the project finding the actual files.
    8 - But, I do not want to work the files from the external hard drive (speed is an issue). So I copy the folder of RAW files to my internal hard drive and delete the RAW files from the external drive.
    9 - Aperture tells me (through the badges underneath the thumbnails) that the RAW images are no longer connected to the project.
    10 - I select all the images in the project and right click (or control click) and choose from the contextual menu, "Manage Referenced Files."
    11 - From the dialog box that appears, I navigate to the internal hard drive where I copied the RAW files to and choose to "reconnect all images." The badges under the thumbnails update to let me know that the images are back online.
    12 - I futz with the images some more and do whatever else I need to do.
    13 - Done. Job finished. No need to have access to RAW files anymore, although I want to keep preview images in Aperture for websites, email, etc.
    14 - At this point I think I can do several things. I can export the project and "consolidate images into exported project," and archive that exported project to whatever medium I use for archiving. Or I can just archive the folder of RAW images and eventually delete them off my internal drive. This last option will leave me with preview images inside Aperture (along with badges that tell me the originals are offline). I can back up that project using the vaults method that comes built into Aperture. That way I'll have several copies of the project (with the JPEG previews) and offline RAW files (also copied and archived) that I can reconnect at anytime I want to in the future. This will help keep my Aperture library smaller and more manageable with plenty of backups.
    How does that sound?

    I tried out something like your flow, though I attempted to let Aperture do the intake step right to the Aperture library on the laptop and then work to a portable drive by exporting the consolidated project (I tried my iPod as a temp drive which worked just ok) from there.
    The G4 17 in - lorez - is pretty marginal for Aperture. Working with a few images was just ok, but I really don't think it's up to a couple of gigs of NEF files. What I wanted to accomplish the same goal - a reference set of pictures on the working hard drives with originals offline and archived in a couple of places.
    But after trying this I'd say your scheme of importing to the portable drive and working in the finder and renaming with ABetterFinderRename prior to any import is a better one. The more I can hold down the Aperture's processing overhead the better. The other thing I plan to try is to use iPhoto for the first look. No messing with the images, but I can look at them and toss out the garbage, do some tagging and then, on the G5, let Aperture import the resulting file structure from the portable hard drive and carry on with your scheme.
    Once the images are to my liking in aperture I can export a finished set for iPhoto on my Laptop for emails and etc.
    After messing with this for awhile, I don't see anything in your workflow that is not going to work.
    I imagine as time goes on that lots of people will be going through all these steps. I hope the designers can figure out some simplifications. A media manager in Aperture, much as the one in Final Cut Pro would be welcome for much of this. Or droplets or buttons with the more tedious bits of the workflow included would be welcome.

  • Managed vs referenced images conundrum

    Hello all,
    I have started using the Aperture 3 trial for about a week and my head is already swimming over the choices to make over managed vs. referenced images. I've read the manual, the "exploring" doc and several posts with respect to this topic and sometimes feel like I'm off to the races, only to then get stuck in the mud. I'm guessing that my case is not all that unusual and hope that someone who has gone down this road can offer up the solution that worked for them and why. I've worked with Aperture on a small set of photos and would not like to import the rest to use it in earnest. Prior to Aperture, I imported about 7000 photos using the camera manufacturer's software, Canon Image Browser, then also Nikon ViewNX. I previously "organized" these by creating a separate folder for each full CF card, which I named with the camera model and the date range, eg. S70-100907-110112. Once I had enough, I burned a CD as backup.
    I have a copy of this organization on my laptop, my desktop and the backup CDs, so for some reason I feel slightly attached to it, though it does not provide much information. For this reason and to more easily be able to see which files I have or have not imported into Aperture (somewhat worried I'll leave something behind), I thought I would use referenced images. I also thought referenced images would allow me to utilize my stack of old 20 - 80 GB hard drives as on & off site backups. I also have a 1 TB OWC external drive that I bought for this purpose and possibly Time Machine (yet another issue to plan out). While copying over the files from the Nikon, I realized that the camera was re-using file names after each upload emptied the CF card. Nikon ViewNX creates a new folder for each upload, so there's no conflict, but I think Aperture may see them as duplicates. I have since asked the camera to use persistent serial numbers for naming files.
    I intend to rate all my images, delete the bad ones, then keyword and improve the good ones. Can anyone who has waded through this type of problem share how they came to whatever scheme worked for them?
    Thanks,
    Scott

    3) How to partition external disks to use with vaults and Time Machine.
    With Disk Utility
    I know you could not tell from the way I worded it, but I want to know how much of the 1 TB external disk to partition for Time Machine, how much for Aperture Vaults. I know to use Disk Utility for partitioning disks.
    A Vault for a Managed Library is a complete back up of the Library. A Vault for a Referenced Library is not much of a back up as you also need a back of the referenced files. Actual saved disk space? Zero.
    I was not suggesting that referenced masters saved any space, just that it made it easier to back up those masters in whatever sized chunks one chooses. I believe that a vault cannot be spread across multiple disks, right? Assuming that is the case, then a large library of managed masters will require a single large partition for the vault. With referenced masters, you can save one set of files/folders to one disk, another set to another disk. One rebuttal to this is that my collection of 20 to 80 GB drives can still be used for archives since the Masters can be read from the Terminal, and therefore backed up using rsync.
    You can only have one Library open at a times. So, go to search for something and sure as eggs it'll be in the other one... It's also unnecessary. You can do a simple keyword to separate the two kinds: 'Snap' and 'Art'. Now you can restrict your searches to either.
    A good point. Also importing files to 2 different libraries becomes a huge hassle. Do I put it in the Art or the Snap library? Did I already? Is it in both? Did I miss it?
    I think one of the best arguments I came up with for managed masters is related to vault maintenance. Deleting bad pictures is a big part of organization. If you delete a managed master, that delete will be carried into subsequent vault backups. If you delete a referenced master, you will need to manually carry that delete forward into your self-maintained backups. This is taken care of if you use rsync with the --delete option, but most people don't use rsync.
    Yes, I'm over-thinking it, probably because of the assumption that once it is done, it's a pain to change.
    Thanks,
    Scott

  • Aperture 3.4.3: Referenced images lost in time machine restore but previews remain

    Dear Aperture Community,
    I recently purchased a new iMac and used a time machine backup of my old iMac to move my files over to the new Mac. All seemed to work well, and I have been using my new iMac happily for a couple of weeks.
    I have Aperture 3.4.3 with about 40,000 photos in my database.
    However, I just noticed that a small handful of semi-recent photos (~100) have a badge showing that "The referenced image’s master has not been found" (the yellow triangle arrow badge). I tried "Locate Reference Files" for all photos to redirect to the new hard drive name, but that failed to locate the ~100 missing images. I tried to inspect the Aperture library by Control-clicking on the Aperture library and choosing Show Package Contents - indeed the ~100 images were not there, but the ~40k other images were.
    I can imagine that this issue may or may not be due to Time Machine, but I certainly never deleted any images. I always import my photos directly into Aperture.
    How can my thumbnails and high resolution previews of the 100 images still be visible in Aperture, and yet the masters be lost?
    I'd like to recover the images. Worst case, I will use Grab to capture the previews, which are of course much lower resolution than the originals, but at least I'll have something...
    Thanks for your help!

    thanks for the reply Frank:
    Masters.  I do not know.  I left it as the default.  I assume that means managed?
    Error message was the LONG error code with the jist of it being related to what sounds like a PLUGIN error. I don't have the EXACT coding right now as I am not home.  I've googled the code +/- other stuff on it and according to discussions here and elsewhere (albeit all archived), it looks like it was related to my plugins. 
    as far as the restore is concerned, I am POSITIVE that the restored library was the NEW library not the original.  But keep in mind, Time Machine only lets me restore the backup to the exact place where the file was before.  I am just worried that somehow Time Machine backup hosed my Aperture library somewhere along the way.  This is why I was wondering if there is something else I need to restore with my time machine backup besides the library file/database itself?
    Thanks for the quick reply.

  • Can i use an old iPhoto library for referenced images?

    I upgraded to Mavericks today (from Snow Leopard) and want to find a way to continue to view + edit images from my old iPhoto library.
    My version of iPhoto is 8.1.2, and is 390GB.  I have also been using Aperture for some time, and now have 3.5.1.  The Aperture library is 71GB of Managed Images.
    I have several backups of the iPhoto library of external disks.  Can I set things up so that the images can be accessed by Aperture as Referenced Images'?
    And if so, will the iPhoto structure (events, folders etc) be retained?

    It's achieveable, but somewhat of a hack, and the best you'll get is something close to your event structure, but not albums.
    I'd really recommend lêonie's approach above.
    However, if you really want to play...:
    There are two main problems to solve.
    1) The files are inside the iPhoto library bundle which is not selectable from the import panel.
    2) You'll have a combination of master, non-destructive edits, and previews. I no longer have an 8.1 library to check so I can't decribe the structure). You'll need to decide if you want to bring in originals and edits (where available).
    You'll need to have a look around the iPhoto library structure; navigate to it in finder, right-click the library and choose 'Show package contents'.
    Explore this until you are happy you know where the images are stored (orginals and edited copies), these are the images you can access directly.
    To make them accessible for import in Aperture, drag any folders your are interested in (eg: originals, masters, previews, etc) to your finder favourites sidebar. This doesn't move them anywhere, it just gives you shortcuts to those folders that reside inside the iPhoto library bundle.
    In Aperture, use 'Import->Folders as Projects' from the file menu. Here you can specify that the images stay in their original location (imported as referenced) and you can use the shortcut on your finder sidebar (created above) to navigate into the iPhoto library to pick up the images.
    You can try the different options for the stucture of the import ('Folders and Projects' or 'Projects and Albums'). 'Folders and Projects' will probably work best as it will give something approximating your import history which may match your event structure, but the project names will likely not match the event names.
    Once you've got them in Aperture, youll probably need to tidy up the structure, but in Aperture you can move and change projects as much as you want withouth affecting anything in the old iPhoto Library. The things that can impact the iPhoto Library are deleting or relocating any of the masters.
    As I say, it's a bit of a hack, and in the long run you will probably be better off by just importing the library and relocating the masters. This will keep your event and album structure and be much cleaner, but it will give you an additional copy of the images, which I suspect is what you are trying to avoid.
    Also, if you get future problems with your images, you'll have to explain all the above or people may have trouble helping you!
    Andy

  • Referenced images on time capsule disk

    hi,
    because i'm running out of space on my mbp's hard disk, I'm thinking of putting referenced images on a time capsule disk, keeping the library on the mbp, wil this disk be fast enough. The network will be "n" and i'll connect anonther disk to it for back up?
    wil this setup be possible?

    The setup is possible but it will be slow, especially if you are using raw or tiff files. Most jpegs are probably workable.
    Just get an external drive for your MBP and connect using hardwire of some type.
    I have my library on my 15" MBP (and yes, I have previews turned to match 1440x1440) so that I can view the overall content of my library - and also share with iWork/iLife suite. My referenced masters are all on external dirve (2x, one being a backup).
    Cheers

  • Referenced Images Say They are Referenced But Are Not.

    Is anyone having the following problem? I have about 4500 images that were Imported into Aperture as Referenced. Have been working with them over the past month. Tried making a Web Journal recently and after exporting the pages, many of the images did not show up in the web pages although the caption did. I went back to my Album and went through the images. The ones that didn't show up in the web pages were very strange looking within the Album. As a thumbnail they looked fine but when I put the loupe on them at 100% it was obvious that they were some sort of small jpeg or something due to lots of jaggies and poor quality. Even though the Reference icon was supposedly fine, telling me it was online since it did not have a yellow warning label, for some reason Aperture was not accessing the original RAW file.
    I now have hundreds of images I have to try and find in the Album that say they are referenced but really are not.
    Prior to this web journal problem showing up Aperture had been showing me many of these files were not online even though the drive was definitely hooked to the computer and I was able to go to the same images via the Finder and actually see that they were there. One minute the overall project registered images offline, I would click on an Album and they would register as Online. Then switch back to the Project and amazingly they register as online. Back down to the Album and it tells me they are off line. Back and forth from project to album and a different icon 50% of the time. I knew something was up.
    I eventually tracked down many of the images that said they were online but by reviewing them it was obvious they were not due to the jaggies I mentioned above. When I would find one like this I went to Manage Referenced Photos and reconnected the image even though it's telling me it is already connected. After doing this to many of the images I reproduced the web pages and they then showed up. I nearly had all the images showing up except for one that I must have missed in reconnecting so I went back to do just that. As I scrolled through the Album and the Web Journal, many of the thumbnails would turn gray and then finally an image would show up. This happened to dozens of images. I found the one that had not shown up in the last export of the web pages, reconnected it (even though it said it was connected) and then exported the web pages again. Unfortunately I was back to square one. Once again dozens of images were now not showing up in the export of the web pages again.
    I just can't believe how buggy 1.5.2 seems to be. I thought maybe it was something to do with Repairing Permissions so I went and did all of that. Still no luck! Anyone else experience anything like this? I'm about ready to give up on this software.

    Victor,
    Yes larger hard drives will help but the day they are large enough to fit in a laptop with a professional photographers entire collection is a long way off and may never happen. There is no reason why Referenced files needs to be so difficult. Two quality programs that handled it with ease was RAW Shooter (now gone having been bought by Adobe) and Photo Mechanic which is superb for some tasks. For Aperture to have this many issues with referencing images is unacceptable and the market place will bear this out. I've quite using the program all together and have gone back to Photo Mechanic combined with IView and Photoshop. There's still room for an Aperture like product but Apple better get moving to make it work better. Microsoft just announced some of the upcoming IView capabilities that will be available next year. Adobe has CS3 and Lightrooom and I'm guessing Photo Mechanic isn't resting on it's heels. I really, really wanted to like Aperture and I worked with it day in and day out for nearly two months. As time went on the Referenced files just kept getting more and more unstable and I lost a ton of work due to it no longer being able to see some of those files.
    MacBook Pro Mac OS X (10.4.7)
    MacBook Pro Mac OS X (10.4.7)
    MacBook Pro Mac OS X (10.4.7)

  • How to move referenced images to a new Hard Drive

    All my Aperture referenced images (about 80.000) are stored at a 300gb firewire HD. That's not enough and I plan to move all my photos to a new HD, 1Tb probably.
    I understand that I can't move the images directly from one drive to another. So what's the easiest and painless way to upgrade and still maintain the integrity of Aperture Library ?

    {quote:title=Bauhausler wrote:}I understand that I can't move the images directly from one drive to another.{quote}
    Well, that's exactly what you can (and should) do. Then use the "Manage Referenced Files..." command.
    Take a look at my answers in this recent thread:
    http://discussions.apple.com/thread.jspa?threadID=1721897
    Regards
    Paul K

  • Moving Referenced Images to a new HD

    Hi,
    I have my 500GB external HD almost full with all my Aperture referenced images.
    I got a new 1TB HD.
    I Would like to move all my original folders keeping Aperture modifications on the images (metadata, adjustments, etc...).
    Can I just copy the content of 500GB HD into the 1TB and somehow give to Aperture the path to the new HD? (the library file is on the computer's HD)
    Thanks!

    You can copy everything and then reconnect the files, but you'd be better off using the File>Relocate Masters... command.
    Ian

  • Exporting projects with referenced images

    I want to import referenced images from an external hard drive, edit them and then export the project in order to archive it. Is this something that I can do now? Will I end up with a bunch of referenced previews in my library and an exported project that can link back up to the master images that are on a separate hard drive?
    Antonio

    No, this only exports a "copy" of your projects and does not remove the master image. It is still in the Aperture Library. I am also trying to find an easy way to move the entire project outside of the library and still maintain a reference link to wherever I move the images to. Any thoughts?

  • Upgrading from Aperture 2-3. What happens to referenced images?

    I'm upgrading from Aperture 2 to 3. I have referenced images on some external hard drives. Will my referenced images be okay and still read correctly from my HD if I upgrade?

    Hi
    I had no problems it retained the Referenced File location info you will have to ensure the externals connected.
    If they are not linked as indicated by a red line through the referenced file icon bottom RH corner
    Select the images that need reconnecting and then go to File / Locate Referenced Files
    You will get a dialogue box which enables you to find the Referenced File/s then click Reconnect or Reconnect All
    I just had to do it because I renamed an external drive
    Hope this helps

  • Loupe Offline for Referenced Images?

    In the Aperture 3 documentation, we get this...
    Even though the masters are offline, you can browse, search, and assign metadata to preview images. You can even use the Loupe to zoom in on preview images, because they are high-quality JPEG files.
    And in Aperture 2, this was correct. Now that I have finally gotten around to upgrading to Aperture 3, I find this functionality is broken. The loupe is displayed as "offline" for referenced images and refuses to magnify my previews (though I can zoom in on them just fine).
    This is a big problem, because i rely on the loupe for sorting images, and don't always have my master images available.
    Is there a way to restore the loupe for viewing previews like Aperture 2?

    In the Aperture 3 documentation, we get this...
    Even though the masters are offline, you can browse, search, and assign metadata to preview images. You can even use the Loupe to zoom in on preview images, because they are high-quality JPEG files.
    And in Aperture 2, this was correct. Now that I have finally gotten around to upgrading to Aperture 3, I find this functionality is broken. The loupe is displayed as "offline" for referenced images and refuses to magnify my previews (though I can zoom in on them just fine).
    This is a big problem, because i rely on the loupe for sorting images, and don't always have my master images available.
    Is there a way to restore the loupe for viewing previews like Aperture 2?

Maybe you are looking for