Aperture Library Thumbnails

I have a problem I cannot figure out. I have 155,000 photos in 1120 projects in A3 (ver 3.2.4). My photo files are referenced on external hard drives, and the Aperture library folder resides on my imac hard drive in the pictures folder.
I started to remove previews in the Aperture library to make space because my 500GB internal hard drive is almost full. When I got into the Aperture folder I found this:
My preview folder is 39GB for 488,000 items and my thumbnail folder is 173GB for just 4504 items. What is happening here?
I don't understand 488,000 previews, and how can I have 173GB of thumbnails for only 4504 items?

First off going into the library like that to remove anything is a bad idea. You should be using the Aperture command delete previews. In addition you need to turn off previews not just in the Preferences but also in the projects or else Aperture will juts regenerate them.
As for the sizes issue. The Aperture library is a database, even though you can open it up and see some regular files and folders the entire package acts as a database. Taking the size of different pieces of ti is usually not vert helpful.
Each image can have multiple thumbnails as you will see if you look in the folder. In addition in order to speed ip operation there are two actual database files in the Thumbnails folder in which Aperture caches recently used thumbs (at least as near as can be figured out trying to reverse engineer it).
As for the item count remember each of the folders contain more then just a collection of image files. Every preview is stored in its own subfolder.
Again you should not be managing the Aperture library as if it was a regular folder of images or data. If your short of space on the library drive you can delete the previewss from within Aperture and set Aperture up to not regen them and also not to create new ones. Remember this will have some negative consequences especially with referenced originals.
regards

Similar Messages

Aperture Library size different after restore from TM and rebuild Thumbnails

I have just completed an erase-install-migrate from Time Machine using Setup Assistant.
The size of the managed Aperture Library originally was 397.8Gb
After completion of the migrate back in I opened Aperture and as expected it rebuilt the thumbnails (TM does not backup the Thumbnails).
After doing this I tested the Library as far as possible and all seems well, and the number of photos is exactly the same as before (49,883).
However, the size of the library is now 357.8 Gb.
The only logical explanation (to me) is that the restore process has eliminated previews and thumbnails from photos which I have deleted over the years.
I still have a backup of the original (397.8Gb) version which I could put back with the Finder, but if the restored library has cleared years of redundant previews and thumbnails I would prefer to stay with that.
All done with Mavericks and Aperture 3.5.
Any insights very welcome.
Thanks

Just had the idea of looking at sizes in the Library package contents, and the explanation for the change in size is due to three things:
Thumbnails old: 44.95 Gb
Thumbnails new: 15.13 Gb
There is also an iPod photocache of 14.6 Gb which is not yet present in the new.
However Previews old was 27.95 Gb and Previews new is 33.18 Gb, so I assume some previews were smaller in the original Library.
Masters is 304.3 Gb in the original and new libraries.
I am beginning to feel more confident about the new library.

What is the best way to move an aperture library from one full drive to an external drive?

Just want to make sure I move my existing Aperture library on my internal drive (which is full) correctly to an external drive that has plenty of space.
Thanks for the help!

As I use a MBP with limited internal drive space, my approach is to have the image files on an external drive, while leaving the library itself on my internal drive. The library takes up about 80GB while the images are closer to 1TB.
The library always contains 'Thumbnails' of the images which it shows in place of the disconnected image files.
This means I can still open the library even when the external drive is not attached, and I can still do keywording and rating and organising and so on.
I also maintain 'Previews' for my best images. Previews are like thumbnails but larger in size and can be shared with other apps, so I can still use and share these copies of the images, again even while the external drive is not attached.
I don't like the idea of having the actual library on an external drive connected to a laptop (although I have done so from time to time without issue). There's always a chance it can become accidentially disconnected (kids, pets, etc) and if this happens while using Aperture it can corrupt your library. A corrupted library can be repaired with Apertures first aid tools, but it's better to avoid it in the frist place when you can.

How can I slim down the aperture library?

