Aperture crashes when files are imported

I am using the Aperture 3 trial currently, and while it starts up just fine, whenever I try to import my iPhoto library Aperture chugs along for a bit, and then crashes. When I open Aperture again, most of my events are there (as projects) but they are almost all empty. A select few appear to have photos in them. If I try to import again, the same crash happens. If I import folders as projects from my pictures folder, it crashes. If I delete the Aperture library and try to import again with a fresh start, it crashes. Right now I really don't know what to do about this, I want to try Aperture, but I can't very well do that without being able to get my photos into it.
Admittedly, my iPhoto library is rather large (40,000+ photos), but iPhoto can handle this, and I should think Aperture was built for this.
Thanks for the help!

I am having a very similar problem. I purchased the full version and get the exact same results. I rebuilt my library using iphoto's rebuild tools and the crash still occurs. I have rebuilt the library using iphoto library manager and the crash still occurs. I am frustrated that I spent 200 dollars and I am unable to import my iPhoto library. Any help would be great.

Similar Messages

Premiere Pro CS5 Crashes when graphics are imported

This doesn't happen with every graphic in the known universe. I have permission to get photos from certain sites (.gov, .mil) and those pictures are crashing CS5.
I've tried importing and dragging from the media browser. The crash occurs when the playhead hits the image, or I select the image to resize etc.
As a working process, I've been opening the images and re-saving them in photoshop CS5, which appears to be working. Here's an example of an image causing these types of crashes:
I'm not getting any error message. Windows just pops up a screen saying that the program has stopped working.
Any help will be much appreciated.
Thanks,
Marmaduke

JustinJrm125 wrote:
Harm,
For starters, I'm not going to take someone seriously who actually said that you can't use 16 GB of RAM with my processor. I mean, you actually said that.
And then there's this whole performance thing. Considering performance is not a quantifiable number…especially since you don't know my RAM selection, bus speed, RAM timings, voltages or motherboard model…and flat out ignore that I'm running quad channel memory in a quad channel configuration…well, you just don't make any sense. In fact, it just shows your ignorance on the whole topic.
There's no crippling…in fact the only thing that seems crippled is Adobe's software till they patch the issue. Furthermore, you're completely trolling this topic, never once having contributed to the original, or additional issues.
Now, I see that you're a regular on here (more than regular, it's actually closer to an obsession)..so I'll just assume you like having the last word. So here's some advice…if you don't know what you're talking about, don't answer. If someone's new, help them. Don't accuse them of being wrong out of the gate, and then don't steer the topic elsewhere so you can wave your e-phallus around about computer specs.
Better luck next time. Should take a page from the other commentors, they were polite and helpful. I'm done with you, as you offer nothing.
Seriously, seek professional help.
As I've mentioned several times in this forum, Harm does more harm than good. And hard drive speed is 95% of his advice. Just ignore him.

When I import TIF and JPG files with same metadata, only the TIF files are imported. How can I change that?

I have imported and renamed TIF and JPG files with the same metadata re recording date and time. Only the TIF files are imported, the JPG files remain unimproved. Thus I have in the Finder e. g. 13 image files in the same folder in which Lightroom only finds 10 files. Any ideas for resolution welcome!
Thanks

Turn off the option Preferences > General > Treat JPEG Files Next To Raw Files As Separate Photos. Then do an import again. It appears that, in this instance, LR considers a TIFF to be a "raw" file.

How to Delete imported JPEGS after matching RAW files are imported as masters

