Making adjustments with referenced images

my master files are located on an external HD . when it is offline, i can't make any adjustments. when it is connected, i can make adjustments and aperture creates a version out of the master file. i also use Nik Software (such as Silver Efex Pro) to make adjustments. when i save changes, the version is saved to aperture library ?? or should i click on the version and relocate it on the external HD? If I don't relocate it after making adjustments, then is it gone after i quit using aperture ??? please advise..

OkanUmit wrote:
my master files are located on an external HD . when it is offline, i can't make any adjustments. when it is connected, i can make adjustments and aperture creates a version out of the master file.
Yes, that's exactly how it works. You can't make adjustments unless the original file is online and available.
i also use Nik Software (such as Silver Efex Pro) to make adjustments. when i save changes, the version is saved to aperture library ?? or should i click on the version and relocate it on the external HD? If I don't relocate it after making adjustments, then is it gone after i quit using aperture ??? please advise..
I'm not sure what you expect to happen but Aperture will never edit the Original file. The point of Aperture is that the original is always preserved.
Remember what you have on that external is simply file storage. If you want to acess a photo then you do so via Aperture.
Regards
TD

Similar Messages

Exporting projects with referenced images

I want to import referenced images from an external hard drive, edit them and then export the project in order to archive it. Is this something that I can do now? Will I end up with a bunch of referenced previews in my library and an exported project that can link back up to the master images that are on a separate hard drive?
Antonio

No, this only exports a "copy" of your projects and does not remove the master image. It is still in the Aperture Library. I am also trying to find an easy way to move the entire project outside of the library and still maintain a reference link to wherever I move the images to. Any thoughts?

Problem with Referenced Images

Hi all,
I have some documents that all follow the same structure.
doc1\doc1.book
\*.fm
\images\A.jpg
doc2\doc2.book
\*.fm
\images\A.jpg
In both documents, I have an imported image file that I want to be "images\A.jpg".
my doc2 directory would have been created by copying and renaming doc1 (because they all follow the same document template/format). But in doc2's .fm file, my referenced image file's path is "..\doc1\images\A.jpg", referencing to the original file.
I've tried renaming doc1\images\A.jpg to doc1\images\B.jpg, and opening the doc2 .fm, which then says it can't find "..\doc1\images\A.jpg" and asks me to replace it with another file. So, I use "images\A.jpg" (which is in the doc2 directory). That seems to work. But this seems to also change the link in the doc1 .fm file to point to "..\doc2\images\A.jpg".
So, the problem seems like both .fm files will always point to the same image file. I don't know how to disconnect these, so that they can work independently from each other. i.e. each doc directory (doc1 and doc2) is self-sufficient.
Any ideas?
Thanks in advance.
Kevin

