Can you explain exactly what you are trying to imply? I don't understand your logic. Are you suggesting that the problem is with the files I'm trying to import and not with the library?
There are at least two very common reasons for this hanging behaviour.
- A corruption of your Aperture library - e.g. an unwritable database file: This is usually fixed by repairing or rebuilding the library.
- A corrupted video or or image file.
What I was trying to say is that your tests are not yet excluding any of these possibilities : Your test with importing into a new library is suggesting a library corruption and not a data problem with one imported image, but you cannot yet be perfectly sure, unless you are isolating exactly that file that is making Aperture hang. As I said, processing the imported images and generating previews is a background process, and you do not know, if and when each image will be processed. And if you imported a bad image a long time ago, Aperture will try over and over again to process the image, when it gets around to that particular image.
So be prepared and have the Activitiy viewer up and running, when processing imported images starts, to be able to see the filename. Then you can tell, if it is alwas the same image or video and remove the culprit. Rebuilding will not help in that case.
But it also be a corrupted database file, that makes it impossible to write the edited versions to the database. Then only rebuilding will help.
I get this problem with almost everynew batch of photos I take from the camera.
That is why your import into a new library was a valuable test. Since that works well, your camera, card, cable, card reader seem to be o.k.