Aperture hangs upon Relocating Masters

I'm trying to relocate my masters to an external drive.
First time I tried it it started working then hung on one photo (untitled-1, or something generic like that).
I Force quit Aperature then thought it was because Iphoto was open, so I closed it.
I tried it again (relocate masters) and the progress bar doesn't even stop and it says Aperture is not responding.
So, what do I do now? Does Relocating Masters MOVE them, deleting them from their original location? If you do it twice will it just try to move what it hasn't already?
I have a time machine backup from yesterday, but would like advice on how to proceed now. ugh!

When you imported your images from iPhoto how did you do it? Try to be as exact as possible.
If you used the *File->Import->iPhoto Library* there were 3 choices:
# Leave masters in iPhoto library
# put masters into Aperture library
# put masters somewhere else on your HD
Cases 1 & 3 would make referenced masters, case 2 would make the masters managed. In cases 2 & 3 the files are copied out of the iPhoto library. In case 1 the masters stayed in the iPhoto library.
Assuming that after you did the import you didn't do anything like delete the iPhoto library then the iPhoto library should be as it was before you did the import into Aperture.
You could create a new empty Aperture library and do the import from iPhoto again starting from scratch with the added bonus of your increased knowledge of the whole process. When I first got Aperture I imported by iPhoto library numerous times trying out different scenarios each time until I got it the way I wanted it.
If you have any other questions post back, good luck.

Similar Messages

Aperture hangs upon quitting

It doesn't happen all of the time, but often enough to make me want to post an inquiry here. I can't pinpoint a reason, but upon quitting, Aperture starts to go through its saving and updating preview process, but never completes it. The progress bar makes it a portion of the way and everything appears to be running still, but it never finishes. I've even let the process run over night, but in the moring it is still in the same spot. I have to manually force the application to quit. It tells me that all of my edits will be lost, but upon opening the application the next time, that doesn't seem to be the case. Still, having to force quit is a bit unnerving, especially when I have to do it consistently. Is there any data on this problem? What could be causing this?

Speaking of a working backup, I do have all of my images stored and kept as referenced images. I also have the masters backed up in multiple locations. I also have a vault of my library stored on an external disk and I have that vault backed up in multiple locations. I am assuming that should an issue occur, I could just use the vault to get my library back? I've always been a little confused as to how the vault works. Let's say I completely lost my Aperture Library. Could I just open the vault to restore the library to full working condition? My confusion lies in the fact that I have a referenced library, so I am assuming that the vault only stores information about the masters, and not the masters themselves. If I were to lose my library or something were to happen, would I have to first load all of my masters again and then open the vault? Would I load the masters, reference them and then open the vault, or would I just open the vault and it would take care of everything?
Thanks

Aperture 3 and Relocated Masters

Hi all,
I'm using Aperture 3 and I store my master files on NAS (external network drive)
When I try to delete all masters and versions from Trash, I'm having:
• You don’t have access to the System Trash on the master files’ volume.
This is very annoying. I have full RW access on my NAS, why Aperture can't delete it?
I've seen workarounds with Consolidating Masters (but I don't want to move big amounts of photos all the time when I want to delete masters - it is very slow through wi-fi)
Also I've seen AppleScript implementation - but not for me also - you have to delete masters with script, and then not forget to delete versions and previews with Aperture tools.
Maybe there are other advices?

If both libraries somehow pointed to the same masters, and you deleted the masters via one library, it's possible the masters are gone and the references the second library has now point to a file which no longer exists.
I can't say how you got in the state you did, but until you reconcile things, I wouldn't recommend you go around deleting things that you don't want to lose.

Can't get hold of my relocated masters on an external drive?

All of a sudden I am not any longer able to get in touch with my relocated masters (on an external drive). I can SEE them, but is not allowed to "consolidate" them or use them for f. inst. EXPORT to 3rd part (Smugmug etc). The drive as such is mechanically ok, well functioning, and in Finder I can see all of the files (masters)...which in Aperture are having a "RED" dot in the small logo in the corner of the photo, indicating that they are held on an external drive...Would be most thankful for any help/advide about how to solve this problem, thanks.

Thanks a lot Frank for your willingness to help. YES, you are right (just did not the right expression: BADGE for offline referenced original" I have quite a few of such files, in order to economize with the space on my system HD (Macbook Pro), and I'll have to continue that way in the light of my recent investment - a NIKON D800, the files of which, as you will know, are huge.
The whole problem started when I had to find a new hosting place in the light of Apples closing down of "Me.com". When I closed my account with Apple with a view of leaving Me.com and start moving the majority of my photos to Smugmug, for unknown reasons I ended up with 2 (TWO) databases within Aperture - most recent version. And a big number of my MASTER photos held on an external drive all of a sudden proved to be unreachable, however, I could/can SEE them (with the badge in question) when in Aperture AND also in Finder - but can't CONSOLIDATE them/get them back to the appropriate PROJETS within Aperture.
Meanwhile I have tried to bring things back to normal by merging the two databases, and or by a "REPAIR" database - all steps so far in vain.
Thus, I am nowin Aperture left with two databases with a lot of referenced files scattered all over and outside the proper projects to which they belong. AND the MASTERS of the said files, or most of them, remaining on the external drive, where I can't get hold of them....
Having tried your proposed step - in vain - I realize that it is a stupid situation, and fully understand if you have no more proposals to me....

Aperture Hanging in Books

I upgraded to Leopard a few weeks ago and was using Time Machine and included Aperture backups while Aperture was running. I've since read that there's a problem with this, so I stopped Time Machine backups of my Aperture Library.
But now, every time I try to edit text on a page of a book, Aperture hangs. If I type 25 characters, for example, it will lag behind... showing one character every 5 MINUTES or so until it catches up with my typing... which would take about two hours for the 25 characters. I have to force quit. I've tried restarting and repairing permissions. No help.
Do I have a corrupt library? If so, what do I do? I have 3 vaults, all created in the last day or two.

Delete Aperture, open App Store > Purchases and download Aperture. This should fix your issue

Both iPhoto and Aperture hanging up immediately on launch

Both iPhoto and Aperture hanging up immediately on launch..
Please help in resolving the issues

Report generated by Etrecheck:
EtreCheck version: 1.9.12 (48)
Report generated 24 July 2014 8:31:31 am IST
Hardware Information:
MacBook Pro (15-inch, Early 2011) (Verified)
MacBook Pro - model: MacBookPro8,2
1 2.2 GHz Intel Core i7 CPU: 4 cores
4 GB RAM
Video Information:
Intel HD Graphics 3000 - VRAM: 384 MB
Color LCD 1440 x 900
AMD Radeon HD 6750M - VRAM: 1024 MB
System Software:
OS X 10.9.4 (13E28) - Uptime: 0 days 0:14:47
Disk Information:
TOSHIBA MK7559GSXF disk0 : (750.16 GB)
EFI (disk0s1) <not mounted>: 209.7 MB
Macintosh HD (disk0s2) / [Startup]: 749.3 GB (427.2 GB free)
Recovery HD (disk0s3) <not mounted>: 650 MB
MATSHITADVD-R   UJ-8A8
USB Information:
Apple Inc. FaceTime HD Camera (Built-in)
Apple Inc. BRCM2070 Hub
Apple Inc. Bluetooth USB Host Controller
Apple Inc. Apple Internal Keyboard / Trackpad
Apple Computer, Inc. IR Receiver
Thunderbolt Information:
Apple Inc. thunderbolt_bus
Gatekeeper:
Mac App Store and identified developers
Kernel Extensions:
[not loaded] com.ZTE.driver.ModemDriverMac (1.0.2d1) Support
[not loaded] com.ZTE.driver.ZTEUSBCDCACMData (1.3.33) Support
[not loaded] com.ZTE.driver.ZTEUSBMassStorageFilter (1.3.33) Support
[not loaded] com.lct.driver.LJACDDriver (1.0.0d1) Support
[not loaded] com.lja.driver.LJACDDriver64 (1.0.1) Support
[not loaded] lja.driver.USBModemCDC (1.0.0) Support
[not loaded] lja.driver.USBModemCDC64 (4.0.2) Support
[not loaded] lja.driver.USBModemData (1.0.0) Support
[not loaded] lja.driver.USBModemData64 (4.0.2) Support
Startup Items:
HWNetMgr: Path: /Library/StartupItems/HWNetMgr
HWPortDetect: Path: /Library/StartupItems/HWPortDetect
Launch Daemons:
[loaded] com.adobe.fpsaud.plist Support
[loaded] com.google.keystone.daemon.plist Support
[loaded] com.microsoft.office.licensing.helper.plist Support
[loaded] com.oracle.java.Helper-Tool.plist Support
[not loaded] com.teamviewer.teamviewer_service.plist Support
[running] PPPMonitord.plist Support
Launch Agents:
[loaded] com.google.keystone.agent.plist Support
[running] com.lja.startupAgent.plist Support
[loaded] com.oracle.java.Java-Updater.plist Support
[not loaded] com.teamviewer.teamviewer.plist Support
[not loaded] com.teamviewer.teamviewer_desktop.plist Support
[running] Swapper.plist Support
User Launch Agents:
[loaded] com.adobe.ARM.[...].plist Support
[loaded] com.facebook.videochat.[redacted].plist Support
[loaded] com.fastestyoutubedownloader.TrialExpired.GoldFreeFirstWeek.plist Support
[loaded] de.metaquark.appfresh.plist Support
User Login Items:
PopClip
LockScreen2
Dropbox
Degrees
Internet Plug-ins:
JavaAppletPlugin: Version: Java 7 Update 60 Check version
FlashPlayer-10.6: Version: 14.0.0.145 - SDK 10.6 Support
EPPEX Plugin: Version: 10.0 Support
AdobePDFViewerNPAPI: Version: 10.1.10 Support
AdobePDFViewer: Version: 10.1.10 Support
Flash Player: Version: 14.0.0.145 - SDK 10.6 Support
Default Browser: Version: 537 - SDK 10.9
QuickTime Plugin: Version: 7.7.3
RealPlayer Plugin: Version: (null) Support
SharePointBrowserPlugin: Version: 14.0.0 Support
iPhotoPhotocast: Version: 7.0 - SDK 10.8
Safari Extensions:
Turn Off the Lights: Version: 3.0.0.12
Awesome Screenshot: Version: 1.4.3
AdBlock: Version: 2.7.7
Audio Plug-ins:
BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9
AirPlay: Version: 2.0 - SDK 10.9
AppleAVBAudio: Version: 203.2 - SDK 10.9
iSightAudio: Version: 7.7.3 - SDK 10.9
iTunes Plug-ins:
Quartz Composer Visualizer: Version: 1.4 - SDK 10.9
3rd Party Preference Panes:
Flash Player Support
Java Support
Time Machine:
Skip System Files: NO
Mobile backups: OFF
Auto backup: NO - Auto backup turned off
Volumes being backed up:
Macintosh HD: Disk size: 697.84 GB Disk used: 299.98 GB
Destinations:
Time Machine Backups [Local] (Last used)
Total size: 931.19 GB
Total number of backups: 2
Oldest backup: 2011-08-25 14:26:36 +0000
Last backup: 2013-10-23 11:24:28 +0000
Size of backup disk: Adequate
Backup size 931.19 GB > (Disk used 299.98 GB X 3)
Time Machine details may not be accurate.
All volumes being backed up may not be listed.
Top Processes by CPU:
      7% WindowServer
      3% Safari
      1% hidd
      1% fontd
      1% com.apple.WebKit.Networking
Top Processes by Memory:
156 MB com.apple.IconServicesAgent
90 MB mds_stores
78 MB Safari
70 MB Dropbox
66 MB Finder
Virtual Memory Information:
911 MB Free RAM
1.49 GB Active RAM
616 MB Inactive RAM
1.01 GB Wired RAM
342 MB Page-ins
0 B Page-outs

LR4 Hanging Upon Startup in Win7 - Application Un-useable

I recently upgraded LR3.6 to LR4 64 bit, and the program is no longer useable. CPU is current generation Win 7 64-bit, powerful efficient machine with 6 gb of memory. Longtime user of LR and never had any problem with previous versions. Have tried uninstalling and reinstalling LR4 - same hanging or freezing result while opening. Have to close the program using Task Manager. LR-3.6, which has always worked well, is now also hanging upon launch. I am now considering downloading the most current LR4.1 RC (Release Candidate) to see if that will correct the problem, but Adobe release notes make no mention of bugs or fixes. Adobe is not helping - no acknowledgement of any problems. Any thoughts from folks would be helpful.

Update: Tried loading LR4.1 RC. No change - program still freezing or hangs when I first open program.

Final Cut Pro X hangs upon opening due to large project. Way to access previous project Version?

I'm running FCPX on what I assume is close to the bare minimum... low end 2011 Mac Mini, upgraded to 8GB RAM. I was working on a project, not too long, but a lot of clips, and for one near the end I decided to "zoom out" to a sort of tile collage of a couple hundred clips (each 1080p24). Whoops. FCPX hung pretty much all night, and after a Force Quit, the app now hangs upon starting up again.
I tried Apple's suggestion for hiding events and projects that aren't being used at the moment, to try and lighten the load, but I guess the current project with that one short clip of those hundreds of simultaneous clips is, on it's own, still too much. FCPX still hangs upon opening, once the project shows up in the project tray. The rotating beach ball mocks me.
I noticed a backup file in the Project folder, but there's only one file and it's not dated old enough to not have the troublesome clip. I can't access Versions because I can't do anything upon opening FCPX except Force Quit. Is there another way I can access a previous Version in order to not resort to starting the whole project over from scratch?

There is only one backup file - I think it gets over-written every fifteen minutes so unless you have some other backup, you'll have to resort to inginuity.
Try moving the Media to a temporary folder - that way the Project will open with disconnected clips. You can then re-link them a few at a time - leaving out the ones which you believe are causing the problem.
Then duplicate the project and in the new project, concentrate on the complex clip - ditch all the rest and work on getting that clip back up. Then you could export that clip as one movie file and import it back into the project.
Always keep regular duplicate projects - they are your backup - or, do as I do, and clone your working external HD to another of the same size and speed.
Andy

Aperture hangs on import from iPhone or camera

Since a few weeks I can't import from my iPhone or digital camera anymore.
If I try to import Photos from my iPhone or camera Aperture hangs forever. The Photos should be imported as referenced ones to a folder on a network share on a Mac OS X Server. This works fine, if the Picture source is i.e. a memory card or a HDD. And it has been working with the iPohne and camera before.
What happens is, that Aperture creates a file like "..importing.IMG0815.JPG" with 0 Bytes in the target folder. And than it hangs.
From this point on there is a permanent network traffic, and reasonable CPU load on both Macs (the kernel_task on the client and the AppleFileServer task on the Server). If I delete the "..importing.IMG0815.JPG" file it is instantly recreated. This continues even if I kill the Aperture application. The only way to stop this is to unmount the Network Volume.
Does anyone has an idea what this may cause?

sizzling badger wrote:
Aperture, Lightroom etc. are all designed to make use of direct import. They are safer than copying your files via the OS tools for the simple reason they access the cards read-only. If you use OS tools to copy then you are accessing the cards read-write which is far more dangerous if something goes wrong.
Culling your images during import saves time and disk space also. Copying your images directly and then importing is a WASTE OF YOUR TIME.
We disagree. Although such apps are indeed "designed" for direct import, my empirical observations since the earliest days of digital imagery have been that interacting indirectly using an app like Aperture is much, much less stable than directly interacting via Finder when properly done. One can peruse literally hundreds of digital image threads including this one to see overwhelming real-world evidence of what I am talking about.

Aperture not seeing referenced masters on Samba share

Hello all,
I have moved my referenced masters from my laptop to a Samba-mounted RAID server. I go to mount the Samba share and for some reason, Aperture won't see my referenced masters. It also shows the volume as being offline, when I know for a fact it is mounted, and can browse the Aperture masters directory to find each and every master...
Is there any way to get aperture to see these masters?
Thanks,
-Noah

OK, this is a long shot, but it happened to me once.
I tried to relocate some managed images to an AFP share which I thought was mounted but wasn't. Because the path that I wanted to relocate to was already loaded I just clicked OK and this is what happened - Aperture created a Folder in /Volumes/ with the name of the AFP volume. So later when I did mount the volume none of my referenced files showed up. This is because while the name on the desktop was correct the Path to it was /Volumes/AFP-share 1/ instead of /Volumes/AFP-share/.
So in short look in /Volumes/ (you can get there by using the Go-->Go to Folder menu in the Finder and typing /Volumes/) and see if there is a folder in there that should not be:-) If there is check to see if there are any images in it and move those to your desktop before deleting the folder.

Aperture hangs creating previews

Since installing Leopard (a clean install then Migration Assistant to get my user across) I haven't been able to view slideshows, because Aperture hangs when it tries to create previews. The "Rendering previews for slideshow..." popup appears and it never moves. Clicking "Cancel" has no effect - I have to quit Aperture from the Dock.
As soon as I try to render the previews (and before I quit Aperture) the following message appears in the System log (/var/log/system.log):
Nov 26 09:34:34 mbp17 Aperture[552]: * -[NSLock unlock]: lock (<NSLock: 0x22f174e0> '(null)') unlocked from thread which did not lock it
Nov 26 09:34:34 mbp17 Aperture[552]: * Break on _NSLockError() to debug.
And on at least one occasion the following as well:
Nov 26 09:35:36 mbp17 Aperture[552]: * -[NSLock dealloc]: lock (<NSLock: 0x22f174e0> '(null)') deallocated while still in use
Nov 26 09:35:36 mbp17 Aperture[552]: * Break on _NSLockError() to debug.
I've tried all the obvious things, including removing preferences (plus removing all preferences, not just Aperture preferences), starting with a new Aperture library, reinstalling Aperture, and the only thing that worked was creating a new user that did nothing except Aperture. So it's some combination of Aperture, Leopard, and my user account.
Apple support was no help at all. They suggested it was probably a user preference somewhere and told me to recreate my user from scratch. That's a huge job, so I resisted it for a long time. But eventually I decided to bite the bullet and did so. It took many hours to complete the task. I tried it again immediately after recreating the user and it worked, but when I got everything else back working again such as Mail, calendar etc, I found it was failing again. This was not migrating the user, either, it was reinstalling everything and recreating preferences (with few exceptions - I copied over ~/Library/Mail, for example).
This is extremely annoying! Anyone else seen anything similar?
Allan

anpacker wrote:
...I haven't been able to view slideshows, because Aperture hangs when it tries to create previews. The "Rendering previews for slideshow..." popup appears and it never moves. Clicking "Cancel" has no effect - I have to quit Aperture from the Dock...
hi, allen
have you repaired permissions in safe mode and then restart osx and aperture?
http://www.victorfoto.com/etutorialsvf/eosx_vf/e_osx_t_rdp_vf/e_osx_trdpvf.html
victor

Aperture hangs on imports and other stability issues

My aperture will hang on imports, does not like me to do anything else at all when importing, lest it hang and if it hangs once and I force quit I have to restart the system to make it work again. I have had 5 crashes today and really PO'd. This is 1.5.6 and I am running 10.5.5.

Have you done anything to the files before importing them? In particular I'm thinking about giving them keywords through Bridge or LightRoom?
I have experienced Aperture hanging until force quit if I had done keywording to the (in my case) DNG's via Bridge / LightRoom prior to importing them into Aperture.
Regards
Paul K

Firefox hangs upon startup

When I try to start firefox it does nothing. Via CLI it does the same - nothing. It just sits there and appears to be hung up. No pid, nada.
Deleted ~/.mozilla and tried to run firefox -profilemanager. Same thing, just hangs.
Tried to run firefox -v just to see if it return the version -no joy. Hangs.
no locks present and did a killall firefox before each attempt.
Uninstalled via yum and reinstalled via yum. Same.
Is there a log file I can view to try to determine whats hanging upon startup?
Thanks in advance for your help.

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
<b> To Enable SafeMode </b>
*You can open Firefox 4.0+ in Safe Mode by holding the '''Shift''' key when you open the Firefox desktop or Start menu shortcut.
* Or open the Help menu and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
*''Once you get the pop-up, just select "'Start in Safe Mode"''
If it works in Safe Mode and in normal mode with all extensions (Tools > Add-ons > Extensions) disabled then try to find which extension is causing it by enabling one extension at a time until the problem reappears.
Close and restart Firefox after each change via "Firefox > Exit" (Windows: Firefox/File > Exit; Mac: "Firefox > Quit Firefox"; Linux: "Firefox/File > Quit")
*https://support.mozilla.org/kb/Safe+Mode
*https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes

HELP! Aperture corrupting my library when relocating masters

I keep my aperture library on my system disk, and I use referenced masters on a NAS. Everything seems to have been working fine until now. I had a rather large project that I was cleaning up, wanting to delete my no longer needed masters (about 2200 out of 3500 files). Unfortunately, I forgot to check the box to delete referenced masters - I didn't even realize it was there until I went searching when it didn't delete them. Anyway, what I thought I would do is simply relocate the masters from by project to a new project, then I could delete the masters left behind.
What happened was that Aperture started moving masters from other projects into the new project - Files that were not selected in Aperture when I executed the relocate masters command. Now these other projects have lots of images with "unsupported image format", I'm assuming for the masters that got moved into this new project. What happened?

I've attempted to fix this by restoring the JPEG files that I had originally "removed". This did not seem to resolve the problem as when exporting the masters I still find many, many files from other projects being exported as part of this project.
Granted, I brought this problem on myself by deleting the JPEGs, however this seems like a pretty serious defect in Aperture. I could understand if after deleting a JPEG Aperture could not locate the JPEG master and displayed some sort of indicator of such. However there is no indication that anything is wrong, it's just picking up random files in place of the JPEGs, and in those other projects, the images are "unsupported file format" with the filename showing some sort of metadata in an iPhoto library on the same disk.
I have a vault that probably has the database from these other projects intact. Is there a way to restore that information? (remember that all the masters are relocated).
Thanks in advance for any advice you can offer to help fix this.
- Howie

Relocating Masters

I want to relocate my masters to a library location outside of Aperture.
Does it move your masters as well as all versions of the masters?
Once all are moved do I have to rebuild the Aperture library system to actually remove them from Aperture?
Thanks

You import image-format files. Importing means "make a record of this file". That record includes information about where to find that file. Once imported, that file is known as a Master (or, since Ap3.3, an Original). That file can be anywhere on your system. By default, Aperture stores Masters inside the Library. The Library is a large collection of files, called a package. It appears to you as one file in the Finder. (In Finder, you can "{right-click}➞Show Package Contents" to see all the files in a Finder package. Don't move or alter any of them.) You can, at import or any other time, move any or all of your Masters to any location on your system that you want, including into and out of your Library.
Your Masters are never altered. You can access them at any time from within Aperture: press "m" to see a representation of them, use "File➞Export Master" to create a copy of the Master (remember, it's a file) that you can use in any other program.
In Aperture you see representations of your photos. These are called Images. Each record in your Library has an Image. The Image is built, on the fly, from the Master and a text file of instructions telling Aperture what adjustments and metadata changes you have made to the Master. This text file is called a Version. Since every record has an Image and a Version (the initial Version exists, but contains no instructions), "Image" and "Version" are used interchangeably. (NB: I didn't name these parts of the interface.)
The Version is always kept in the Library.
Moving ("Relocating") your Masters does only that. It does not move any Versions.
There are no commands in Aperture that require you to rebuild your Library afterward, or to follow up with any manually-applied maintenance.
HTH.
Message was edited by: Kirby Krieger -- formatting, typos, minor re-wording.

Aperture hangs upon Relocating Masters

Similar Messages

Maybe you are looking for