Hi,
My aperture library grew a lot. Is there any way to slimmed it down, without erasing content? I am talking about recreating previews with less quality or smaller size, deleting old thumbnails (I read that even if you delete a picture from the library, Aperture won't delete the thumbnail).
Does anybody knows any tricks about how to do that?
Thank you very much for your answers!
Gus

Easy. Switch to Referenced-Masters Library with Masters on external drives.
More complete explanation:
First make a Vault to an external drive as backup.
Then from within Aperture:
File Menu--> Relocate Masters. Choose external hard drive(s) and direct Aperture to move the Masters to those drives. Give it plenty of time depending on how many Masters are being moved. The Library remains on an internal drive, only the Masters get moved.
Next back up the drive that the Masters were relocated to, because now you have a Referenced Masters Library so Masters are backed up (once) separately from the Library Vault backups.
In the future back up originals (once) on external drives prior to import into Aperture or any other images app. I cannot overstate how important that is, and various manuals, texts, etc. present workflows that skip that critical step. Also back up the Aperture Library using Aperture's Vaults, which are designed for that purpose.
A complete Referenced-Masters workflow follows. Note that for image security reasons Aperture is not involved until the end of the process:
• Create a folder ("abc") for the incoming images. Easiest is to create the folder on the external hard drive where the Masters will permanently live, but Referenced Masters can be temporarily on the laptop's internal drive, then moved later as described above. I initially put Masters referenced on my MBP internal drive, then after backup and editing I use File Menu--> Relocate Masters to move the Masters to a permanent external drive location.
• Connect a card reader with the camera card in it. The camera card should show on the desktop. If it does not show, restart the Mac with the reader and card still plugged in. You can of course use the camera directly in this step, but I do not recommend it. Obviously cameras like the iPad2 do require direct camera-to-computer uploading.
• Drag the contents of the card's image folder(s) to the abc folder that you previously created on the hard drive.
• Review the abc folder contents to be sure they all copied properly.
• Software-eject the camera card.
• Physically disconnect the camera card reader from the Mac. This step is important to help avoid all-too-common human error.
• Again review the abc folder contents to be sure they are indeed all there (because stuff happens sometimes...).
• Back up the abc folder contents on to another drive.
• Review the files on the backup to be sure they all copied properly.
• At any time after but not before the previous step you can reformat the camera card in-camera. Do not delete images on the card using the computer.
• Start Aperture.
• Import the images from folder abc into Aperture, selecting "Store Files: In their current location" on the right-hand side of the import window (important!). Note that the Library remains on an internal drive, only the Masters are on externals.
HTH
-Allen Wicks

Aperture Library/Database hacks

After one week playing around with aperture, i want to share my current insights with 'customizing' (my) aperture's way of dealing with my picture files.
Warning:
The following thoughts and arrangements are working for me, they're
undoubtly NOT supported by apple and the programmers of the aperture
application!
Reading a lot of articles in the forum when aperture hit the masses, i've been disappointed about how aperture will fit with me.
Over the years my growing picture collection moved over from one computer to the other, deploying more storage, and will continue to do so in the future. So the technical equipment has to be independent from the treasure's of my data, to follow state of the art hard- and software development.
For me, aperture approved to be of such a kind.
Despite aperture stores away all my digital masters into it's own Library, thus duplicating data during imports, it just brings in some kind of more detailed
directory hierarchies to my way of organizing my picture library. How does it do?
How do i store my Library?
Sorry to be that longish, but to explain my concepts i have to.
Modern operating systems distinguish private/personal and public/common data for their file storage locations. Hopefully they follow the 'FHS' (Filesystem-Hierarchical-Standard) brought up by linux, to name the diverse locations for classified data.
I do run mixed os'es within my networks, as no computer should be isolated from a networked environment anymore. But to be honest it's more a single-user situation in reality, then the multi-user aspects i always keep in mind when designing my infrastructure environment for a network.
My picture library/online-archive is classified 'common' data, so it stores outside my home-directory, and every user allowed to, has access to it. I do not support locales within my filenaming-conventions, users and me are german-spoken, so the 'common' data for my systems is always called
'/Bibliothek'.
Furthermore we're dealing with pictures (Bild), movies (Film), music (Musik) and documents (Dokumente) in all common used operting systems (os x, windows), storing private data to the home-directory within appropiate directories and public/common data to the equivalent directories at a common storage.
/Bibliothek
/Bibliothek/Bildarchiv
/Bibliothek/Filmarchiv
/Bibliothek/Musikarchiv
BTW, i customized windows to reflect this filetree within explorer windows, so users click to 'Eigene Bilder' (my pictures) and 'Bildarchiv' (common pictures) there, to change between directories, making it very convenient to work with.
Especially the 'common' picture files are strongly organized by date, which is reflected at the directory-structure, for example:
'/Bibliothek/Bildarchiv/2004/2004-04-17, make a good description/'
'/Bibliothek/Bildarchiv/2005/2005-12-00, a bunch for the whole period/'
A descriptive directory name is highly portable between operating systems, applications and last but not least, users!
For now, aperture seems to be pretty much a single-user solution.
But it's library can be 'distributed' to accomodate my needs.
I started to import my data by drag'n'drop, which works best for me. I didn't like the import assistent, which seemed to result in a different structure of my data in aperture's 'all projects' list. By creating a folder in aperture for the year, then drag'n'drop the multi-selected directories from the finder, i got within aperture:
All Projects + * (<-Aperture)
<div class="jive-quote">Library (smart-albums, collapsed)
2005 (folder)
2005-11-00 (folder, nested)
2005-11-17, sample bla (project, from directory)
Images from 2005-11-17, sample bla (album, inherited)
2005-12-08, take a better name (project)
Images from 2005-12-08, take a better name
Using aperture's preferences to switch between libraries i did import to different aperture libraries for the years, resulting in a bunch of directories, each holding an 'Aperture Library.aplibrary' paket there.
/Bibliothek/Bildarchiv/2004/2004.aplibrary
/Bibliothek/Bildarchiv/2005/2005.aplibrary
Yes, the pakets can be renamed, to better reflect whats in there. Aperture has to be restarted to change from one library to another!
The total amount of imported data, yet: 130 GB, ~33164 pics.
I am working with a 15" powerbook, 1,5gb ram, 80 gb hdd on the road and a 200gb external drive at home/office.
to make me feel comfortable with aperture, i switched to (terminal hacking!):
~me/Pictures/Aperture Library.aplibrary/
~me/Pictures/Aperture Library.aplibrary/2004/ ->
/Bibliothek/Bildarchiv/2004/2004.aplibrary
~me/Pictures/Aperture Library.aplibrary/2005/ ->
/Bibliothek/Bildarchiv/2005/2005.aplibrary
~me/Pictures/Aperture Library.aplibrary/Texturen/ ->
/Bibliothek/Bildarchiv/Texturen/Texturen.aplibrary
~me/Pictures/Aperture Library.aplibrary/...
/Bibliothek/Bildarchiv/2004/2004.aplibrary
/Bibliothek/Bildarchiv/2005/2005.aplibrary
/Bibliothek/Bildarchiv/Texturen/Texturen.aplibrary ->
/Volumes/HD39.1/Bibliothek/Bildarchiv/Texturen/Texturen Library.aplibrary
Linking folders to where i believe they are right placed in my systems.
Now aperture's settings don't have to be changed each time to switch between libraries. Not connecting the external hdd gives me grayedout
folders within aperture, for data stored on the external drive. Having a folder located on my inetrnal hdd and 'linked' to aperture:
~me/Pictures/Aperture Library.aplibrary/local ->
/Bibliothek/Bildarchiv/working.local.aplibrary
i can work with aperture normally, even if the external drive is not available.
the grayedout folders/subfolders/projects are browsable, but all thumbnails are just gray rectangles with its 'version name' underneath. same with smart-albums. available pics have colored thumbnails, unavailable pics are gray, naturally.
And aperture's database? well, i am very happy with it, really. Compared to my pre-aperture structure all the above mentioned tweaking gave me:
~me/Pictures/Aperture Library.aplibrary/Aperture.aplib/Library.apdb
This file is actually the sqlite3 database file. it's size is 111 MB now.
~me/Pictures/Aperture Library.aplibrary/Local ->
/Bibliothek/Bildarchiv/Working.local.aplibrary
I can store pictures there into folders and projects when i am on the road, filling up my local harddisk. Inspecting the paket shows up how aperture differenciated my pre-aperture filestructure:
/Bibliothek/Bildarchiv/Working.local.aplibrary/2005-12-08, take a better name.approject/2005-12-08 @ 01/49/06 PM - 1.apimportgroup/DSC0168/dsc0168.nef
All nicely packed into a single unit from the finder, easily browsable from aperture, and searchable by sql queries. Every Master enclosed in its own folder box, hm. Every import of files seperated to one folder, which makes clearly apparent that we will import redundant(duplicate) files for ever.
Adding two/three levels to my previous filestructure, strange namings all inclusive. As i sort my files with aperture into projects, the files accordingly move around at the filesystem-level. I'll let them go. They are there if i need access to them in case of failure.
T H E G L I T C H E S
within my setup the most current sql database is stored at:
~me/Pictures/Aperture Library.aplibrary/Aperture.aplib/Library.apdb
importing the way i did results in a sqlite3-database file for each library i switched to before linking them together. Right after linking one of those aplibrary pakets as a new folder, aperture will rebuild the current database at startup, which can indepently be invoked with 'option command aperture' anytime the program is started.
Changes to the metadata of a picture are written to the current database aperture is running on, but can be transfered to any other database file
when rebuilding the library at startup (which can be a time-consuming thing!)
Even if the external hd is reconnected before startup, some thumbnails are not properly generated all the time. At the current state i don't have any glue what's the cause for this. All Versions are properly accessable anyway.
Once again,
DO THIS AT YOUR OWN RISK,
if you try some of the suggestions i've made. Better you know how to handle a terminal before you even think about what i told here. Don't bother me, if something does not work for you - it works for me.
I can do this because it's my data, i am the only one affected by failure and i still do have my data on my windows system as a backup, for now.
Do the same before you trash your treasures.
Why i did made this post? Aperture really lacks support for team-working now. I cannot see how aperture can be really employed to its potential for an environment with more than a single user?. The sqlite3 database is said to handle concurrent users, i read on its homepage. So i still hope, there will be a group-worked aperture someday.

my reports, just for the logs.
drwxr-xr-x 2 fo03c fo03c 68 Dec 19 20:15 ArchiveInfo
-rw-r--r-- 1 fo03c fo03c 362 Dec 19 20:17 DataModelVersion.plist
-rw-r--r-- 1 fo03c fo03c 173107200 Dec 20 00:26 Library.apdb
comparing the timestamps, the time needed to recreate 'my' library, is:
4h 11 min.
The sql database contains 972 projects with 57952 picture items, as the startup overlay tells me. not that bad, i think. depends on the situation, and how much zen you learned, if you can wait for the 'recreate'.
but i didn't stop to mature aperture!
i switched to one of my 'old' libraries (choosing from preferences panel) and set some new
a) ratings
b) keywords
c) deleted a master from that 'old' library.
after changing back to the 'linked' aperture database file (within my home-directory, as described previously), and restart aperture -
yes, it crashed! oops.
yet another try - crash. i realized, i deleted the first pic from the 'current view' aperture tries to load after relaunch. ?! =:-(
if the database is corrupted again, i would have to reinvest ~4 hours to recreate the database? but how about the preferences?
apple this is a bug! when i made the preferences file
~me/Library/Preferences/com.apple.Aperture.plist
UNAVAILABLE (delete or rename as you like), aperture starts with the import assistent, as at its first time.
Since then i can start aperture and navigate to the project i deleted the file from (very unpolitly). The corresponding thumbnail shows up with a new 'icon' to lower right corner of the thumbnail. It clearly means: this file is UNAVAILABLE.
YES =:-) i deleted it!
the rating and keywording on the 'old' database is gone -
thus making the precedence of the database against the sidecars obvious, doensn't it?
selecting the 'orphaned' thumbnail, now leaves aperture with the message 'loading', but it does not crash. Changes in ratings or keywording to the current library (the 'recreated' new one) on different files are persitent across restarts of aperture. btw, aperture restarts with the focus on the orphaned first thumbnail, now marked with the icon 'i am NOT available', but it does not crash anymore, when starting.
my conclusion:
someone in the forums pointed towards the difficulties maintaining a database of pictures and the separation of their storage, as users will delete or move files seperated from that database, breaking everything.
NO, aperture does widely tolerate such doing.
But why should we do so? =:-)f
For me: its fun, i will not complain about failure, when i do mature an application like this.

