Aperture Vault saving different sized previews

Hi all,
I am trying to back up my rather large (1.04TB) Aperture managed library to an external hard drive vault. Trouble is that when "generating previews" message came up at the bottom of Aperture the vault size started growing way bigger than the 1.04TB original library. It is currently at 1.56TB and growing slowly.
When I investigated the package content I found the masters folders where EXACTLY the same size so that is a good start but the Previews folder is 506.34GB in the vault versus 440KB in the library (see attached photo). Does anyone know why Aperture is doing this? What would be the best course of action to remedy it? Is there a setting in Aperture I am missing or does Aperture need a preview size to use else it reverts to half size previews? It seems that Aperture is saving half sized previews.. I have made sure that the preview generation was off and I even deleted all the previews before I did the back up. Bit perplexed....

I think I have found an answer to my question..
It looks like you have to force Aperture to regenerate all the previews after you change the setting even if you delete the old previews. I just assumed by deleting them that they were gone. It looks like Aperture looks at the current preview setting for each master so if , as I found out it started with the default "half size" option it will keep that option stored even if you change your preference and delete the old previews. Thus , when I created the back up it regenerated the old setting that was stored . ie. half sized previews..
Looking at it logically it makes sense as you can have some old sized previews and mix them up with a new size going forward. Makes it much more flexible in the long run..
This article explains it as well..
https://support.apple.com/en-us/HT203497

Similar Messages

Backup Storage - Aperture Vault versus Time Machine versus daily SuperDuper

What value does dumping the Aperture library to an Aperture Vault give in addition to running Time Machine to one drive and a daily SuperDuper copy to a second drive with irregular SuperDuper copies to an external drive that can be removed from the machine room.