Using a 5D Mark III and shoot JPEG (SD) and RAW (CF).
Aperture 3.5.1, using a managed library
Perviously, using a 7D so new to shooting JPEG and RAWs from an aperture Aperture workflow standpoint.
I know that i can import the JPEGs > delete images that do not make the cut > then import the matching RAW files in the import dialogue that correspond to the JPEGs in the Aperture Library.
I use the RAW files as my Camera Master images and once the RAW files are imported, the smaller resolution JPEGs are no longer needed or viewed in my normal edit workflow. I only need the JPEGs to quickly go through the images to find out which RAW files i need to import at a later time to increase the speed of import > edit > deliver.
My Assumptions:
1. Logic would lead me to believe that after import the user should see a stack like image representation with whatever file type is considered Master to be on top and the viewable secondary file type on the bottom. clicking on the image stack should allow you to see both file types as you would normally see with image stacks with the same files types. This is not the case... What am i missing here?
2. Logic again would lead me to believe that when i have the ability to delete one of the 2 image types as i do not need both in the end. After the import process is complete and RAWs are backed up, I want to delete the JPEG files as they are just taking up more space on my DAS drive array... There is no need to keep a duplicate of every file in both JPEG and RAW format. This is not the case as when i delete the JPEG or RAW, both files formats are deleted simultaneously. What am i missing here?
Problems: (correspond to Assumptions above)
1. I do not seem to have access to both images (JPEG & RAW) in a stack where i can expand and close the stack to see both? It seems like i only have access to the image type i have selected as Master? This seems counter intuitive to what the workflow should be as why would aperture 'lock the secondary file types away' so you can't easily view both file types as the same time for comparison?
2a. Reality seems to be that i do not have access to the JPEG and RAW image files. I can only see one at a time by selecting the images and choosing 'make JPEG master’ and then respectively... 'make RAW master', but you can't see both at the same time for file comparison.
2b. Also, I can't find a way to delete the JPEG images after the RAW files have been imported. I would presume most professional photographers shoot RAW and do not shoot JPEG as their camera master or editing master images. I do not understand why aperture has captured both as a pair in the library that does not allow me to delete the JPEG (in this case) as i have selected the RAW as my master.
If someone can please help... The function seems like either i am missing something obvious or that the implemented function of using RAW + JPEGs files for import is broken from a real world workflow standpoint.

leonie...
thank you for clearing that up for me.
I think that at this point it is silly to use the JPEG+RAW import functionality as it seems that it takes longer to do the above steps than to just import only the RAW files and press on from there.
I seems what i have done in the past of only importing the RAW files and then using the quick preview functionality to reduce image load times is the best thing in can come up with without keeping 'duplicates' in the database.
That really baffels me that there is no built in functionality to remove the JPEG from a RAW+JPEG pair and i wonder how the real world photographers who help Apple test and implement software to solve real world workflow problems thought the JPEG+RAW import was going to be used.
I do understand that i can use a smaller JPEG file size to reduce the bloat of the database, but used over hundreds of thousands of images is certainly going to make a dent in my total aperture database size and therefore storage needs down the road.
If you have any other workflow thoughts, or know of a 3rd party plugin/ etc... to fix this obvious shortcoming then i am all ears..
thank you again Leonie and have a great week

Keeping Photoshop Raw Image Adjustments When Images Are Imported

I've got a bunch of raw images that have been adjusted in Photoshop. When these raw images are imported into Aperture, all the data stored in the .xmp files are stripped out, meaning the raw files are imported without any adjustments. Is there a way to import raw images so they retain the adjustments that have been made in Photoshop? I hope so. The idea of importing all my raw files into Aperture and having to readjust every single image is unthinkable.

With all due respect, I do "want" desperately to be able to use Aperture as a RAW converter-good workflow.
Sure... different meanings of "want". I "want" Aperture to be usable for that, but in its present state, you don't "want" to use it, because it's not very good at it. I tried a number of different pictures; it ranges from "okay" to "astoundingly bad", depending on the subject matter. In no case does it approach Adobe Camera Raw in quality; but it is not hideous in all cases.
Take a bunch of your own pictures and burn them to a CD, both RAW files and edited versions. Bring the CD to an Apple Store, sit down, and have a go at Aperture. In my case, it was the final thing that saved me the money of buying the software.
As a "better iPhoto" I think it's a winner. But it is, by no stretch of the imagination, a "professional" photography application. If it were a $50 replacement for iPhoto I'd probably have already bought it. It could be useful from an organization standpoint -- except for the fact that it can't read many of my Photoshop PSD files at all since they are in LAB color mode.

RH Crash when linking or importing word documents

RH9 build 9.0.1.232
Office 2010
Webhelp (custom skin)
I have created a template from a successful project which i completed over three months ago.
I am now trying to create a project using the template and getitng persistent crashes when attempting to Import or Link Word documents.
This is causing a great hold up to the project delivery.
Any help would be appreciated

Please see the article on my site about Project Templates. The script has been found to have some issues.
You say have deleted the file and then ask what will happen if you remove it. You did, you said so "Deleting the file seemed to work". If that is not what you mean, please clarify what you mean by removing the file.
If you create a project using the script, then close the project and delete the CPD, it should be OK. If there ae going to be problems, you will know pretty soon.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Aperture crashes when I try to create a new project

Hello all, having an odd problem with Aperture crashing when I try to create a new project.
I suspect the problem is likely related to the library file's permissions, as I was previously working with this library as another user (stopped using the account because of issues solved by too many fonts being installed).
The problem occurs when I finish naming the project and hit enter, so presumably when Aperture attempts to save the new project into the library file.
Any ideas?

Ha i figured as much...
Thanks for the help. Wish i could just update I movie!!!!

Aperture crash when start and the database is damaged

Hello
I have been playing around with a trial of Aperture
My mac crashed when i was importing a big library -my fault, because the hot-
After that Aperture has not been able to start, until i have deleted the database -moved to a different location-
Is this the normal behaviour when the database is broken?
Would be nice if Aperture was able to "keep alive" even when the photo database library was broken
Something like "Sorry it seems the library has a problem, do you want to create a new one or choose one that actually exists?"
Bruno

Bruno
have a read of the articles at these two links
Aperture 3: Troubleshooting Basics
http://support.apple.com/kb/HT3805
Aperture 3: Frequently Asked Questions (FAQ)
http://support.apple.com/kb/HT4007
See if these help.
Tony

FCPX has suddenly started crashing when trying to import media

I updated FCPX to 10.0.8 a couple of weeks ago and everything has been fine until today (I'm fully updated with Mountain Lion as well) . Now every time I try to import media, FCPX crashes. This occurs right after I hit the "Import Selected" button -- and occurs regardless of type of media, where I'm importing it from, or how many clips. I get a very long error message -- I've attached just the first part of it (through Thread 0) below. The entire error message runs through Thread 37.
The only thing I did right before this happoened was to delete some old unused applications that were not even on the system HD (they were on a different internal HD - drive A). The applications included very old versions of Final Cut and iMovie that had not been opened in a couple of years. After I did this, FCPX suddenly started to recognize another internal HD (drive C) as a camera for the first time, and tried to import a bunch of old home movies, which it has never done before. And ever since then it started crashing when trying to import new media -- even after I "ejected" drive C.
Any ideas? I'm at a total loss and in the middle of a big project for a client, and could really use some help. Thanks!
Process:         Final Cut Pro [326]
Path:            /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier:      com.apple.FinalCut
Version:         10.0.8 (221398)
Build Info:      ProEditor-22139008018000000~1
App Item ID:     424389933
App External ID: 14685451
Code Type:       X86-64 (Native)
Parent Process: launchd [152]
User ID:         502
Date/Time:       2013-03-31 13:00:19.713 -0400
OS Version:      Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report:          14013 sec
Crashes Since Last Report:           9
Per-App Interval Since Last Report: 12180 sec
Per-App Crashes Since Last Report:   9
Anonymous UUID:                      11BDDCCB-5BCF-05B8-C04A-9A39067B1572
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Application Specific Information:
objc[326]: objc_removeExceptionHandler() called with unknown alt handler; this is probably a bug in multithreaded AppKit use. Set environment variable OBJC_DEBUG_ALT_HANDLERS=YES or break in objc_alt_handler_error() to debug.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                         0x00007fff8d168814 objc_alt_handler_error() + 0
1   libobjc.A.dylib                         0x00007fff8d1686a0 alt_handler_error(unsigned long) + 52
2   libobjc.A.dylib                         0x00007fff8d162f35 objc_removeExceptionHandler + 92
3   com.apple.CoreFoundation                0x00007fff893ebb49 _CFDoExceptionOperation + 89
4   com.apple.AppKit                        0x00007fff86e2bbcf -[NSApplication endModalSession:] + 24
5   com.apple.prokit                        0x00000001003283c3 -[NSProApplication endModalSession:] + 45
6   com.apple.FinalCut                      0x0000000100033870 -[PEAppController windowWillClose:] + 416
7   com.apple.CoreFoundation                0x00007fff893aceda _CFXNotificationPost + 2554
8   com.apple.Foundation                    0x00007fff8575ae26 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
9   com.apple.AppKit                        0x00007fff870c49e0 __18-[NSWindow _close]_block_invoke_0 + 260
10 com.apple.AppKit                        0x00007fff870c48b5 -[NSWindow _close] + 364
11 com.apple.FinalCut                      0x0000000100073be7 -[PEImportWindow timer] + 439
12 com.apple.Foundation                    0x00007fff85785af3 __NSFireTimer + 96
13 com.apple.CoreFoundation                0x00007fff893b7804 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
14 com.apple.CoreFoundation                0x00007fff893b731d __CFRunLoopDoTimer + 557
15 com.apple.CoreFoundation                0x00007fff8939cad9 __CFRunLoopRun + 1529
16 com.apple.CoreFoundation                0x00007fff8939c0e2 CFRunLoopRunSpecific + 290
17 com.apple.HIToolbox                     0x00007fff84842eb4 RunCurrentEventLoopInMode + 209
18 com.apple.HIToolbox                     0x00007fff84842c52 ReceiveNextEventCommon + 356
19 com.apple.HIToolbox                     0x00007fff84842ae3 BlockUntilNextEventMatchingListInMode + 62
20 com.apple.AppKit                        0x00007fff86f2e563 _DPSNextEvent + 685
21 com.apple.AppKit                        0x00007fff86f2de22 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
22 com.apple.AppKit                        0x00007fff86f251d3 -[NSApplication run] + 517
23 com.apple.prokit                        0x00000001003286c5 NSProApplicationMain + 378
24 com.apple.FinalCut                      0x0000000100001e14 start + 52
I'th Mountain Lion as well. *and FCPX 10.0.7

Update: the problem is definitely with the internal HD "drive C". Before restarting FCPX after the last crash I unmounted the C drive -- then restarted FCPX and was able to import media just fine. I thought I had tried this already, but I guess not.
So, what did I change with my C drive when I deleted the old apps off my A drive? There is both an iMovie events and projects folder on the C drive -- but FCPX has never tried to import them until after I deleted the old iMovie app (I still have the most recent version of iMovie on my system drive -- but have never used it to open these old folders). I read on another thread on this forum that if I "hid" these folders, FCPX would not try to recognize them, so I moved them to within another folder on the same drive -- but FCPX is still trying to recognize and show them when the Import Media window is launched -- and still shows the C drive as a camera.
So, what can I do to stop this from happening?
Thanks!

What is actually happenning when we are importing a class of some other pac

Sirs,
I have a doubt which is very basic to java,
I want to import a class say "HashMap" to my class.
If i put import "java.util.HashMap" or "import java.util.*;"
Which will be better ?
If i put "import java.util.*; " will it affect the performance?
What is actually happenning when we are importing a class of some other package to our class
Your help solicited,
Sudheesh K S

Many of your questions of this nature can be quickly answered by a search of prior posts to the forums, like this:
http://forum.java.sun.com/thread.jspa?forumID=54&threadID=631979
And why do you tend to post boldened text? It's harder to read.

I have been using Lightroom 4.4 successfully for over 2 years. Just tried to import some new photos after a vacation and the application crashes when I click "import" every time. Tried restarting computer. Version says it is up to date.

I have been using Lightroom 4.4 successfully for over 2 years. Just tried to import some new photos after a vacation and the application crashes when I click "import" every time. Tried restarting computer. Version says it is up to date.
How do I get formal support for this from Adobe?

Thanks for the response. The application was crashing. A Windows message was displayed showing "Lightroom.exe has stopped working", "Windows can check online for a solution the problem.". Etc.
I just launched Lightroom to check the exact message for this reply - and the Import worked. It had failed dozens of times before.

Lightroom 6 crashes when attempting to import from camera.

Never had a problem importing from same camera using LR 5.7. LR 6 crashes when attempting to import from camera.

Actually I have found out that it's not related to importing, but to face recognition being turned on (which I had just done shortly before I started the import).
See here for more details: Re: Lightroom 6.0.1 standalone always crashes less than a minute after start

Imovie 11 crashes when i choose 'import from camera'.

suddenly, imovie 11 9.0.4 crashes when i choose 'import from camera'. never happened before, always worked fine. driving me crazy! can anyone help? i tried to delete the plists, did disk permissions, etc etc. am running 10.6.8, haven't changed anything except to delete a bunch of old projects.
can i just reinstall imovie from the install disk?
thank you!

Open console in Applications>Utilities, check the system log for the date/time of the last problem & the Startup right after that for clues.
Also look for crash Logs>iMovie.

Why does FCP looses its source file reference when files are copied

Why does FCP looses its source file reference when files are copied from another project??
i have this happen all the time, I move all my media to another drive and files that originated in another project do not reconnect because they have lost there source?
Any way to fix this mess? i am in the middle of reconnecting 400 files by hand one at a time!!!
Thanks, mark

Because you changed the file path. From one hard drive to another...the hard drive name is no doubt different, and then if you have the files in different folder structures then yeah, it will lose the connection to that media.
Best thing to do is to clone your media drive, or name the other drive the same name, and keep the exact same file structure (folders in folders) as the original drive. Then you won't need to reconnect.
Shane

Why does Aperture crash when importing modified image into Photoshop CS2?

I have been using Aperture 2.1.4 for the past 2 years and really like the interface. But, I've had one nagging problem: I begin by scanning all of my slides with the Nikon Coolscan 4000 and save them as large tiff files @ approx. 55mb each. I then import each slide with a custom color profile into Aperture. I then optimize the image including white balance, levels, and color adjustments. When I want to make additional changes that I'm not able to do in Aperture, I attempt to send the image to Photoshop CS2 for further processing. But, at this point, Aperture crashes. After this, I get a message saying "do you want to re-open Aperture or quit?" Additionally, I often get the message "Aperture has applied new settings. Do want to keep these new settings or use the original settings?" Since I don't know what will happen if I choose "use the new settings," I always select "keep the original settings." And, when I open Aperture again and try, again, to send the image to Photoshop CS2 to edit, Aperture crashes again. Has anyone had the same or similar problem who can give me some ideas of how to solve this issue! Thanks.

Welcome to the forums!
It sounds like there may be a permissions issue between the two apps, Aperture using one and PS another.
1. Are you logged in as an administrator?
You need to be.
2. Where is your library stored, is it in the picture folder of your user directory?
If so moving it in to the general area of your MacHD may help get over some of these issues.
3. Have you run any of the Ap First Aid steps? Have a read of this page;
Ap2
http://support.apple.com/kb/HT2945
Ap3
http://support.apple.com/kb/HT3805
4. Is it possible that the upgrade to Ap3 would get you around the need to jump into PS?
Start with these ones and then come back letting us know how you go.
Tony
Message was edited by: Tony Gay Added Ap2 First Aid link.

Aperture crashes when files are imported

Similar Messages

Maybe you are looking for