Does anyone have any experience of using an Aperture library on a Drobo or Promise Pegasus? If so any problems or tips?

My intention is to place my Aperture library a Thunderbolt Raid device and access via my Macbook Pro SSD Retina. The thinking is that I would have the capability of having a large library and wouldn't run out of space for some time - I understand that the library would also need to be backed up.
If anyone could share their experience positive or negative I'd be very grateful.

I have Aperture installed on a three month old Drobo 5D ( containing five WD 3 TB RED NAS hard drives) attached via Thunderbolt to my Macbook Pro with Retina Display, and Aperture is beautifully responsive with this setup. I do have a 60 GB mSATA card installed in the Drobo 5D, but I find it makes a real difference only when you are trying to acess a lot of small files, e.g. Aperture thumbnails. The Drobo 5D and Aperture make a good combination.
With a folder containning a mix of large and small size files, I find that it often looks like it is going to take a long time to copy the files with the Drobo 5D, and then after a short period of time the Drobo 5D really takes off and copies files at a very high rate of speed. In other words, don't form too hasty an opinion of how fast a group of files is going to be copied. Also, measured speeds with the Drobo 5D are not as impressive as you might expect, but the real-world performance is quite remarkable and fully in line with my expectations.
Tom

Restoring Aperture Library from Vault

