Aperture library transferring very slowly

I have bought a new Retina MBP and want to transfer my Aperture library from my old MBP to this one. I first tried via Ethernet and the transfer was unbearably slow (estimated time 17 hours). I then tried a Firewire cable with the Thunderbolt convertor and again, the same amount of time. Finally I thought about transferring the library to an external HD and then transferring to my new MBP, and again, exactly the same thing.
My thoughts here then are that this can't be anything to do with the type of cable I'm using or my new MBP, but rather the actual library itself.
Is there anything pertinent to an Aperture library that would prevent it from transferring faster? (I have also tried the Export/Import options in Aperture itself and I've had exactly the same unberarbly slow transfer rates.)

Thank you Léonie
At the moment I use managed files during the time of working on them for my clients in an aperture library called "Work". Later I "archive" the older ones by moving them as referenced to an external Drobo RAID System to free space on my computer within a special Aperture library called "Archive". For this I use the Export/Import library commands. The working Aperture library is managed, the archive library is referenced. But the transfer between is much work. But I had trouble with bad libraries from time to time, so I decided to seperate my images in two libraries. "Work" has a maximum of about 5.000 images. If I get in trouble with it, a rebuild or a reinstall from TimeMachine won't take too long. "Archive" has 200.000 images plus, but referenced. Because I don't touch those images very often, except export, there is a very small level of failure here.
Maybe I move "Work" to referenced too, because of your hints. Thank you!
One question to caughtredhandedand other users of the Retina MacBook Pro: Is ist fast enough for heavy work with Aperture and Photoshop? I thought about switching my whole work environment to a Retina with 16 GB RAM, instead of using a notebook plus a desktop. At the moment I use a 2007 MacPro Quad 3 GHz at the office for Photoshop and Aperture and a 2009 MacBook Pro for on location work with Aperture. I would be glad not to need to do synchs and transfers between two machines any more.
In this case I have to put the described "Archive" Aperture library itself oo an attached external drive because of the imited space in the internal SSD of the Retina MBP. Only the "Work" library and its images can stay internal. Will such a big library like my "Archive" with 200.000 plus referenced files work fast enough when started from an external RAID? At the moment my RAID is a Drobo S with Firewire 800.
There is a thunderbolt RAID from Promise available, but I want to wait for the new Drobo 5D:
http://www.drobo.com/products/professionals/drobo-5d/index.php
Maybe any Retina MBP owner wants to share his experience?
Best regards
Wolfram

Similar Messages

Copying of iPhoto library going very slowly

Hello, all,
Yesterday I purchased a brand new 1TB firewire 800 external drive. It's correctly formatted for my Mac. I had wanted to put my iPhoto library on this drive, OR use it as a backup location for the library. Either way, I needed to copy it over from my iMac's internal drive.
I tried twice to copy the library (using the Finder), which lists itself as 89GB. Each time the Finder progress bar indicated the copy would take two to three days. That sounded like way too short a time over Firewire 800. To test things out, I did a different backup copy of my *iTunes* library, which is also over 80GB. That library lives on a different external drive, using Firewire 400. THAT copy took less than an hour, and it had to go downstream from one external and then upstream to the new external. A second copy of other files from that external drive also went swimmingly: 22GB in about 12 minutes.
Does anyone have any insight into what might be happening? Is there something unusual about iPhoto libraries that makes them copy more slowly than other kinds of files?
Thanks for your help!

I found a fast soution 45 Gb Library copied in ~30 min. over USB 2.0
I did a semi-manual copy, by opening the iPhoto Library - "Show package contents" (in right click menu) then copying the contents to a new iPhoto libaray "Package"
Instead of copying all at once copy the small files/folders in one batch, wati to complete, then copy the larger files folders. You can copy the package contents one folder at a time or a few at a time. I found that copying the Library files in one batch, then copying the Masters, Previews, & Thumbnails in a second batch seemed to work well without choking up.
Here's the steps
Connect your hard drive or Mac in Target disk mode
navigate to the folder containing the iPhoto Library you wish to copy
'Right click' Show Package Contents
You'll see apx 19 files - select all but exclude 3 folders: Masters, Previews, & Thumbnails you'll come back for theses later
Copy these files to an empty folder on your destination drive/Mac (Later you'll use iPhoto to make a new libary "Package" then you'll put these files inside it) The copy should take a few minutes, high volume + tiny files
When the first copy is finished, go back and copy the remaining 3 folders Masters, Previews, & Thumbnails. This is the opposite as previous step, lower volume + larger files. Copy speeds should be normal ie 30 min. for 45 Gb over USB 2.0.
Once all these files and folders are copied you need to put them into an empty iPhoto Library container. An easy way to do this is
Launch iPhoto holding the Option key
Choose 'New Library' (choose an apprpriate name)
Quit iPhoto
in Finder go to the new Library you just created (User/Pictures/) - be sure its the one you just made
Right Click (Control + Click) the iPhoto Libraray
Choose - Show Package Contents (now you're looking at the contents that makup an iPhoto library)
Select all these files and folders and delete them to the trash Open the folder that has your freshly copied files and put them in this empty iPhoto Library package.
Close finder windows (disconnect your hard drive or Mac)
Launch iPhoto (you can hold the Option Key while launching iPhoto to choose the correct Library if you have more than one).
Viola. You should have a functional copy from your old Mac/External hard drive.
REMEMBER!
The easiest way to mess up your iPhoto Library is to move things around inside the "Package contents" of your iPhoto Library. Its hidden in there for a reason, so don't go mucking about under the hood. Best practice is to touch nothing inside the "Show Package Contetns" of your iPhoto library. As described above, we're merely just speeding up a file transfer and copying files so they mirror their source in a new destination. Good luck.

Podcasts transfer very slowly

For some reason all my podcasts are transfering very slowly onto my ipod. before today it was fine, but now it taking half an hour to transfer one podcast. Can anyone help. Ive tried reseting it twice and nothings happening.

Only with the Q tool used in conjunction with the y feature (history picture and developped picture side by side)!

FCPX and Aperture Library Issues

Does anyone else have issues with FCPX being unbearably slow when loading an Aperture library when accessing the Photos window on the lower right? I have all the most current versions of both Aperture and FCPX. I have a Macbook Pro Retina with i7 2.6gig processor. 16 gigs of RAM. My Aperture library is very large, about 300,000+ images. The Aperture is located on an external Thunderbolt drive. It can take as much as an hour for the still images to show up in the photo window. Any suggestions our there for speeding this process up. It's one of the main reasons I use Aperture, the supposed terrific integration between all Apple programs. I this speed it's much faster to just export the images and forget about going through FCPX. Any suggestions are greatly appreciated.

If you don't need all 300,000+ images in FCP, I would export what you need and import it into the event library.

Can't Import Aperture Library

I am trying to import my Aperture Library into Photos. I open Photos and select the Aperture Library and the conversion starts.
After about 1 hour the conversion stops at 69% and an error message appears. See attachment.
Second question. When I move my Aperture library to Photos is the original Aperture library altered?
Thanks
Derek

I have exactly the same issue. I have a large (535 GB) aperture library stored on an external HD. The HD is correctly formatted and I have rebuilt the aperture library to ensure there are no problems with it. It works fine in aperture.
When I start the conversion it runs for hours (I had to leave it overnight. At some point in the process photos must have begun to repair the library because when I check it it has reached 69% and then I get the same message as you.
When i close the dialogue box photos "cleans up" which takes another few hours. Oddly when I check the contents of the HD before the clean up process there is a file that looks like a photo library and is the same size as my aperture library.
Very frustrating. Any ideas very welcome!

After upgrading to OS X Lion Aperture 3.1.3 runs very slowly and crashes

After upgrading to OS X Lion Aperture 3.1.3 runs very slowly and crashes regularly when editing and/or exporting images. Prior to the upgrade these problems did not exist - has anyone else encountered this behavior and found a resolution?
My iMac has 2GB of RAM (max RAM is 3GB according to the machine specs) and uses a 2TB external drive for the Aperture library and Time machine backups.

Thanks for the suggestions. Unfortunately after doing the Repair Permissions and rebuilding the Aperture Library the performance has not improved.
I cleared out the cache(s) by removing all of the files in the following folders and restarting:
Hard Drive/Library/Caches
Hard Drive/System/Library/Caches
Hard Drive/Users/(Your user)/Library/Caches
which seems to have helped a little bit. I did notice that in my Users folder there are 111 items:
username
username 1 (then folders with the same name up to 109)
Shared
could the extra username folders be causing the performance issue? In each folder is a Library folder, in the Library folder is a Preferences folder and in the Preferences folder is a com.apple.internetconfigpriv.plist file and sometimes a com.apple.LaunchServices.plist file.
Only the username 1's Library folder has the standard Caches, Fonts, Logs & Preferences folders.
Is it safe to remove the username 2 - 109 folders? If so is the creation of these folders something I can turn off?

Transfering aperture library via vault to new comp

I apologize in advance if my question already have been answered in another thread. But I couldn't find any threads matching my problems.
I recently bought the new iMac after my old 24" could not handle the pressure anymore. I wanted to move my aperture library from the old to the new. And ofcourse I wanted all info (adjustment changes and so on) to come with in the move. After reading a few threads on the subject I created a "Vault" that I later opened up in the new comp. At a fist glance everything looks great in aperture but when opening up a picture to make adjustments it says "image offline".
On my old comp I can see (where my pics are stored) two aperture files:
Aperture Library
Aperture Library_original
…so far so good.
But then that are tons (well, many) folders named like my projects in aperture. And not folders within the aperture library file but stand alone…if that makes any sense.
What am I doing wrong? I get all the pics over to my new comp with the help of Vault but can't edit any of my pics from a few months back (when for some reason aperture started to create folders outside the library file)
On my new iMac i have 2 files
Aperture Library
Aperture Library_old
...so no folders got transfered
/Jonatan, sweden

It looks like your Aperture library were a referenced library. When you imported your image files you did not import the originals into the Aperture library, but stored them in folders outside the library. That are folders named like your projects that you are seeing. When Aperture needs to access the originals to render edited versions, it will reference the image files in those folders, see this section in the Aperture 3 User Manual: Aperture 3 User Manual: Working with Referenced Images
When you create a vault, Aperture will only include images that you imported into the library, not the originals you stored outside. You need to copy the folders with projects as well to your new mac and reconnect them to the image versions, otherwise you will not be able to edit your images.
But it looks like you did create these folders outside accidentally and did not intend to use referenced original files. If that is so, I'd suggest to repair this, by consolidating your library.
Select the "Photos" view in the source list of your Aperture Library and select all your images at once.
Then use the command "File > Consolidate Originals" from the main menu bar. This will move (or copy) all referenced images from the folders outside into your Aperture library.
When you now create a vault, it will contain all images. Use this new vault to recreate your Aperture library on your new mac. You can also simply copy your Aperture library itself to your new mac. You do not need the detour using a vault.
BTW: Where Aperture will store the originals image files depends on the settings in the "Import" panel. Make sure the "Store Files" option is set to "In the Aperture Library".
Regards
Léonie

Aperture Library Very Slow Copy to LaCie Thunderbolt Drive

Just installed new LaCie Thunderbolt drive and copying various media files to it. Music and video files copied like a rocket. My Aperture folder is copying as slow as molasses. Right now it says 2 days to copy 211GB. Any help would be appreciated.

Sorry, I misread Mtn Ed's last note. My USB2 was stalling out at 2-3 MB per second. Quite a bit slower than the stated Thunderbolt rate to say the least. There is a portion of the Aperture Library that copies at a very slow speed, but after an hour or so it kicks back up to normal file transfer rates. Finder was originally estimating over 20 hours for the copy to complete. Now the total elapsed time will be about 3 hours for 350GB.

Aperture suddenly becomes very slow opening library

Hi.
I've got only 100 or so photos, and Aperture suddenly becomes very slow, it take a couple of minutes now to open the library.
Just before this started to happen, I got a very short massage, saying something like, "It's repairing some files."
I wonder if there are some corrupt files there, causing very slow opening the program.
Is there any way to check this and fix this problem?
I'm using 3.4.3, and OS 10.8.3.
I appreciate your help.
Hiro

I'm surprised nobody has responded to this yet. Hopefully you have already figured it out, but if you double click on the aperture library while holding down the option and command keys, Aperture will bring up a dialog that gives you three options for dealing with potential library issues: repair permissions, repair the library or rebuild the library. You should try them in that order, and it is a good idea to back up your library first (especially before rebuilding the library).
Hope this helps.

Transferring Aperture Library to Time Capsule, 63GB taking 6 days?

I've checked my connection speed says on the Network Assistant, says the Ethernet Connection speed is 1GBit/sec, I've turned wireless off so in theory it should be transferring a LOT faster than it is. Its taken 1/2 and hour so far and only done 366MB. There's around 400GB of space left on the Time Capsule so I'm just about at my wits end

Wow. I was thinking of getting this but those speeds are really slow. Once you have your Aperature Library on your Time Capsule, will you be able to access your Aperture Library from any Mac on your network? For example, I have a 27'' iMac and a Mac Mini. I have my iPhoto Library on my iMac but would like to use that iPhoto Library when I turn on my Mac Mini. Can I do that? Have both computers open my Library from the networked Time Capsule? Is that what you are trying to do?

Transferring images out of Aperture library

I recently acquired Aperture and plan to import my existing library into the Aperture library. My existing library consists of a lot of .nefs and almost as many jpgs. Once my existing library is imported I plan to let Aperture manage and backup the images in a vault, and delete my old library file structure (after waiting long enough to be confident everything is safe).
My question: is it possible to pull an old jpg out of the Aperture library and insert it into another program without opening Aperture? For example, if I want to put an image in a greeting card, is there any way I can go into the Aperture library through the Finder to locate and transfer the image?
Thanks!
Steve

Yes, but it isn't elegant.
Right click on the Aperture Library and select "Show package contents"
Pick the Project and again, right click and select "Show package contents"
Then, out of the list of folders, one per image, try and figure out what image you need (or Spotlight if you know the filename).
There again, launching Aperture and exporting the image isn't that slow after all.
Possible to do it with Automator/Applescript as well I believe. Unsure there is a script out there but quite likely.

Opening Aperture Library from my Drobo (Very Slow)

I have a Firewire Drobo, which I love, and I use Aperture on my Mac. I currently have my primary Aperture Library (~125GB) on my Drobo. I have been experiencing an issue with slowness when opening my Aperture library from my Drobo. It takes several minutes (5-6) to open my library from the Drobo and am wondering if 1) others are experiencing excessive slowness when opening their Aperture Library from a Drobo and/or 2) if I would be better off just using a regular firewire drive for my Aperture library and using the Drobo just for my Aperture Vault and not my primary library?
It seems that this issue has gradually gotten worse as my library has increased in size. When the library was 50GB it seemed to open pretty quickly, but the bigger it gets the longer it takes to open. Once it is open it is fairly snappy, although if I am reading and writing a lot of data to the Drobo simultaneously I will see some slowness sometimes. This machine is the current generation of 24" iMac with 4GB of RAM. My Drobo is filled with 3 - 1TB Western Digital Green drives and 1 500GB WD Green drive.
Would love to hear if others are having a similar experience and any ideas for better performance.
Thanks!
Guy

I don't think the FW is the problem, although it might be
I was keeping my Aperture library on a Drobo and ALL of the images were referenced and not managed.
And like you, it became progressively slower (5-10-15-20 minutes to open) and then became corrupted on more than one occasion. After the last episode and after substantial heroic efforts (48 hours of rebuilding), I was able to recover the library. Once recovered, I moved the library to my internal drive and left all of my images as referenced on the Drobo. The library since the move has been fine. I have occasional images which appear to become corrupted on the Drobo (not recognizable by Aperture or Photoshop or Preview), that fortunately, I simply replace the RAW file in the appropriate location from a back up copy of the RAW file and everything is fine.
This has been discussed with Data Robotics and after several weeks I still don't have an answer from an email I sent providing all the requested information.
Bottom Line. Place your referenced your images on Drobo, but make sure you have at least two other additional backup of your original datafiles. Move your library to some other drive immediately!!
My suspicion is Aperture and Drobo RAID system do not work well together and Data Robotics has been disappointing in terms of technical response to inquiries.
I have two Drobo boxes and they are used daily, but at this point I always, always always have at least two back ups on whatever is on the Drobo. My dream was it would be a highly or super reliable copy of my data, but at this point, I really do not consider them to be even a reliable copy, given the random corruption issues and Data Robotics poor support.
I am investigating alternative large data systems and the most interesting thus far is the WD Share gigabit system. Data Robotics says that they only certify one other FW drive and it HAS to be a Data Robotic drive and not another vendors. FW is supposed to support up to 16 devices according to Apple so there is a huge disconnect. I do use several drives downstream from my 2nd Gen Drobo units, I mount/unmount religiously and have not had obvious problems with other drives.
Having said that, I have not had another corruption problem since December 26 or so, but I also have not looked at every RAW file of the 40,000 stored on the Drobo. I figure I will find more, but will replace them as I find them.
Regards, Steven

Aperture library to lightroom plugin not transfering all photos or projects.

I am trying to use the recent aperture import plug in added to LR5. Many of my projects and photos are failing transfer stating "(Possible reasons include asset offline or unsupported asset type.)" I cannot find the difference of the failed jpegs, NEFs, from the others which tranfered. Any help, suggestions??

No, no, no. Can't believe they still don't understand the plugin after all this time. Adobe support is abysmal. And you pay a subscription fee!
The plug-in is a great alternative, but it does have issues. And the most important steps for migration need to be done in Aperture, which may explain their skills gap.
See this post for a partial explanation.
How did your migration to Adobe Lightroom go?
The key to NOT running out of disk space is to relocate your images from "managed" status to "referenced". You can specify a better folder structure for your resulting Lightroom library. Be aware that you will need some overhead, as your Aperture library (metadata) takes space, as your Lightroom catalog will, too. But migrating "managed" Aperture images results in a full copy.
There's other considerations for Aperture previews. Although much smaller, all previews "should" be copied. I've actually found that the plugin fails to copy a majority of previews.
Lightroom will copy managed raw files, but will just point to referenced raw files. If you choose to copy previews, it will copy all previews. Not much to the plugin, but it helps to know to pre-tag images in Aperture, and make sure you do some sort of file-level compare to make sure everything is copied over. I've made several posts on these issues under "Photo Enthusiast" in this forum.
https://forums.adobe.com/community/lightroom/content

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.

Running VERY slowly, software quitting unexpectedly...

Hi,
A couple of days ago my MBP started running very slowly – everything from opening an app to surfing the net. I put the slow internet down to an issue with my internet tethering (via iPhone 4), but then everything else started going wrong…
I was trying to update Skype from version 2.x to version 5, but the download never completed; I had also been in the process of downloading a few podcasts, but had paused these transfers to try and speed up the Skype download.
Then I kept receiving error messages that were saying that Firefox had ‘quit unexpectedly’, and then the same happened with error messages for Skype. I tried reporting these issues, reopening the app, and ignoring the issue, but nothing happened. Now I have uninstalled Skype.
I then noticed that my shortcut bar wouldn’t appear properly when I moved my cursor to the bottom of the screen, although it would pop up maybe 15-30 seconds later. Trying to open a Finder window, or clicking on a shortcut would take forever for the action to complete, and now iTunes and Firefox wont open at all.
I have started backing things up to an external hdd, and this takes forever too – it took all night to update my Aperture 3 Vault, and I was told it would take >90 hours to backup iTunes. With my iTunes backup, it actually stops midway through the process because of some issue with an iPhone app (Urbanspoon). Once I have everything backed up, I guess I’ll need to reinstall OSX, but would like to avoid doing that if I can – especially as my hdd is starting to overheat from all the work it is doing (and the fact that all backups are taking so long!). The last thing I want is my external hdd to crash and lose my backups! I left the MBP this morning whilst it was running the Repair Disk element in Disk Utility, and I have just read about Hardware Test, which I will try after work.
My research has suggested that this issue could be due to a memory issue, RAM or hdd overload, or even a failing hdd. Either way, it’s very disappointing as I’ve only had the machine since Dec 2010.
I am running Snow Leopard, and am up-to-date with all system updates, and would be very grateful for any suggestions.
Thanks.

If it's not functioning the way it was intended then take it to an Apple store or AASP. You are under warranty.

Aperture library transferring very slowly

Similar Messages

Maybe you are looking for