Referenced files show up as managed

Using Aperture 3.4.1
I have about 10.000 images (each is a 125MB TIFF file) in Aperture.
As the AP library became very large (about 1,3 TB), I decided to go from Managed to Referenced.
So I used the "Relocate Original for Project" from the File Menu.
This worked fine, but..., unforunately Aperture crashed a couple of times.
So now I have  about 200 images of which Aperture thinks they are Managed, although they have been moved to where I told Aperture to Relocate them as Referenced.
What I suspect that happened is:
- Aperture relocated the Original file to outside Aperture, then crashed before it had time to store the new File Status and the link to the Referenced file in thedatabase.
I have tried to Repair and Rebuild the database but to no avail.
If I try to Relocate Original -> Unavailable original files cannot be relocated.
I I try to Locate Referenced Files -> No Referenced Files
I cannot use Show in Finder, as Aperture thinks the image is Managed.
Anyone an idea how to solve this?
Would be greatly appriciated.
Jan

Léonie,
I do not get any error message.
Aperture just dissappears from the screen.
I have different Libary's.
1 filled with TIFF files that came from Nikon scanner (approx 10.000 images)
1 filled with a mix of RAW (from different camera's) and JPG's. (approx 20.000 images)
1 filled with JPG's (approx 3.000 images)
I had the crash with all Library's.
I am trying to go from managed to referenced.
The TIFF files are stored on external disk, connected through USB.
The other 2 library's store their referenced files on the local hard disk
All Library's are alson on the local hard disk.
But this morning I noticed that while the "Relocate Original for Project" was running, also Time Machine was running it's back-up job. Maybe that that has something to do with it.
From the logfile the entry's around the crash, and the first lines of the crashlog itself:
10/13/12 10:29:08.625 AM com.apple.security.pboxd: kCGErrorIllegalArgument: CGSGetWindowTags: Invalid window 0x1e0
10/13/12 10:29:08.625 AM com.apple.security.pboxd: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10/13/12 10:29:08.625 AM com.apple.security.pboxd: kCGErrorIllegalArgument: CGSSetHideOnDeact: error getting window tags
10/13/12 10:29:09.037 AM com.apple.security.pboxd: kCGErrorIllegalArgument: CGSCopyWindowColorSpace: Invalid window 0x1e0
10/13/12 10:29:33.785 AM Aperture: kCGErrorIllegalArgument: CGSRemoveWindowFromWindowMovementGroup: Invalid window
10/13/12 10:29:58.905 AM com.apple.launchd.peruser.502: ([0x0-0x65065].com.apple.Aperture[1011]) Job appears to have crashed: Segmentation fault: 11
10/13/12 10:30:00.708 AM ReportCrash: Saved crash report for Aperture[1011] version 3.4.1 (3.4.1) to /Users/imacjan/Library/Logs/DiagnosticReports/Aperture_2012-10-13-103000_iMac-B eheerders-iMac.crash
10/13/12 10:30:24.097 AM com.apple.backupd: Copied 1798 files (5.4 MB) from volume Macintosh HD.
10/13/12 10:30:27.080 AM com.apple.backupd: 3.88 GB required (including padding), 310.11 GB available
10/13/12 10:30:28.768 AM mdworker: (Error) ImportPluginLoading: Couldn't load plugin 'file://localhost/Library/Spotlight/VMware%20Virtual%20Machine.mdimporter/'
Process:         Aperture [1011]
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 [168]
Date/Time:       2012-10-13 10:29:53.834 +0200
OS Version:      Mac OS X 10.7.5 (11G63)
Report Version:  9
Interval Since Last Report:          203614 sec
Crashes Since Last Report:           2
Per-App Interval Since Last Report:  104689 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:                      B540CD5B-922C-41AB-B033-2BE4DAECBD38
Crashed Thread:  13  Dispatch queue: com.apple.security.pboxd.xpcq
Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
VM Regions Near 0x18:
-->
    __TEXT                 000000010ec66000-000000010f3b8000 [ 7496K] r-x/rwx SM=COW  /Applications/Aperture.app/Contents/MacOS/Aperture
Application Specific Information:
objc_msgSend() selector name: retain
objc[1011]: garbage collection is OFF
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff8751367a mach_msg_trap + 10
1   libsystem_kernel.dylib                  0x00007fff87512d71 mach_msg + 73
2   com.apple.CoreFoundation                0x00007fff8fc2350c __CFRunLoopServiceMachPort + 188
3   com.apple.CoreFoundation                0x00007fff8fc2bc74 __CFRunLoopRun + 1204
4   com.apple.CoreFoundation                0x00007fff8fc2b486 CFRunLoopRunSpecific + 230
5   com.apple.Foundation                    0x00007fff8afcef7b -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267
6   com.apple.Foundation                    0x00007fff8b052b56 -[NSRunLoop(NSRunLoop) runUntilDate:] + 66
7   com.apple.Aperture                      0x000000010ede782b 0x10ec66000 + 1579051
8   com.apple.RemoteViewServices            0x00007fff8ed1823c __111-[NSRemoteSavePanel beginSheetForDirectory:file:types:modalForWindow:modalDelegate:didEndSelector:c ontextInfo:]_block_invoke_0 + 38
9   com.apple.RemoteViewServices            0x00007fff8ed1386a -[NSRemoteSavePanel sheetDidEnd:returnCode:contextInfo:] + 223
10  com.apple.AppKit                        0x00007fff91d6f047 -[NSApplication endSheet:returnCode:] + 275
11  com.apple.Aperture                      0x000000010f0db320 0x10ec66000 + 4674336
12  com.apple.RemoteViewServices            0x00007fff8ed169d5 -[NSRemoteSavePanel _handlePanelComplete:] + 386
13  com.apple.RemoteViewServices            0x00007fff8ed111c3 __45-[NSRemoteServiceConnection _setupConnection]_block_invoke_0141 + 69
14  com.apple.CoreFoundation                0x00007fff8fc4bdfc __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 12
15  com.apple.CoreFoundation                0x00007fff8fc03f02 __CFRunLoopDoBlocks + 322
16  com.apple.CoreFoundation                0x00007fff8fc2bfa7 __CFRunLoopRun + 2023
17  com.apple.CoreFoundation                0x00007fff8fc2b486 CFRunLoopRunSpecific + 230
18  com.apple.HIToolbox                     0x00007fff87f6c2bf RunCurrentEventLoopInMode + 277
19  com.apple.HIToolbox                     0x00007fff87f7356d ReceiveNextEventCommon + 355
20  com.apple.HIToolbox                     0x00007fff87f733fa BlockUntilNextEventMatchingListInMode + 62
21  com.apple.AppKit                        0x00007fff91abb779 _DPSNextEvent + 659
22  com.apple.AppKit                        0x00007fff91abb07d -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
23  com.apple.Aperture                      0x000000010f0da00d 0x10ec66000 + 4669453
24  com.apple.AppKit                        0x00007fff91ab79b9 -[NSApplication run] + 470
25  com.apple.prokit                        0x0000000110176be1 NSProApplicationMain + 387
26  com.apple.Aperture                      0x000000010ec759c2 0x10ec66000 + 63938
27  com.apple.Aperture                      0x000000010ec75314 0x10ec66000 + 62228
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x00007fff875157e6 kevent + 10
1   libdispatch.dylib                       0x00007fff903ef786 _dispatch_mgr_invoke + 923
2   libdispatch.dylib                       0x00007fff903ee316 _dispatch_mgr_thread + 54
I hope this is readable.
Regards,
Jan

Similar Messages

  • Version/Referenced File name changes and managing reference files.

    I had an issue with wrong version names for reasons of my own DAM workflow. I changed the name in the metadata portion of Aperture and changed the name in the drive the has the referenced files for the versions (and there are no duplicated versions, etc). When I go to manage the referenced files, I get the old version names popping up in the manage reference files window/dialog. the names I want show up elsewhere in Aperture and on the reference external drive, but not in the manage reference files dialog. Is there a way to ensure that all of Aperture knows my new version names and new referenced file names?

    Oh, and I did restart the application, but not the machine.

  • Image size problem after converting from Managed files to Referenced files.

    I recently moved to Referenced files for all my images. I use a plug-in (Graphic Converter 8.8.2) to resize all images to a consistent size (1440 pixels wide, landsacpe format) for a web app that I use (Sandvox). With Referenced files, when I drag and drop the externally processed image, it shows up at exactly one-half the correct size (720 pixels). As a test, doing exactly the same opeartion with an Aperture library utilizing managed files, there is no problem...it works as expected.
    As a temproray work-around, I found that instead of dragging and dropping, I use the Aperture Export function, everything is correct. This is not really what I want to do because I have a lot of images to process.
    This is Aperture 3.5 and Mavericks,  but the problem was there with with Aperture 3.4 and OS 10.7.5.

    Thank you for the suggestion and running the test. I changed the Preview settings to 1440, and then 2560 and finally, Don't Limit. Quit and relaunch Aperture between each setting. No luck.
    But you gave me a hint: maybe the problem has to do with the images being first Managed and then moved to Referenced files. So I tried one that has never been a Managed file and everything works correctly! Don't know if this is a bug or a feature.
    Mystery solved, but I still have a lot of images to reprocess.
    Thank you for the help.

  • 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/

  • How do you convert managed files to referenced files?

    I have exported all the files that I mistakenly saved to my aperture library.
    since I've exported them by year and month I can easily incorporate them into my referenced files on various external hard drives.
    but how do I now actually get the managed files in the aperture library out of the aperture library? (I am trying to make the aperture file smaller so that it can more easily stay on my laptop).
    and is there a way to get rid of the managed files without having to reimport all the files and reimport all the metadata …

    As I understand it:
    You had a bunch of original image files and imported them into AP using managed.
    At this point the original files are totally separate from AP, since AP has copies of the originals in its library file (a package). If you relocate, AP will not put the files back where they were, especially since you have moved some files around in the database.
    If you haven't done much editing to the masters, consider creating a new library and a new import. Otherwise, try relocating a small amount of your projects to see how AP sets up the folders on the disk.
    But AP will not automatically write the masters back to where the originals were - the relocate process involves you indicating where the files will go. As I recall, you have to choose a folder structure from several choices and these may not parallel the originals. Plus, as I said above, since you have moved files around the database, you will definitely not get the same layout as the originals.

  • Managed or Referenced files?

    I'm using Aperture 1.5.6 for a year and although pretty familiar I still have a few questions about managed vs referenced files and they are:
    1) Are all Aperture features available to both managed & referenced files. i.e., metadata, keywords etc. etc.?
    2) If I choose to change referenced files to managed from my hard drives into the Aperture Library are those files duplicated or now only in the Aperture library?
    Thanks

    Despite this quote from page 140 of the User Manual,
    "Choose whether you want the image files moved or copied to a new location by clicking the 'Move files' or 'Copy files' button".
    If you choose to store them in their current location, they are neither moved nor copied.
    If you choose to have them stored in the Aperture Library or elsewhere they are copied.
    This is probably a good thing because, no matter what you do, it keeps your iPhoto Library intact.
    DLS

  • Change from managed to referenced files

    My hard drive is full, so I'd like to move all the managed master files in my Aperture 3 library off my internal hard drive onto an external 'photos' hard drive as referenced masters instead. Although I feel like I understand the general principles of what's involved, I have some specific questions I'm hoping some more experience A3 users can help with:
    What command in Aperture do I use to move all the managed master files in my Aperture 3 library off my internal hard drive onto an external one, converting them all to referenced masters? (I can only seem to find instructions for going the other way (consolidating referenced masters into the library) or for moving masters that are already referenced.)
    After all my master files are converted to referenced masters, if the referenced external hard drive is disconnected, will I still be able to make adjustments to the 'off-line' files using the previews stored in the library? (e.g.: adjust colours, crop)
    After all my master files are converted to referenced masters, if the referenced external hard drive is disconnected, will I still be able to edit the metadata for those off-line files using the previews stored in the library? (e.g.: change time, add keywords)
    Time Machine automatically back-up the referenced master files on the external 'photos' hard drive? (I understand that this would at the very minimum require that my Time Machine external back-up hard drive be big enough to back-up both my internal drive and my photos external drive -- which it is.)
    Regardless of the Time Machine answer in #4, if I duplicate the photo directory on my external 'photos' hard drive onto another external drive as a back-up, and then if the 'photos' hard drive fails, is it a simple process to get Aperture to point to the files on the back-up hard drive and use those instead?
    Thanks everyone!! I really look forward to your feedback.

    1. Under File use Relocate Masters for ... (project, library, depending on what's selected on the Library tab) and choose the destination on your external Hard Drive
    2. You won't be able to make adjustments to the files once the Hard Drive is disconnected ( the masters are offline). You can only rotate the images.
    3. Yes, you can make all sorts of metadata edits to off line masters as well as create albums, rate, etc.
    4. Yes it will. You need to deselect your External Hard Drive from the list of excluded files to Back Up from System Preferences, Time Machine, Options.
    5. The process to re link Aperture to your back up Masters on your 2nd Hard Drive is simple, but not automatic. Aperture keeps track of your Hard Drive on which masters are stored, so you'll need to use the Locate Referenced Files menu under File. Ideally, if you select the Library and use the Locate Refernced Files, you just point Aperture to the first file on the list and then select Reconnect All, but it can be time consuming depending on the size of your library.

  • Manage referenced files?

    As a newbie to Aperture, I'm uncertain how to bring my "referenced files" into Aperture so they will become "managed" and available to the Vault process. I am finding it a much better option to have all my files in one location for ease of backup. Any pointer w/b much appreciated
    thanks

    I guess I've not been clear.
    I've referenced files in Aperture, they are located in Adobe Bridge folders. If I consolidate with move option they will leave Bridge? If I use copy option they will then be managed in Bridge but available in both locations?
    I'm sorry to belabor this, but want to be sure to keep my Bridge files secure while I continue to evaluate Aperture. Thanks for your patience.
    Again, thanks for your effort on providing this assistance.

  • Aperture Quits when using Manage Referenced Files

    Hello everybody
    All my images are on an external hard drive, but since the last Aperture update, It has several problems to connect them. When I try to reconnect them all using "Manage Referenced Files..." option, Aperture suddenly quits (whan I press reconnect button).
    Is this normal? Is there anything I can do?
    Thanks a lot in advance.
    Message was edited by: Ainvar101

    Hi,
      It's entirely possible that if you were experiencing this frequently prior to the update, that errors have crept into the database.  Does this tend to happen to all raws, old ones, or new ones?
    Another consideration is that if the raws are large, then you may need to upgrade to 8GB.
    Regards,
    Calx

  • Manage Aperture Referenced Files

    I had thousands of files in Aperture, all referenced to an external hard drive. The hard drive is back-up and all the files are safe, but I dropped the original hard-drive that aperture was referenced too... Well, I didn't think it too big a problem, except that I had shot, and edited a few thousand more photos after my last vault back-up... I copied all my backed-up files onto a new hard-drive and thought I was OK... My aperture library looks in tact, except that Aperture thinks that it cannot find the Master files. Aperture Support tells me to simply "Chose File>Manage Referenced Files> except that it appears that I need to chose them all one by one! Is there anyway that I can relate all the Projects to their respective folders - they are all date sorted - in fact the filing system I use is YYYY-MM-DD-24HR-MN-SD-N, so identifying each file is actually quite easy, but I'm not very inclined to go through all the thousands of files I had saved, easier to just back-up from my last vault and then sort through all the lost work from the past few days, and learn to be more fastidious with the vault, and never ever drop a hard drive again!

    Thanks. I did try that, but it would not allow me to select "Reconnect" unless I selected individual files and associated them correctly. I wasn't even able to do this for a project, let alone an entire library; but I can do it one by one!
    I think my best bet is to just re-import my entire library... as it is well defined and sorted, so I can just use the file names already created and keep them in the current location. I may lose some editing, but most of the really important files have versions exported elsewhere.
    My biggest question is: If the hard drive which stores referenced files is damaged again, how can Aperture restore to a facsimile back-up file on another drive?

  • Manage Referenced Files dialog -- Hangs constantly in v2

    The Manage Referenced Files dialog is hanging on my system costantly. It goes OK as I navigate to the first drive in the lower pane but hangs when I try to change to a second drive.
    Message was edited by: thomas80205

    I just tried archiving some more files to DVD and ran into this problem again. I've used the "Relocate Masters..." command to move the files to a folder on my desktop. Then I use Toast to burn them to DVD. When I use "Manage Referenced Files..." this is what happens:
    It would appear that the PSD file isn't relinking because Aperture thinks the file size is smaller than it actually is.
    Also, is there a way to contact tech support by email or phone?
    MacBookPro Mac OS X (10.4.8)

  • Duplicate entries showing up in "Manage Open Files"

    We are seeing an odd phenomenon with file sharing on our Windows Server platform. I'm posting here because I haven't seen anything quite like this in my Google searches.
    Off and on, when a user will try to access a file stored on the share of our file server, the file will open in "Read Only" format. Usually this has to do with multiple users having the file open at once, but by the time the user experiencing the
    issue would get around to telling me about it, I couldn't find any indication of a conflict in "Share and Storage Management" and they would be able to open the file after I prompt them to try again.
    I've done my due diligence by checking for leftover locking files on the share, but have not seen any, so up until this point I've just chocked the issue up to happenstance.
    However, I finally managed to catch the problem in the act. A user was showing me something on their computer when the file they tried to open showed up as "Read-only." I opened the share manager on our file server, and saw only that user had opened
    the file. I asked them to close the file and try again. They did, and got the "Read-only" version again. I refreshed the view in "Manage Open Files" and saw this: 
    When the user opened the file, it looks like the file server thought the user opened the file 5 separate times all at once. 4 instances of the open file are marked "Read" while only one is marked "Read, Write." 
    Has any one seen this behavior before?
    Thanks for your help,
    DSell

    Hi DSell,
    From the screenshot it is a doc file. So please first check if there is any temp file created in the folder e:\users\nk\documents\signs. This including tmp files and files with no extension. 
    Shaon,
    In response to your reply, I'd like to point out that I already mentioned looking for temp files and didn't find any: 
    "I've done my due diligence by checking for leftover locking files on the share, but have not seen any, "
    Specifically this means I was on the look out for files matching the open file in the users folder starting with a "~$". In each instance, the temp file was not there. I would
    also like to point out again that the file was completely closed, there were no entries of open files in the file manager before the user tried to open the file once. As soon as they tried to open it once, 5 entries of the open file showed up immediately in
    the File manager. Very strange.
    The user indeed has permission to read and write to the folder. I have not seen the issue occur for non-Office files, but I will report as soon as I see that behavior.

  • Can I take a managed file and link it to a referenced file?

    Is this possible?
    I am creating a referenced library. Going forward, I know that I need to use only the referenced file to make new versions within Aperture.  But going back through my old files, I have originals and then all the edited copies.  These are only linked together in my head, because my practice was to make a copy of an original before working on it, so when Aperture imports it, it sees my copy as a new "original". I wondered if it is possible to reestablish any kind of link between my edited copies and the actual original file.
    Thank you.
    LCA

    Sorry not possible. To Aperture every file imported is an original (master). There is no way to say this import is a version of that original.
    You can come close using keywords and possibly stacks. It's not exactly what you are looking to do but at least you'll be bale to locate and group all similar images.

  • How do I know if the image is a master or a referenced file?

    I imported images into Aperture, and am now not sure whether to delete the originals (that were already on my hard drive in a photos folder).
    How can I tell, after having imported them, whether the images in Aperture are referenced or master?
    I'm just scared of deleting the original folder (the outside aperture one!)
    Thanks!
    Hannah

    Not really...
    That merely shows you the master image with no adjustments applied - I think the question was how to tell the difference between masters that are referenced vs. managed - the answer to that question is that you can either use one of the functions under the file menu to consolidate the images into the library as managed masters (not available if images in the current selection are already managed) or use manage referenced files to take a look at the location on disk (not available for managed masters).
    The other thing that you can do is do a search based on file status (add a search element to the search HUD)
    more info here;
    [Aperture File Management|http://photo.rwboyer.com/2009/01/aperture-2-file-management>
    There are probably some useful info regarding searching near the end of the article.
    RB

  • Importing into Aperture 3 from iPhoto as referenced files

    Apologies if this has been asked before, but I can't find anything this topic...
    I've just upgraded to Aperture 3. In Aperture 2, my way of working was to store RAW images in iPhoto and import as referenced files into Aperture. This was very straightforward. Now, I have 2 problems:
    1 - I can't see how to import referenced images from iPhoto. If I use the import command, my iPhoto images don't show up in the list of locations to import from; if I use the iPhoto browser in Aperture and drag from that, it imports the file into the Aperture library rather than importing as a referenced file...
    2 - If I import using the iPhoto browser, not only does it import into the Aperture library, it imports the jpeg preview rather than the RAW file.
    The only way I can see to get the RAW file into Aperture is to find it in the Finder then import into the Aperture library. This seems excessively long-winded and also duplicates the file, using up extra disk space.
    I'm using Aperture 3.0.1 and iPhoto 7.1.5
    Thanks in advance for your input

    I have not imported an iPhoto library because my workflow is to to use Aperture for storing and archiving Raw files and iPhoto for exported jpegs.
    However the instruction in the Aperture 3 PDF Manual are as follows:-
    To import your iPhoto library
    Choose File > Import > iPhoto Library.
    Select the iPhoto library in the dialog that appears.
    Choose a location for the imported images by doing one of the following:
    • To store imported masters in the Aperture library: Choose “In the Aperture Library” from the Store Files pop-up menu.
    • To import the files as referenced images stored in their current location on your hard disk: Choose “In their current location” from the Store Files pop-up menu.
    Tip: Choosing“Intheircurrentlocation”isrecommended.Whenyouchoosethisoption, Aperture refers to the original files in their current location and does not have to duplicate the files, which doubles the disk space needed to store the files. For more information about referenced images, see What Are Managed Images and Referenced Images?
    • To store imported masters as referenced images in the Pictures folder on your hard disk: Choose Pictures from the Store Files pop-up menu.
    • To store imported masters as referenced images in a location other than the Pictures folder: Choose “Choose” from the Store Files pop-up menu and select a folder. Choose “No folder” from the Subfolders pop-up menu to specify that the files be stored as separate, individual files in the selected folder. You can also specify that Aperture create a hierarchy of subfolders with specific folder names to hold your files.
    =====
    This extract is from page 169. Perhaps it clarifies and identifies a step you have omitted.
    AW.

Maybe you are looking for