Master files Vs. Referenced files

I'm new to Aperture and have to admit I'm a bit confused by all the terminology- masters, reference files, etc.
What I want to do is store my photos on an external drive because I don't have a lot of room on my computer. What I think I would like to do, is keep photos on this external drive, but manage them in Aperture, e.g. deleting some, rating them, stacking, doing some basic corrections and then making sure that all these corrected files end up on my external drive. Do I have to export the corrected images to the external drive, or do I just leave the changes as is, in Aperture, and when I need to access it in future, just use Aperture? Once I make all the changes can I just export the whole project to my external drive? In the past, I was used to making sure all my changes, deletions, corrections were done before I backed up to an archive.
Sorry for maybe missing the obvious, but somehow I'm having trouble understanding all the "stuff" about files. Reminds me of the problems I had in Math at school.
Thanks for any help.
Carl

check out these articles:
http://www.bagelturf.com/aparticles/index.php
they should help bunches ...
next thing is to buy this book:
http://www.amazon.com/Apple-Pro-Training-Aperture/dp/0321539931/ref=sr11?ie=UTF8&s=books&qid=1221487998&sr=1-1

Similar Messages

  • 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

  • Workflow:  Master files to referenced files

    I am seeking advice on how best to go about making thousands of managed master files, referenced files. I have been importing everything as a master file into my aperture library thus far. Now, my library is getting too large to manage and I need to free up some space by moving some older shoots to other hard drives. I suppose I could export each project individually, but it seems like this would take days, if not weeks to move all of these RAW files. Can anyone recommend an efficient procedure?
    Thanks,
    Ryan

    1. Select images in Aperture.
    2. File>Relocate Masters...
    3. Pick a location and sub-folder format.
    Ian

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

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

  • Aperture referencing files to time machine HD instead of from 'working' HD

    Every once in a while I will go into a project see the "broken link" icon on my previews. In Finder I check the location I have all my images stored (and initially referenced) on an external HD. They are there.
    I go to File>>Locate Referenced Files and see the referenced images have been changed to a location on my separate Time Machine external HD. I locate them and everything is fine but it's annoying.
    I don't not have Time Machine on automatic because I have a laptop and like to choose when it backs up. I've looked through other Time Machine/Aperture problems and couldn't find anything. Does any one know of a setting, advice, or have experienced this at all?
    Thanks.

    Thanks. Sorry, for the delay to answer your questions:
    I'm the only one managing the files, and it has happened quite a few times now. The files are in multiple projects ranging from recent imports to projects from a few years ago.
    I didn't need to use "File→Relocate Master ..." just the "File→Locate Referenced Files" because my masters are still intact on my working HD. It says that my previous location was on "Volumes/Time Machine/photography/...etc." when I always import masters to "Volumes/My book/photography/...etc"
    Does Aperture notice if I move master files because my thought is that Aperture is noticing my TM copying files to another HD and then referencing those instead of my original working HD I import to. Then, the next time I open Aperture it cannot reference the Time Machine files.
    Is it because I have TM (USB) backing up my internal HD and my external working HD (FW800)?

  • How can my own hard drive be considered off line to find referenced files?

    my iPhoto library for some reason could not be imported to Aperture when I converted to Aperture.
    However, I selected the option to create a referenced library and it worked fine.
    I upgraded my hard drive from 160 to 750 at a professional apple reseller and they copied all of my data, programs etc as well.
    While I never checked to see if this was the case before, becuase I had no reason to check for it, I notice now that all of the aperture thumbnails have the "reference offline" icon and when i try to "locate reference", I can do so, but Aperture still considers my own hard drive offline!!!   How's that for strange. 

    Every hard drive has a volume name (they also have a UUID but I don't think Aperture cares about that.)  If the new drive was not given the same name as your old drive then as far as Aperture is concerned, the drive it's looking for is not present (it's looking for a drive with a specific name and not finding it.)
    While YOU know that all the data on the old hard drive was copied to the new hard drive, Aperture doesn't know that (and makes no assumptions).  So if the volume name it's looking for isn't found, then the drive is "offline". Aperture is working as it should.
    You could rename the hard drive back to the original name, but then that would just cause it lose all any new 'referenced' masters you added since upgrading the drive.
    To fix:
    You'll need to reconnect the masters.  In the lower right corner of the thumbnail you should see a small icon which ordinarily has a tiny rectangle with an arrow pointing away (indicating this image is a "referenced" master).  If the master is missing you'll have a little orange triangle with the "!" inside it (indicating a problem).
    In the main menu, select "File" -> "Locate Referenced Files..."
    A box will appear and you can check the box which reads "Show Only Files Not Found" (this will hide all the files which are currently fine so that you only have to deal with the files that have a problem.)
    In the lower part of the panel is filesystem browser.  You can navigate to the directory drive & directory where these files are located and click "Reconnect" or, if they're all in the same place, "Reconnect All". 
    Pick "Done" when you've finished.
    If you don't like using "referenced" masters, you can tell Aperture to bring the masters into the Aperture Library so that it will manage the files for you (and avoid this problem in the future).  In the main menu pick "File" -> "Consolidate Masters".  You'll be given the choice to "copy" the files (it'll copy the masters but still leave the old files back in their original locations... but Aperture will no longer need those originals.)  or you can "move" the files (Aperture will copy them into the library then delete the original after the copy is completed... effectively "migrating" the masters into your library and cleaning up the originals when it's done.
    Regards,
    Tim

  • "Using the Filter HUD to Search for Referenced Files" (and "Locate Referenced Files")

    I am trying to follow the Help Documentation item "Using the Filter HUD to Search for Referenced Master" (not sure if there is a way to post a URL to this) and I am not seeing what it is telling me to do.
    I am going to Edit > Find and it is telling me to "Click the Filter HUD button beside the search field in the Browser". Is this referring to a browser in the Aperture UI or is this in the Filter HUD display? I am not finding this.
    Also, it saying that in the Filter HUD I should "choose File Status from the Add Filter pop-up menu, and select the 'File Status' checkbox." and I am not seeing this either. Does anyone know where this is at?
    Lastly, I see that there is a command called File > Locate Referenced Files and when I run this I get a "No Referenced Files in the /current/ selection. I have realized that I don't quite understand whether I am running this search for a specific Project and/or whether I have to make a specific selection in the left hand pane when I run a FILTER HUD or whether this automatically defaults to search the whole database. Does it matter what I have selected in the current Browser View when I run either of these commands?
    Thanks for any help in my getting this working better for me.

    hotwheels 22 wrote:
    I am trying to follow the Help Documentation item "Using the Filter HUD to Search for Referenced Master" (not sure if there is a way to post a URL to this) and I am not seeing what it is telling me to do.  1
    I am going to Edit > Find and it is telling me to "Click the Filter HUD button beside the search field in the Browser". Is this referring to a browser in the Aperture UI or is this in the Filter HUD display? I am not finding this. 2
    Also, it saying that in the Filter HUD I should "choose File Status from the Add Filter pop-up menu, and select the 'File Status' checkbox." and I am not seeing this either. Does anyone know where this is at?  3
    Lastly, I see that there is a command called File > Locate Referenced Files and when I run this I get a "No Referenced Files in the /current/ selection. I have realized that I don't quite understand whether I am running this search for a specific Project and/or whether I have to make a specific selection {4}  in the left hand pane {5} when I run a FILTER HUD or whether this automatically defaults to search the whole database. Does it matter what I have selected in the current Browser View when I run {6} either of these commands? 7
    Thanks for any help in my getting this working better for me.
    1.  Just copy and paste the URL from the on-line User Manual.  Very helpful.  Are you on this page?
    2.  From the above-linked page:
    Show the Filter HUD by doing one of the following:
    Choose Edit > Find (or press Command-F).
    Click the Filter HUD button beside the search field in the Browser.
    The instructions specify ONE of the following.  Your question indicates to me that you are trying to do both.
    3.  The User Manual has used the wrong term here.  It should say "Choose 'File Status' from the 'Add RULE' pop-up menu."
    4.  The command -- like all commands? -- works on the currently selected Images.  On the same page in the User Manual it says:
    You can select a group of images in the Browser and Aperture can show a list of the referenced images within the selection, including information about where the masters are located. {Emphasis mine.}
    5.  The Aperture workspace is highly configurable.  I don't know what you mean by "the left-hand pane".  Of what?
    6.  Yes.  Of course it matters.  At some point in the 80's when the GUI became standard computers standardized on the "Noun→Verb" syntax:  Select object(s), select command(s).
    7.  Not sure what the second command to which your refer is.

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

  • 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).

  • Finding referenced files

    I am unable to get my referenced files to re-link to the original RAW file on my external hard drive. I have gone through many post and have experience relocating referenced files which works great when you can actually get to that screen. I have tried all the repairs in the repair menu with no luck. I click on the preview of the picture and select "locate referenced files" and I get "No referenced Files". If I go to File>Locate Referenced files I get "Unavailable original files cannot be relocated". I seem to be stuck in a error loop and I'm not sure why it won't me just redirect it to the correct file? I know I can reimport but I don't want to loose all the adjustments I've made to various pictures. I know the files are on my hard drive. It's also very strange because it magiaclly happened to library's that have worked fine in the past and that I haven't touched in some time. I keep my pictures on an external hard drive and have the latest updates of Aperture and OS.

    Are the files in question really referenced files and not managed?
    I click on the preview of the picture and select "locate referenced files" and I get "No referenced Files".
    That error message usually will appear, when you try to locate a referenced file for managed files.
    If I go to File>Locate Referenced files I get "Unavailable original files cannot be relocated".
    And that error message will occur, when you use the command "File > Relocate Original", not when you try to use the command "locate referenced Files".
    From the symptoms you describe, I suspect that the files in question might be managed files, but Aperture has lost the connection to these managed files. Unfortunately, Aperture has no tools to fix broken references to managed files, because that is not supposed to happen.
    Check,if you can find the originals in question inside the Aperture library. Ctrl-click the APerture library, select "Show Package Contents" from the pop-up menu, and then browse the "Masters" folder, if your missing originals are inside. The originals are filed by the dates of the import session.
    Regards
    Léonie

  • How do I Move Library and not referenced files?

    I would like to move the library from my external HD to my internal laptop hd so I can look at the thumbnails of my shots while on the road. I want to keep the referenced files on the external HD. How can I achieve this?

    russxdrums wrote:
    I would like to move the library from my external HD to my internal laptop hd so I can look at the thumbnails of my shots while on the road. I want to keep the referenced files on the external HD. How can I achieve this?
    It sounds like your current setup is using *referenced masters*. If this is the case then you can just move the Aperture library over to your internal disk. As the masters haven't moved Aperture should be able to find them without any intervention on your part. If Aperture can't find the masters then you'll need to run *File->Locate Referenced Files...* to reconnect them.
    If your current setup is using *managed masters* you will need to turn those into referenced masters. Whether you do this before copying the library over to the internal disk isn't critical, unless you're low on space on the internal drive. If you copy the library over before turning the masters into referenced masters you'll need enough disk space to whole library.

  • Locate referenced files for whole library?

    Hello,
    I have a referenced library (internal drive, iMac) with Masters (on an external drive). I made a back-up duplicate (finder copy) of that Masters volume, on another drive. Now I'm working from that duplicate copy of "Masters" (same name, spelling, as original "Masters", on a separate external drive).
    How do I reconnect all 60,000 referenced files (from the duplicate "Masters" drive) with my library (on the iMac). I know how to do them one file at a time from the Aperture library (File > Locate Referenced Files) but can not figure out how to reconnect everything in one or two easy clicks.
    Help!
    Thanks!
    Patrick

    Select a batch of images, and go into +Locate Referenced Files+ - just the same as doing one at a time. Match up one image from your batch with the file and then, instead of hitting the <Reconnect> button, hit the <Reconnect All> button.
    Do a small batch initial until you get the hang of it, and then make a bigger selection and go and have a cup of tea...
    Here's an [earlier description|http://discussions.apple.com/message.jspa?messageID=11334896#113348 96] I gave of this process with some background details of how I handled it first time around.
    Hope this helps.
    Regards,
    Gary

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

  • 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

Maybe you are looking for

  • Some '???' appeared in the LOV Column Mapping window ...only

    Hi, I installed the Forms6i with the patch 12 on Windows XP platform. The installation language is Greek. The only problem i have faced up with the installation is the appearance of some question marks in LOV Column Mapping window ... instead of the

  • ICloud Mayhem - Shared Family Account

    I'm wondering if the support community can help with my family's iCloud woes because I'm at a loss. Between the four of us we own nine seperate Apple devices, we each have an iPhone and iPad as well as a shared family MacBook Pro. Ideally I want to b

  • Can not select March in month view with out it crashing bach to home screen

    Whenever I am in calendar month view and swipe to next month, it crashes when I try to access March.  I can access March in week view however.  Any help?

  • Target Display Mode as a docking solution - What are the downsides?

    Hi, I have a work 13" air with T.B and a new personal imac 27" at home which also has T.B. I have found this great feature that allows you to put the air in target disk mode (hold down t whilst booting) and then boot the imac whilst holding down the

  • Mapping requirement about grouping with restriction

    Hi,experts:   There is a complex mapping requirement.   There are 2 document types(A and B) in the source records.   I need collect the amount with the document which is type A.   The source records are as follows:   Doc_No    Doc_Type   Doc_Itm_No