SImon,
Vault and Time Machine address different needs. Probably you will want to have both.
The advantage of Time Machine: incremental backups of previous versions, very compact storage. And you can integrate it into your regular backup of the whole system and include the regular masters as well. But the disadvantage: Time Machine decides for you, what will be deleted, if the backup drives get full. You do not have control over what will be saved and what not from the previous versions.
The advantage of vaults: You can make full backups of your library for well defined moments in time - snapshots of important states. I'd create a vault, whenever I make a major upgrade of the system at least.
Is there anyway of cancelling a stuck Vault update other than the sledgehammer approach of Force Quit?
If the graphical user interface is unresponsive, like when updating a vault, you can use the Terminal to send the "termination signal" to Aperture: Sometimes this will succeed, even if the "Quit" button does not work:
Look for the Process ID of Aperture in the Activity Monitor (launch Applications > Utilities > Activity Monitor" and click the CPU heading. This will bring Aperture close to the top of the list. Make a note of the PID number in the first column, in this case 66550.
Launch a Terminal window and enter the following command:
kill -TERM 66550 (insert Aperture's PID instead of 66550)
This will send the "Software Termination Signal - TERM to Aperture, the same as pressing the "Quit" button should do, but send it directly, and not from the GUI that is unresponsive. This way I always succeded in cancelling a vaul update without force quitting. Not all processes can be terminated this way, however. The Terminal.app is also in the Applications > Utilities folder.
Regards
Léonie

Aperture Vault Question

Okay, so I am looking to simplify my photo storage process, as I recently got Photoshop and am going to be doing more and more editing and what not.
I also have Aperture that I back up using its vault feature on my external hard drive, creating two locations for all my pictures - within Aperture and the vault on my external hard drive. Is it necessary (aka, would it be a good idea) to keep the original pictures in my home folder/pictures folder? I am hoping to free up space if not necessary.
Also, I would probably end up burning the master images to a DVD from Aperture for a third back up. I may sound paranoid about this, but I don't want to lose anything.
I'm just looking for an easy back-up process for my photos.
Thanks!
Josh

Also, I would probably end up burning the master images to a DVD from Aperture for a third back up. I may sound paranoid about this, but I don't want to lose anything. I'm just looking for an easy back-up process for my photos.
You do not sound paranoid, just prudent. The essence of competent digital photography is multiple redundant backup.
Your Managed-Masters-Library and Vault workflow is fine now but only in the short term because hard drives slow as they fill and using a Managed-Masters Library image files will sooner or later overfill the internal hard drive unless 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 recommend to Manage by Reference with Master image files stored on external hard drives. Especially important for iMacs and laptops with a single internal drive. The workflow as described below uses a Referenced-Masters Library.
I feel pretty strongly that card-to-Aperture or even camera-to-Aperture handling of original images puts originals at unnecessary risk. I suggest this workflow, first using the Finder (not Aperture) to copy images from CF card to computer hard drive:
• Remove the memory card from the camera and insert it into a memory card reader. Faster readers and faster cards are preferable.
• Finder-copy images from memory card to a labeled folder on the intended permanent Masters location hard drive.
• Eject memory card.
• Burn backup hard drive or DVD copies of the original images (optional recommended backup step).
• Eject backup hard drive(s) or DVDs.
• From within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location." This is called "referenced images." During import is the best time to also add keywords, but that is another discussion.
• Review pix for completeness (e.g. a 500-pic shoot has 500 valid images showing in Aperture).
• Reformat memory card in camera, and archive originals off site on hard drives and/or on DVDs.
Note that the "eject" steps above are important in order to avoid mistakenly working on removable media/backups.
Also note with a Referenced-Masters Library that use of the "Vault" backup routine backs up the Library only, not the Masters. Masters should be separately backed up, IMO a good thing from a workflow and data security standpoint.
External drives that are not eSATA (or at least FW800) decrease speed, so your Aperture Library should stay on the internal drive.
When using Referenced Masters the Library does not actually hold the large Master images themselves. That way even a laptop drive can hold an Aperture Library of 100,000 images by referencing Master images that live on external drives. To store Master images by "Reference," in Aperture when you go to Import on the right hand side of the import window you must select "Store files in their current location."
Note that by sizing Previews carefully (I suggest creating Previews manually and only during down time, and sizing to the pixel dimensions of the laptop display) all images can always be viewed on the laptop even when the Masters are off-line.
Good luck!
-Allen Wicks

Aperture vaults - setting up new computer with vault

Hi there.
I have a MacBook with a large aperture vault on a separate hard drive. I have now bought a new iMac. Can I use the vault from my Macbook to set up all my photos on my new machine, thereby saving me hours of work. HELP
Di from Devon

Yes, you can restore Aperture to another Mac from a Vault. Just do not expect it to be quick.
-Allen Wicks
From the manual:
Restoring Your Aperture System
If you buy a new computer or use another system at a different location and want
access to the Aperture library, you can install Aperture and then transfer the library
from your vault (on your backup disk) to the other computer. If you experience
equipment failure or other unexpected events, such as fire or weather-related damage
to your equipment, you can easily restore the entire library to your new computer from
a backup disk.
To restore the entire library from an external backup disk:
1 Connect the hard disk drive that contains the most up-to-date vault to your computer
and open Aperture.
2 Choose File > Vault > Restore Library.
The Restore Library dialog appears.
3 Choose Select Source Vault from the Source Vault pop-up menu.
4 Navigate to the vault from which you want to restore, then click Select.
5 Choose Select Destination from the Library Destination pop-up menu.
6 Navigate to the location where you want to place the library, then click Select.
7 Click Restore, then click Restore again.

Bridge CC - Content Panel looks different than Preview

Problem - Images in the Content panel look dull and desaturated. The view of the same image in the Preview Panel, as well as Photoshop CC, looks fine (ie, like I expect from working with these images in CS6). This applies to NEF, JPEG and PSD files. In the attached screenshot, note the distinct lack of red in the skin tones in the Content Panel compared to Preview. Blues look a little dull as well. This is a PSD file. This image is tagged sRGB, verified in the Metadata panel as well as in Photoshop CC.
I have read similar threads here (where all of Bridge was dull and desaturated), but I don't see anything that mentions the two panels in Bridge displaying images differently.
Background - 10 years as a pro photographer, and I know what I'm doing around a Mac and color management. I finally "upgraded" from CS6 to CC when I got my new Mac.
System -
Retina iMac w/Yosemite. Second monitor - HP LP2475w (Bridge sits on the HP monitor)
Both monitors have profiles generated with an i1 Display and the i1 Profiler application.
Both monitors are using their correct profiles
Steps Already taken (condensed)
1. Purge cache (multiple times throughout the process).
2. Check color cache and cache permissions.
3. Reinstall Bridge at the behest of Adobe support, even though this was a new install.
4. Check that "Always high quality" thumbnails is checked in Bridge (this seems to have no effect either way).
5. Check color settings - NA GP2 in Bridge. Interestingly, the same behavior is exhibited no matter what I select here.
6. Drag Bridge to the iMac display - everything now looks good. Drag back - now BOTH Content and Preview are desaturated. Will stay like this until Bridge is restarted.
7. Recalibrate the HP (Bridge) monitor. No change in behavior.
8. Verify no sidecar xmp for this image, to rule out ACR in the problem.
9. Open Output module to verify that the content panel looks the same way there (it does).
10. Investigate ~user/Library/Caches/Adobe/Bridge CC/Cache/ folders. Wow, the preview for this particular image in /1024/xxxx LOOKS CORRECT (like it does in the Preview panel). So Bridge IS generating high quality previews correctly.
Thoughts -
1. This seems unlikely to be a monitor profile issue. Bridge itself is displaying the same PSD two different ways. A bad profile would make everything on that monitor look wrong, wouldn't it?
2. Some of my images sit on an external drive, but the screenshot here is from the internal mac drive, to try and rule that out.
3. It's not some strange issue with the HP monitor not displaying color evenly across it's surface - if it were, than the screenshot would not show the difference between the panels. I also moved the Bridge window around the display to further verify that color is the same across the whole panel.
4. Maybe Bridge ignores the profile for the content panel - but in the case of no profile, it assumes sRGB (or does it?) which is exactly what this image is. I have tried this with Adobe RGB images and the same behavior is exhibited.
5. Previews are being generated correctly, but do not seem to be what is read off disc to display in the Content Panel.
Any thoughts would be appreciated. My gut feeling is that for some reason, Bridge is not showing me the saved high quality preview in the Content panel. But why?

Is your file tagged? I.e. does it have the proper color profile embedded?
Is your monitor accurately calibrated and profiled?
What are your preferences in Bridge re previews and profiles?

My 3.4.5 has ~ 35000 jpg masters. I have set aperture not to create previews on import and have ensured "maintain previews" is not ticked. Every time I start aperture it insists on creating previews for ~ 4300 images. Why?

Having had the previews created I selected all photos and "delete previews". It did this quickly and no more previews being created. Once aperture is closed and then re-opened aperture immediately sets about creating the previews for the same photos. I don't understand why this should be happening.
This is occuring on my Mackbook Air (Aug 2012) which has 256 GB storage. I am fast running out of space as I am using "Managed Masters". I intend to make the masters referenced by relocating them to an external HDD but before doing this would like to clear up this problem first. I keep my Vault on the external HDD and have Time Machine and Time Capsule. When I have relocated the masters to the external HDD I intend that TM backs the external HDD to the TC. I tink that I will use the second partition on the external HDD for Carbon Copy Cloner to back up the Mackbook Air.
Any help or advice warmly welcomed.

Frank
Many thanks for your input.
Following your advice I have selected all the projects individually and checked the status of Mantain Previews. Some were indeed marked up for Mantail Preview so I have unmarked them.
I have also selected Photos and deleted previews and also repeated this for My Projects.
Checking the Get Info for the Preview folder in Aperture Library in Finder this now tells me that I have zero bytes for 564 items.
Close and then reopen Aperture and it regenerates these564 previews in the blink of an eye. I haven't been able to locate these photos yet. I know there are about 120 in facebook and 10 in photostream but dont know where the rest are.
It seems the issue is not with Aperture but with myself and not understanding Aperture sufficiently well
Do you see the problem this way?

Pdf color looks different in preview and acrobat?

I notice that the colors in various PDF files I have look different in Preview and in Acrobat. Is there some weird color profile issue?
To be specific, I can create a PDF file in various ways, of a slide deck I originally created using Keynote. It has various different color blocks in the slides. In particular some acid green colors look very different depending on whether I open the PDF in Acrobat or in Preview.
Preview shows the colors as they were in the original keynote application. But Acrobat shows them far more muted.
I learned from another post that if I create the PDF by first saving to postscript and then creating the PDF using Acrobat, the issue seems to go away. However this is very inconvenient.
In short, it seems as though there is some peculiar difference between the way Preview and Keynote (and probably Pages ) handle color and the way Acrobat handles color.
Is there some way to fix this using some setting in one of the programs?
By the way, this is not a new problem. I noticed it with previous OS's as well as previous versions of Keynote. I am currently using the latest version of everything.

Same problem here. I was printing a PDF that my designer had sent me. Before I have always used Acrobat, but I've started using Preview in Leopard since it's faster and more powerful than before. But the colors were seriously wrong, often reversed completely. I believe this file was originally created in Illustrator.

Aperture vault with no mother library - how do i update it?

hello. i had an aperture library i created for a project. when i was done with the project i created an aperture vault on an external drive. but stupidly i deleted the actual library that created the vault.
now i have a 50g vault on a drive and i need to get back into the library.
when i try and open the vault, it says the vault was created with an older version of aperture and it needs to be updated. but i can't update it. i can't figure out how to even get aperture to recognize the vault at all... what to do?

Simple, effective answer: Yes, make copies of your Libraries as back-ups and don't use the Vault feature.
Vaults are no more than a back-up created from within Aperture. (I suspect Apple added this feature on the assumption that users of Aperture did not regularly back up their data.) They can be problematic (they can also be problem-free). If you are comfortable with Finder or with a program such as SuperDuper or CCC, use it and don't bother with Vaults. (That's what I do, and that's what other top posters here do as well.)
As far as data back-up goes, I recommend that all users maintain at all time three copies of their data. A working copy, a copy of the working copy that gets regularly updated (no less than once a day, unless the data is unchanged), and another copy of the working copy that is kept off-site. Never have all three copies in the same physical location (don't bring your off-site copy on-site. Take your on-site copy off-site, and then bring the off-site copy on-site, effectively swapping them while never having all three copies in the same location).
As for making on Library for each project ... it is generally not recommended. One of the great empowerments of Aperture is that it functions as an index of all the work it contains. I have _every photo I've ever taken_ in my personal Library. I can search my entire oevre. Your needs may be different -- and may be different enough that making one Library for each project you do is sensible -- but using separate Libraries takes the power of this global indexing away. (Fwiw, the reasons I can think of having separate Libraries: image security, image quarantine, multiple photographers, and Libraries of images where the photographer is not important.)
HTH,
--Kirby.
(Sent from my magic glass.)

Is there a need for Aperture Vaults if I'm using Time Machine and/or SuperDuper?

Hey all
What's the benefit of Aperture Vaults if I'm using Time Machine or SuperDuper for my regular backups?
John

John,
Aperture vaults are snapshots of a certain moment. So you can create a collections of vaults saved at specific intervalls, say one each year, or before you upgrade your system. If you keep your older vaults, you will be able to restore images from many years back. If your library is huge, you may only notice years later that an important image got corrupted.
Time machine backups are very convenient and you can go back in time easily, but you can never be sure, how much back in time your backup will go. You have no control over which older versions will be deleted, when TM runs out of space.
Clones are great, i.e. if you create bootable clones. This way you will be able to revert to a previous system without reinstalling. With respect to Aperture libraries cloning your library will give you the same benefits as vaults.
My experience tells me, that a mixture is good. If you can, keep three backups, and not all in the same place.
I keep one backup at my office and two at home. I have a bootable clone, a TimeMachine backup, and occasionally create a new vault. My most important images are in my dropbox and synced to all my macs.
regards
Léonie

Cannot convince Aperture 3 to create 1920X1920 previews...

It seems there is a bug in Aperture 3.0.0 and 3.0.1
I chose my previews to fit within 1920X1920.
However, Aperture seems to ignore this most of the time.
For example:
Select 100 photos => Delete Previews => Generate/Update Previews.
Now, *only a few* of them will have properly sized previews. Most of the previews are much smaller than 1920.
It seems that the process that creates the previews encounters a problem that messes up its internal state, and then continues to create previews of another size.
This is very frustrating, especially if you have many offline masters like I do.
Most of my masters are raw files from Canon EOS 5D Mark I and II.
Some masters are of type raw+jpeg.
Can anybody confirm this?

This is what I've discovered so far.
Quit Aperture (and automatically generate previews) --> launch iTunes: iPhoto Albums show up in iTunes but smart albums all missing
If I proceeded to sync my iPhone with iTunes, it will delete all my photos off my phone because nothing is synced!
Quit Aperture (and automatically generate previews) --> launch iPhoto --> quit iPhoto --> launch iTunes: Smart albums correctly show up, and correctly 'ticked' to indicate it will sync.
I suspect this is a limitation of using a supposedly 'unified' iPhoto Library in Aperture, but it isn't listed in the "Using the Unified Photo Library" guide at http://support.apple.com/kb/HT5043?viewlocale=en_US&locale=en_US.
Effectively though, it appears to me to be a data loss bug in the current implementation of Aperture / iTunes Library sharing.
I've tried to import my iPhoto Library to a new Aperture Library to no avail.

HT201269 My Iphone 4 is water damaged and won't work at all so I've bought a new Iphone 5c - can I get my messages and whats app chats from my old to my new phone - they have different sized sims?

My Iphone 4 is water damaged and won't work at all so I've bought a new Iphone 5c - can I get my messages and whats app chats from my old to my new phone - they have different sized sims?

There is nothing saved on the SIm card in an iphone. If you have a backup of the old phone restore that to the new phone

Library - Previews - Render Standard-Sized Previews

Is there a limitation to the number of images that Lightroom processes when you select to manually Render Standard-Sized Previews?
I deleted my preview folders (Lightroom Catalog Previews.lrdata) because it was previously set to highest quality at highest resolution which was chewing up disk space needlessly (I changed the settings down but didn't know if Lightroom would re-render already existing standard previews).
Lightroom re-created the folder when it re-started and I then selected all the images and selected Library -> Previews -> Render Standard-Sized Previews
But this finished in awfully quick for 8000 images, so I ran it again, and it started to render more (different) images. And then I did it again, and it started to render more (different) images, and so on. I've done it enough times now that it has finally completed all of the images - but it seems like it only renders only a few hundred images at a time?
Am I missing something - why doesn't it render all the images you have selected?
I've observed this in both LR 1.0 and LR 1.1 on a Mac.

The direct link seems like one of the things Ian Lyons might include with the stuff at the top of the UtoU main forum page along with the FAQ listing and other items.
Don
Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
http://donricklin.blogspot.com/

Aperture Vaults on TC

I would like to use TC, without Time Machine, to hold Aperture vaults, i.e., straight Aperture vault backup to the TC as external hard drive. In the CREATE VAULT dialogue box and selecting TC under SHARED DEVICES, the ADD button is greyed-out/unavailable to designate location of the new vault. Any insight into this matter or suggestions would be appreciated.

The permanently connected vault (vault 1) caused me problems and I was forced to recover all images from it into aperture on my imac
Not really sure what this means. What problems were you having and how did you recover all images from it into aperture?
the No2 back up does not seem to sync to the system anymore and I cant back up on it.
What do you mean by sync to the system ? Does the library not see the vault? Something else?
Should I delete the No 2 Back and re create a new vault on it by copying vault no 1 on my external drive that is permanently conected???
As vaults as just snapshots of the current state of the library (not much different then just copying the library except for speed) nothing is lost by making a new vault.
However I'm not sure what you are looking to do by copying one vault (vault 1) I thought that was the vault that was giving you problems?
If you are having troubles I would just create a new vault and update it,
regards

Aperture Vault vs Time Machine~which is best to retrive photos with all info

Aperture Vault vs Time Machine~which is best to retrive photos with all info?

Both will restore your Aperture library. And both will not allow to restore single images. You always have to restore the complete library.
The difference is, that Aperture vaults are archival backups. You make a snapshot at a certain point of time. Time Machine will give you the option to go back in time to several different moments. A vault is snapshot of only one moment and you would need to create several vault to be able to go back to earlier versions of the library.

Inefficient Aperture Vault Synchronization Behavior?

I've begun planning for a trip abroad, and as such anticipating the possibility of losing my laptop/external hard drive. After a bit of research I came across Amazon's S3 service for storing files online. Using a nice little application called JungleDisk, I can mount this online storage as a 'local' disk...and as such drop my Aperture Vault into it.
A nice little setup...except that when I go to synchronize my vault it ends up starting from scratch...so my initial 13GB upload of my vault resulted in another 13GB (@ 125KBps...a long time).
I realize it is an 'unsupported' function, but I'm curious if anyone else has experienced this inefficient synchronization method. I'm currently evaluating the possibility of using something like RsyncX to synchronize my Aperture library from an external hard drive...which isn't as streamlined as I'd like it.

Given that Vaults don't normally behave that way, I'd think this is almost certainly down to trying to do something it's not designed to do.
I'd recommend either using a Vault on an external HD as the easiest and fastest option, or use ChronoSync with all the 'go into packages' options turned on. This will be slower than the Vault as it will also be copying across all your previews and thumbnails, but it will be a regular Library rather than a Vault that you have to restore from.
Ian

Aperture Vault saving different sized previews

Similar Messages

Maybe you are looking for