Hi all,
I hope someone can help. I recently had my 'Drobo' die on me as two discs failed at the same time. I also have a copy of my Aperture Library backed up in a Vault. I have carried out a 'Restore from Vault' and my new external HD shows 1.5TB of data (same as my original library). When I open Aperture, I can see all my folders and projects, but each project has no photos in it. I have tried repairing the database and rebuilding the database using the option key on start up, but I repeatedly get to approx 83-89% complete and my system hangs and I get a message that I have run out of applications memory. I then get the Spinning wheel and eventually have to reboot the iMac.
1. How can I recover my data?
2. Is there anything else I can/should do? Am I doing anything wrong?
3. Is there anyway of recvering the files seperately of the external hard drive with other data recovery software?
I am running Aperture the most uptodate version of Aperture 3.4.x, on OS X Mavericks, on a 3.4GHz i7 iMac with 12GB ram.
One point I may need to add, I was backing up to Vault when my 'Drobo' unit failed, although based on the size of the vault, I think it had finished backing up, although can not be certain.
Any help/assistance or advice would be greatfully received as I have lost my library, its parity due to two failed drives simultaneously and possibly a corrupt vault(?).
Thank you in advance for your help.
Paul W

Will rebuilding the library place the images into their correct projects/folders?
Will rebuilding return the images to their edited version state?
This library is the restored library from your vault, correct?
What seems to be missing are all of the 'version' images processed in Aperture.
In what way "missing"? Are all your projects empty or are you seeing broken thumbnails of the missing images in the projects?
I am afraid, rebuilding will not be able to reconnect the "recovered" originals to the versions. The images are in the "Recovered" project, because Aperture does not know the link to the version.
If your missing versions are still showing thumbnails, however correpted, you could use the lift&stamp tool to transfer the adjustments from the unusuable versions to the recovered versions.
But that would be a bit daunting for 14000 recovered originals.
I'd try something different - quick and dirty emergency measure: Try to open your vault directly on the drive where it is now without restoring it.
Keep the restored library you are now having save and don't delete it.
Change the filename extension of your vault to ".aplibrary", this will turn the vault into an Aperture library and try to open it directly in Aperture by double clicking it. This needs to be done in-place, on the Drobo-attached drive where you originally created the vault. Do not move it.
Aperture will now try to open the vault as the current Aperture library and upgrade it. There is a slim chance, that the links between originals and versions will remain intact, if the vault is not restored to a different volume but repaired in-place on the original volume.
Frank, what do you think? Should Snurge first try to repair the permissions on the drive?
-- Léonie

