Reconnecting
Aperture: Don't Import Unsupported Images As Referenced Masters
2007-10-26
A short Knowledgebase article from Apple:
Another good reason for using managed masters, or just not dealing with unsupported cameras at all.Referenced images from cameras that are newly supported sometimes cannot be connected after you update to a version of Mac OS X that supports them.
|
Aperture: Hazards of Referenced Masters -- Bone-Headedness Part 4
2007-07-19
This is the last in a series of short articles about how to protect referenced masters from one of their worst natural enemies: bone-headedness. From Part 1: The best medicine, then, is prevention. So how do you go about protecting referenced masters? They could be stored anywhere and called anything -- what kind of barriers can be constructed to protect them?
From the Finder I select the top-level folder of the folder structure to protect and press command I to bring up the Info window. I open up the permissions part at the bottom, and it looks like this:
By changing the Details pop-ups to Read Only and applying it to all enclosed items, the settings are propagated to all the files and folders:
Now if I try to modify a file, I get a dialog like this:
I get an opportunity to override by authenticating, but usually I would not want to, just accepting the OK button. If I drag a file to the trash, I get the same dialog.
To change everything back, I use the same procedure, this time setting the permissions to Read and Write for myself.
Part 4: Write Protect
For maximum paranoia against accidental modification or deletion, write protect the master image files. This can be easily achieved from the Finder.From the Finder I select the top-level folder of the folder structure to protect and press command I to bring up the Info window. I open up the permissions part at the bottom, and it looks like this:
By changing the Details pop-ups to Read Only and applying it to all enclosed items, the settings are propagated to all the files and folders:
Now if I try to modify a file, I get a dialog like this:
I get an opportunity to override by authenticating, but usually I would not want to, just accepting the OK button. If I drag a file to the trash, I get the same dialog.
To change everything back, I use the same procedure, this time setting the permissions to Read and Write for myself.
Aperture: Hazards of Referenced Masters -- Bone-Headedness Part 3
2007-07-14
This is a series of short articles about how to protect referenced masters from one of their worst natural enemies: bone-headedness. From Part 1: The best medicine, then, is prevention. So how do you go about protecting referenced masters? They could be stored anywhere and called anything -- what kind of barriers can be constructed to protect them?
But when they are relocated, where should they be put? Everyone has a different system for doing this. Often that system arose from a need to either find images or process them, but these are requirements that Aperture does not have of disk storage: the library and its tools take over that organizational role.
What is left to organize? There must be some logic to the folder structure. My answer is to organize around change and minimize risk. What can change?
If you are storing referenced masters primarily chronologically, say by month, then you add a new drive and all the new images get put on the new drive and the old ones stay on the old drive. It's a quick upgrade and you are unlikely to accidently delete or damage anything. Further, you can stop backing up the old drive: it will never change. Just keep the old off-site back up until you get rid of the smaller drive a few years from now. One small catch is that the addition of the new drive will happen mid-month. So do you have two July folders, one on each disk, or move the July folder to the new disk and then continue adding to it? I recommend the latter, and will be looking at how that can be achieved in this article.
If you are not storing referenced masters primarily chronologically, then the approach is different. Masters organized by client and then by project cannot be handled the same way as the strictly chronological system because any client could ask for another project and overrun an already-full disk. In this case it makes sense to copy everything over and stop using the old disk. Copying between disks can take a little while, even with fast disks -- about an hour per 100GB -- so this is something that may take some planning. The catch with this method of storage expansion is that backing up will need to include both drives now, so don't forget to change your settings or procedures to do that.
Both method of adding storage require copying, and Aperture can do it for you. In fact you should always use Aperture to do the copying. In that way Aperture always knows where its library masters are at all times and reconnecting is never needed.
To move referenced masters to another drive using Aperture, relocate them using exactly the same system of organization that was in use on the old drive. You already have a preset for this because the current organization or referenced masters was built with it.
I described one folder systems based primarily on date, and another based on client and project. But there are others. Which one is best? In my mind the best folder system is one that Aperture can create and maintain and that can be adequately backed up incrementally.
That may sound restrictive because you may not want to look at a library organized that way, but remember that the folder organization on the disk does not have to follow the library organization at all. For instance your library may be organized by client and then city (both using blue folders) and then by project because your work involves travel to different locations for each client to shoot vacation accommodation. But since renovation is common, you almost never need access to images that are more than three years old. So you organize your referenced masters on the disk by year and project (using Finder folders) and archive a whole year at a time to DVDs or a hard drive each time you start a new year. Note that the library still contains the thumbnails and the metadata for all images, allowing you to view, tag, and find those other images at any time.
Organize masters to reflect how you archive images and manage storage. Organize the library to reflect how you find and work with images.
Part 4 has been posted.
Part 3: Organize Masters For Growth
Relocating and renaming masters imported into Aperture helps to ensure that they will not be accidently altered, misplaced, or deleted as referenced files.But when they are relocated, where should they be put? Everyone has a different system for doing this. Often that system arose from a need to either find images or process them, but these are requirements that Aperture does not have of disk storage: the library and its tools take over that organizational role.
What is left to organize? There must be some logic to the folder structure. My answer is to organize around change and minimize risk. What can change?
Adding Storage
The first thing that changes is that the disk fills up and more is needed. Unless you have a RAID system that can be transparently expanded, you must either add a new disk to your computer and split the masters across both, or replace the old disk with the new one and copy everything over. Which is the better approach depends on how the masters have been organized, so ideally your master organization is planned according to your plans for expansion. Do you have any plans for expansion?If you are storing referenced masters primarily chronologically, say by month, then you add a new drive and all the new images get put on the new drive and the old ones stay on the old drive. It's a quick upgrade and you are unlikely to accidently delete or damage anything. Further, you can stop backing up the old drive: it will never change. Just keep the old off-site back up until you get rid of the smaller drive a few years from now. One small catch is that the addition of the new drive will happen mid-month. So do you have two July folders, one on each disk, or move the July folder to the new disk and then continue adding to it? I recommend the latter, and will be looking at how that can be achieved in this article.
If you are not storing referenced masters primarily chronologically, then the approach is different. Masters organized by client and then by project cannot be handled the same way as the strictly chronological system because any client could ask for another project and overrun an already-full disk. In this case it makes sense to copy everything over and stop using the old disk. Copying between disks can take a little while, even with fast disks -- about an hour per 100GB -- so this is something that may take some planning. The catch with this method of storage expansion is that backing up will need to include both drives now, so don't forget to change your settings or procedures to do that.
Both method of adding storage require copying, and Aperture can do it for you. In fact you should always use Aperture to do the copying. In that way Aperture always knows where its library masters are at all times and reconnecting is never needed.
To move referenced masters to another drive using Aperture, relocate them using exactly the same system of organization that was in use on the old drive. You already have a preset for this because the current organization or referenced masters was built with it.
Archiving
In deciding how to organize referenced masters there is more to consider than just storage expansion. The other change that occurs is that archiving is needed: some images no longer need to be at-hand and can be stored more cheaply or in a place that is not immediately available. These are not back-ups (copies stored short-term as insurance that you hope to never need) -- they are archives (originals stored long-term with the expectation that they will be needed).I described one folder systems based primarily on date, and another based on client and project. But there are others. Which one is best? In my mind the best folder system is one that Aperture can create and maintain and that can be adequately backed up incrementally.
That may sound restrictive because you may not want to look at a library organized that way, but remember that the folder organization on the disk does not have to follow the library organization at all. For instance your library may be organized by client and then city (both using blue folders) and then by project because your work involves travel to different locations for each client to shoot vacation accommodation. But since renovation is common, you almost never need access to images that are more than three years old. So you organize your referenced masters on the disk by year and project (using Finder folders) and archive a whole year at a time to DVDs or a hard drive each time you start a new year. Note that the library still contains the thumbnails and the metadata for all images, allowing you to view, tag, and find those other images at any time.
Organize masters to reflect how you archive images and manage storage. Organize the library to reflect how you find and work with images.
Part 4 has been posted.
Aperture: Hazards of Referenced Masters -- Bone-Headedness Part 2
2007-07-10
This is a series of short articles about how to protect referenced masters from one of their worst natural enemies: bone-headedness. From Part 1: The best medicine, then, is prevention. So how do you go about protecting referenced masters? They could be stored anywhere and called anything -- what kind of barriers can be constructed to protect them?
You can relocate masters in two ways: either by selecting individual images and from the File menu going to Relocate Masters For Library... or by control-clicking on a project and selecting Relocate Masters for Project to relocate an entire project full of images at once:
Relocating the masters also has the ability to rename as it moves. To relocate and rename at the same time, set up a new Name Format preset from the Relocate masters sheet:
By clicking on the Name Format drop-down and selecting Edit... Give the new name format a name and set it up something like this:
Then select that new name format and do the relocate. As the files are moved, the names will be changed. Here is a referenced master on the disk after it was relocated (I used a slightly different prefix than above in this example to show this image is referenced, omitting the dash):
The original image was called 6830-1.JPG. Importing added MAS-2005-04-20 and relocating added REF.
Why work this way? This workflow keeps all the images that are still being worked on in one place so they can easily be found with a smart album that shows only managed masters. This workflow means that if it's managed, then you're not done with it. The library becomes a staging area. Once relocated and renamed, the master files are immediately identified as being referenced from their name and you know that they have already been processed and so are ready for use or to be archived. And, since importing into the library makes a copy, the originals are still on the card or disk they came from and another layer of corruption insurance has been created.
Creating a smart album to show only managed files is straight forward. Create a new smart album by clicking on the magnifying glass next to the library (so it will apply globally) and add a File Status filter:
Then filter on Managed status and check the Ignore stack groupings box so that stacks don't hide any images:
Part 3 has been posted.
Part 2: Manage, then Relocate
Always import new images into the library as managed masters as a first step. Then edit, cull, rate, tag, stack as usual. Then finally move the masters out of the library using the Relocate command to a reserved area of your disk and add another prefix to show that they are referenced, such as "REF". Finally, possibly much later, delete the rejects.You can relocate masters in two ways: either by selecting individual images and from the File menu going to Relocate Masters For Library... or by control-clicking on a project and selecting Relocate Masters for Project to relocate an entire project full of images at once:
Relocating the masters also has the ability to rename as it moves. To relocate and rename at the same time, set up a new Name Format preset from the Relocate masters sheet:
By clicking on the Name Format drop-down and selecting Edit... Give the new name format a name and set it up something like this:
Then select that new name format and do the relocate. As the files are moved, the names will be changed. Here is a referenced master on the disk after it was relocated (I used a slightly different prefix than above in this example to show this image is referenced, omitting the dash):
The original image was called 6830-1.JPG. Importing added MAS-2005-04-20 and relocating added REF.
Why work this way? This workflow keeps all the images that are still being worked on in one place so they can easily be found with a smart album that shows only managed masters. This workflow means that if it's managed, then you're not done with it. The library becomes a staging area. Once relocated and renamed, the master files are immediately identified as being referenced from their name and you know that they have already been processed and so are ready for use or to be archived. And, since importing into the library makes a copy, the originals are still on the card or disk they came from and another layer of corruption insurance has been created.
Creating a smart album to show only managed files is straight forward. Create a new smart album by clicking on the magnifying glass next to the library (so it will apply globally) and add a File Status filter:
Then filter on Managed status and check the Ignore stack groupings box so that stacks don't hide any images:
Part 3 has been posted.
Aperture: Hazards of Referenced Masters -- Bone-Headedness Part 1
2007-07-06
Hello, I stumbled onto your page looking for help with Aperture., I'm new to digital photography and I think I accidentally moved my, master files to a removable hard drive and then deleted them, thinking, that they were saved in a vault somewhere else. Obviously I don't know, what I'm doing, but is there anyway to get aperture to let me work, with the library images that it has on my hard drive? All of my, pictures are there, in good enough resolution, but aperture won't let, me do anything with them because I don't have the masters. No, exporting, no emailing, no editing, nothing., Am I stuck with looking at these pictures forever and that is it?, Thanks a bunch for any help.
I see a quite a few postings on message boards and get emails from Aperture users who have done disastrous things to their referenced masters because they didn't realize that the files were still part of their Aperture library. Referenced masters are master image files stored outside the Aperture library. This feature allows a small internal hard drive, such as on a laptop, to maintain a very large image library where the originals are stored on a separate removable drive or central storage system. In the other kind of master storage, managed masters, the masters live inside the Aperture library itself. While not impossible, damaging managed masters takes some persistence and the barrier formed by the library protects them against most bone-headed errors.
That referenced masters live outside the library leaves them prone to several kinds of abuse. Moving them by hand is harmless, unless the move goes to another volume. That will break the connection with the library and require a reconnect. Aperture's Referenced File Manager does this well, but it is very fussy about restoring the connection. If the image has been edited, for instance, it will likely not reconnect. If the pixel dimensions have changed, it will not reconnect. If the file size has changed, it will not reconnect. And this is where the big problems start. Since Aperture only checks these things when reconnecting, problems can go undetected for a very long time. A reconnect is needed and suddenly many masters (and hence their versions) are effectively lost.
The best medicine, then, is prevention. So how do you go about protecting referenced masters? They could be stored anywhere and called anything -- what kind of barriers can be constructed to protect them?
This the first of a four-part series on protecting referenced masters.
The input screen allows a selection for the version name and can optionally rename the masters:
Above that setting is a block of information that gives confirmation of the change if an image is selected:
Another recommendation is to rename the masters in such a way that all of them have unique names. For instance, add the current date to the name given by the camera. This will ensure that as the camera or card numbering rolls over, the images still have unique names. While not critical, this defensive step may help in the future when it is necessary to list or index all of the images. Ensuring unique naming now will obviate managing duplicates and messing with hierarchies later on.
At the bottom of the Version Name drop-down the Edit... option allows the naming schemes to be edited. Here is how MAS prefix used above is defined:
Part 2 has been posted.
I see a quite a few postings on message boards and get emails from Aperture users who have done disastrous things to their referenced masters because they didn't realize that the files were still part of their Aperture library. Referenced masters are master image files stored outside the Aperture library. This feature allows a small internal hard drive, such as on a laptop, to maintain a very large image library where the originals are stored on a separate removable drive or central storage system. In the other kind of master storage, managed masters, the masters live inside the Aperture library itself. While not impossible, damaging managed masters takes some persistence and the barrier formed by the library protects them against most bone-headed errors.
That referenced masters live outside the library leaves them prone to several kinds of abuse. Moving them by hand is harmless, unless the move goes to another volume. That will break the connection with the library and require a reconnect. Aperture's Referenced File Manager does this well, but it is very fussy about restoring the connection. If the image has been edited, for instance, it will likely not reconnect. If the pixel dimensions have changed, it will not reconnect. If the file size has changed, it will not reconnect. And this is where the big problems start. Since Aperture only checks these things when reconnecting, problems can go undetected for a very long time. A reconnect is needed and suddenly many masters (and hence their versions) are effectively lost.
The best medicine, then, is prevention. So how do you go about protecting referenced masters? They could be stored anywhere and called anything -- what kind of barriers can be constructed to protect them?
This the first of a four-part series on protecting referenced masters.
Part 1: Name Defensively
When you import, rename the masters in such a way that all of them can be seen to be masters. Prefixing with "MAS" or an equivalent short word will make masters instantly recognizable and you will no longer feel compelled to trash them in haste.The input screen allows a selection for the version name and can optionally rename the masters:
Above that setting is a block of information that gives confirmation of the change if an image is selected:
Another recommendation is to rename the masters in such a way that all of them have unique names. For instance, add the current date to the name given by the camera. This will ensure that as the camera or card numbering rolls over, the images still have unique names. While not critical, this defensive step may help in the future when it is necessary to list or index all of the images. Ensuring unique naming now will obviate managing duplicates and messing with hierarchies later on.
At the bottom of the Version Name drop-down the Edit... option allows the naming schemes to be edited. Here is how MAS prefix used above is defined:
Part 2 has been posted.
Aperture: How Do I Manage Adjusting, Rating, and Keywording In The Field With A Small Hard Drive?
2007-05-27
After I erase the master files the images and ratings etc still appear in Aperture but of course the images show as off line. Upon returning home I copy all of my images onto my eSATA hard drives (from DVD or from Wolverine). Now I want to have Aperture look for the master images on the eSATA drive and re connect, but cannot figure out how to do this. The only solution I have so far is to re do the rating, culling, keywords etc referencing the images on the eSATA drive and erase the older versions. This besides being time consuming is for me fraught with peril. My administrative skills are almost non existent.
You can reconnect the copied masters with the Referenced File Manager. I have an article that describes how to do this called Burning Masters To DVD and The Referenced File Manager. However, you can make all of this workflow faster and less perilous by working with complete projects rather than individual masters. And you won't have to go near the Referenced File Manager to do it.
As you import images into the Aperture library on your laptop, make the projects fairly small. Do your rating and sorting. When your laptop is too full, export these projects a few at a time.
You can check that the projects look OK by dropping them onto an open TextWrangler document and seeing if the expected files are present:
Looks good to me. Also check the size of the project in the Finder as a sanity check:
My project has 18 images of about 2.5MB each, so that looks right.
Burn as many as will fit onto a DVD, verify the DVD, and then delete the project in the Aperture library and empty the trash. Emptying the trash is necessary because the deleted masters in the projects will be moved there. Repeat with all the projects you want to move. You'll have to come up with a foolproof scheme for naming these projects so there is no chance of deleting the wrong thing.
Now when you get back into the office, just import the projects into Aperture's library. That's it. Mount the DVD and drag the projects to the library:
If you trust that the keywords coming in with the projects are well-behaved (ie match the scheme you are using, have the correct spelling etc.) then before importing the projects, unlock the keyword HUD by bringing it up with shift H and clicking the lock icon. This will give the newly-imported images the same keywords are are already used in the library. If you leave the keyword HUD locked, the imported keywords will be added to a separate keyword hierarchy called Imported Keywords and have to be merged later.
The big advantage of using projects to move images around is that they are self-contained. They include all the masters, versions, keywords, ratings, albums, adjustments, and everything else needed to work instantly as soon as they are put back into the library. They even contain thumbnails, so you won't have to wait for them to be regenerated once you are back in the office.
Aperture 1.5: Burning Masters to DVD and The Referenced File Manager
2006-10-24
Now that Aperture supports image masters outside of the library (referenced masters), it is possible to store these large files on removable media. Accessing referenced masters on entire drives, such as networked volumes and Firewire drives this is straight forward: just mount the volume.
However, for write-only media such as DVDs and CDs there is a hiccup that will require a trip to Aperture's Referenced File Manager. I will burn a CD with some images to illustrate. Here are my images in the Grid view:
They are currently all inside my library (managed), so to put them on a CD I have to make them referenced with the Relocate Masters. First I put a blank CD in the drive first so it shows up on the desktop and I will be able to specify it as a destination for my masters:
I select all of my images and go to File > Relocate Masters and choose a folder scheme that stores them by date. Aperture does not split a group of files across several disks, so it is necessary to make sure that all my files fit on a single disk --easy in this case because there are only a few.
I press Relocate Masters and my files are been copied to the CD. But they are not really there yet. They are on a disk image that the Finder has created for me that mimics the CD. Here is the Finder view of this disk, all ready to burn:
So the next step is to actually burn the files onto the disk. Once I have chosen a name for this disk (Masters) and the burn is complete I have my finished disk:
Of course that's a terrible name for a disk if I were doing this for real. I'd pick something with a date in it and make sure that the disk name was unique.
But now there is a problem. If I try to do anything with the images on the CD, they are tagged to show that the master cannot be found. Not only does Aperture not have the masters in its library, but it knows that it does not know where the masters are. They are disconnected:
So where are my masters? Why can't Aperture find them? If I Iook on the CD they are definitely there:
So what has happened?
Aperture has recorded the location of the masters as being on the disk image the Finder created for me instead of on the CD I just burned. So the library references point to locations on my hard disk that no longer have the master files. Somehow I have to correct those references.
It is time to fire up the Referenced File Manager and tell Aperture where the masters really are. I'll work with just six images first, by selecting them and control-clicking:
The window that appears has two halves. The upper half shows the status of the files that are referenced. This is the "problem" half:
On the left are the volumes that the images are supposed to reside on. Clicking on a volume will bring up the selected files that were last seen on that volume on the browser in the center. Red means that they cannot be found. And on the right is a pane that details the selected image from the browser:
The lower half of the window is the "solution" half, known as Reconnect Options:
It is a standard column file browser. I can reconnect the image I have selected in the upper half to its master by using this browser and checking that the image matches. I locate the selected master image like this:
After a short delay (and a confusing one too) the Reconnect and Reconnect All buttons become enabled. If I click on Reconnect, then the status on the top half changes, since one out of five is now reconnected:
And the file name in the upper browser turns black from red. If I had to do this one at a time it would be horribly tedious. But I don't. If I select all the remaining images in the upper half, and then navigate to just one of them in the lower half, pressing Reconnect All will do exactly that and all will be reconnected with their master files:
Once repeated for all the remaining images in this project, the thumbnails look like this:
If I eject the CD, the icons change to indicate that the masters are offline, but not disconnected:
Now what if I decide that I don't want the masters on the CD any more? It may be that I have pulled this CD out of storage and want to use the images. It's way too slow to try to work with the masters this way. I simply make the images managed again by using Consolidate Masters. They are copied off the CD into the library and Aperture uses them from that location. I can pop out the CD.
But when I am done with that project I don't want the images in the library any more. I can't delete them or I will lose everything about them. I don't want to burn another CD or DVD with my masters on again -- I already have a perfectly good copy in storage.
If I try to relocate them, then it does not work:
There is a way to do it. First create a temporary folder on your desktop called Temp. Then relocate all the masters into that folder using the same naming scheme that you used on the CD or DVD. That step gets them out of the library. Next, drag that folder to the trash. Yes really. No need to empty the trash.
Select all the images in the grid view and Open up the Referenced File Manager. Select All Volumes from the list of volumes and click the Verify button. Aperture will suddenly realize that it has lost the masters and they will appear on the browser pane. Now on the lower half of the window navigate to the CD or DVD and reconnect all the images.
Once you are happy that everything is OK, empty the trash.
However, for write-only media such as DVDs and CDs there is a hiccup that will require a trip to Aperture's Referenced File Manager. I will burn a CD with some images to illustrate. Here are my images in the Grid view:
They are currently all inside my library (managed), so to put them on a CD I have to make them referenced with the Relocate Masters. First I put a blank CD in the drive first so it shows up on the desktop and I will be able to specify it as a destination for my masters:
I select all of my images and go to File > Relocate Masters and choose a folder scheme that stores them by date. Aperture does not split a group of files across several disks, so it is necessary to make sure that all my files fit on a single disk --easy in this case because there are only a few.
I press Relocate Masters and my files are been copied to the CD. But they are not really there yet. They are on a disk image that the Finder has created for me that mimics the CD. Here is the Finder view of this disk, all ready to burn:
So the next step is to actually burn the files onto the disk. Once I have chosen a name for this disk (Masters) and the burn is complete I have my finished disk:
Of course that's a terrible name for a disk if I were doing this for real. I'd pick something with a date in it and make sure that the disk name was unique.
But now there is a problem. If I try to do anything with the images on the CD, they are tagged to show that the master cannot be found. Not only does Aperture not have the masters in its library, but it knows that it does not know where the masters are. They are disconnected:
So where are my masters? Why can't Aperture find them? If I Iook on the CD they are definitely there:
So what has happened?
Aperture has recorded the location of the masters as being on the disk image the Finder created for me instead of on the CD I just burned. So the library references point to locations on my hard disk that no longer have the master files. Somehow I have to correct those references.
It is time to fire up the Referenced File Manager and tell Aperture where the masters really are. I'll work with just six images first, by selecting them and control-clicking:
The window that appears has two halves. The upper half shows the status of the files that are referenced. This is the "problem" half:
On the left are the volumes that the images are supposed to reside on. Clicking on a volume will bring up the selected files that were last seen on that volume on the browser in the center. Red means that they cannot be found. And on the right is a pane that details the selected image from the browser:
The lower half of the window is the "solution" half, known as Reconnect Options:
It is a standard column file browser. I can reconnect the image I have selected in the upper half to its master by using this browser and checking that the image matches. I locate the selected master image like this:
After a short delay (and a confusing one too) the Reconnect and Reconnect All buttons become enabled. If I click on Reconnect, then the status on the top half changes, since one out of five is now reconnected:
And the file name in the upper browser turns black from red. If I had to do this one at a time it would be horribly tedious. But I don't. If I select all the remaining images in the upper half, and then navigate to just one of them in the lower half, pressing Reconnect All will do exactly that and all will be reconnected with their master files:
Once repeated for all the remaining images in this project, the thumbnails look like this:
If I eject the CD, the icons change to indicate that the masters are offline, but not disconnected:
Now what if I decide that I don't want the masters on the CD any more? It may be that I have pulled this CD out of storage and want to use the images. It's way too slow to try to work with the masters this way. I simply make the images managed again by using Consolidate Masters. They are copied off the CD into the library and Aperture uses them from that location. I can pop out the CD.
But when I am done with that project I don't want the images in the library any more. I can't delete them or I will lose everything about them. I don't want to burn another CD or DVD with my masters on again -- I already have a perfectly good copy in storage.
If I try to relocate them, then it does not work:
There is a way to do it. First create a temporary folder on your desktop called Temp. Then relocate all the masters into that folder using the same naming scheme that you used on the CD or DVD. That step gets them out of the library. Next, drag that folder to the trash. Yes really. No need to empty the trash.
Select all the images in the grid view and Open up the Referenced File Manager. Select All Volumes from the list of volumes and click the Verify button. Aperture will suddenly realize that it has lost the masters and they will appear on the browser pane. Now on the lower half of the window navigate to the CD or DVD and reconnect all the images.
Once you are happy that everything is OK, empty the trash.
The Bagelturf site welcomes Donations of any size