AP3 collaboration, referenced files on external RAID

We are a small photo-studio with three photographers working together.
Here's how we work now:
- we import into AP3, unreferenced.
- when we finish the project we export as new Library and save it to an external RAID-solution (Synology) for all to have access to the project(s)
problems with this:
The weight of the exported projects, hence the time to copy and import
what we would like to do:
- use referenced for the RAW images
- keep these on a shared drive
- pass around projects which weigh less and speed up the process
Will the Libraries pick up the correct referenced files after importing them into each users Library or after opening them as a stand-alone Libary?
Any problems we can expect?
Any good references or help on the subject is welcome and appreciated.
many thanks
Henk

Yes it may work but also yes you can expect problems. Aperture is a single-user application not designed for the collaborative workflow you describe.
Apple badly needs a pro single-user laptop/desktop Apple-supported synch workflow. Badly needed and requested since v1. Here we are years later still dealing with workarounds, some flaky. Filemaker, Apple's other database app, has had this capability for decades.
Hopefully other folks will post solutions that may work, but remember that multi-user workarounds of this single-user app are prone to being flaky. Plan accordingly, including most importantly to back up original image files on and off site prior to import into Aperture or any other images management app.
Good luck!
-Allen Wicks

Similar Messages

  • Importing masters from iPhoto to Aperture 3 and saving as referenced files on external drive

    I'm making the move from iPhoto to Aperture 3.I'm new to Aperture 3 and want o make sure I am importing and saving correctly. So far, I have imported my library of events from iphoto to Aperture 3. I understand that for the most part, it makes sense to house this library on an external drive as "referenced files" vs within Apeture as "managed files." I'm not clear on exactly how to accomplish this set-up. Is this something I should have set-up when doing the initial import or can I move the files now? Once this is done, when importing new files, how do I import to Aperture 3 but save on external drive?
    Thanks in advance for your help!

    A fabulous answer:
    In the olden days ( ) when hobbyists made their own telescopes from kits, everyone wanted a six-inch lens, and the kit makers shipped six-inch lens blanks.  Which the hobbyists used to learn lens grinding.  Which is arduous and requires skill.  Which the hobbyists didn't have until they'd ground that six-inch blank -- an expensive piece of high-quality material at the time -- into a lumpen flawed approximation of a good lens.  Then the hobbyists would contact the kit makers and ask for another lens-blank, so they could build their telescope.  At which point they would drop the project because the six-inch lens blank cost so much.  And much calumny was rained on the kit manufacturers.
    Now the kit manufacturers wanted to promote a hobby, and make, in addition to telescope kits, money (not calumny), so they together and separately hit upon the idea of supplying the hobbyist with _two_ lens blanks: a four-inch blank, and a six inch blank.  Nobody wanted a four-inch telescope -- but that's not what the blank was for.  The instructions read (I've shortened this part) "Grind the four-inch blank into the most perfect lens you can.  Check it and re-check it.  Now throw it out.  You likely now have the skill to grind the six-inch blank into a useable lens."
    Thus endeth our fable.
    The point, of course, is:  start small and gain skill before committing time and material to a task.  Port just a small sub-set of you photos into Aperture.  Experiment with it.  Try different workflows.  Think about how to best use the containers and organization tools Aperture provides.  Develop a long-term naming convention for files and Projects.  Work out a back-up strategy that is scalable and that you will stick with.  My specific recommendation for beginners is: don't worry about Referenced v. Managed at first.  Make all your Masters Managed.  When you have your four-inch Aperture Library all smooth and even, put the entire thing in the system trash -- and then you can start working on an Aperture Library fit for your photos -- one that will allow you to see far, and clear, for years.
    Good luck.

  • I'm confused: 2 Aperture libraries + folder of externally referenced files

    Ok...I might be doing this completely the wrong way...but its how I "learned".
    I import files from my camera onto my MacBook Pro.
    After that, I move the photos to my external drive (via File>Relocate Master).
    Now on my external drive I have another Aperture Library, which exists at the same level as the folder for all the relocated files.
    Is this "normal"? I figured there should be only one Library. Can I delete the Library (~29GB) on my external drive and just keep my folder of externally referenced files (~21GB)?
    Confusedly,
    J

    Thanks Karsten!
    2 more if you are willing...
    1.
    So I started Aperture off the library on my external, and it appears to be older (fewer photos by about 10% or so).
    I think I can trash it, but is there any harm in me simply dragging it away in some folder and never looking at it again...just in case I missed something when comparing the two and trying to determine which was the "correct" version to keep? I'm just freaked out about losing something (or previous adjustments done to a file).
    Hard drive space is not an issue for me fortunately - I have lots left.
    2.
    I now have to rename my external drive, but per your other post (thanks for that too!) - it sounds like it should be easy.
    I looked for "Referenced" using the HUD and it showed all the pics. So I think I have moved all my pics to the internal drive.
    Now I think I can rename while Aperture is not running, then "Relocate" the masters.
    3.
    Why is my Aperture library (the one I am using to launch the app, and should be the correct one) so large?
    It is 9.67GB in size. It is referencing 7600 images, a lot of which have keywords, and very few have any type of adjustments done to them yet.
    Thanks again so much, this is a great assistance...

  • Externally edited image not stored with referenced files?

    When I open an image in the external editor, do my work in PS, and then save, the new file is located in the Aperture Library even though the master for the image is a referenced file. Is there any way to change this so the new images will be placed in the same folder as the referenced images? Thanks...gary
    mac book, G5 dual   Mac OS X (10.4.8)  

    I'm afraid for the moment you have to do it manually by selecting the image and going to File/Relocate Master.
    We should have and option in Aperture to allow us to have ALL the images in an external location.

  • File opened in external editor not stored with referenced files

    If I open a referenced raw file in an external editor (CS2) and work on the image adding layers etc., the image is not stored where I have all the other referenced files. It gets stored in the Aperture Library. Is there a way around this. I want to keep all my files together. This can be done in Lightroom, but I am trying to make Aperture work for my workflow.
    Thanks,
    gary
    mac book, G5   Mac OS X (10.4.7)  

    Well, here's the feedback I submitted to Apple:
    With the introduction of Aperture 1.5, you offered users the ability to manage their own libraries, and for Aperture to work with 'referenced' images. In fact, because of this very reason, many of us consumers decided to buy Aperture 1.5.
    Most of us photographers also use Adobe Photoshop routinely.
    But there is a huge problem/bug for us users who manage our own library (force Aperture to work with 'referenced' images) AND use Photoshop (or any external editor for that matter). When we open a file in an external editor via Aperture, Aperture creates a new 'master' for editing -- but does so in its own 'managed' library! When we save from Photoshop, the image remains in the 'managed' library! So now we have one 'master' in our own directory, and the externally-edited 'master' in Aperture's 'managed' library! This is very CONFUSING and renders external editing via Aperture USELESS... no one in their right mind would want one version of their image in an organized directory, and an edited version in Aperture's managed library (where it is difficult to find manually)! No, it makes much more sense to create the edited 'master' in the same location as the original 'master'!
    PLEASE fix this bug ASAP! Aperture already has a good method for automatically renaming files by adding (1) or (2) or (3) or so forth when it is relocating files and finds a file with the same file-name. The same logic can be applied when creating a new 'master' for external-editing: that is, it should just create another .tiff (or .psd, or what have you) file with the same name but with a (1) or (2) tagged on. For example, if my master image is \Pictures\Seattle\SpaceNeedle.tiff, then when I open this image in an external editor, Aperture should automatically make the file: \Pictures\Seattle\SpaceNeedle (1).tiff, and open that file in the external editor... rather than create SpaceNeedle.tiff in its own managed library where I can't even find it using Finder or Windows Explorer, etc.
    Many of us have this complaint (just search Apple discussions)... PLEASE rectify this problem ASAP as it is completely messing up our workflows by requiring us to manually save through the external editor and then having to manually remove every 'managed' file that Aperture makes. This is really a pain and seriously makes me want to switch to a different image management program... though I love Aperture thus far and would love to stick to it as I believe it is visionary and shaping the future of how photographers will manage their digital workflows!
    Many thanks in advance for your time!
    Best,
    Rishi

  • Slow file access-Elements 12:  I store all my photo files (".nef" RAW files) in a RAID 1 external hard drive, which the Elements Organizer links to the reference thumbnails.  Over some time - say, the past year, and especially recently, the time to bring

    One further bit of information:  I did recently run a "disc scan", in case there were file system errors, then ran defragmentation -- on the external drive.  This did not solve the problem.

    I think I'll deal with your different questions in several posts, it'll be easier for me.
    josephunit2n a écrit:
    A few comments:  recently, for the first time, I did a full "backup catalog" routine (with external RAID storage connected) to a second external usb drive, which ran successfully (done, at the time, over longstanding concern that even the RAID 1 storage was not enough data security - as you have mentioned). 
    Good thing, and it's not really a surprise for me, I would have expected no slow down in a process which only reads your RAID drive data.
    One big concern:  in all transactions (backup catalog; move to external storage) I always ignore the "reconnect missing files" dialogue.  This is due to past experience.  Long ago, when I ran it routinely, it was a disaster.  At first, I thought I might reconnect a few randomly missing files.  While this was so long ago I cannot recall all details, everything went to hell.  Even after manually locating a "missing" file,  the "reconnect" never worked.  The number of "missing" files skyrocketed, far out of any realistic number.  Even with Adobe phone support (which is critical for such an application - and must be made available again, I have no problem paying for it), the catalog was hopelessly corrupt, and I manually built a new catalog, file-by-file.  Adobe advice then:  NEVER USE "RECONNECT MISSING FILES", which I have followed religiously (while also trying to be meticulous in my transactions, not to ever create any "missing" files).
    I have never read Adobe advising to never reconnect missing files. Maybe it's not the best course in all circumstances, but I don't see a possible problem there. What is recommended by Adobe is to always reconnect files before doing a backup... Now, my own experience is that if you don't reconnect before a backup you get a restoration where the catalog still points to missing files and where those missing files have not been backed up, totally logical. I would not consider this question as a BIG concern.
    .  Finally, "just for fun", moments ago I connected the RAID storage drive, opened the organizer, and randomly opened a few images in "full screen" view - then opened a scattered group of 4 or 5 images -- and, they all came up promptly!!!!!  So, this "slow access" problem isn't consistent, all the time.  Also, I must comment, your advice to avoid the RAID 1 external usb drive, for future catalog storage, seems "tech superstition", which I will not harshly criticize, as I also have my own technology irrational superstitions.  I believe the computer "sees" this drive no differently than any other external, usb, drive.
    There's a difference between 'technology irrational superstition' and 'reasonable doubt due to ignorance' ... Understanding the problems which may arise when using a RAID drive array supposes understanding of:
    - how the organizer catalog recognizes any drive in its database. That's ok for me, but I have no personal experience of such systems. What I can tell you is that most of the problems I have seen with RAID systems were of that kind.
    - How efficiently the organizer deals with the OS when using a catalog stored on the main drive, with adequate RAM and scratch disk space while the files themselves are on the external RAID drive. Some organizing tasks imply writing to the files themselves. The xmp sidecar files (very small) are stored together with their raw parent. The thumbnails are stored in a database in the catalog folder...
    - How the organizer works with the OS (the APIs) and the particular disk driver. (I am totally ignorant, but I have seen similar problems for other Adobe applications in the feedback forum).
    ... As I said, I have to leave for a moment...
    To be continued!

  • Keeping externally-edited images as referenced files

    I use a MacBook Pro and would like to keep all my masters on an external disk due to space constraints. Aperture's support for referenced files is perfect for this since I can keep preview images on the local disk and have them available even if I'm on the road.
    The problem I have is that I use Photoshop to edit the bulk of my images. Whenever I do so, the new version is created as a managed file within the Aperture library. Is there a way to have Aperture create the new version as a referenced file in the same directory as the original? Having to remember to relocate a master each time I do an edit seems tedious.

    It will always put the edited version in the library. However you don't have to remember what is in and what is out: create a filter on the library (or project or whatever) that shows you all the images that are managed (+ menu, File Status) and then relocate them with File > Relocate Masters.

  • How to update after external change of referenced file

    Hello, I've imported some pictures as referenced. Then I've changed one of those pictures with another program (just orientation) and my expectation was to see the change update as well in Aperture, but when I re-opened Aperture the thumbnail was still with the previous orientation as well as the image itself. Is this correct ? How can I update the informations in Aperture as soon as a referenced file is changed by an external program ?
    Many thanks.
    Davide

    Hi Davide.  Never.  That's just not how Aperture works.
    In fact, it works much better than that.  You do know that Aperture has extensive and robust image adjusting tools?  In many cases -- and certainly in the trivial case of changing an Image's orientation -- Aperture's adjustment tools are more than up to any job you throw at it.  In the cases where it is not, you can use plug-ins, or any external editor you have set Aperture to use.
    You should _never_ change, move, rename or in any way alter any Referenced Master file except using the controls within Aperture.  Doing so will almost certainly break the link between the Image (in Aperture) and the Master file, with crippling results.  Sometimes these breaks can be fixed.

  • Aperture 3 doesn't see Network Drive that holds masters of referenced files

    Hi
    I created a new referenced library with about 35000 images and for the few days it worked fine. The Referenced files are located on a Drobo that is connected to My Mac OS X server. I connect to it Via AFP.
    About 2 days ago, I opened the library and the library does not see the referenced files. When I choose a file and select 'Locate referenced Files from the File menu, the locate window pops up and it shows the Drobo as being offline, even though I have mounted it, and outside of Aperture, I can access it and use it - it is definitely mounted. the "Mount" button is greyed out in the Locate referenced files window, and when I select the file using the file browser in this window, which I am able to do even though Aperture Shows the Drobo as Offline Volume Status section above, the "reconnect button remains greyed out.
    I have rebuilt the library, rebooted the server, unmounted and remounted the Drobo, and no matter what I do, it does not see the referenced files.
    Can anyone help me recoonect these files?

    I am having the exact same problem in Aperture 3.0.2. Aperture says that 529 files in a particular library are "offline" when they are on a mounted volume. The external volume on which they reside is very much ONLINE despite the fact that Aperture says it is offline.
    In fact that same volume shows up in the bottom half of the window that pops up when you select the files in Aperture and choose "Locate referenced files". I was able to successfully reconnect several thousand files by simply navigating to the files that Aperture identified as "offline" in the bottom window. But these 529 (out of a total of 4266) won't reconnect and in the bottom window the pixel dimensions for the file I'm trying to reconnect are missing. If I navigate to the files in the Finder the pixel dimensions are shown. I was able to reimport some of the so-called "offline" files on the "offline" volume. There were originally 572 that would not reconnect, and I reimported 43 of them, leaving me with 529 that should be connected, but aren't.
    Last week I spent several hours on the phone with the tech support team at Apple, but they so far have been unable to help me solve this problem. I could just reimport the files, but then would have to lift and stamp adjustments for all 529 files and get rid of the "offline" masters. One of the tech support people was going to research whether it might be possible to somehow do a "force reconnect", but hasn't gotten back to me about this.
    The external volume on which these files reside is an OWC Qx2 which is a 4.5 GB Raid 5 connected via firewire 800. In addition to being completely accessible outside of Aperture, I have run Disk Utility on it, and it verifies.
    I am hoping that Apple will come up with a fix for this problem soon.

  • Unable to capture to external RAID drive FCP 7

    Here are my specs:
    Model Identifier: MacPro1,1
    Processor Name: Dual-Core Intel Xeon
    Processor Speed: 2.66 GHz
    Number Of Processors: 2
    Total Number Of Cores: 4
    L2 Cache (per processor): 4 MB
    Memory: 4 GB
    Bus Speed: 1.33 GHz
    Boot ROM Version: MP11.005C.B08
    Running:
    OS X 10.5.8
    Final Cut Studio 3 (recently upgraded from Studio 1)
    At the end of last year I had a problem with capturing and upon research it seemed to be that the most recent update of QuickTime was not compatible with Final Cut Pro 5, which was causing my machine to not be able to capture at all. So we upgraded to Final Cut Studio 3 (FCP7) and part of the problem was solved but an issue still remains.
    For over 3 years we have been using an external Raid drive as a capture scratch and we still have over 5 TBs free. The Raid is connected by SCSI. Earlier last year I was able to capture to the Raid drive without any problems but now the capture will freeze whenever that is set as the capture scratch. If I set the internal drive as the capture scratch it captures without any issues.
    The problem is that using the internal as the capture scratch can only be a short term solution. The drive is only so large and I have a problem with finder if I try to move files from the internal drive to the external. Finder freezes up and I can't even force quit properly. So being able to once again use the external as the main capture scratch is the only real solution. The external is fully functionally and communicating with the Mac.
    Any help with resolving this would be appreciated!

    Off the top of my head, because I haven't worked with SCSI in years--
    "The problem is that using the internal as the capture scratch can only be a short term solution. The drive is only so large and I have a problem with finder if I try to move files from the internal drive to the external. Finder freezes up and I can't even force quit properly. So being able to once again use the external as the main capture scratch is the only real solution. The external is fully functionally and communicating with the Mac."
    Are you trying to move files while you have FCP open? The fact that simply moving files is giving you finder issues and freezing you up, says that all is not well with the scsi raid. You should not see that at all.
    You might try powering down the mac and the raid, unplugging and letting the machine sit for a while to discharge the capacitors. Then try reseating the scsi card. (pull it out carefully and plug it back in.)
    On another note, when you upgraded fcp, did you do a clean install?

  • 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

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

  • Moving files to external drive - need Mac and PC compatibility in future

    Hello -
    I'm moving a client's video files to an external drive so they have the original files. I'm moving both the DV files (always usable with program that accepts DV files) and the Mac project files in a separate folder (in case they ever work on them in a mac - includes all the referenced files). I know they won't be able to open the latter on a PC but I'd still like to include.
    BUT, can they get any external drive? If I plug it into my computer and move files, are they going to run into problems if they use then on a PC? Thinking about getting this one for them (they are paying but want a good price for them):
    http://www.buy.com/prod/western-digital-500gb-my-book-essential-usb-2-0-external -hard-drive/q/loc/101/206409667.html
    Thanks for your help -
    Alexa

    Don't have a solution for you, but I did encounter a very similar bug.
    I was moving files from one iMac's external drive to another's internal drive, using a drag'n'drop move command on a directory. The move generated an error message, maybe the same as what you saw (I'm not sure), then aborted the move. Only one small file had been moved, and the source directory was gone! Not in the trash. Mac OS X 10.4.8 on both systems, an iMac DV and an iMac 24. The external drive was formatted as "Mac OS Extended (Journaled)."
    This sure seems to be a basic programming mistake. So, for me, it's back to doing 3 steps: copy, verify, delete. It's lousy not to be able to rely on proper execution of a basic command, but I've never won an argument with a computer.

  • How to move referenced photos to external hard drive and maintain "faces"

    I created an iphoto library on an external hard drive.  I chose not to copy imported photos to iphoto (reference instead) under iphoto preferences.   I dragged a large folder of photos from my internal hard drive to iphoto and spent countless hours adding faces to all the photos.  I now decide i want these pictures referenced from the external drive too, not the internal.   I moved the file of folders to my external drive and of course iphoto now cant find these referenced pictures.   I do "find photo" and point to where i moved these photos on the external drive and all works, until i close iphoto and restart it.  (in other words, iphoto doesnt remember the new location i pointed to)
    Is there a way to move the referenced photos to the external drive and still have iphoto faces work correctly?
    thanks

    This is just one of the many reasons that a referenced library is not recommended with iPhoto
    it has been reported that File Buddy - http://www.skytag.com/ - can help resolve the broken aliases - I have not used - as always backup before messing with your iPhoto library
    LN

  • Finder freezes when trying to move files to external hard drive

    Whenever I try to move files from internal hard drive to my external finder freezes it. I have over 5 TBs of free space on my external, so I know it's not a space issue. This happens no matter the size of the file. It starts the copy and then will freeze before it finishes. If I try to force quit and select relaunch it acts like it is relaunching but my icons never re-appear and the command bar at the top never returns. So I end up having to hard boot.
    I just reinstalled the 10.5.8 combo update and verified both hard disks, if any repairs came up I repaired and then did the same with disk permissions....it's still freezing on me. I am frustrated because there are some files I'd really like to move to my external raid hard drive but I'm not able to.
    The freezing happens if I'm trying to transfer files from a disc or an additional external HD. My internal HD is only so big and the external Raid drive is for my capture scratch on Final Cut Pro and I'm even having issues capturing to that drive. Everything wants to be on my internal HD and that doesn't work for me.
    Any help would be greatly appreciated.

    Sean Dale1 wrote:
    Do you get any error messages and if so what are they? Do you have any problems copying files off the problem drive back to your Mac or do the freezes only occur when copying to the external?
    No I don't get any error messages, the finder just freezes and when I try to relaunch finder it doesn't relaunch properly..all icons are missing and I'm not able to access the the task bar to properly shut down so I have to hard boot.
    It happens only when trying to save files to the external, whether through drag and drop or within programs. I am able to access files on the external and copy files from there to my internal without problems.
    Have you tried attaching this drive to another Mac and if so do you get the same issues?
    I don't have another Mac to attach the drive to.
    How is this RAID attached, SCSI, FireWire, SATA or what? How was the RAID created, Disk Utility or third party software and have you verified the integrity of the RAID?
    The RAID is attached via SCSI. In an attempt to solve this finder issue I re-installed the drivers to the most current drivers available and in doing so updated any firmware....and there was no change. I was not the one who set up the RAID so I don't know how it was created. It's an Enhance UltraStore R16 and I've been using it without issues since January 2007 and this freezing thing has been intermittent for a few months now but now it's constant and annoying. I've verified the disk through disk utility but I don't have any software to check the integrity otherwise. Do you have any recommendations as to what software I could use to do this?
    Message was edited by: Emily80

Maybe you are looking for