Discrepancies between vault size and library size

Can anyone explain to me why there is large discrepancy between the size of my vault and the Aperture library?
I just synced my library to a vault and there is a 9 GB difference in the size of the two, with the vault being larger. Now I know there is a container of deleted images in the vault, but that only adds up to about 800 MB, so that still leaves an 8.2 GB difference. I'm wondering why there is such a discrepancy.
Both the drive that the library lives on, and the vault drive, are exactly the same size (300gb). In fact, they are the same brand of drive. Also, both are formatted the same.
I'm not sure I know what's going on, and that makes me a bit nervous since I'm dealing with my archive here.
Any thoughts?
Antonio

So, you can see from this that something is strange.
http://amrosario.com/vault01.jpg
This image shows a screen shot of the Aperture Library compared to the Vault which I just synced. The Aperture Library is on the left, with the "Get Info" box behind it. The Vault is on the right with its "Get Info" box behind it.
There are some BIG differences in the size of the project folders, as you can see, with the vault's folders being smaller across the board.
I mean, maybe I could chalk this up to some formatting differences between the drive (although I think I remember they were formatted the same). But if there was a formatting difference, wouldn't the folders all exhibit a similar proportion of discrepancy? Look at the "New York City" folders - almost 2 GB in difference, but the "Commercial Work" folder is less than 1.4 GB difference.
Arrrgh!
Antonio

Similar Messages

Very different color noise between develop module and library

There is a marked difference in the appearance of an image when viewed in the library versus the develop module. The color noise in the library module is very bad, while in the develop module, the noise reduction is doing a pretty good job. This is strictly a view problem, because if I export from the library, the proper color noise reduction is applied and it appears as it does in the develop module. This is not the first time that I have found this problem between the two modules. Any idea why this is happening? And, is there a fix in the works? It makes it hard to view images in the library.
If I boost the color noise reduction up to 100, the library image starts to look ok, but that doesn't account for the huge difference at lower settings.
There is also a dramatic slow down in the develop module when trying to make any of these changes in noise reduction and more, and also in side-by-side when trying to scroll around in the image to compare areas. Things really crawl. There is a definite two or three second delay before things respond. I have 8gigs in this mac pro, which worked beautifully with LR 3.6

And, is there a fix in the works?
Try rendering 1:1 previews for noisy images.

Strange library and vault sizes

Hi there, I have been updating my library, vault and back-ups with some surprising results:
managed library (internal HDD on MacPro) - 140.76GB
vault (on separate internal HDD on MacPro) - 132.66GB
library back-up (copied to NAS) - 142.56GB
vault back-up (copied to NAS) - 56.96GB
offsite library back-up (copied to Maxtor 1TB drive) - 67.94GB
offsite vault back-up (copied to Maxtor 1TB drive) - 134.2GB
Does anyone know why:
1. The vault should be a smaller size than the library
2. The vault and library copies should be a different size than the files on the Aperture generated packages?
This makes me feel uneasy - do I actually have a reliable back-up? Also, these are large files and take many hours to copy from the Pro to the NAS and then the Pro to the Maxtor. I'm wondering if it would be more efficient to change to a referenced system and then use software like Sync! to copy across files that have been edited rather than the entire managed library.
Any comments, suggestions welcome. Also, any pointers to information re back-up philosophies.
Thanks in advance, Mark

Hi Mark,
This could be your answer.
http://discussions.apple.com/thread.jspa?messageID=9291855&#9291855
Cheers!

VAULT size is smaller than the LIBRARY

my vault size is smaller than the aperture library. is it saving everything? it seems like the two should be the same size or at least close to the same size. i regularly update my vault so that it is current with the library. VAULT = 168 GB | LIBRARY = 262 GB

what is the consequence if i totally turn previews off?
The major consequence is that you will not be able to share images from your library through the media browser. So if you want to email an image for example or add an image to a document you will need to export the image first rather then be able to get the preview from the library.
Also if you have referenced originals and the originals go off-line nothing will appear in the library. If you had previews for those images you would still see them and be able to do tasks like rate them.
Finally some operations might appear slower as you won;t see anything on the scree until the image you are looking at is rendered. With previews while Aperture is rendering the image in the background it will display the preview.
It is possible to selectively maintain previews for some projects and not for others. This might be a comprise position between having previews for al images and having no previews at all.

Vault size smaller than Library

I have 30k referenced photos (188 gb) with a Library size of 11 gb. The Vault size is only 1.7 gb! This makes me nervous. In the past, both have been about the same size. What is happening?? thank you

Here is more detail: I started with a 7gb Library, with about 6gb of managed files and limited referenced files. I then brought in all of my old files with Import Folder into Project, which added 28k files. After that, the Library went to 16 gb (seems large!). Next I relocated the managed files out, about 6 gb, and the Library shrunk to 10 gb. I did a new Vault store and the Vault size shrunk from the original 7 gb to 1.7gb. I can also see along side of it the Deleted files, 6gb, of those moved out.
If I look in the Vault at a given folder (from the Import Folder into Project), its size is 313mb; the same folder in the Library is 2.2 gb. Looking at a given imported project, Library has a folder of 17mb, AP.Minis of 41mb and AP.Thumb of 76mb. The same file in the Vault has a folder of 20 mb and several little 8k things. Clearly thumbnails were generated although Preview was turned off, and tested that I could not drag thumbs out.
Hope this helps, thanks, gib

Difference between text size in General setting and large type in Accessibility settings

Difference between text size in General settings and large type in Accessibility settings?

None that I can see.

File size difference between DNG Converter and Lightroom Beta 4

Hi,
I want to go the all-DNG route and am trying several things ATM. I want my files to be as small as possible, thus I disable previews and RAW embedding and enable compression in DNG Converter. In Lightroom, there are no options at all. What I do get, are pretty amazing file size differences:
Original .NEF as it came from my D70s: ~5MB
.DNG created by DNG Converter: ~1MB
.DNG created by Lightroom: ~4MB
The very small file size in DNG Converter is the one that bother's me most. I get these small files from time to time. I checked both the DNG and the NEF in Photoshop, and they seem to be identical. So my question is: What triggers these small file sizes? Do I loose anything? Or is the Lightroom DNG converter not as advanced as the stand alone version?
Maybe this helps: I get the ridicolous small files for very dull subjects that tell the computer scientist in me that it should be easily compressable by common compression algorithms.
Thanks for any pointers,
Markus

Thanks for the hint! It did make me revisit those files and now I see the reason for the small file sizes: The Apple Finder does note update the file size view once a file was added to a folder. Here's what I did:
Opened a folder full of .NEFs in detail view in Finder.
Converted them using DNG Converter
Looked at the sizes of the files as they were shown in the Finder window allready open.
Unfortunately, those file sizes are not correct. If I open a new Finder window of the same folder, file sizes are correctly reported as between 3.5 and 5 MB.

Library size differs from Vault size

I just made a new Aperture Vault. My Aperture Library file is 41.66GB. My Vault file is 35.41GB.
Why are these different?
I have consolidated the library as well, so I am sure that the issue is not related to referenced files.
Thanks,
~BC

Thanks for that. Does my vault size (85% of the library size) seem about right to you?
I only ask because the whole point of the vault is to be sure nothing is lost ... so I want to be sure I have this set up properly.
Thanks,
~BC

I converted video into frames. There is a big difference between video size(700 MB) and All frames s

I converted video into frames. There is a big difference between video size(700 MB) and All frames size(More than 5 GB). What are the reasons ?

Please, are you sure that you posted this in the correct forum? This is the Adobe Captivate forum, not a forum for video created with other applications like Premiere Pro.
Lilybiri

File size difference between version 3 and 4

I'd like to know how to publish a file at the smallest possible size with Captivate 4.
I have 1 file that is 9176KB published with Captivate 3. The same file published with Captivate 4 becomes 10300KB. I didn't add any functionality just publish it once saved in 4.
What is the same content ~1MB bigger with the new version? How do I make it smaller?
Thanks,

Thanks for the hint! It did make me revisit those files and now I see the reason for the small file sizes: The Apple Finder does note update the file size view once a file was added to a folder. Here's what I did:
Opened a folder full of .NEFs in detail view in Finder.
Converted them using DNG Converter
Looked at the sizes of the files as they were shown in the Finder window allready open.
Unfortunately, those file sizes are not correct. If I open a new Finder window of the same folder, file sizes are correctly reported as between 3.5 and 5 MB.

Vault size

I have a large, referenced aperture library. When I do "update all vaults" the file size is very small. Is there any way for me to make sure that all of my projects are being backed up in the vault

I'm guessing that the "Aperture Library" is in your Pictures folder and the Vault (default name: "Untitled Vault") is on a backup device. When you "Add" a vault it goes thru a dialog box where you picked its location. Otherwise, you can open the Vault pane at the lower left of the Aperture window and click the triangle to the left and it will show you the Vault's name and location.
(Your next reply just popped up.)
The size of the folder containing your original image files doesn't really matter here. (Bigger does mean a bigger Library and Vault but there is no specific formula I can offer.)
The Aperture Library is databases with keywords, adjustments, etc., and image previews. Part of its size is determined by the Preferences setting (size and resolution) for your Preview images. They can let you organize but not adjust your images without the Masters being online.
The Vault size will be similar to your Library size. Over time this relation may change.
If you had a Managed Library, it would be 233GB plus databases plus previews. And the Vault would be a similar size.

Backup vault size

My library seems to be growing larger and more rapidly than I would expect. I have about 28,000 photos. Most D200 jpegs about 5-6 GB, some older and smaller few thousand at 1-2 GB, about half -scanned slides and 35 mm about 8-10 GB. The vault size is 437 GB. Seems that on average I am using about 15 GB per photo. Recently I added 1118 scanned 35 mm avg 7-10 GB. They came on 3 DVDs - 1 about half full - est 11-12 GB of Jpeg data. I loaded them into Aperture and rebacked up vault and it grew by 45 GB - no other changes since last backup. I also back-up to an online archive and it sits on about 75 GB though files somewhat (smaller 3- 8 GB). When it approached my internal 500 GB drive capacity, I got a 750 GB drive added a few thousand images and tried to back up and got warning "insufficient disc space available". I still had about 300 of 698 GB available with vault size of 437 GB. I did determine that if you delete the vault and write a new one it will fit on a 500 or 750 drive. Any Help? Thanks.
MacPro Qaud Mac OS X (10.4.10) 4GB RAM, 30 CD

