Moving Referenced Images to a new HD

Hi,
I have my 500GB external HD almost full with all my Aperture referenced images.
I got a new 1TB HD.
I Would like to move all my original folders keeping Aperture modifications on the images (metadata, adjustments, etc...).
Can I just copy the content of 500GB HD into the 1TB and somehow give to Aperture the path to the new HD? (the library file is on the computer's HD)
Thanks!

You can copy everything and then reconnect the files, but you'd be better off using the File>Relocate Masters... command.
Ian

Similar Messages

How to move referenced images to a new Hard Drive

All my Aperture referenced images (about 80.000) are stored at a 300gb firewire HD. That's not enough and I plan to move all my photos to a new HD, 1Tb probably.
I understand that I can't move the images directly from one drive to another. So what's the easiest and painless way to upgrade and still maintain the integrity of Aperture Library ?

{quote:title=Bauhausler wrote:}I understand that I can't move the images directly from one drive to another.{quote}
Well, that's exactly what you can (and should) do. Then use the "Manage Referenced Files..." command.
Take a look at my answers in this recent thread:
http://discussions.apple.com/thread.jspa?threadID=1721897
Regards
Paul K

Moving still images to a new location

I am part way through creating a slide show and I would like to move the image files to a new location on my HDD. I think there is a Move tool to do this in Premiere Elements 7 without breaking the links and having to reconnect the images however I cannot find the way to do it.
Can anyone help?
Doug.

As Neale points out, the "Where is file ____ ?" message will pop up on the first "missing" file, and then PrE will help you locate the new folder/drive. For all Assets, in the same folder, once you find the first, PrE will then look in that folder and relink to all others in that folder. If you have moved several folders of Assets, you will need to do the Find, for each folder, and PrE will find all Assets in THAT folder. "Rinse and repeat... "
As a suggestion on how to set up your Project for the next time, I always create what will be my Project's root folder, with the Project's name. Below that, I will create one folder each for: Video, Audio, Music, Stills, Titles ( often use PS to create Titles as PSD files), and then point PrE to locate my Scratch Disks/Media Cache "Same as Project." Though there is a tiny performance hit, by setting that last location, it keeps everything within my Project's file structure. This allows me to Move, or, when done, Delete everything. With the exception of Captures, the Assets in each of those folders is a Copy, and the originals are still safely located on my NAS - just in case.
Good luck,
Hunt

I am using referenced images, saved on an external hard drive. It would be most helpful to transfer the new captions (version name) to the referenced images which still have the camera code on them. How can this be done? Thanks so much!

I am using referenced images, saved on an external hard drive. It would be most helpful to transfer the new captions (version name) to the referenced images which still have the camera code on them. How can this be done? Thanks so much!

You're question is hard to follow. Are you looking to rename your master files to the version name? Or are you looking to do something with IPTC caption field and the masters?

Moving Ref Images in Multiple projects

Does anyone know if its possible to batch move multiple projects of referenced images in one library. I am moving to a bigger external drive and don't want to have to go in to each project and repoint it to the new referenced file location.

Yes,
Just use any view where you can see the images - even a search based on whatever criteria you want, select them all and use file->relocate. The subfolder options will even let you restructure them in various subfolder formats based on date, project name, whatever.
Or...
Just move them outside of Aperture and use file->locate to reconnect them. Personally I would choose option one.
I have a bunch of stuff here on various Aperture topics
[http://photo.rwboyer.com/
RB

Corruption of the Location of Referenced Images

In other threads we have discussed problems with Aperture becoming confused about which referenced files it is supposed to connect with. Here is my analysis of one aspect of this problem.
When you have a group of referenced files, if you move some of them to another folder on the same volume or rename them Aperture attempts to find the moved file and change the reference to it. This might be what you want, or it might not, so Aperture ought to ask you whether to change the reference or not. But it does not.
If the volume on which you have your original files is not mounted, Aperture will mark the files as unavailable but will not change any links. This is clearly the behavior one would expect.
A problem occurs when your files are missing, but the volume they were on is mounted. This might happen if, for example, if one of your folders had been inadvertently deleted and needed to be reclaimed from a backup disk. In this situation Aperture "reconnects" the references in your Aperture library to what appears to be arbitrary files on the volume. The new references likely bear no relation to the files you really want. This is clearly not the behavior you would expect or want. When this happens it is usually impossible to use the "Manage Referenced Files" command to reconnect the files, because the correct files and the ones now referenced in the database aren't the same size and don't share the characteristics which permit the "Reconnect" button to be enabled when the reference and correct file are selected in the "Referenced File" dialog. Even the "option key" trick which sometimes allows the "Reconnect" button to be forcibly enabled will not work once this happens.
Obviously, this is a potentially catastrophic issue if a huge number of file references become corrupted in your library. The only way to fix things that I have found is to reimport all of the correct referenced image files, then lift and stamp metadata and image corrections from the corrupt reference entries in the library to the "new" referenced files. This is extraordinarily tedious if the number of files affected is large.
In any event, this is a serious bug and it should have been found long ago in Apple quality assurance testing and fixed. It ought also to be possible to just hand enter the correct reference to a referenced image in the library if nothing else works.

Possibly going to settings, general, international, region format, then select the country you are in.

Vault restoration with referenced images - SEEKING HELP

Long story short: I have, had, a library that contained both managed and referenced images. 2 vaults set up for managed images, RAID system set up for referenced images.
Rebuilt library the other day because Aperture was moving kinda slowly. Followed the typical protocol of backing up first then rebuilding and to later back up again. In the middle of rebuilding, Aperture froze (Activity Monitor said Aperture was using only .50% of resources) and hung there for over 8 hours. Force quite wouldn't work. Had to hard restart.
Problems surface with the primary library. Decide to restore from recently backed up vault. Worked for only 13 projects but hung/froze again on the 14th project for another 8 hours.
Freaking out that my redundant back up system completely doesn't work, I put the managed projects back together in a new library by going into "show contents" of the vault and importing projects individually. This took another day of work. Managed projects are working just fine now and are backed up once again.
Referenced projects will not import at all. I can not reconnect them to their referenced images in any reasonable manor. The only way I've figured out how to do this is by hand, placing the referenced master image file into the "show package" content file of the said image. This is a daunting task for the 7 weddings of 700-1000 image each. Even if I do this, there is no guarantee that the project will import with out issue.
Anyone know how to do this? Does anyone know what happened here? Any thoughts would be greatly helpful.
Thanks in advance,
cd
Mac Pro 2x2.66GHz, 4 GB RAM, duel HD displays Mac OS X (10.4.10) MacBook Pro 17" 2.33 GHz 3 GB RAM

Andreas Yankopolus wrote:
Dudley,
I'm experiencing the same problem on my MacBook Pro: Aperture will periodically show all of my reference masters as being disconnected. They're on the laptop's internal HD, which is the only one connected to it. Quitting and restarting Aperture usually reconnects them temporarily.
My main piece of advice is to not install Leopard. It's been nothing but trouble for me, my wife, and a friend that's done so. If there was an easy way to drop back to 10.4.11, I'd do so in a heartbeat.
Hi, Andreas
I think there is something else going on. (would like to know what it is). We've been on Leopard/Aperture combo since day one and running without any hickups on PPC, Intels and Laptops.
Is there anything that seems to trigger this disconnect?
victor

Moving Master Images after Facebook Upload

I'm using a fully updated version of Aperture 3 and ran into a problem today moving master images that I have not experienced before. My normal workflow is to batch import images from my camera every few days in one large import, so I often have multiple subjects in every batch. For my 9 months with the program I have always downloaded everything into a temporary holding project I literally call "Hold". When I get the time to do a detailed review, I then delete what I don't want and move (drag) the master images I want to keep from "Hold" into other subject-matter-unique projects across the library. This works for me and has worked flawlessly until today when I downloaded about 20 images. What I did differently today was I took things out of my usual order and decided to quickly upload 3 of the images from the "Hold" folder to Facebook using the Aperture Uploader. The upload went fine, as it has in the past, but the problem surfaced when I then tried to move all the master images out of "Hold" to my permanent library file (project) structure. The 17 images (which were not uploaded to Facebook) moved out to their new projects just fine, as always, but the 3 masters which were the source for the Facebook upload will not allow themselves to be moved out of "Hold". When I drag them to the intended project, Aperture copies them into that project, but the original stays in "Hold." Of course, if I try to then delete what is in "Hold" (with a copy safely filed away elsewhere in the Library) I get the warning that I am attempting to delete a master upon which other versions are dependent (to include "Facebook albums" it says), and all will be deleted.
My take on this is the Facebook upload from "Hold", and the resulting versions created in the Facebook album (far bottom entries on the Library listing), now make "Hold" a permanent home for those associated master images. Is there some way to get around this and actually move the master images to where I want them to be AND to de-clutter the "Hold" folder? Or does this mean any use of Aperture's very handy (at least to date) Facebook uploader permanently glues a master to whatever project it was in when it was uploaded, never to fully and completely move again? Thanks.

I just made a test of this, and can confirm the apparent behavior. However, I examined the Masters folder in the Package of the Library (and I have a Managed Library) and I believe there may be some referencing between Projects taking place. The same appears to result where you have created a slideshow. In the Facebook album and in the Slideshow album, the file info reports the master file name -- in my case the xxxx.NEF file, which clearly none of them really are, but rather some version.
I will try to do a more precise test where I can measure the size of the Masters folder to see if the "Move" adds to its size by an amount equal to the size of the Master file.
Interesting!
Ernie
Message was edited by: Ernie Stamper

Referenced Images Say They are Referenced But Are Not.

Is anyone having the following problem? I have about 4500 images that were Imported into Aperture as Referenced. Have been working with them over the past month. Tried making a Web Journal recently and after exporting the pages, many of the images did not show up in the web pages although the caption did. I went back to my Album and went through the images. The ones that didn't show up in the web pages were very strange looking within the Album. As a thumbnail they looked fine but when I put the loupe on them at 100% it was obvious that they were some sort of small jpeg or something due to lots of jaggies and poor quality. Even though the Reference icon was supposedly fine, telling me it was online since it did not have a yellow warning label, for some reason Aperture was not accessing the original RAW file.
I now have hundreds of images I have to try and find in the Album that say they are referenced but really are not.
Prior to this web journal problem showing up Aperture had been showing me many of these files were not online even though the drive was definitely hooked to the computer and I was able to go to the same images via the Finder and actually see that they were there. One minute the overall project registered images offline, I would click on an Album and they would register as Online. Then switch back to the Project and amazingly they register as online. Back down to the Album and it tells me they are off line. Back and forth from project to album and a different icon 50% of the time. I knew something was up.
I eventually tracked down many of the images that said they were online but by reviewing them it was obvious they were not due to the jaggies I mentioned above. When I would find one like this I went to Manage Referenced Photos and reconnected the image even though it's telling me it is already connected. After doing this to many of the images I reproduced the web pages and they then showed up. I nearly had all the images showing up except for one that I must have missed in reconnecting so I went back to do just that. As I scrolled through the Album and the Web Journal, many of the thumbnails would turn gray and then finally an image would show up. This happened to dozens of images. I found the one that had not shown up in the last export of the web pages, reconnected it (even though it said it was connected) and then exported the web pages again. Unfortunately I was back to square one. Once again dozens of images were now not showing up in the export of the web pages again.
I just can't believe how buggy 1.5.2 seems to be. I thought maybe it was something to do with Repairing Permissions so I went and did all of that. Still no luck! Anyone else experience anything like this? I'm about ready to give up on this software.

Victor,
Yes larger hard drives will help but the day they are large enough to fit in a laptop with a professional photographers entire collection is a long way off and may never happen. There is no reason why Referenced files needs to be so difficult. Two quality programs that handled it with ease was RAW Shooter (now gone having been bought by Adobe) and Photo Mechanic which is superb for some tasks. For Aperture to have this many issues with referencing images is unacceptable and the market place will bear this out. I've quite using the program all together and have gone back to Photo Mechanic combined with IView and Photoshop. There's still room for an Aperture like product but Apple better get moving to make it work better. Microsoft just announced some of the upcoming IView capabilities that will be available next year. Adobe has CS3 and Lightrooom and I'm guessing Photo Mechanic isn't resting on it's heels. I really, really wanted to like Aperture and I worked with it day in and day out for nearly two months. As time went on the Referenced files just kept getting more and more unstable and I lost a ton of work due to it no longer being able to see some of those files.
MacBook Pro Mac OS X (10.4.7)
MacBook Pro Mac OS X (10.4.7)
MacBook Pro Mac OS X (10.4.7)

When exporting files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might do 524 images but not the full 600. I've tried resetting Aperture, it's the latest version etc etc. Help please!

If anyone can help me with this I would be seriously grateful.
When exporting mutliple files to web pages Aperture keeping losing files, so for instance, if I choose to export 600 images to a new web page, it might make 524 pages but not the full 600. I've tried resetting Aperture and its persmission and am using the latest version of 3.
I have 3600 images which I need to upload as sublfolders, each with their own URL and at the moment Aperture is dropping of anything from 1 to 90 images.
This is critical as people need to see each and every on of these images online. So if a file has 600 photos in it, Aperture should make a URL with 600 full image pages. And this is what it's not doing. On small files, say 30 or so it seems to work well, it's when it gets to more than that the problem starts.
I've used Aperture in the past under previous versions and not had this problem.
Any help would be great.
Thanks.
Bob.

Hi Jack,
Thanks for responding (as it seems as though no one else has been able to provide any insight as of yet)! Not sure if you saw my recent post, but the version of Aperture on the 2008 MacBook has been upgraded to 3.1.2 (not sure how; I bought it in 2009, but only have OS X 10.5.8... which apparently can't house 3.1.2 of Aperture, but hey, like many other anomalies i'm encountering, I'm no longer surprised!). I am unable to upgrade it any further, as it warns me that my OS X does not fit the requirements. I exported the projects as libraries; however, like I posted before, apparently these are from too old of a version for the new Aperture (3.3.1) to handle and import.
It's getting to the point where I'd almost pay to upgrade the OS X on my previous MacBook (10.5.8) to something newer in order to THEN update Aperture to a newer version; however, my previous MacBook simply cannot handle this (the specs are awful -- hence my decision to save up and upgrade to the newest MBP with Retina).
I've spent hours upon hours transferring files, libraries as projects, previews, versions, even masters (though, apparently some of them aren't accessible?) with no luck. I've rebuilt the library and reprocessed everything. And this is all after having to return one MBP already since Aperture 3.3.1 is glitch-y as it is, and froze everything for having a "managed library". So, now that I know that I have to deal with a referenced library in Aperture... I just need to actually transfer my previous library to my new one (hopefully WITH adjustments since these are years worth of photos and work).
Again, any help is appreciated. I've lost enough sleep, time, and vision health over this at this point.
Also, I know Migration Assistant is an option, I was told that it wouldn't work properly anyway because of the different operating systems, and the potential for problems.

When I use Export Project to New Library in Aperture does it create a copy of the images in the new Library?

I am going through my only library now and trying to better organize everything. I am grouping my images into projects by year then cleaning up each year. As I finish a year I use the Export to New Library option to create a library for each year. My question is when I do this and I tell it to Consolidate Masters into exported library does it create copies of the images in the new library as well as leaving a copy in the original library? My goal once I get this completed is to delete the original library but I certainly don't want to lose any of my images. Just looking at file sizes for the libraries I can see that the main library never gets smaller and the new libraries don't really seem large enough to contain everything.
Thanks.

To be honest a 6 year old machine with 4gb of memory and 300gb of disk running Lion and Aperture is not going to give you the greatest performance no matter how you split the library.
You're going to need more disk, What's your backup procedure now? The best performance will be had by getting an external disk putting the masters on it as referenced and having the library on the internal drive.
More memory would be nice but a 6 year old iMac, I think, is maxed out at 4. You'll need to keep other programs running to a minimum when you're working with Aperture.
How much free space is on the internal drive? That will be an issue also. If even with the masters relocated to an external drive cause the internal drive to fill up you'll need to move the library off the internal. If you do that you'll want to go with a FW drive. As long as only the masters are on the external you can get by with a USB but once the library goes out there you're really want to look at FW.
Hope this helps, post back if you have more questions
regards

Updating Referenced Image Folder names

Hi,
My Aperture library is a Referenced Library. My referenced images are stored on an external FW 800 drive and my file system is setup as: Folder Name/Project Name. This has worked great for me, but causes issues when I make changes to the organizational system of my library. I know that Aperture is smart enough to still link the correct files even if the folder/project system is off.
My question is: How do you keep the folder system synced and intact when using a Referenced Library after making changes to the names of Projects, etc? Is this possible? If not, what system of fouler organization works best for keeping things simple, organized and in sync with as little confusion and downtime in terms of work flow?
I'm looking for some general (and specific) ideas from users here.
Thanks,
Mac

macorin wrote:
The question for you is: What need are you trying to meet by mimicking in your Master file storage and retrieval structure?
Kirby,
First, thanks for the lengthy and helpful response. In thinking about what you wrote, I probably don't need to worry about my Master file storage structure. So long as Aperture is able to find my Masters no matter the folder, project, album they sit in, I should be fine. My initial thinking was that if I wanted to access my Masters (for some reason) outside of Aperture, it would be easier for me to know where everything was. That being said, I don't really ever need to do that, as everything can be done straight from within Aperture. Still, it just makes me a little uneasy knowing that my images are organized and structured one way in Aperture and another outside of it where those images are linked to.
Don't let it make you uneasy. Even if they are all in one 55-gallon bag (or Finder folder), they are easily sorted by date (and time) taken, and by file name. These two alone -- esp. if you have renamed your Masters with a good and rigorously applied file-naming convention -- should meet every need you might have.
Moreover, your Aperture Library of images should be deeply hyperlinked. That's a big reason to use Aperture. None of those hyperlinks are create-able in a file storage system.
At the risk of being (even more) off-putting than usual: think on that. Beginning to understand that difference allows you to manage your data in much more successful ways.
The second reason I was asking is because when I import into Aperture as a Referenced Library, I also back up those images to a second external hard disk. I generally keep this back up archive organized and structured the same way as my Masters structure. If I ever deleted a Referenced Master and then later on wanted to re-import it from my back up archive, it makes it easier to find things, etc if they are organized the same way.
I don't buy it. Can you give an example of a situation in which you need to find a file and you don't know the date it was taken (at least roughly) or some part of the file name?
Your Masters need almost no storage structure at all.
IME, once I started using Aperture's extensive image management tools, I found I had almost no -- zero, nada -- file management needs beyond back-up.
If you read what I wrote just above, I guess this plays to that. How do you manage your back-up file management system if things change in ways that I have suggested, i.e. renaming projects, etc and moving things around from one project to another?
I try to keep two additional copies of every Library and every set of Referenced Masters at all times. One set is kept off-site. It's not hard to do -- but I do run copy operations that last all night. Aperture's Vault can serve as one of the Library copies. I have found it easier to manage when I don't use Vaults, so I stopped using them. If you find Vaults convenient, use them.
Just to be clear: My main goal is to make sure that my back-up file management structure mimics my Aperture Library Folder, Project, Album (well, not album as you can't organize at this time by album name) structure. I am not talking about the structure of where my Masters are stored, but rather the structure of my back-up. I hope this makes sense.
This does not make sense. +File management+ refers to Referenced Masters and not to Aperture Folders, Projects, or Albums.
Your Aperture Folder, Project, & Albums (all of 'em) structure is part of your Library. Back up your Library, and you have backed up that structure.
The files an Aperture user needs to back up are
- your Aperture Library (an OS X package of hundreds of thousands of files)
- all your Referenced Masters.
That's it.

Drawing moving GIF images?

Is it possible to draw moving gif images on a simple Frame applet?
I made an image drawer class for my applet and i can draw simple 2d images.
Here is the basis of my GameSprite class;
    public byte[] pixels;
    public int width;
    public int height;
    public GameSprite(String imageName, int requestIndex) {
     try {
                // Removed code, it's zipInputStream, but it can be used just as ./image.jpg etc
     javax.swing.ImageIcon icon = new javax.swing.ImageIcon(fileBytes);
     width = icon.getIconWidth();
                 height = icon.getIconHeight();
                 pixels = fileBytes;
     } catch(Exception e) {
          e.printStackTrace();
    public void drawSprite(int x, int y) {
     try {
          Image image = Toolkit.getDefaultToolkit().createImage(pixels);
                                //Removed code here
          graphics.drawImage(image, x, y + 7, width, height, observer);
     } catch(Exception e) {
          e.printStackTrace();
    }If i try to draw an animated gif image it dosn't move.
Thanks for any help.

In Java you need to override the paint method in AWT and paintComponenet method in SWING to do graphics/animation. If you go to an offscreen rendering, then you can paint to the graphics context of an image you use for a drawImage in your paint/paintComponent...
If you where overriding a Panel in AWT you would override paint:
public void paint(Graphics g){
g.drawImage(im, 0, 0, this);
}Then where you are maipulating your graphics you would do something like this:
//code snippet
Graphics g = im.getGraphics();
//make what ever changes to im by manipulating the graphics context g
repaint();

Referenced Images

Has anyone tried using their iPhoto library for referenced images (in other words, unchecking the "Copy Photos To The iPhoto Library" box in preferences)? I have always wanted more control of my file structure in iPhoto, and thought this might be a viable solution. My option is Aperture, which I own, but still find the learning curve daunting.
Any advice or tips would be welcome. Thanks.

I have always wanted more control of my file structure in iPhoto
You’re rather missing the point of iPhoto, I’m afraid. The point is to organise your Photos without reference to your files. If you want to organise Files, use the Finder, that’s what it’s for.
In referenced Mode: iPhoto will create an alias in the Originals Folder that points to your file. It will still create a thumbnail and, if you modify the pics, a Modified version within the iPhoto Library Folder.
However, you need to be aware of a number of potential pitfalls using this system.
1. Import and deleting pics are more complex procedures
2. You cannot move or rename the files on your system or iPhoto will lose track of them on systems prior to 10.5 and iPhoto 08. Even with the later versions issues can still arise if you move the referenced files to new volumes or between volumes.
3. Most importantly, migrating to a new disk or computer can be much more complex.
Always allowing for personal preference, I've yet to see a good reason to run iPhoto in referenced mode unless you're using two photo organisers.
If disk space is an issue, you can run an entire iPhoto Library from an external disk:
1. Quit iPhoto
2. Copy the iPhoto Library as an entity from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
If you're concerned about accessing the files, there are many, many ways to access your files in iPhoto:
There are many, many ways to access your files in iPhoto:
*For Users of 10.5 Only*
You can use any Open / Attach / Browse dialogue. On the left there's a Media heading, your pics can be accessed there. Apple-Click for selecting multiple pics.
Uploaded with plasq's Skitch!
You can access the Library from the New Message Window in Mail:
Uploaded with plasq's Skitch!
*For users of 10.4 and 10.5* ...
Many internet sites such as Flickr and SmugMug have plug-ins for accessing the iPhoto Library. If the site you want to use doesn’t then some, one or any of these will also work:
To upload to a site that does not have an iPhoto Export Plug-in the recommended way is to Select the Pic in the iPhoto Window and go File -> Export and export the pic to the desktop, then upload from there. After the upload you can trash the pic on the desktop. It's only a copy and your original is safe in iPhoto.
This is also true for emailing with Web-based services. However, if you're using Gmail you can use iPhoto2GMail
If you use Apple's Mail, Entourage, AOL or Eudora you can email from within iPhoto.
If you use a Cocoa-based Browser such as Safari, you can drag the pics from the iPhoto Window to the Attach window in the browser.
*If you want to access the files with iPhoto not running*:
Create a Media Browser using Automator (takes about 10 seconds) or use this free utility Karelia iMedia Browser
Other options include:
1. *Drag and Drop*: Drag a photo from the iPhoto Window to the desktop, there iPhoto will make a full-sized copy of the pic.
2. *File -> Export*: Select the files in the iPhoto Window and go File -> Export. The dialogue will give you various options, including altering the format, naming the files and changing the size. Again, producing a copy.
3. *Show File*: Right- (or Control-) Click on a pic and in the resulting dialogue choose 'Show File'. A Finder window will pop open with the file already selected.
Regards
TD

Unsuported Image Format error with referenced images

Hi,
importing referenced images does not work for me: when selecting "store images in their current location" (i.e., referencing them), the preview is visible for a moment and then becomes gray; the large preview says "Unsupported Image Format" (if AP doesn't crash at all).
When moving the same images into the library, it works fine. This applies to Nikon RAW (NEF) files (from a D70 and D2H) as well as plain JPEGs.
I'm using Aperture 1.5.2 / OSX 10.4.8 on a Mac Pro; DigitalCameraRAWUniv200601.dmg is installed.
Thanks in advance for any hints,
Bernhard
Mac Pro 2.66 Mac OS X (10.4.8)

Just if anyone cares (somehow this seems to be a rare issue), using referenced images seems to work if I choose a specific location ("Pictures") in the import dialog. The images get copied to a project-specific subfolder of ~/Pictures/ from where they are referenced, seems to work ok.
BB

Moving Referenced Images to a new HD

Similar Messages

Maybe you are looking for