![]() ![]() My Library 1 has 41,000 images with 1,000 projects and library 2 has 15,000 images with 350 projects, growing daily, so I am testing with other tiny libraries. If PSU works then it will save me lots of time, but if it doesn't then just the opposite. I have edited the wording of my original posting. Aperture just 'references' the libraries and can read/write as normal. However, they are saved as iPhoto libraries as opposed to Aperture libraries. Hope that thanks for the detailed steps.įirstly, I must correct myself. Import button to import (and optionally copy) new images Stop using Aperture as a management tool because you shouldn't run the import twice.ħ. When finished importing the metadata, select Tools-Built missing thumbnails and previews (again a time consuming task)Ħ. Depending on your volumes, this will take a while.good to start it before going to sleepĥ. When finished, select all files and read the metadata from the file to the catalog (right click on thumb-Metadata-Read metadata from file). A referenced database holds all the images in the Apple Library package and so your images are locked in. if you're using a referenced aperture database then change that to a non-referenced (managed) database. What you need to do to get the most info returned:ġ. Info from the database will be copied to the PSU database, that includes the albums. The Import-Aperture will import the Aperture database to the PSU database. Aperture isn't storing the Albums to the metadata and so that info won't return. The Import button is doing a import of the files and reads all the metadata to the catalog, optionally renames etc. Sorry for the length of this posting, but it might save some time in ping-ponging. Their information can be used to manually or batch update the descriptions and/or IPTC fields at a later date.Īs I have invested hundreds (or thousands) of hours creating these 'best shot selections', I wish to be able to keep them when I move 100% to PSU. These are very useful 'headlines' or 'placeholders' for sorting. One must also empty the system trash before importing, as iPhoto/Aperture appear to remember what had been there. This is an application internal trash and PSU will import any images there, so users must empty this trash before importing. I realize that some people do, but I cannot discover how to deactivate it. This can explode the number of images in the database and I don't want it. Nevertheless when importing, PSU picks all faces from group shots and creates additional images. IPhoto and Aperture have the ability to activate this feature. *** These are points I wish to address, in chronological order, NOT order of importance. Usually for personal purposes, but also for work. I once used this to create slideshows with audio. I have used this for creating online books for printing or more commonly, selections of images to create PDFs (with or without 'captions') for customers. PROJECTS (Aperture calls them iPhoto print projects, presumably only if the Aperture database is referenced to iPhoto). These become my archives of the best shots. I use this to sort images for editing and making my final choices. Either a smart album can be used to automatically collect several images according to selected criteria, or an album can be created manually. In my case a long list which can be hidden. It is a field I always use to help identifying shots and can be used later (in Aperture at least) to batch-change IPTC data. This is a name you can choose when importing new images. In my case a long list which can be hidden and usually is. LIBRARY: - Events (Aperture calls them projects) IPhoto's left hand column shows among other things: My prime interest lies in those points with a * Now to the other terms used and an explanation of my goals. My libraries are incidentally on external drives to make them future proof. ![]() Aperture has a useful plug-in to upload images to Photoshelter, which is very useful, but I will not discuss that here. I also import all images into iPhoto first before using Aperture for the bulk of my work. My databases are called iPhoto Libraries and are managed, i.e. doubling the size of the database, thus creating two independent applications which will then no longer talk to each other OR alternatively it can 'reference' the iPhoto database. Aperture has the facility to 'import' images from iPhoto, i.e. My Aperture handbook has fallen behind the bookshelf, so in this preface, I am guessing a few terms. I hope that this thread will help PSU and other users (including myself) who wish to transition from Apple's iPhoto or Aperture to Photo Supreme (PSU).ĭo other people here sometimes have trouble remembering terminologies? I know that I do, so to explain my goal, here is a short glossary. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |