Aperture 3 Referenced Masters on a Network Drive

I purchased a Synology Disk Station as my network attached storage solution. I was hoping to have my iTunes media and my Aperture referenced masters on the RAID-enabled network drives. I have had nothing but trouble with iTunes referencing media (extremely slow) so I gave up. Now I am attempting to relocate the Aperture masters to the network drive. According to this article, http://support.apple.com/kb/TS3252 I should definitely not be moving my images to the network drive, as the drive must be formatted as Mac OS Extended, but the Synology Disk Station volumes must be formatted as FAT32. Meanwhile, I did try to relocate some images. One problem I have is that if another user logs in to my iMac before me and mounts the network volume named Sally, when I log in and mount the network volume, the volume name is not the same, it is Sally-1, and Aperture cannot find the referenced masters! I imagine this would happen with any network drive when multiple users are logged into the Imac.
It seems like I have a gigantic network brick that I may be able to use as a glorified Time Machine backup drive, or is there something I can do about this? How does one have networked Mac OS drives? Connecting a drive to an Airport Extreme the only way?

Re iPhoto on a NAS:
Still trying to solve this.
iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos. Simply a NAS is not a suitable home for an iPhoto Library.
Workaround: Make a dmg formatted Mac OS Extended (Journaled) and put the Library on that and store it on the NAS.
I think I have to mirror the iTunes solution above,
This involves having iPhoto reference the files on the NAS with the Library on your internal HD or some other volume. I strongly suggest that you don't do that. Unlike Aperture, iPhoto has no tools to reconnect with lost masters (Originals in iPhoto) so should anything go wrong you'll find yourself re-connecting each individual photo in the Library with its Original +one by one+.
but figure out which folders to move
You would need to recreate your Library as a Referenced Library.
Regards
TD

Similar Messages

  • Referenced masters or library on external drive?

    My Aperture library with managed masters has outgrown my macbook pro. Is it better to switch to referenced masters on an external drive or move the whole library to an external drive and continue with managed files?
    thoughts on this, please...

    Matthew Bergsma wrote:
    Keeping your library on one drive and your masters on another has noticeable speed benefits.
    I totally agree with that.
    I store my files on a ReadyNas Duo that mirrors the images using two hard drives. Gives you some protection when a hard drive dies.

  • Deleting masters from network drive

    I have my masters on a network drive for backup purposes, but when I try to delete them (CMD+backspace), although the references to them get deleted from the project, the originals are still there on the network. This isn't a permissions problem, because I can delete them through the Finder.
    How can I get Aperture to actually delete masters on a network drive? Or is this an impossible dream?

    I have my masters on a network drive for backup
    purposes, but when I try to delete them
    (CMD+backspace), although the references to them get
    deleted from the project, the originals are still
    there on the network. This isn't a permissions
    problem, because I can delete them through the
    Finder.
    How can I get Aperture to actually delete masters on
    a network drive? Or is this an impossible dream?
    I am thinking this is the way you have it set up:
    1) Masters go on Network drive
    2) You import masters
    3) You work with masters in Aperture
    If so, the reason Aperture is not removing the masters on the network drive is that on import it copies the masters into the lirbary and then does not know about them after that. So from that sense your dream is impossible, because Aperture will not touch the masters outside of the Aperture library.

  • Network drive

    I've been a long time user of iPhoto on a network drive, and it seems to work fine. I have about a 60GB library.
    I thought recently I'd upgrade to aperture, since it seems to be an improved version of iPhoto.
    The first problem I encountered is that the import from iPhoto option seems to hang when using a network drive. So I got around this by importing the library on a local drive.
    But then I tried to open this Aperture library over the network drive, and it just sits there on a dialog box for 24 hours.
    Is anyone using a big Aperture library on a network drive? Is this worth persisting with?

    The Library should be on an internal drive maintained less than 70% full. You can, however, reference Masters on a network drive using a (strongly recommended) Referenced-Masters Library located on an internal drive. The Referenced-Masters approach will allow the Library to remain a civilized size for your MBP, Vault backups, etc. Back up Masters separately prior to import into Aperture.
    -Allen Wicks

  • Vault + Time Machine w/ Referenced Masters

    I know this general question has been asked several times, but I can't find a solution that matches my specific setup. I'm running Aperture off my MBP, so I have set up one external drive to hold my referenced masters. My internal drive has my aperture library with previews, etc. I also have one other external drive that is my dedicated Time Machine backup drive. How should I approach backing up? If I have Time Machine backup the aperture library and referenced masters, is there any advantage of adding a vault as well? Thanks for any help!

    Gerry,
    This ain't hard, just a bit complex.
    To answer you first question: At this point, a Vault is of little value; Time Machine does everything you need and does it automagically. (Unless you leave Aperture running all of the time.) Time Machine is much better if you use referenced masters as the Vault does not back them up.
    Time Machine is great as it creates images of your disk every hour - wonderful if you delete something by accident. People worry about filling their Time Machine disk. Don't. As long as your disk is large enough for one full back up the extra space only gets you time - that is you can go further back. For most of us, one month is all the history we will ever need. And when your disk fills, Time Machine diligently deletes the oldest data to assure that you always have a current backup. Nice.
    A clone, on the other hand, is just that, an exact (usually bootable) copy of your disk. Normally, when you update a clone it adds what you have added but it also deletes what you have deleted. Delete something by mistake two days ago and last night's backup will delete it as well. On the other hand, have your Mac die (as mine did, 3,000 miles from the nearest Apple Store) and you can plug your clone into any other Mac and you are good to go. Slick.
    Finally, off site is just that. What happens if your house burns or is robbed? You could lose your mac and all of your backups as well. There are many ways to do off site, from a hard disk that you sneaker net to your neighbor to a commercial service like Crashplan or Carbonite.
    Hope this helps.

  • The Best Method To Backup Referenced Masters?

    I cannot find in Aperture help any mention of backing up the referenced masters which seems odd that Apple would consider backing up managed photos on the internal Aperture Library while not considering the very common (and supported by Apple) method of working with referenced masters on external hard drives.
    This is what I am doing: I am using super duper to clone the HDD with the referenced masters to another external drive. If the HDD with the referenced masters dies I just hope that I can somehow reconnect the masters on the other HDD.
    Is there a better way to back up those referenced masters? Perhaps a method I am not aware of from within Aperture to make it easy to use or reconnect the back up images?
    Aperture 3, MacBook Pro running Snow Leopard

    It makes me wonder. Since Aperture places the backups and therefore "knows" the location, does it in the event of losing the originals, have a dialog box or other means for "finding" and reconnecting to the file backups?
    afaik, no. Kirby, do you know differently?
    But there is of cause the "File > locate referenced files" window, that will allow you to reconnect the versions with their masters. But you will have to point Aperture to the location of the masters.
    I am a fanatic with keeping at least two but preferrably 3 copies of everything in at least two different formats.
    and preferably in two different places, see Kirby Krieger's post - "offsite location".
    And if you are very concerned about the safety of your images, you will create the first backup of your masters directly from the card - before the images enter any image editing software.

  • How do i backup referenced masters on EHD

    Hello. If all my Masters are held in an EHD, how do I back them up? (They are all held offline as I ran out of space in Aperture Library) Vault doesn't back up Referenced masters.... do I connect one EHD to the Vault EHD and miss out Aperture? Sorry if this is a dumb question.

    You back up the referenced masters on the external drive as you would any other files. As referenced masters they are not in any way connected to Aperture with regards to backing them up.
    There are many ways to handle the situation. Time Machine, cloning the drive with the images onto another drive, etc. Again don't think of them as Aperture master files they are just files that need to be backed-up.

  • Moving aperture masters to external hard drive and changing to reference

    I am using my iMac's internal drive to store manage my aperture masters and versions. I'm now up to 200 GB and aperture at times is running very slow . I believe i have to move my masters to an external harddrive but i'm not sure how and then once I do how do I convert to using reference files? ? In this configuration will using the vault feature stop backing up my masters if they are separated?

    Thank you for your help. One question if I down load my masters directly to the external harddrive as you suggest and then import into Aperture as referenced files won't that mess up the hierarchy system that Aperture sets up. When I relocated all my masters to the external HD Aperture automatically set them up as specific folders corresponding to all of my projects in a well organized hierarchy if I haphazardly download first to the Hard drive and then import will this then be messed up? ie will I need to specifically organize how I do my original masters download to the Ext HD from my compact flash?

  • Aperture 3 Backing Up Referenced Masters

    I am trying to develop my workflow better.
    I shoot images into the field and download them to my laptop. I then transfer them back to my iMac when I get home. I use Aperture 3 for my pictures.
    In Aperture, I have all of my files referenced to a external drive. I want to back these photos up overnight using a Drobo or Synology NAS drive.
    Does anyone have any experience on which would be better?
    I could also implement a workflow in which the files will be referenced on the Drobo or NAS and then backed up overnight. I will be backing up the referenced just in case something were to happen to it.
    Anyone have opinions on this?

    Aperture 3 added a "Trash".
    The deleted versions go into the trash, and you have to empty the trash to truly delete them. At this point it will ask if you want to delete the referenced masters as well.
    As a pro, I'd rather not have a trash... But oh well, gotta appease the newbies.
    Message was edited by: Matthew Bergsma

  • Moving a lot of masters from an external drive to Aperture library

    I have just treated myself to an iMac, 3.06 GHz with 1 TB Hard drive. I have some 2,000 pictures that I have done a lot of work on already on an external Firewire drive. I have copied the Aperture library to the hard drive on the new iMac - but, they are referencing them from the external drive. I would like to import all the 45 project containing all the photos masters into my Aperture library so that I have them all together.
    What is the best way to do this? Do I have to do it with individual pictures - which will take forever! I cannot seem to get the option of Relocate Master. When I tried to import - from the external hard drive - I was not able to see any pictures to import. Was this because they were already in the library and I had checked 'Do not import duplicates"
    Do I need to make a new Aperture Library?
    Any advice would be most welcome!

    Hi William These are the two reports that seem to relate to Aperture. It is all "Gobbledygook" to me!
    May 24 12:13:19 MacBook-Pro Aperture[1001]: * NSRunLoop ignoring exception 'Exception in Aperture: [<BKiPhotoFolderItem 0x28841d90> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key itemiPhotoEventDisplayName.\nBacktrace:\n0x00071fea (in Aperture)\n0x91e8beb7: +[NSException exceptionWithName:reason:userInfo:] (in CoreFoundation)\n0x90c25510: -[NSObject(NSKeyValueCoding) setValue:forUndefinedKey:] (in Foundation)\n0x90b1b028: _NSSetUsingKeyValueSetter (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x26a5bfe6: -[BKiPhotoEventsFolder loadFolderSubfolders] (in iLife)\n0x26a5274d: -[BKiLifeFolderItem itemsFoldersOnly] (in iLife)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x010078ea (in BrowserKit)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x01003016 (in BrowserKit)\n0x0100341c (in BrowserKit)\n0x90b1c7a7: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x90b4a39a: -[NSObject(NSKeyValueCoding) valueForKeyPath:] (in Foundation)\n0x93992e48: -[NSBinder _valueForKeyPath:ofObject:mode:raisesForNotApplicableKeys:] (in AppKit)\n0x93992a50: -[NSBinder valueForBinding:resolveMarkersToPlaceholders:] (in AppKit)\n0x9399253c: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01003c94 (in BrowserKit)\n0x01002447 (in BrowserKit)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01013b9f (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x00ff2ee4 (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x00ff39a8 (in BrowserKit)\n0x90b2e02d: __NSFireDelayedPerform (in Foundation)\n0x91e12b5e: CFRunLoopRunSpecific (in CoreFoundation)\n0x91e12d18: CFRunLoopRunInMode (in CoreFoundation)\n0x969da6a0: RunCurrentEventLoopInMode (in HIToolbox)\n0x969da4b9: ReceiveNextEventCommon (in HIToolbox)\n0x969da32d: BlockUntilNextEventMatchingListInMode (in HIToolbox)\n0x937cd7d9: _DPSNextEvent (in AppKit)\n0x937cd08e: -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)\n0x00369f54 (in Aperture)\n0x937c60c5: -[NSApplication run] (in AppKit)\n0x00979e5a (in ProKit)\n0x00003252 (in Aperture)\n' that raised during posting of delayed perform with target 0x2694c080 and selector '_setOutputSourceProviders:'
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Con trast.monitorPanel/Contents/MacOS/Contrast and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Geo metry.monitorPanel/Contents/MacOS/Geometry and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/VPT .monitorPanel/Contents/MacOS/VPT and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Bez el.monitorPanel/Contents/MacOS/Bezel and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Ext endedTouchSwitch.monitorPanel/Contents/MacOS/ExtendedTouchSwitch and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Pow erMode.monitorPanel/Contents/MacOS/PowerMode and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization.
    May 24 12:13:38 MacBook-Pro [0x0-0x62062].com.apple.systempreferences[1012]: objc[1012]: Class O3Panel is implemented in both /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/Aut horization.monitorPanel/Contents/MacOS/Authorization and /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions. Using implementation from /System/Library/MonitorPanels/AppleDisplay.monitorPanels/Contents/Resources/TVO ptions.monitorPanel/Contents/MacOS/TVOptions.
    May 25 17:55:41 MacBook-Pro Aperture[1018]: * NSRunLoop ignoring exception 'Exception in Aperture: [<BKiPhotoFolderItem 0x2375da50> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key itemiPhotoEventDisplayName.\nBacktrace:\n0x00071fea (in Aperture)\n0x91e8beb7: +[NSException exceptionWithName:reason:userInfo:] (in CoreFoundation)\n0x90c25510: -[NSObject(NSKeyValueCoding) setValue:forUndefinedKey:] (in Foundation)\n0x90b1b028: _NSSetUsingKeyValueSetter (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x2c9a6fe6: -[BKiPhotoEventsFolder loadFolderSubfolders] (in iLife)\n0x2c99d74d: -[BKiLifeFolderItem itemsFoldersOnly] (in iLife)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x010078ea (in BrowserKit)\n0x90b1c81a: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x01003016 (in BrowserKit)\n0x0100341c (in BrowserKit)\n0x90b1c7a7: -[NSObject(NSKeyValueCoding) valueForKey:] (in Foundation)\n0x90b4a39a: -[NSObject(NSKeyValueCoding) valueForKeyPath:] (in Foundation)\n0x93992e48: -[NSBinder _valueForKeyPath:ofObject:mode:raisesForNotApplicableKeys:] (in AppKit)\n0x93992a50: -[NSBinder valueForBinding:resolveMarkersToPlaceholders:] (in AppKit)\n0x9399253c: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01003c94 (in BrowserKit)\n0x01002447 (in BrowserKit)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x01013b9f (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x90b1aa8e: -[NSObject(NSKeyValueCoding) setValue:forKey:] (in Foundation)\n0x9399276a: -[NSObjectParameterBinder _updateObject:observedController:observedKeyPath:context:] (in AppKit)\n0x939921bc: -[NSObjectParameterBinder _observeValueForKeyPath:ofObject:context:] (in AppKit)\n0x90b7958e: NSKVONotify (in Foundation)\n0x90af5f22: -[NSObject(NSKeyValueObserverNotification) didChangeValueForKey:] (in Foundation)\n0x00ff2ee4 (in BrowserKit)\n0x90b78914: _NSSetObjectValueAndNotify (in Foundation)\n0x00ff39a8 (in BrowserKit)\n0x90b2e02d: __NSFireDelayedPerform (in Foundation)\n0x91e12b5e: CFRunLoopRunSpecific (in CoreFoundation)\n0x91e12d18: CFRunLoopRunInMode (in CoreFoundation)\n0x969da6a0: RunCurrentEventLoopInMode (in HIToolbox)\n0x969da4b9: ReceiveNextEventCommon (in HIToolbox)\n0x969da32d: BlockUntilNextEventMatchingListInMode (in HIToolbox)\n0x937cd7d9: _DPSNextEvent (in AppKit)\n0x937cd08e: -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] (in AppKit)\n0x00369f54 (in Aperture)\n0x937c60c5: -[NSApplication run] (in AppKit)\n0x00979e5a (in ProKit)\n0x00003252 (in Aperture)\n' that raised during posting of delayed perform with target 0x2373bbd0 and selector '_setOutputSourceProviders:'
    May 25 17:55:09 MacBook-Pro [0x0-0x79079].com.apple.Aperture[1018]: CoreImage failed to create context: CGLCreateContext return: 10002

  • Aperture loose link with Referenced Masters

    I just upgraded to Aperture 2 and spent days organizing and creating an elaborate library of referenced files. The masters were placed on an external HD via FW 800. Things were working perfectly until I launched Aperture and there was no sign of my library. Aperture looked brand new with an empty library other than the sample images from the Installation Disc.
    If I go to Aperture Preferences it is correct is pointing to the attached external disc where I have my masters stored. Fortunately, when I look on my external HD the images are still there. The Aperture application just won't recognize the files on the external HD.
    This is very frustrating as I spent days creating this elaborate organization.
    Any thoughts would be greatly appreciated.

    midnightsun wrote:
    I just upgraded to Aperture 2 and spent days organizing and creating an elaborate library of referenced files. The masters were placed on an external HD via FW 800. Things were working perfectly until I launched Aperture and there was no sign of my library. Aperture looked brand new with an empty library other than the sample images from the Installation Disc.
    Really dumb question. Where is the actual Aperture Library located? Do you have more than one Aperture Libraries? In other words, Aperture Library on your internal and external drives.
    If so, just start Aperture by double clicking the external drive Aperture Library where you store the referenced master files. Or do what I do, is to have the Aperture Library on my internal drive and all of my image master files on an external drive.
    Hope this helps...

  • Using the same Referenced Masters across Multiple External Hard Drives?

    I have a large (2TB) desktop external hard drive that I am now using as the source of my referenced masters for Aperture.
    I would like to copy this reference library ("My Photo Library") to a small, mobile external hard drive to use "on-the-go". But, if possible, I'd like to continue using the desktop external when I'm at home.
    What's the best way to do this? Should I just copy "My Photo Library" from the desktop external drive to the mobile external and Relocate Masters? But then, how do I switch back to using the desktop drive when I'm home without having to Relocate Masters every time (my library is quite large: 17K+ photos of 8-21MB each). Is there a way to "trick" Aperture into thinking that both drives are the same drive???

    Computer:
    5" Mac Book Pro OSX (10.4.11) 2.2
    Drives:
    1x WD Studio Edition - 750 GB (Firewire 800)
    1x LaCie - 750GB (USB)
    Final Cut Express HD 3.5.1
    (My minimal memory allowance is set to 3000MB)
    (No external editors set)
    HDV-Apple Intermediate Codec 1080i50
    HDVFireWirePAL
    Quicktime - 7.5
    Camera - HVR-V1 connected with firewire
    MiniDV Tapes, Mix of Sony & Panasonic (DVM60) - i know this is not advised, but i was in kenya, so getting the right tapes was not easy!
    Is that everything? Is there any other information you need?
    I have been working with Final Cut express while it has been installed on my WD hard Drive.
    I have been capturing and editing my film through the WD hard drive very happily up until now, but now it is full with 10 of the tapes (and the application), and so I am now wanting to save the rest of my tapes on the LaCie.

  • Changed disks in my RAID, Aperture lost all referenced masters.

    I have a G-Speed eS RAID system. I had 4 X 1TB disks.
    I decided to change the hard disks to 2TB ones to double my storage capacity.
    I retained the same volume name. I backed up the 2.5TB of data to 3 other disks and then copied it back to my upgraded RAID.
    So I have a completely identical file structure. My photos were in /Volumes/GS/photo, and this is where they are now. However Aperture lost all connections to the 35000 referenced files.
    It seems that there is no way to tell Aperture that old /Volumes/GS and new /Volumes/GS is the same location from my point of view (is your point of view different?). This means I have to reconnect each one of the 100+ projects manually. I DO NOT LIKE THAT. Am I missing something, or is this a nasty oversight? Don't tell me that this is a "feature" and one can only move REFERENCED masters from within Aperture...
    Note: Repairing or rebuilding the library does not help.

    Your suggestion works, but
    1) You have to first select all photos in the "photos" smart album. If you do select them all, "Reconnect All" will not work.
    2) Most important, after reconnecting, I also told Aperture to rebuild my library. And it lost them again... The photos got connected to a <null> named drive which is shown as offline.
    We are talking about a big deficit of reliability here...
    I had a backup of my Aperture Library. So I reconnected the files again, without a Library rebuild this time.
    But what if I need to rebuild my library in the future?? I AM SCARED...
    No need to mention that I have lost all day moving around many gigabytes of data, reconnecting files, etc etc. This is hardly a productivity boost.
    The worst part is that I like a lot the Aperture UI and I hate the alternative.
    But Aperture is unfortunately unreliable.
    Just play enough time with the loupe on my MacPro and the application will crash.

  • Referenced Masters on network

    It appears that Aperture 3 broke support for storing Referenced Masters on an NFS share. My library is stored on the regular HFS+ drive used to boot the Mac, and in Aperture 2 I had no problems storing Referenced Masters on NFS. This allowed them to be automatically backed up when the file server did it's nightly backup.
    As anyone else seen this issue, and if so, any chance you have a solution? Without this being fixed Aperture 3 is completely useless to me.

    Re iPhoto on a NAS:
    Still trying to solve this.
    iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos. Simply a NAS is not a suitable home for an iPhoto Library.
    Workaround: Make a dmg formatted Mac OS Extended (Journaled) and put the Library on that and store it on the NAS.
    I think I have to mirror the iTunes solution above,
    This involves having iPhoto reference the files on the NAS with the Library on your internal HD or some other volume. I strongly suggest that you don't do that. Unlike Aperture, iPhoto has no tools to reconnect with lost masters (Originals in iPhoto) so should anything go wrong you'll find yourself re-connecting each individual photo in the Library with its Original +one by one+.
    but figure out which folders to move
    You would need to recreate your Library as a Referenced Library.
    Regards
    TD

  • In Aperture 3.4.1, I am not able to connect with referenced files on a network

    I am running OS X 10.8.2 and Aperture 3.4.1, and am unable to connect with referenced files on a network.  Specifically, the referenced files reside on my iMac and I am attempting to connect to them from my MBP.  They appear in red in the dialogue box.  While I know this has been a long standing issue in other versions, I was hoping it had been solved by now.  Any assistance will be appreciated.
    Thanks -
    Dudley

    http://support.apple.com/kb/HT5922
    If you want to mirror your desktop, see:
    http://support.apple.com/kb/HT5404
    Regards.

Maybe you are looking for

  • Unhandled exception in Word when building PDF output

    We have a RoboHelp 7 project that has worked fine for quite some time.  Now, after what seemed to be a minor edit, we are no longer able to generate PDF output because Word dies with an exception.  Other projects on the same system build just fine. T

  • Database --simple problem 2

    if i have this line String query = "UPDATE DVD SET Info='OUT' WHERE Code='" + DVD_Code.getText () + "'"; and the Code value in my database is set to AutoNumber,how do i get the statement on top without getting a data type mismatch error

  • Just bought a macbook air and my contacts from my iPad have not synced what can  do ?

    just bought a macbook air and my contacts from my ipad have not synced. what can i do ?

  • Anyone have succes configuring SNMP traps?

    anyone have succes testing SNMP with snmptrap command? Hello, I am new to Ironport and the setup configuration of these devices. I am in the process of testing the snmp feature of these servers. As such I have configured the SNMP via snmpconfig comma

  • Timeout for telnet

    Guys, I need to check if an application is running on hte servers. It's for close to 10,000 servers. The easiest way is to telnet to the application port and it responds with the version. That's easy, but some nasty servers do not timeout the telnet