Kevin,
If I understand you correctly, you have created the doc1 folder, inside is the doc1.book, *.fm files, and an images folder. One of the *.fm files references the A.jpg image in the images folder.
Create the doc2 folder, then copy all the files and folders inside doc1 to inside doc2. Do this in Windows Explorer, NOT FrameMaker.
Rename the doc1.book inside the doc2 folder to doc2.book. Everything should be as you want it to be.
NOTE that if you open doc1/*.fm in FrameMaker and then save it as doc2/*.fm, then FrameMaker recalculates the path to A.jpg to point to the file doc1/images/A.jpg, because FrameMaker assumes you want to retain your links to the original image files. The difference from the procedure above is that you are doing the copying within FrameMaker, not within the Windows file system.
Van

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

Aperture not making adjustments to selected image but to the previously selected image. Any ideas?

After making adjustment to an image I select the next image to work on. However, none of my adjustments appear to apply to the image. Then I noticed that the image I previously adjusted is messed up. The adjusts for my second image (the image selected) are actually being made to the previously worked on image (which is not selected). Any ideas on what is going on and how to correct this? Thank you for you help.
Bill

My first suggestion would be to uninstall Perfect Layers and see if the strange behaviour is still happening. From what you've described in your post, this wasn't happening before the plugin was installed?

Making adjustments on multiple images which already have adjustments

i have about a thousand images that have been adjusted for exposure, etc, and i just realized i need to go in after the fact and adjust the white balance for all the images now. if i lift and stamp, it will lifty all adjustments from 1 image as opposed to just the white balance, so i am wondering if it's possible to adjust just the white balance for all these pre-edited images.
any suggestions?
thanks!

Also (and I don't know if you have worried about this yet) the default behavior of Stamp is to only add the things you have checked in stamp - if the image to be stamped has existing Adjustments, they will not be modified when Stamping (though if you already had a white balance set it will be overwritten).
If you want to stamp many images at once select them all and then use the "Stamp Selected Images" button in the Stamp dialogue.

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

When making adjustments with lens correction, the crop isnt contrained to the image

When I first installed CC I was able to rotate, or adjust the image in lens correction and it would automatically crop to the available image dimensions.
But I deselected the contrain to image section in crop mode, and since then it hasnt work, even though contrain to image in crop tool has since been re-selected, many times.
Any idea whats wrong?

Thanks! All of my shots for this current interior shoot are panoramic. At a halt until I can resolve this.
Lightroom: 5.7
camera Raw 8.7
Photoshop CC 2014.2.2 Release / 20141204.r.310 x64
Other notes:
- converted arw sony raw (from a6000) into dng and still no results.

Making adjustments to still images in PS crashes FCE

When I drop still pictures into my project (tiffs), sometimes they need a little tweaking back in Photoshop to look just right. So, I hold down the control key and click on the clip, and in the box that pops up I choose Open In Editor. That opens the original still picture in Photoshop, and I make the necessary adjustments there.
But after dismissing Photoshop and returning to Final Cut Express, first I get the little watch symbol, which I assume means that FCE is accepting the changes to the clip, and then the beachball starts spinning, and it spins forever. The only way to get out of it is to force-quit FCE. In the Force-Quit window, FCE is shown in red with the note that it is "not responding," which means it's definitely stuck, and no amount of waiting for the beachball would do any good.
I've had to force-quit FCE several times now like this, and when the program opens back up, the results in the clip vary. Sometimes the changes I made in FCE are there in the clip. Other times the changes are not shown. Sometimes if I double-click the clip up into the Viewer, I see the changes there in the Viewer, but not in the Canvas.
Sometimes I can force the clip in the Canvas to show the changes by removing transitions from it, rendering, and then replacing the transitions and rendering again. But often when I do this, the changes are seen ONLY in the part of the clip that was rendered, and not in the rest of it.
Is this a glitch in the program, or am I doing something wrong?
Tom B.

Tom,
Thank you for your help. I am making progress. For the first time I was able to work in DV-NTSC Easy Setup.
My original image: 1 MB jpg, 1020 X 1419 - a client scanned I am guessing 600 dpi - since this was a 4 X 6 print.
After testing I had good results with adding the 1 pixel vertical blur you suggested to this original file, still over 1 MB and dimensions same. Swimming was next to nothing.
When I resized 720 X 540 the image was distorted (I followed your link and thought "unconstrained" was to be de-selected...perhaps not?, haven't retested yet.). When I changed the aspect ratio in Motion in FCE to 60 the image was normal AND I lost the "swimming". This file is 720 X 540, 504 KB.
Is the answer lying in perhaps the file was way too big? Doesn't make sense to me, but I don't code programs
Thank you so very much! I will be glad to be able to begin working with the tools of FCE.
I DO set the QT Conversion to "High". Is this better than "Best"?
Thanks, again,
Brenda
iMac Mac OS X (10.4.8)

How to change to working with referenced images but keep library on laptop

Hi,
So, my iPhoto library is getting too big - I'd like to be able to have the images stored on an external drive and refer to them from within iPhoto, whilst keeping the iPhoto Library itself on the laptop. I know exactly how to do this from scratch, by unchecking 'copy items to my iPhoto library' in advanced preferences, but I'm trying to figure out how to convert my existing library, which has all the photos stored within it, to one where all the original files are on an external drive and are referenced by iPhoto. This way, I can see the previews when I'm away without the external drive attached.
Thanks!

There is no easy way to do it and I would strongly urge you to reconisder.
In a Referenced Library, iPhoto creates aliases to the location of the actual file. While there is at least one app that will help you replace those aliases with the actual files (convert a Referenced to Managed library) there is no app that will convert those files to aliases that point to the new location of the files. You will need to do each file manually.
More importantly, iPhoto has no tools to manage Referenced files. While on the same volume, aliases will track moved files. However this is not the case where the files are on different volumes. The upshot of this is that should the link to the files be broken then you could find yourself reconnecting each and every alias in your Library, one by one.
Also, I'm not sure about 09 but earlier versions of iPhoto would not open if there were movie files in the Library that were not available at time of launch.
You can move an entire Library to an external disk. There are firewire and usb disks now no bigger than a pack of playing cards and will run from the laptop's power supply.
Regards
TD

Printing with referenced images

I have a print component in my Flex application which works fine if I embed the header image to be printed. But if I merely link it as an external file, it appears to load, but somehow the print code creates the page too rapidly and the header does not get included in the print output (though it appears in the component micorseconds after the print dialog closes).
I tried a workaround to give the image a chance to upload into the print component completely (see below), but it is inconsistent and only works for faster connections.
callPrint is only called when creationComplete of the component, but it does not appear to be the case--the image is not completely created when the print function is called by creationComplete="callPrint()"
Has anyone else experienced a problem with this, and is there a workaround?
thanks
WORKAROUND ATTEMPT CODE BELOW:
public var printTimer:Timer=new Timer(500); //might have to tweak this value for slower connections?
public function callPrint():void{
printTimer.addEventListener(TimerEvent.TIMER,okayNowPrint);
printTimer.start();
public function okayNowPrint(evt:TimerEvent):void{
var printJob:FlexPrintJob = new FlexPrintJob();
if (printJob.start()){
printJob.addObject(this,FlexPrintJobScaleType.SHOW_ALL);
printJob.send();
parentApplication.removeChild(this);
evt.currentTarget.stop();
printTimer.reset();

STILL doesn't work--this is baffling me. Is it possibly because my print component is a VBox???
Here is my code:
private var ldr:Loader = new Loader();
private var urlReq:URLRequest = new URLRequest('logos/printHeader.jpg');
public function init():void{ //called by creationComplete
ldr.load(urlReq);
ldr.contentLoaderInfo.addEventListener( Event.COMPLETE, loaded);
private function loaded(event:Event):void{
trace("printHeader loaded");
printHeader.source=ldr;
callPrint();
public function callPrint():void{
var printJob:FlexPrintJob = new FlexPrintJob();
if (printJob.start()){
printJob.addObject(this,FlexPrintJobScaleType.SHOW_ALL);
printJob.send();
parentApplication.removeChild(this);
It's something to do with the fact that callPrint gets called early, for some reason. Only by microseconds, but the image is always blank, even though if I make the component visible it appears almost simultaneously with the print dialog (but NOT immediately).

How to find originals in AP3 if I use several harddisks simultanously with referenced images ?

Is there a way to right-click and select "show in finder", like in itunes ?

I like em short and sweet

Concerns with Dropbox to store/backup referenced images?

Hi,
I'm looking for an alternative for my current cloud backup solution (Mozy) since the current scheme requires me to pay 23$ per month for my ca. 260Gb of image data. Since I also pay 10€ per month for 1TB of Dropbox space, I seriously consider to cancel the Mozy subscription and use the available Dropbox space as a cloud-based backup solution for my original images (next to my Time-Machine backups).
To be clear : I only work with referenced images. I have no originals inside my Aperture library. I do not plan to transfer my Aperture library to my Dropbox. I do not need to work with my originals from multiple computers. I only use Aperture from one single iMac.
I have read multiple threads about Aperture/Dropbox combinations, but they all cover storing your library on Dropbox. That's not what I intend to do. I just want to transfer the folder structure (where my referenced images are stored when importing into Aperture) to Dropbox.
Are there any concerns with storing the referenced images on Dropbox?
Thanks for your help,
Mitch

Funky,
What is the best way to back it up? Just copy the files to another hard drive?
That will definitely work, but how will you tell what you have backed up and what you have yet to backup? A better solution (if you are using Aperture 3) is to use the backup function when importing.
I am also using Time machine, I assume that it is backing up attached external drive (I have not "excluded it"), is that correct?
Well, that's a Time Machine question, but according to the following thread, just because you didn't explicitly exclude it doesn't mean it's not excluded.
[http://discussions.apple.com/message.jspa?messageID=12222390]
has anyone had good experiences with on-line backup solutions?
You should search the forum for a thread with lots of input from the last week or so. There was a lot of talk about some on-line backup.
nathan

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)

Strange stack behaviour with referenced files

I have just started to notice peculiar behaviour with referenced images within stacks. I have been reviewing last years pictures with a view to clearing out the junk.What I have found is rather alarming in that on clicking a stack to open it all the images within the stack were the wrong pictures, wrong as in taken with a different camera in a different year.The top picture does not seem to be affected.On attempting to find the correct files using 'manage referenced files' all the wrong images are shown as found in the list view with their own file names at the same time the thumbnails (top right hand pane) show the original correct file names but with the wrong thumbnails,Aperture does not realise that it is referencing the wrong files and so will not let me reconnect to the correct files.
Anyone with a similar problem or a cure for this behaviour?

Ok I have deleted and rebuilt thumbnails files to no avail.
What appears to be happening is that aperture is using the wrong file-path for the affected pictures.
I keep all pictures arranged by date order so for example where the correct file path for an image would be;
Raid Zero/Pictures/2006/0609/060928/pict3722
Aperture is giving a file path of
Picture Library/2007/0712/071223/_DCS1023
in the manage referenced files pane it shows the wrong path as above, the thumbnail picture is of the wrong file but the thumbnail name and date is correct.
Interestingly since rebuilding the thumbs it is now possible to reconnect to the correct original file whereas before the reconnect option was not available, however it is only possible to do this one file at a time,the re-connect all function does not work presumably because Aperture is not aware that its filepath is wrong.
Oh dear.... Aperture has just crashed,this immediately after reconnecting 6 files and waiting for the files to update to the correct image in viewer mode.
GRRRRRRRRR!

Making adjustments with referenced images

Similar Messages

Maybe you are looking for