Merge two iPhoto libraries into an Aperture library for my Macbook Air

Hey,
I've searched around a bit for this but can't seem to figure out how to to it.
I'm trying to manage my ~140GB photo library on my Macbook Air which has 128GB of HDD. On top of that, you can imagine that most of that 128GB is filled with system stuff.
My objective is to keep most of my library offline from the Macbook Air, but still keep it all together.
I kinda went "all-in" with iPhoto a few years back to organize my photos so gave up on Aperture. I'd always wanted to move to Aperture or Lighroom but the migration appeared to be a complete disaster. Now with "transparent" compatibility it seems like a no brainer to get the best of both worlds.
I thought that Aperture allowed you store files on external hard drives but still have "thumbnail" access to them even when the drive wasn't connected. Or did I misread that? (Is that Lightroom?)
Anyway with the new update I thought that I could merge my available iPhoto libraries into one Aperture library that I could always have access to, while offloading the actual photos somehow to an external HDD.
This would be a real winner for me. It seems tho that an iPhoto library stays an iPhoto library. So while merging might be helpful for someone with a big hard drive, it's completely useless for me as if anything, I need to split. Or create more. Or some other form of adding complexity.
Any ideas here?

Figured this out on my own.
Make a backup of everything - Aperture seems to require rebuilds and stuff and stories abound of "things going a bit wrong."
Did you make a backup? If you don't want to or can't, I wouldn't do this. After all, it's your photos!
Setup your Aperture library on a USB drive.
Update iphoto to the newest version. Open all your libraries in iPhoto to update them. This may take awhile depending on library size.
Import whatever iphoto libraries you have to Aperture. This make take awhile (hours!) - if your stuff is more than say 25 gigs I'd recommend setting it up for overnight.
Once everything is in Aperture - check its all working right. Then go ahead and maybe make another backup
Then migrate your photos out of the library. This takes all the originals and stores them elsewhere, called "offline". Once they're there, you can't move them around, so pick a good spot!! This also takes forever.
Once this is done your Aperture library should be smaller and just copy it to your MacbookAir
I'm still working on this as it looks like something went funky and I have to rebuild my thumbnails, another overnight processing thing. Like I said, keep a backup But I have a slimmed down Library on my Macbook Air now which is what I wanted.
This whole thing is kinda a mess and while it's feasible Apple hasn't made it easy. There's also some crazy stuff Aperture does with thumbnails and "previews" so that they take a bunch of space up (in my case almost as much as my photos), so you might have to work with that.
The guy at Apertureexpert.com is a genius.
Check out this post for more on slimming your Aperture Library:
http://www.apertureexpert.com/tips/2010/1/20/reducing-library-sizedramatically.h tml
Edit:As a side-note I put some HTML in my message and it looks like it isn't used in the forum - why does Apple bother having the formatting tools if they don't work? Kinda like the close-door button on an elevator?
Edit2: Haha it shows up in the answer but not in the normal thread. Strange, eh?

