Cannot reconnect to referenced files

I have copied all my pic folders to another external drive and want to now reconnect these linked files to the library...but I can't.
Am I doing something wrong?
this is my procedure:
- I see my files as linked but not online
- i then choose locate files
- i get to pick the new drive and match the referenced file to the same file but in a new location
BUT the reconnect/reconnect all won't become available (it stays greyed out).
what's wrong? the same files exactly but I can't reconnect using another drive?! seems strange...
Can't find the info in the manual either.

I am seeing the same thing. I had all of my images stored on a USB drive shared by an Airport Extreme Base Station. Due to ridiculously poor performance of this setup, I recently unplugged the drive from the base station and plugged it directly into my MBP. I was surprised Aperture couldn't find my photos, considering the volume name was the same, but no matter I decided to reconnect. This worked fine for ~16000 photos but failed for 5.
Now, I can find those 5 photos on the drive and they are readable (e.g. viewable in Preview), but when I try to reconnect, both the "Reconnect" and "Reconnect All" buttons are greyed out.
Any help would be appreciated!

Similar Messages

  • Aperture 1.5.3 upgrade - now cannot connect to referenced files?

    I just did the update to 1.5.3, and now my referenced files are all "offline" according to Aperture even though nothing has changed in the physical setup of my system.
    Worse, when I attempt to "manage referenced files", the upper half of the window shows the 500GB external drive (Western Digital firewire 'Mybook') is offline, and the 'Mount' button is disabled. In essence, all of my image files are now offline according to Aperture, and it is not allowing me to Mount the drive that is there, plain as day, for FInder and other apps to see.
    Also, the 'Reconnect' and 'Reconnect all' buttons on the bottom of the lower half of the window are disabled. The only buttons that are live are 'Update selection in browser', 'Hide reconnect options' and 'Done'. And the window's close and collapse buttons (upper left corner) are also disabled, though I can make the window full screen.
    Anyone else notice this rather major problem?
    TIA
    MacBook 2GB RAM   Mac OS X (10.4.8)   23" Cinema Display

    Oops - user error after all - when the MacBook rebooted somehow the 250GB firewire drive (they're daisy chained) didn't mount, so while I saw the 500GB in Finder Aperture evidently was having a problem because of the 250GB.

  • Missing photos - cannot reconnect - found in mov file!!

    Using Adobe Photoshop Album Starter Edition 3.0 on Windows XP Pro
    Everything worked fine for some time, then error message appeared when trying to print or attach photo to email.... "Searching for missing file". There are about 30 photos that are "missing" although they can be viewed in the album. Tried the "Reconnect" feature but it cannot reconnect the missing files. Searched for the names of the JPG photos and they do not appear in the list... cannot be found. After some research discovered that they were all in an MOV file named "Picture054.MOV". Any idea how they got put into MOV format??? Or how to put them back into the album as JPG photos??
    Thanks

    BOB:
    Can you help me with my issue? It is on the FORUM UNDER:
    *System Crashed, LOST ALL photo files shows THUMBNAILS only now!*
    BGBlake - 04:04am Jun 6, 2007 Pacific
    PLEASE help me to get back my pics! HOW can I COPY the THUMBNAILS and NOT loose my photos! If I try to open them or copy them they say "Searching for Missing File Location", then it says "Cannot continue requires at least one connected file"!
    These are precious because they are 3 years worth and some family members are no longer with us! PLEASE HELP!
    OS:WINDOWS XP SP#2
    Photoshop Album Starter 3.0
    Basically, I had to do a factory restore and the PICS file was NOT under an "XP User Acct" so the files were not saved during restore and were lost! When I re-installed Adobe 3.0 the THUMBNAILS appeared, but of course the file "location" is missing as is all the actual pics! It says one file must be connected to open. Can you help?

  • All referenced files broken....

    Hey,
    i recently did a clean install of snow leopard and used timemachine to restore all my files however i have been working with a referenced file management structure in aperture 3 and although all the files are in the correct path and the hardrive name has not changed etc, aperture wont recognise my library files is there any way of forcing it to recognise them, or building a new managed library without losing all the versions of my files?
    Thanks
    Anthony

    I have a referenced file library. I started having this problem after I installed the 3.1 update in October - I did NOT have this problem prior to that installation.
    After the 3.1 update, when I unsuccessfully tried to export a version, I found that many - indeed most of my files have the 'red-line' badge, indicating that the referenced file cannot be found.
    I do the File / Locate Referenced Files thing, reconnect my photo, and sometimes (yes, sometimes!) the red slash goes away. I've tried to determine why is seems to be hit-or-miss, but I've been unable to identify why they connect and usually not. I test by trying to export a version.
    So then, after checking the support boards and this forum, I tried rebuilding my library. (And yes, before I did the rebuild, I ran the 'Repair Permissions ' and 'Repair Database' fixes also. Multiple times.)
    Here's a real whacky part of this problem: Sometime when I attempt to reconnect my referenced files, the red-slash badge remains, but I'm able to export a version. And just as intermittently, again after attempting to reconnect referenced files, the badge will go away, and I'll think I have success, but the histograms reads "Image offline." (And it is - I cannot export and my reconnection has failed.)
    Today I took my external HD with my to the Apple Store for a 1"1. They initially removed the plist, which didn't change anything. My store has a pretty knowledgeable crew, but this one stumped them too. I showed them what I did, they did the same thing, with the results I described above. They told me to AppZap and re-install A3 and A3 updates - which I've done. My problem persists. They thought that if a clean install didn't work, that maybe I might have a 'corrupt library' - which sounds serious - and I'm not sure I understand HOW that would've happen.
    I sure could use some help on this one - when A3 works, I love it! But I've had major headaches after the last two updates, and I'm just exasperated. (Oh yes - I'm stressin' too since my wife is asking me about the photo cards and gifts we were planning on giving for Christmas. Since I can't export, I'm kinda stuck. I haven't tried reprocessing my images in CS5 just because I thought I could fix this...)
    Many thanks ~
    Greg
    (tzargregory)

  • Copying referenced files

    Hello,
    I use Snowleopard and Aperture 3, all latest updates.
    I have located the majority of my photos as referenced files on an external harddrive A in a folder called Photography and sorted identical to my Aperture file structure which goes by year: ex: 2003 and "relocated 2003" on external harddrive A.
               I wanted to make a backup copy onto other external harddrives of all these referenced master files and I copied the folder " photography " and all its contents onto hard drive B. The contents are all there...but how do I reconnect my files? when I hook up drive A, and run Aperture, I can edit and work on my referenced masters files.    But when i hook up drive B, I cannot locate the referenced files and it says the file is off line. If I go and navigate in the "locate referered file"...i can see my drive B and navigate to all its contents but searching manually for one file among 16.000 is too daunting .... Is there a better way to make working copies of my referenced master files that work when i connect the drive with the referecend master copies on it?
    How should I proceed and how should I best make copies of my referenced masters and vaults?
    Any help is very much appreciated,
    thank you,
    angelique

    Angelique,
             You would have copied your referenced photos across using Finder, so Aperture doesn't know anything at all about the copies, as they have never been referenced(imported) from the drive B to which they've been copied.
    This isn't a problem, as you are, after all, taking a backup copy of drive A photos, and will only be resorting to drive B if the photos get lost.
    For referenced photos, a good approach is to run a vault to save the database that keeps track of all the changes to the photos, and a backup of the actual photos (as you have done).
    If you need to restore lost photos (assuming Aperture still has a record of them, and it's only the referenced image itself that's been deleted), you could restore the image using Time Machine, or by copying the image from drive B back to drive A.
    If you lose the entire A disk and need to use B instead, you'll need to reconnect the images.  Why?  Each disk as a unique id number that Aperture uses to reference the source of the images.  Even though the B disk may be an exact copy of the A disk, it's id number will be different - so you have to tell Aperture where to find the images again.
    Does that make sense?

  • Find a referenced file

    Just started using Photos and when I try to turn on iCloud syncing, it says "1 referenced file cannot sync to iCloud...select referenced files in your library and choose  "consolidate" from the file menu..."
    I get why this is happening, but I cannot find the referenced file in my library for the life of me. I created a smart album and set the photo to referenced and it pulls up 0 images. I have meta > referenced turned on and i visually scanned my photos and don't see a single one with this icon. I could have missed it because there's thousands.
    How do I find this referenced file so I can deal with it?? I want to know what photo is referenced. Thanks.

    No, but somehow the issue has been resolved for me. I moved quite a bit of photos around to different (new) albums and changed some dates on photos. Somehow there's no more message about any referenced files. I'm not sure how it happened though.

  • Volume ID change - cannot find referenced files

    It seems that recent security update or Aperture update caused a change in handling CIFS/Samba volumes. I have my photos stored on network server which is exporting CIFS volume under the name 'Photos'. It worked fine until I rerun Aperture after recent update and reboot. All files are now unreferenced and I am getting the 'The file xy cannot be found because the volume on which it resides is currently offline'. I found that the problem is that all files are referenced with volume name 'photos'. (note the lower case letter 'p') Once I reconect the photos, the volume is now reported as 'Photos' (with capital letter 'P')
    I tried the usual trick with opening the files directly from Finder but this does not work. It seems I will have to reconnect all files. (Anyone knows how to reconnect all photos in all projects at once ?)
    It's seems to me that this is caused a change in behavior of OS X or Aperture because the server configuration has not been changed in years.

    I'm having the same issue.
    I moved some of my masters to an external drive.  I recently tried to move the masters for one project back into my main Aperture library, but 15 of the 916 masters in this particular project did not move back.  In Aperture I'm getting the little "The referenced image’s master has not been found." badge on these 15 images. 
    The master is still resident on the external drive, but the value in the "File Name:" metadata field in Aperture does not match the file name on the external drive.  The file name on the external drive is the correct and original file name, but I have no idea why Aperture has a different value (e.g. IMG_1128 29.CR2 vs IMG_1128.CR2).
    I've tried renaming the name of the file on the external drive, which didn't make a difference.  I also tried moving the file to the local drive, but that didn't change anything.  I can't see any way to edit the metadata field in Aperture.
    I've tried "Repairing" my Aperture Library, but that made no difference.  I haven't tried completely rebuilding it though.
    Selecting one of the images and clicking:
    "Relocate Original" gives me the following message:
    "Unavailable original files cannot be relocated.  The selected original image is either offline or not found. Please reconnect it and try again."
    "Consolidate Original" gives me the following message after letting me choose "copy" or "move":
    "No Referenced Files.  The selection doesn’t have any referenced files."
    "Locate Referenced" gives me the following message:
    "No Referenced Files.  The selection doesn’t have any referenced files."

  • How do I stop Aperture consistently crashing when attempting to reconnect a few referenced files?

    Has anyone else run into this? It's driving me nuts.
    Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
    So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
    So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
    It sometimes works with a single image, but not yet more than once before it crashes.
    Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
    Any ideas on what I can try next? Thanks!
    Here's the first lines of the crash report that Apple generates:
    Process:         Aperture [29772]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4.1 (3.4.1)
    Build Info:      Aperture-301039000000000~2
    App Item ID:     408981426
    App External ID: 11130653
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [177]
    User ID:         501
    Date/Time:       2012-10-25 08:47:06.464 +1300
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Interval Since Last Report:          122141 sec
    Crashes Since Last Report:           9
    Per-App Interval Since Last Report:  102826 sec
    Per-App Crashes Since Last Report:   8
    Anonymous UUID:                      C8AB497A-18DB-3A43-8663-4B28960DFA6E
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    Application Specific Information:
    objc_msgSend() selector name: dealloc
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libobjc.A.dylib                         0x00007fff897cf250 objc_msgSend + 16
    1   com.apple.Aperture                      0x0000000106f2ce46 0x106e03000 + 1220166
    2   com.apple.Aperture                      0x0000000106f2cf32 0x106e03000 + 1220402
    3   com.apple.AppKit                        0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
    4   com.apple.AppKit                        0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
    5   libdispatch.dylib                       0x00007fff8b431f01 _dispatch_call_block_and_release + 15
    6   libdispatch.dylib                       0x00007fff8b42e0b6 _dispatch_client_callout + 8
    7   libdispatch.dylib                       0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
    8   com.apple.CoreFoundation                0x00007fff899b30fe __CFRunLoopRun + 1614
    9   com.apple.CoreFoundation                0x00007fff899b26b2 CFRunLoopRunSpecific + 290
    10  com.apple.HIToolbox                     0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
    11  com.apple.HIToolbox                     0x00007fff8df75e42 ReceiveNextEventCommon + 356
    12  com.apple.HIToolbox                     0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
    13  com.apple.AppKit                        0x00007fff9178b613 _DPSNextEvent + 685
    14  com.apple.AppKit                        0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
    15  com.apple.Aperture                      0x000000010727700d 0x106e03000 + 4669453
    16  com.apple.AppKit                        0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
    17  com.apple.AppKit                        0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
    18  com.apple.Aperture                      0x0000000106f7fcb3 0x106e03000 + 1559731
    19  com.apple.Aperture                      0x0000000106e4b0b5 0x106e03000 + 295093
    20  com.apple.AppKit                        0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
    21  com.apple.prokit                        0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
    22  com.apple.Aperture                      0x00000001072780bf 0x106e03000 + 4673727
    23  com.apple.AppKit                        0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
    24  com.apple.AppKit                        0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
    25  com.apple.AppKit                        0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
    26  com.apple.AppKit                        0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
    27  com.apple.AppKit                        0x00007fff919aa245 NSSLMMenuEventHandler + 342
    28  com.apple.HIToolbox                     0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206

    Has anyone else run into this? It's driving me nuts.
    Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
    So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
    So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
    It sometimes works with a single image, but not yet more than once before it crashes.
    Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
    Any ideas on what I can try next? Thanks!
    Here's the first lines of the crash report that Apple generates:
    Process:         Aperture [29772]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4.1 (3.4.1)
    Build Info:      Aperture-301039000000000~2
    App Item ID:     408981426
    App External ID: 11130653
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [177]
    User ID:         501
    Date/Time:       2012-10-25 08:47:06.464 +1300
    OS Version:      Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Interval Since Last Report:          122141 sec
    Crashes Since Last Report:           9
    Per-App Interval Since Last Report:  102826 sec
    Per-App Crashes Since Last Report:   8
    Anonymous UUID:                      C8AB497A-18DB-3A43-8663-4B28960DFA6E
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: EXC_I386_GPFLT
    Application Specific Information:
    objc_msgSend() selector name: dealloc
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libobjc.A.dylib                         0x00007fff897cf250 objc_msgSend + 16
    1   com.apple.Aperture                      0x0000000106f2ce46 0x106e03000 + 1220166
    2   com.apple.Aperture                      0x0000000106f2cf32 0x106e03000 + 1220402
    3   com.apple.AppKit                        0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
    4   com.apple.AppKit                        0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
    5   libdispatch.dylib                       0x00007fff8b431f01 _dispatch_call_block_and_release + 15
    6   libdispatch.dylib                       0x00007fff8b42e0b6 _dispatch_client_callout + 8
    7   libdispatch.dylib                       0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
    8   com.apple.CoreFoundation                0x00007fff899b30fe __CFRunLoopRun + 1614
    9   com.apple.CoreFoundation                0x00007fff899b26b2 CFRunLoopRunSpecific + 290
    10  com.apple.HIToolbox                     0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
    11  com.apple.HIToolbox                     0x00007fff8df75e42 ReceiveNextEventCommon + 356
    12  com.apple.HIToolbox                     0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
    13  com.apple.AppKit                        0x00007fff9178b613 _DPSNextEvent + 685
    14  com.apple.AppKit                        0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
    15  com.apple.Aperture                      0x000000010727700d 0x106e03000 + 4669453
    16  com.apple.AppKit                        0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
    17  com.apple.AppKit                        0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
    18  com.apple.Aperture                      0x0000000106f7fcb3 0x106e03000 + 1559731
    19  com.apple.Aperture                      0x0000000106e4b0b5 0x106e03000 + 295093
    20  com.apple.AppKit                        0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
    21  com.apple.prokit                        0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
    22  com.apple.Aperture                      0x00000001072780bf 0x106e03000 + 4673727
    23  com.apple.AppKit                        0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
    24  com.apple.AppKit                        0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
    25  com.apple.AppKit                        0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
    26  com.apple.AppKit                        0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
    27  com.apple.AppKit                        0x00007fff919aa245 NSSLMMenuEventHandler + 342
    28  com.apple.HIToolbox                     0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206

  • Issues With Reconnecting Library to Referenced Files

    I'm hoping somebody may be able to shed some light on very strange behavior I'm currently experiencing with Aperture. Before I continue let me say ahead of time that I've already run a Repair Permissions, Repair Database and a complete Rebuild Database on the Library. That said here is what's happening.
    My workflow consists of Importing all images via Aperture, as referenced files, on to a  small, external hard drive. When I return to my studio I manually copy the folder of images, from the small external drive, over to my desktop hard drive. The next step is to Import the Field Library to my desktop MAIN library. Once the Field Library is Imported into the MAIN Desktop library I then highlight all the images and select File>Locate Referenced Files. Though I've done this hundreds of times in the past, it's currently not working on some files. Here's where the very strange behavior comes in.
    When the Locae Referenced Files window comes up I see the image in the top pane that I want to reconnect. In the bottom pain I navigate to the drive the image now lives on, I find it and it too appears in the bottom window. So far all seems to be fine, except when I tried reconnecting, Aperture went through the process but didn't actually reconnect. I retried several times but after the first try to reconnect the Reconnect & Reconnect All buttons is grayed out.
    Ok, so what the heck is going on? I start reviewing the Metadata of each image while still in the Locate Referenced Files window. The file numbers are exactly the same but the time stamp on each image is different. Why I have no idea. I plug in the original mini field drive with all the images that Aperture Imported to check the Metadata on the field drive. Sure enough it's identical to the Metadata on the Desktop drive which means it's different from the Aperture Library on the orignal drive Apertue saved it to as well. But what's even more interesting is that the minute the mini hard drive is plugged in, Aperture sees it and reconnects the images automatically, even though the potential issue of the metadata timestamp being different is the same on both the mini field drive and my desktop drive.
    In summary, when Aperture wouldn't connect the images that were on the desktop drive I thought I found the reason; a discrepancy in Metadata. But when the original drive was plugged in, the same files had the same discrepancies yet Aperture found them fine.
    None of this would be a probelm if Aperture had the ability to FORCE RECONNECT. The images are exactly the same except for some minor metadata descrepencies that I have no idea how they got changed and I really don't care about. But............. how the heck am I going to get these fiels reconnected without a Force REconnect option. Any ideas out there?

    William is right - use the provided tools.
    . Never once could it not find the images once I took it and showed the exact path to where  the images were newly located. So what happens if that drive ever fails completely and I have to replace it with a totally new backup?
    There must be something wrong with your external drive, if reconnect is not working. I had never, ever trouble to reconnect the originals after copying or cloning a drive, when I restored a mac from my backup.
    Check the filesystem on your field drive, if the file system is MacOS Extended (Journaled).

  • Reconnecting Referenced Files...every time I use the program! Help!

    Every time I use Aperture, regardless of any outside variables I change, it inevitably unlinks nearly all the photos in my library, or will keep a third linked with no rhyme or reason. I've tested every variable I can think of, stopped using spaces, sent heated emails to our friends at Apple...nothing seems to make a difference. The program is a technological equivalent of a brick 50% of the time I open it.
    These photos are on my main hard drive, not an external disk that gets put to sleep. This problem has occurred while I was in the middle of using the program, switched to finder, switched back.
    Has anyone else had a problem with Referenced Files coming unlinked? Or Can anyone suggest an alternative program to Aperture that actually works?

    Ok, two things I've figured out with 10.5 and Aperture:
    - If you use Spaces, it will eventually cause your referenced images to become unlinked.
    - If you hide or minimize Aperture, it will eventually unlink the album you are working on, and eventually your entire library. Sometimes this problem can be fixed simply by restarting Aperture, but other times, if you let it sit for too long or your computer goes to sleep in this way, your whole library may come unlinked.
    I (so far) haven't had any problems with this since I stopped hiding the application. It is a bug, but at least in my case I'm able to work around it by always keeping the window open if the application is open.

  • Can't locate Referenced Files in Aperture 3

    All my photo master files are in separate directories on a NAS (network attached storage; 4x1Tb) and I import Projects from that into Aperture on my IMac.  I migrated my MAC Aperture Libraries to a separate external drive and lost some of the references to the Master.  I can reconnect some Projects to the masters on my NAS, but not all.  Some projects won't reconnect using  Locate Referenced Files.  I can find the files and match the photos and Aperture looks like it reconnected, but when I look at the separate images, I get "File not found."  I know the original photos are on my NAS because I can see them using a separate PC hooked into it, but can't seem to complete making the link to the master.  My intent is to move all masters into my Aperture Library because I can't stand losing photos this way anymore, but I need help making that link.  Any ideas what's happening and what to do.
    Even though I have the originals on my NAS, all my processed versions (4 and 5* photos) are in my Aperture Library and I hate to lose those.
    Update: I seem to be able to connect one photo at a time, but selecting an entire set of Project photos and doing "connect all" doesn't seem to be working.  I have thousands of photos and working one at a time is impossible.
    How can I get help?
    <Email Edited By Host>

    I migrated my MAC Aperture Libraries to a separate external drive and lost some of the references to the Master.
    How is your NAS formatted, where your original masters are stored? And how is the external drive formatted that holds your Aperture library?
    Your Aperture library needs to be on a drive formatted Mac OS X extended, Journaled. If the drive should not have that formatting, move the Aperture library to disk with the coorrect format.
    If you cannot reconnect originals, that are clearly there, the reason may be, that your Aperture library needs repairing, see: Repairing and Rebuilding Your Aperture Library: Aperture 3 User Manual
    I'd try to repair permissions and to repair the library, before trying to reconnect again.
    Since you want to consolidate all originals in your Aperture library, I'd try to copy the originals that cannot be recoonected, to the same drive that holds yor aperture libryr and try to reconnect them there, then consolidate them from there. It can be, that the network connection of the NAS is not reliable enough.
    Regards
    Léonie

  • Referenced files do not show same folders as in iPhoto/Aperture

    I built my Aperture library based on all the previous work I did in iPhoto. Piece of cake! Then I copied the whole iPhoto folder (including aperture files) to an external drive. Using the finder, it shows the proper file path to the images, but when I "manage referenced files" through Aperture, folders such as "originals" are missing so I cannot reconnect the library. It seems to be seeing only certain folders. What am I doing wrong?

    Not sure if this in an intentional move by Apple to discourage from combining Aperture masters and iPhoto libraries. It is bloody annoying. I finally bit the bullet and have begun copying all my iPhoto masters into a separate folder structure just for Aperture's library. I will then remove many masters from the iPhoto libraries except family photos my wife needs to access.
    I will then have to relink thousands of images by hand (already begun...). Another annoying "apparent bug" with Aperture is that is won't search and relink multiple images properly unless they are in the same folder. Final Cut Express, on the contrary, will search my entire directory structure to try to find the external video references. Not sure why Aperture is so crappy at this...
    A lovely little by-product is that a number (estimated 15%) of my referenced images that I am trying to relink have become corrupted such that Aperture thinks the original file is something other than the file it was. (?) I have to delete the versions in this case and replace the versions with the correct images. I am afraid that I will lose all editing on those images, but haven't really tackled the problem yet. Some examples of these corrupted reference images are below:
    http://www.flickr.com/photos/bradsteelsgallery/4396430491/sizes/l/

  • Aperture, Droboshare, and referenced files

    Hi, I just bought Aperture 3.0.2 as an upgrade from using iPhoto. My iPhoto setup is such that I have all my files stored on a Drobo and connected to my network via a Droboshare. I am attempting to have my Aperture Library file stored on my macbook, while creating reference files of the same photos on the Drobo.
    Now, I have no problems accessing the photo using iPhoto, but when I tried to import the same photos as referenced files in Aperture and leaving the files stored on the Drobo, it initially finds the files in the Import tool, creates thumbnails, and then proceeds to display blurry thumbnails of the pictures.
    When I double-click into the picture, it shows the image enlarged and blurry. If I select Show File in Finder, it proceeds to tell me the file cannot be found and has possibly moved, even though the file remains in the Drobo unmoved. Outside of Aperture, I can still access the file and iPhoto still has no problems seeing the image.
    In Aperture, if I select Locate Referenced Files, the bottom half of the window I can traverse the tree and I can see the file, but clicking Reconnect does not do anything.
    Does anyone have any luck setting up Aperture to use referenced files stored on a Drobo connected to the network via a Droboshare?
    Any help is appreciated.
    Thanks,
    Tim

    hmm, well i did try using referenced files directly off my machine and that seemed to work. Thing is, iPhoto is working fine with the Drobo via the Droboshare, as is my iTunes, which I also store on the Drobo as well, so I assume the problem must be Aperture which doesn't seem to like the Drobo?
    After importing a referenced file from Drobo into Aperture, I did notice a peculiarity: when I click Show in Finder in Aperture, it says the file cannot be found, and it displays the following path:
    /Volumes/DroboShare/0db090320629/LUN0/Drobo/0db090320629/LUN0/Drobo/flowers.jpg
    so I copied the following path into the Finder's Go To Folder:
    /Volumes/DroboShare/0db090320629/LUN0/Drobo/0db090320629/LUN0/Drobo
    and the Finder says the folder can't be found.
    However, I noticed the path is repeating itself after the first Drobo, so then I tried copying the following path into the Finder's Go To Folder:
    /Volumes/DroboShare/0db090320629/LUN0/Drobo
    and this works and Finder can find the folder where the image is stored. This leads me to believe there is a bug in the way Aperture is creating the referenced image path?
    Shortly after I originally posted, Apple released 3.0.3. I was really hoping this would fix the error, but I can confirm I still have the same problem after upgrading to 3.0.3.
    I'm just curious if anyone else out there is successfully using a workflow which incorporates a network attached storage for their referenced files?
    Regards,
    Tim

  • Can't reconnect edited TIFF files back into library

    There's a big problem I'm having.
    After a vault restore, Aperture won't let me reconnect my edited tiff files. I open the "manage referenced files" dialogue and I navigate to the image, but I can't reconnect them. The "reconnect" buttons are greyed out. Here's a couple of pix of what's happening:
    http://amrosario.com/Aperture001.jpg
    http://amrosario.com/Aperture002.jpg
    Not to mention that with some images, Aperture is recorded the wrong file size (as seen in my second screenshot).
    I need help desperately!
    Antonio

    Thanks for all the words of help.
    What is strange about this is this:
    I'm working with NEF raw files from a D2X.
    Before my hard drive issue, I did some editing of the raw files in Aperture. Then, I had Aperture send the tweaked file to Photoshop for more editing. Aperture sent over a 16bit tiff file. The file was about 70 megs in size (a 12.4 megapixel file @16 bits). Fine.
    So, I did some editing and resizing in Photoshop and ended up with a layered TIFF file which was about 300 megs in size. Fine.
    I saved it and went back to Aperture. Aperture took a minute or two to update the thumbnail. Fine - it's a big file. So far, everything was working as it should.
    Back in Aperture, the edited TIFF was (automatically) stacked with the raw NEF file. Fine.
    Then... HARD DRIVE ISSUE (actually, a raid failure, but that's another story).
    After many hours or rebuilding and restoring from a saved vault, I get this issue where Aperture cannot find the stacked, edited tiffs. Ok, fine, so....
    I go to the "manage referenced files" command and navigate to the tiff files stored on my hard drive and bingo....
    No go...
    But the strange thing is (and you can see it in my second screenshot above) that aperture is looking for a 70meg image where the edited image is actually much larger. If you look at this screenshot ( http://amrosario.com/Aperture002.jpg ) you can see that Aperture is looking for a 70.1mb file at 2852x4296 pixels. This is what Aperture originally sent over to Photoshop for me to edit. The actual edited file was saved (and cataloged by Aperture before my HARD DRIVE ISSUE) as a 236.8mb file at 3419x5150 pixels (this was the edited version.
    After my hard drive issue and restore from vault, Aperture "forgot" that I had edited the image and enlarged it. It is looking for the 16bit TIFF that it originally sent to Photoshop when I first started to edit the image.
    This is the big problem and, I think, bug in Aperture.
    I have since reimported the TIFF files and will re-stack them with the original NEFs. But this is a lot of work.
    I'm wondering if someone from the Aperture team can help figure this out.
    I hope that I've made the problem clearer. This is hard to do with words.
    Thanks for everyone's input.
    Antonio

  • 3.1 Upgrade Issues - Referenced File Locations Broken

    I have been through the 3.0.3 to 3.1 upgrade routine now four or five times without success. Each time, the process stalls after the upgrade, during the opening library routine. Eventually, I get an error, quit, and rebuild the library.
    That effort gets the program to open, but now all of my referenced files (about 72,000 of them) have lost their connection. Each image has a badge with a red line through it, and when I right-click on it to 'show in finder' I get an error message that says it cannot locate the file, as the previous location is 'null'.
    When I go through the locate and reconnect function, it will only work on one file at a time.
    I've noticed on the reconnect dialogue, that it shows the correct location except for the .NEF at the end of the path.
    Also, I have noticed that the adjustments are not grayed out as they would be for an offline file, and are operational. However, they do not work.
    There does not appear to be any processing going on in the background, although there is slight activity showing in my OS Activity monitor.
    My db is about 70gb in size. I tried the upgrade on another db, and it worked fine. That db is much smaller, so I am not sure that the problem is related to the size, or that my db may be damaged somehow prior to the upgrade.
    Any help would be appreciated. This is getting pretty frustrating.

    OK.....thanks for the advice. But, confirm for me, please....
    1. Set aside 3.1 app (does that simply mean rename it temporarily)
    2. Restore 3.0.3 app from Time Machine.
    3. Restore 3.0.3 db from Time Machine.
    4. Run Rebuild on db.
    5. Run resulting db from 3.1 app and perform upgrade conversion.
    That should take care of the rest of today....:-)

Maybe you are looking for

  • MSI kt3 ultra aru sound problems

    i have this board (kt3 ultra aru) and i can't make the center/sub outputs on the audio bracket to work. the rear outputs are ok, but center/sub... dead. I only have that channels when I don't use the bracket. Is my bracket damaged? or maybe a softwar

  • Tax item

    Another question: Upon creation of a billing doc and with regards to the creation of pricing procedure, this error occurs: Tax statement item missing for tax code S5 (tax code S5 is a deferred output tax) Message no. FF805 Diagnosis No tax item exist

  • How to install PVM guest in ov 3??

    hi I am little bit of confused about what kind of guest i will be able to install on this server : its a 64 bit, Hyper Technology enabled but it does not have VT/AMD-V enabled so i cant be use at fully virtualized guest. so my question, in this circu

  • Re: Unable to Cancel Premium Subscription (Group v...

    I can't either cancel my Skype Premium account! There is no way to cancel it or to find any answer. Please help me with a link that really works. Thanks.

  • Selecting Key Photo in Faces

    Is there a way to make a photo a key photo in Faces similar to the way you can make a key photo in events?  For some of the people in faces, the pictures appearing are years old, even baby pictures.