Trouble Importing an Aperture Library
My COP import of an Aperture Library has resulted in the preview generation task hanging, although the rest of COP responds to mouse clicks. Any suggestions?
I started with just over 4600 referenced images, exported them to a new Aperture library (which really just moves the catalog edits and metadata), unstacked all the stacks, emptied the Aperture trash. Then I repaired the Aperture Library just to be safe.
The COP import has gone pretty good for the most part, there was a complaint about 1 unsupported file, but all the files were imported. Now COP is sitting at "Generated 3481 of 3492 previews - about 30 seconds left" for the last hour. The import was 4600 images, it seems that not all the previews have been generated.
COP is not very busy, its using about 6.5% of the CPU, however 10.75GB of virtual memory and 2.83GB of real memory.
I'm going to let it sit overnight if it wants, if it hasn't fixed itself by the morning I will have no choice to kill it. (Is there any other option?)
I'm wondering if I'm best off to just erase the newly imported catalog and start over, or open the catalog and see if I can generate the missing previews.
And how do I find which is the unsupported image it could not import?
My COP is currently at version 8.2.0.82, I suppose I should try upgrading it.
Any comments and assistance appreciated.
I started with just over 4600 referenced images, exported them to a new Aperture library (which really just moves the catalog edits and metadata), unstacked all the stacks, emptied the Aperture trash. Then I repaired the Aperture Library just to be safe.
The COP import has gone pretty good for the most part, there was a complaint about 1 unsupported file, but all the files were imported. Now COP is sitting at "Generated 3481 of 3492 previews - about 30 seconds left" for the last hour. The import was 4600 images, it seems that not all the previews have been generated.
COP is not very busy, its using about 6.5% of the CPU, however 10.75GB of virtual memory and 2.83GB of real memory.
I'm going to let it sit overnight if it wants, if it hasn't fixed itself by the morning I will have no choice to kill it. (Is there any other option?)
I'm wondering if I'm best off to just erase the newly imported catalog and start over, or open the catalog and see if I can generate the missing previews.
And how do I find which is the unsupported image it could not import?
My COP is currently at version 8.2.0.82, I suppose I should try upgrading it.
Any comments and assistance appreciated.
0
-
Hi Eric,
I'm doing the same at the moment. The only thing I can add, which you've probably already done, is to make sure Aperture is closed when you're in Capture One (and vice versa). Although not necessary under all circumstances, it doesn't hurt.
Also, make sure your referenced location (external hard disk etc) is mounted (and stays mounted).
I noted also (in the case of my laptop) ensuring that it doesn't go to sleep, etc (aka, set all power settings to 'always on') can rule out any weirdness with the O/S with respect to power management.
Failing that, I've broken up my Aperture import project into smaller chunks which tends to keep things a little more controlled as I'm working through the migration to Capture One.
Paul0 -
Thanks for the comment Paul
The full library is 17000 images, so I was hoping 4500 was a small enough chunk for one import, and other people here seem to have imported over 10,000. What size chunks are you using?
The referenced images are on the main hard drive, so there is no problem about it being mounted. The machine is a desktop, and and computer sleep is off, I have just disabled hard drive sleep to be safe.0 -
If the rest of your library looks okay, and if you're sure it is just preview generation that appears to have 'hung', then it should be fine to just close and restart CO. 0
投稿コメントは受け付けていません。
コメント
3件のコメント