How do I view folders in the aperture library through finder?

How do I view folders in the aperture library. If I look in my pictures I have the applibrary there but can't access it. If I click on it it opens Aperture and I can't find a way to find the info throught aperture either.

You can browse the contents of your Aperture Library from the Finder, but better do not change anything inside.
To look inside the Aperture Library package
Reveal the package in the Finder,
right-click or ctrl-click it and select "Show Package Contents" from the pop-up menu.
You will see a folder with subfolders containing the masters, previews, and thumbnails.
The iLife Applications will let you browse the Aperture Library through the MediaBrowser, that is much safer.
Regards
Léonie
P.S. If your Aperture Library is referenced, not managed, you can view the master image files by selecting the image in Aperture in the Browser or film strip, ctrl-clicking it and selecting "Show in Finder".

Is it possible to Aperture Library by copying over the Contents?

Hi,
My new Drobo 5D is having issues, and i'm not able to copy the Aperture File Directly over directly as its 530GB and the hard drive keeps failing in the last 30GB or so.
so I was wondering is it possible to copy over the contents bit by bit by using the show contents folder and then somehow recreating the Aperture file from the folder of Contents copied over?
Otherwise, is there any other solution?
thanks!
Derrick

Read all this before doing anything.
You select the library in the Finder and right click it and do Show Package Contents. That will revel the inside of the library You would then copy the files/folders out to the other drive MAKING SURE you copy them so that they are in the same relation to each other as they are in the original.
On the destination drive create a new empty Aperture library. You'll probably have the easiest time of it if you have two finder windows open, one on the original library and on on the destination. Revel Package contents on both libraries and then copy from the source to the destination replacing the items in the destination library with items from the source. Make sure you go from source (old) to destination (new). It sounds silly to emphasis this but once you start copying it will be easy to get disoriented and go in the wrong direction. Do something to make sure the source Finder window stands out from the destination Finder window.
I wouldn't worry about copying the previews or thumbnails those will be recreated when Aperture opens the new library BUT don't do anything with the Dobro or previews until you are sure the new library opens. In a worst case scenario you could retrieve the previews and still salvage something from your library.
Of course the possibility exists that you will hit the file(s) that are causing the error that is keeping you from doing this in a normal fashion. If so mark the file(s) that are having problems (color label will work well) and continue with the rest of the library. It is possible that the file(s) that won't copy are not of major importance to Aperture and the new library will open anyway. If not then there may be some other way to work around it. By labeling the files you'll at least know what didn;t copy.
That should do it if you're unsure of anything post back before starting.
good luck
Ps. Read this post Re: New iMac, Pegasus & Aperture? from a recent thread on backups and RAID. In it I explain why RAID is not a backup replacement. Once you recover from this you will need to put a true backup procedure in place.
regards
BTW here is OS X's definiiton of an Error -36
Type -36 error (I/O Errors (bummers)
This file is having difficulty while either reading from the drive or writing to the drive. The file
may have been improperly written data to the drive or the hard drive or disk may be damaged.
This is almost always indicative of a media error (hard error on the disk). Sometimes (rarely) it is transient.
Solutions: Try copying the file to another drive. Use a disk recovery software, such as Disk First Aid to examine the disk. You can try rebooting with all extensions off. Once in a while this will allow you to read the data. The file in question should be restored from a backup that was stored on a different disk. Regular backups can reduce the time to recover from this error.
Message was edited by: Frank Caggiano

IPhoto can't find Aperture library files

Since Apple added the ability to open Aperture libraries in iPhoto, I've been unable to so with my main Aperture library. If I create a new library in Aperture, no problem. Upgraded the library when the latest versions were released, performed all command-option first aid when opening, multiple times, duplicated, moved the library between different drives, relocated originals (it was completely managed), checked and played with permissions, all to no avail. When I open iPhoto, it brings up a notification that it's updating thumbnails. Then I immediately get the error "The photo “xxxxxxxx.JPG” could not be opened, because the original item cannot be found." I cancel and another immediate error, this continues on seemingly forever, and, with thousands of pictures in the library, I've basically got to Force Quit. The library is on an external drive and I've tried this on 3 Macs with the same result. If I'm within Aperture and search for any of the photos that iPhoto couldn't find, they're there and Aperture can show me them in the Finder. However, what I noticed today is that if I perform a manual search from the Finder of the library, it doesn't find the file. Oddly, if there are similar names; img_001 and img_001(1), searching for "img_001" won't show the first exactly matching file at all, but will show the second. Although, I can browse and they're sitting there right next to each other. Again, same behavior on multiple Macs. I'm thinking that the Finder behavior and iPhoto issue may be related. Any ideas?
Thanks in advance,
Dave

Léonie,
Results as follows:
Mac-Mini:~ Dave$ ls -B /Volumes/My\ Passport\ for\ Mac/Photos/IMG_0030.JPG
/Volumes/My Passport for Mac/Photos/IMG_0030.JPG
Mac-Mini:~ Dave$ ls -B /Volumes/My\ Passport\ for\ Mac/Photos/IMG_0030\ $1$.JPG
/Volumes/My Passport for Mac/Photos/IMG_0030 (1).JPG
The first command shows one of the problem files. Second command shows a similar file that has no issues. Nothing apparent problems to me from this test.
I also copied the problem file along with the non-problem file with the similar filename (1) to my desktop. When I begin any search string, the problem file disappears. If I completely rename it including extension, it disappears. If I make a copy and change it's name, neither show up. It seems as though there is some attribute of this file, all copies, and a bunch of others in my photo database, that is causing some kind of issue. I've taken a look at both file's info and there appears to be no differences, including permissions. Appears to be more of a file system/finder problem. I may try a different community.
Thanks again.

Aperture Library

Is it possible to work from my Aperture Library if it's on an external HD?
Additionally, is it possible to remove the images from the Aperture Library and then re-import them leaving them in place?
Thanks
Jeff

I have a problem with importing of a project, of a library from the one too an other computer library. It looks that the size of the library matters with a G5 2.0ghz, 10.4). Is it that it has too do with RAM and/or processor speed?
With smaller sized projects it lloks that it hasn't a problem with import the libary. But it has problems with generating thumbnails ( G5 2.0ghz, 10.4). Aperture starts to generate the thubnails, but freezes and (re)scipping and (re)showing the thumbnails. And aperture stops with to generate while it's not finished and restarts after a restart. Why has aperture to redo generating thumbnails?
Apending to the problem:
Is it possible to go endless in size with the aperture library virtueel.Or goes it together with a fast computer?
Can you update a library from smaal to 1/2 sixe jpegs?