I figured it out - thought I might share.
It turns out that the previews generated at the highest quality for the 30" display are Huge Files. They are anywhere from 2-3X larger than the original file. Hard to believe? Original file 5.0 MB creates preview of 17.4 MB. This overall creates a database that is 3-4x larger than the imported images(including other misc control files). This can be fixed easily by reducing the quality of the preview down to 7, which corresponds to a file size of about 850 KB. Then regenerate the previews (control,option together with click, select generate previews). This can be done for batches, or the entire library. The quality changes was not really apparent. Hope this helps others avoid this situation.

Vault Size/contents ZERO

I created a vault on an external drive, of my 89G Aperture Library.
After it created the vault...the contents and size equaled that of the actual library.
Start and restart Aperture and the Vault status icon is yellow, telling me there has been changes in my library, which there hasn't. So i go and check Vault size, and much to my dismay it says Zero bytes on disk and no package contents.
I click update vault in aperture, does it's comparing for a bit, then finishes with no errors.
Vault status icon is black (stating everything is up to date) but Vault is still Zero Bytes and no contents.
Any ideas!?
Thanks.
kevin

The vault should be smaller: no previews or thumbnails are stored in a vault. So that is odd.
How are you measuring the size of the vault and library?
How is your external drive formatted? If it is not HFS+ case insensitive then all bets are off. That is also called Mac OS Extended case insensitive.

Vault size in AP3

Anybody else seeing Vaults that are as big as their main library ?
I use a library with referenced masters and the library is around 22GB at the moment (still in the proces, after a whole WEEK, of manually exporting and importing projects from my AP2 library).
My vault is the exact same size. It seems to copy all the thumbnails as well, they use 20GB out of that 22GB.
AP2 didn't have huge vaults like that!
Another issue to add to the list for AP3!

Firstlaunch, thanks for your reply - sorry for my delayed response; I've been away for a bit.
Anyway, to respond to yoyur question - it was the error message that appeared which indicated the 14GB size increase. At the time, I couldn't perform the backup as there was not enough space on the drive. Since then, though, I bought a larger external drive and when I ran the Vault on it (having made no changes from the prior situation) the Vault size did not (again, did not) jump in size.
So, to recap:
- I use, and always have used, referenced files, and my AP2 vault was 20GB.
- After I upgraded to AP3, I immediately ran the Vault, whereupon AP3 renamed the original Vault "old" and proceeded to build it's own fresh version - that was 40GB. I.e. - without any alterations to the underlying data set, the Vault doubled in size. In fact, since I only had limited space on the drive I was using, I deleted the old Vault on that external drive (I still had a parallel old vault available just in case) which is what gave me the room to build the AP3 vault.
- After importing 12GB worth of RAW files, my attempt to update the vault was met with an error message saying I would need an additional 14GB of space. Without enough free drive space, I did not run the vault update.
- After adding a larger external drive to my system, I ran the Vault from scratch, and it's actual size remains about 40GB.
So I can only conclude that, as you evidently suspected, the error message was somehow wrong; that I did not in fact require an additional 14GB of space after all.
Perhaps this falls under the same bug (er, undocumented feature) category as the one where when I attempt to e-mail versions, regardless of what settings I make in preferences, AP3 always generates full-size (i.e. - 14MB apiece) output. When I do a simple export, it works fine; it's only when I try to directly e-mail that it does this - seems to be another case of poor file size handling.
I am not going to mark this question answered only because the original question remains - why did the error message warn me about a ridiculously large vault size increase when in fact it never happened? I suspect that the Vault warning simply looked blindly at the fact that I imported 12GB worth of images and somehow "assumed" they were managed files, even though they were referenced.

I store my itunes library on an external drive shared between 2 computers and itunes on computer A isn't seeing or showing the songs I added using itunes on computer B.

I store my itunes library on an external drive shared between 2 computers and itunes on computer A isn't seeing or showing the songs I added using itunes on computer B. How to fix this?

I don't know if this is me adding files to iTunes when the external wasn't connected
it is.
is it OK to just keep deleting that library on the Air?
i wouldn't - at least not until i
mount the external
point iTunes media folder location back to the external via preferences > advanced
consolidate my library via file > library > organize library
The ntfs hasn't seem to be causing any problems, but I've always wanted to know.
in order for your Mac to write to NTFS drives, it needs some help by installing e.g. the NTFS 3G driver. apparently that or something similar is installed on your Mac already. preferably, it would be formatted for Mac but then windows machines would need to have e.g. MacDrive installed to recognize the drive.

Discrepancies between vault size and library size

Similar Messages

Maybe you are looking for