Capture one 10.1 and Aperture
I finally took the plunge and moved over to C1 and the import of 1.2 TB and 73000 photos from Aperture to C1 9 and it went well seemingly and only took about 6 hours with one hang. I then upgraded to C1 10.1 . Capture one pro now sometimes uses more CPU time than any other program I have, nearly 400% of quad core iMac 27inch 5K Retina with 1 TB SSD internal and 40 GB or RAM with the i7 processor not the i5!
Some issues
1- It takes around 5 minutes to open the recent Aperture library import. The C1 10.1 and Aperture libraries are stored on an external RAID 5, 12TB Thunderbolt 2 system. Aperture itself can open the same library in about 15 seconds. C1 10.1 appears to crash when it opens this large Aperture file (1.2 TB and 73000 photos) but even with the spinning beach ball of death or Activity Manager stating that it is unresponsive, I can usually count on it to open the library after about 5-10 minutes. This is clearly way too long. I can see the CPU usage fluctuate from time to time during this process so that is why I waited despite the apparent hang. Both Aperture and C1 10.1 are on the internal SSD. Given the system specs above and the Thunderbolt 2 connection to RAID 5 disc I wonder why C1 10.1 takes so long to open the library?
2 Is the slow load, due to preview regeneration issue? I am letting it regenerate ALL the photo previews again, but it already did this on the initial import into C1 9 pro. So, why is it regenerating the previews? Will it keep doing so every time I open the program?
3 I found the option to verify the C1 10.1 catalog database etc and it reported no issues.
4 I realize that the Aperture import only reference the original photos and does NOT move them to the C1 10.1 catalog. I understand that I could physically copy them over from the Folders area to the User collections area to copy them into the C1 10.1 catalog. However, the way the Aperture library is displayed in the Folders section is very cryptic and only shows the hierarchy of the Aperture library itself with all sorts of cryptic folders labels such Masters, 1, 2, e etc. This is the way the Aperture library looks from the Finder rather than what it looks from within Aperture. I was hoping it would display the Aperture library in the same named folder hierarchy that is visible within Aperture program itself, and indeed, the same way it is displayed in User collections area. In that area I see the hierarchy of photos named in the way it was within Aperture, eg 2011 imports, then various named subfolders etc. Any thoughts?
5 Issue 5, does not allowme a way to copy from the original Aperture library (in the Folders section of C1 10.1) to the C1 10.1 Catalog, as I cannot see the names of the originating folders in the Aperture library and obviously I don't want to import 72000 photos en masse without getting them into the correct folder hierarchy.
Thanks
Some issues
1- It takes around 5 minutes to open the recent Aperture library import. The C1 10.1 and Aperture libraries are stored on an external RAID 5, 12TB Thunderbolt 2 system. Aperture itself can open the same library in about 15 seconds. C1 10.1 appears to crash when it opens this large Aperture file (1.2 TB and 73000 photos) but even with the spinning beach ball of death or Activity Manager stating that it is unresponsive, I can usually count on it to open the library after about 5-10 minutes. This is clearly way too long. I can see the CPU usage fluctuate from time to time during this process so that is why I waited despite the apparent hang. Both Aperture and C1 10.1 are on the internal SSD. Given the system specs above and the Thunderbolt 2 connection to RAID 5 disc I wonder why C1 10.1 takes so long to open the library?
2 Is the slow load, due to preview regeneration issue? I am letting it regenerate ALL the photo previews again, but it already did this on the initial import into C1 9 pro. So, why is it regenerating the previews? Will it keep doing so every time I open the program?
3 I found the option to verify the C1 10.1 catalog database etc and it reported no issues.
4 I realize that the Aperture import only reference the original photos and does NOT move them to the C1 10.1 catalog. I understand that I could physically copy them over from the Folders area to the User collections area to copy them into the C1 10.1 catalog. However, the way the Aperture library is displayed in the Folders section is very cryptic and only shows the hierarchy of the Aperture library itself with all sorts of cryptic folders labels such Masters, 1, 2, e etc. This is the way the Aperture library looks from the Finder rather than what it looks from within Aperture. I was hoping it would display the Aperture library in the same named folder hierarchy that is visible within Aperture program itself, and indeed, the same way it is displayed in User collections area. In that area I see the hierarchy of photos named in the way it was within Aperture, eg 2011 imports, then various named subfolders etc. Any thoughts?
5 Issue 5, does not allowme a way to copy from the original Aperture library (in the Folders section of C1 10.1) to the C1 10.1 Catalog, as I cannot see the names of the originating folders in the Aperture library and obviously I don't want to import 72000 photos en masse without getting them into the correct folder hierarchy.
Thanks
0
-
The issue I'm seeing is the 73k photos, it's not advisable to have large catalogs in C1 (see this thread: viewtopic.php?p=121632#p121632). 0 -
What you have done is set up the C1 catalog as referenced image files, but the referenced image files are inside the aperture library bundle, so Aperture sees them as managed image files.
In my opinion this is guaranteed to cause trouble in the future, as Aperture will feel free to move the image files (they are managed by Aperture after all, and hidden in a bundle) and this will confuse the hell out of Capture One.
And, as you have mentioned, Aperture's internal folder structure is not very user friendly. I was not intended to be, by Apple.
A much better strategy is to start again with Aperture, and change the managed images into referenced images. You could make the folder structure for the referenced images match your project structure in Aperture, or you could just sort the images by year and by camera (my choice). Now Aperture knows it cannot move the image files, and the disk folder structure is one that you can read easily. Should you delete or move your Aperture library, or run Aperture, the image files are not affected.
Now, import the Aperture Library (with all referenced images) into a Capture One catalog, as referenced images. Now Capture One also knows the image locations are not under it's control. Backing up the catalog results in relatively small files. Your regular backup mechanism, Time machine or CCC or whatever, will back up the referenced image files.
The User Collections in Capture One will match your project structure in Aperture (no matter what choice you have made regarding the folder structure for the referenced images).0 -
Unfortunately V10.1 is still much slower (about 4x on my i7) than V9.3 when opening an equivalent catalog. The same holds true for any larger collection of images. During start-up time the computer is mostly idle, i.e. a clear sign of a serious bug. However, PhaseOne has not been able to fix this within 6 months. You can also see lots of discussions about this in several topics (look for V10 and slow).
Even V9.3 was never as fast as Aperture and I have lost several catalogs with more than 20k images due to crashes with V9.1 and 2. PhaseOne was neither able to help recover them nor had any clue why CaptureOne destroyed the catalogs when crashing. I have never seen this issue with V9.3 but it is certainly back in V10 and 10.1.
I still have my Aperture Catalogs (managed) on a second disk and duplicated this catalog before converting it to a referenced catalog using a naming / folder structure similar to my Aperture Album set-up (like Eric explained). I then split the Aperture Catalogs by year / date into smaller (10K) catalogs and imported them to CaptureOne.
I can work with V10.1 if
- I store all referenced images locally (no NAS but external SSD or RAID is fine) in a file structure that I populate with PhotoMechanics (not with CaptureOne);
- Limit the number of images to 10k (gives about 1 minute of start-up, 20k result in 2 minutes);
- Backup my catalog every time I quit on a different external disk;
- Do not include large TIFF (panorama) in the catalogs but rather do work on these in sessions;0 -
Thank you for your comments, it is much appreciated.
Respectfully, if CI cannot handle large libraries,/catalogs what is doing positioning itself as one the best options for Macusers?
The simpler Photos app can handle a large single catalog/library (imported from Aperture) better than C1.
I agree that I could easily break down the large Aperture catalog (which Aperture handled perfectly well, I might add) by year etc. However there is no way to search multiple catalogs at the same time in C1 as far as I know which is the main reason to have one admittedly large catalog... I will ivnvetigage further in case I am wrong about this.
As noted, there are pros and cons for referencing files vs managing them but I am not convinced that a good reason to use one or the other is the ability or inability of program to handle large catalogs or libraries...
I really want C1 to shine and do what Aperture could, if not better. It may well be better in display/editing etc, but so far fails at the presumably simple task of handling large catalogues. I did find that regenerating all the previews in C1 (which took as expected a very looooong time!) shortened the opening time to about 3 minutes vs 5.
I hope that future upgrades improve..
I will finish with the comment that Aperture was much cheaper than C1 -$79 vs several hundred. 😄0
投稿コメントは受け付けていません。
コメント
4件のコメント