Aperture library file size ?

Hello,
I have all my pictures on a specific drive. I don't want aperture to import the files into this aperture library, i only want the files to be referenced. So when i import the pictures from the drive, i select "Store in Current Location". And it seems to be ok (meaning when i click on a file and say show in finder, it shows the drive in question), only my aperture library (even when i import files as referenced) ... increases it's size drastically, no matter whether the files are stored in the library itself or if they are only referenced ... how come? I want to avoid a 100GB aperture library file!!
Can someone explain to me how this works?
regards,
k
(i just bought aperture 3)
Message was edited by: whateveraliasidontcare

K,
Aperture stores many little JPG files for every photo that is in your library (whether referenced or managed). There are thumbnails and previews for every photo unless you run out of space or turn off previews.
Your library should not increase by the *same size* if you store a photo *by reference* as if you store managed. For a managed photo, Aperture will have your original (master) plus the thumbnails and previews. The referenced will have only thumbnails and previews. You can browse your Aperture library by right-clicking and viewing the package contents. You can then look (*but don't ever touch!!!*) at what exactly Aperture is managing. You will see pictures with the same and/or similar names are your original, but you will see they are different sizes. If you see your original, then something is out of whack.
I hope your "100GB" library was just an example. If you store by reference, you would need a LOT of photos to make the thumbnails and previews take 100 GB.
nathan

Aperture Library movement

I need to move my Aperture library to another internal drive due to space considerations. Looked over this forum. I did move the library and redirect Aperture, rebooted, but I see that all the raw files of "projects" are still in my Pictures part of operating system drive - same as original Aperture library. And that's what most of the file space is used up by -raws. When I move these to the new library, they do not seem accessible - I get the warning icon which i think means i'm only seeing a thumbnail.
Any thoughts?
Thanks,
Robert
www.robertholland.com

HI Robert
you need to brush up on the difference between the two workflows, managed and referenced, see
http://www.apple.com/au/aperture/tutorials/
http://photo.rwboyer.com/
At this stage you are wanting to either "Relocate Masters for Project" or "Consolidate Masters for Project".
One moves the files and they remain referenced, the other will bring the files into a managed environment within your Aperture library.
Tony

Now that Xsi support is out - how to update Aperture library?

I have a host of 450D Xsi raw files in my Aperture library which to date Aperture could not read.
Now the RAW support is out, but Aperture is not generating large image previews, and thumbnails remain unrotated (for portrait pictures). Does anyone know what I should do to get it all to work?
Barney

So unfortunately, I deleted the original files off of my SD card after importing to Aperture. I tested exporting & re-importing on a small batch of files and it seems to work okay as far as properly handling the RAW.
My question now is: Is there a simple way to have Aperture treat the JPEG/RAW image pairs intelligently again? Originally, it recognized that I was shooting in JPEG+RAW and treated the pair of files as one item in the libarary. I don't want to create a stack, as that's much messier and not equivalent.
Thanks for everyone's patience and assistance so far.

Aperture Library Thumbnails

Similar Messages

Maybe you are looking for