I would like to transition to Capture One Pro 8 but have heard it is not yet fully functional with OS X 10.10 Yosemite. Is anyone using it successfully with Yosemite?
Yes, Capture One Pro 8.2 (the current version) requires 10.9 or 10.10. It ran fine for me under 10.10.2 and when I upgraded my OS to 10.10.3 last night, Capture One did not seem to have any issues, although I didn’t put it through any “heavy lifting.”
I’ve been using the trial version of C1 for a week. I’m running the beta of 10.10.3. No problem. I’m switching from Aperture and have C1 “referencing” a “managed” Aperture library. C1 is really very nice. However, My library contains 40k images and it takes C1, 2mis, 10 seconds to open. That’s with C1 on an SSD drive and the library on a very fast Drobo-thunderbolt. Very quick within the application, but startup is a drag.
It could be that reading the managed library slows C1 down. I had about 27k images in my managed library and chose to relocate the originals out of it before importing the database into C1. My main reason was that I was suspicious that one day Aperture may not be running anymore and I can’t use the nice relocation feature (where you can easily set up a decent folder structure by date automatically).
My startup time is about 30 seconds with both the application and the catalog sitting on a SSD.
Hi Mike,
When you exported your images out of your managed Apreture library, were you able to save the organization? I have my images as such: year folder–> projects within each year–> albums within each project. How can you export this to maintain the file structure?
Thank you,
Whatever structure you have set up within Aperture is unaffected by moving your master-files.
I have (or better: had) a structure which roughly follows Topic (Folder)>Project>Album/Smart Album/Slideshow etc. My masters were all managed by the library and were in whatever folder structure Aperture uses within the library package file.
When I moved the masters out to a referenced folder structure, I chose a strict chronological path like Year>Month>Day (of shooting). My topic>project structure within Aperture did not change anything at all, just the references to the masters were new.
When I then launched the C1 Aperture-Importer it read the topic>project structure of Aperture, rebuild this inside a new C1 catalog and referenced the masters at the same time from my new chronological folder structure in the finder.
Aperture still looks the same it did for ten years, nothing changed. I just now have a 1:1 copy of its library inside a new C1 catalog. For any NEW images I use a similar folder structure on my HD, but to keep things organised I have this separate from my old Aperture masters (I have two folders, named “Aperture masters” and “Capture One masters”. The first one is write protected, as I won’t import any new images into Aperture).
I have taken a similar approach. I think it is important to move to a referenced system for your originals if you are currently using a managed library in Aperture. It is much easier to set that up in Aperture before you pull things into Capture One. Even if you normally use a referenced library, it is worth doing a quick check in Aperture with a smart album to be sure no files are managed. If you find some, relocate them using Aperture to a referenced location.
The reason I took this approach is that if you import a managed Aperture Library into Capture One, I think Capture One points to the original files buried in the Aperture file. I see that as a problem as you move forward with adding new files through Capture One.
Thirty seconds is pretty amazing! Your suspicion about asking C1 to read a managed iibrary in order to load may indeed be the cause of the interminably long load times some of us are getting. In my case, I have about 28K images in a managed Aperture file and C1 takes close to 2 minutes to load. I’m going to try your step of relocating the originals out of Aperture to see if that will speed things up. Thanks for the tip.
Hi Ron,
I’m curious if you exported your originals from your Apreture library and noticed a speed improvement? Is you plan to have the images referenced or managed in C1?
I plan to use the C1 Catalog as referenced but I’ve not yet completed the process of relocating my all originals from Aperture. I’m extra cautious and so far just tried relocating a few specific folders. Everything worked fine so I’ll now go ahead and relocate all the originals in my Aperture Library to their own folder. I’ll make a post here when I find out if there has been a speed improvement in opening the C1 Catalog.
I finally completed relocating my originals out of my managed Aperture Library. My C1 catalog is now used as referenced only and there is a BIG improvement in speed of loading! I have 28.5K images located in a separate folder on an external drive and they load in 20 seconds. Before, when they were part of the managed Aperture Library, it took close to two minutes.
This is great information. Thank you for posting. I asked C1 support for different options. They suggested having the C1 catalog on my SSD, and have this relatively small catalog reference my large Aperture Library on my Drobo Thunderbolt. (previously I was referencing the Aperture library on my internal spinning drive which is slower than the external Drobo!) However, I think I prefer your method. Keeping my 40k images in the aperture library package doesn’t seem right. I think I should be working with these images completely outside of the Aperture Library package file.
I not sure how you exported/relocated the images out of Aperture while maintaining both the structure (Folder/Year–> Project–> Events–> Albums) and also the edits you’ve made in Aperture. How is this done?
I just followed the Capture One recommended method, i.e., File>Import Catalog>Aperture Library. It was a long, overnight process for my 28.5K images to migrate. Then, another long process for previews to build the first time I opened the C1 Catalog. The folder structure shows up under the User Collections section of the C1 Catalog. As Capture One forewarns„ all edits didn’t carry over exactly as seen in Aperture. Also, out of 28.5K images there were 355 “incompatible files” that did not get imported. I have not investigated thoroughly enough to see which ones they were. Hope this helps.
Ok… it looks like we all did exactly the same thing. We had a managed library in an Aperture Library Package (.aplibrary file) that we:
1) first cleaned up in Aperture getting the images in the right projects/albums/etc.
2) created a new empty catalog in C1 (mine is on my SSD)
3) used the “import catalog” command in C1 and chose Aperture Library
This action make C1 “REFERENCE” my Aperture Library which is a package (at container) holding all of my Aperture masters. It also preserves my photos in their Aperture organizational structure.
Here’s the thing….. all of my Masters are still in the Aperture Library package. They were not “moved” out. They were not moved out to an open file folder structure on my hard rive. They are still tucked away nicely in the .aplibrary package file.
(Please correct me if I’m wrong.)
So, this is my question. Do we want to be “referencing” an Aperture .aplibrary forever? Is there a problem with this?
At some point in time - in future versions of OS X - Aperture may not be launching reliably anymore. While this won’t “destroy” your package file containing all the masters (I assume), you would at least loose the powerful option to “relocate masters” out of Aperture with a folder structure of your choice. This could be quite the difficult task to get all your masters out of the package file manually and then re-establish all the links in your C1 catalog. So I would really think hard about that, since you don’t loose anything in your current Aperture setup if you just move out your masters to referenced folders. Aperture works the same as before, the relocate option is rock-solid. I had 10 years of images in a single, growing managed library and everything went super-smooth with the relocation.
What I did was move them out to a structure (on the same HD as the package) by Year>Month>Day (of shooting) in a folder called “Aperture masters” (which I write-protected in the finder), THEN import the library into C1 and from here on out put all my NEW images in a new folder called “Capture One masters”. So I have a clean cut between the old and the new and won’t get confused.
Also there seems to be some consensus here, that a C1 catalog referencing a managed Aperture package file is performing worse then one using masters directly from a flat folder structure.
Maybe it was not clear that I moved my Aperture Masters into a new, separate folder on an external drive. That means both my Aperture Library and C1 Catalog can now reference that folder that I call Photo Masters. I suppose you could go on keeping all images in a managed Aperture Library indefinitely but it seems cleaner to me to have all images in a folder that is not “owned” by any application. A BIG advantage that I have seen so far is much faster loading of images in C1 now that they are free from Aperture.
Oh, I understand. Thanks for clarifying. How did you export your edited photos from Aperture? I have 40k pictures, and many many edited versions. I read in the Apple site that export master will not export versions of the masters. Is there a way to “bake” the edits in so they will export? Thank you!!
Someone else can probably provide better information on this than I can, but I believe what you need to do is:
1) Set up the folder that will become the location of your Masters (the one that will contain the migrants from your former Aperture Managed Library and will now be referenced by your C1 Catalog and Aperture Library.
2) Select the edited images you want to export.
3) Go to Aperture File menu and select Export>Versions.
4) Specify your new Master Photo Folder as the location for the export.
The “versions” you exported should have all the baked in edits but I suggest seeking confirmation of this procedure from others in the forum.
Ron: I have been using C1 for about 18 months. It has worked well with every OX including the latest. It is an excellent RAW converter, if you shoot RAW, and has extensive features that they keep on improving and adding to. Great program and customer support.
Thanks for this very helpful testimonial. It gives me more confidence to continue on in trying to master C1. I really like what I have seen so far. Could you recommend any resources for learning to use it, other than the C1 You Tube videos?
They have an online newsletter, to which you should subscribe, and there are some good ideas in them. However, YouTube is about the best resource. I spent a lot of time using trial and error! Again, focussed questions put to their customer service are usually quickly responded to. Hope this helps. I don’t miss Aperture now.
To get a grip with C1 I HIGHLY recommend checking out their YouTube-Channel with lots of videos about working with C1 Pro 8. Especially the “Webinars” are very extensive and informative:
I found the Capture One Pro video series sold by the Luminous Landscape site to be quite useful. It is based on version 7 rather than version 8 but the major features are the same and it provides a good overview. David Grover from Phase One, who does their webinars, is present as “the expert”, and walks the hosts from LuLa through the details. I will say that I purchased at the recent sale they had. I think the full price of $60 (I think that is what it was,) is a bit steep. But I got a lot out of it.
Yes, Capture One Pro 8.2 (the current version) requires 10.9 or 10.10. It ran fine for me under 10.10.2 and when I upgraded my OS to 10.10.3 last night, Capture One did not seem to have any issues, although I didn’t put it through any “heavy lifting.”
Best,
Tim
I’ve been using the trial version of C1 for a week. I’m running the beta of 10.10.3. No problem. I’m switching from Aperture and have C1 “referencing” a “managed” Aperture library. C1 is really very nice. However, My library contains 40k images and it takes C1, 2mis, 10 seconds to open. That’s with C1 on an SSD drive and the library on a very fast Drobo-thunderbolt. Very quick within the application, but startup is a drag.
ACS
It could be that reading the managed library slows C1 down. I had about 27k images in my managed library and chose to relocate the originals out of it before importing the database into C1. My main reason was that I was suspicious that one day Aperture may not be running anymore and I can’t use the nice relocation feature (where you can easily set up a decent folder structure by date automatically).
My startup time is about 30 seconds with both the application and the catalog sitting on a SSD.
Hi Mike,
When you exported your images out of your managed Apreture library, were you able to save the organization? I have my images as such: year folder–> projects within each year–> albums within each project. How can you export this to maintain the file structure?
Thank you,
ACS
Whatever structure you have set up within Aperture is unaffected by moving your master-files.
I have (or better: had) a structure which roughly follows Topic (Folder)>Project>Album/Smart Album/Slideshow etc. My masters were all managed by the library and were in whatever folder structure Aperture uses within the library package file.
When I moved the masters out to a referenced folder structure, I chose a strict chronological path like Year>Month>Day (of shooting). My topic>project structure within Aperture did not change anything at all, just the references to the masters were new.
When I then launched the C1 Aperture-Importer it read the topic>project structure of Aperture, rebuild this inside a new C1 catalog and referenced the masters at the same time from my new chronological folder structure in the finder.
Aperture still looks the same it did for ten years, nothing changed. I just now have a 1:1 copy of its library inside a new C1 catalog. For any NEW images I use a similar folder structure on my HD, but to keep things organised I have this separate from my old Aperture masters (I have two folders, named “Aperture masters” and “Capture One masters”. The first one is write protected, as I won’t import any new images into Aperture).
Hope this helps.
I have taken a similar approach. I think it is important to move to a referenced system for your originals if you are currently using a managed library in Aperture. It is much easier to set that up in Aperture before you pull things into Capture One. Even if you normally use a referenced library, it is worth doing a quick check in Aperture with a smart album to be sure no files are managed. If you find some, relocate them using Aperture to a referenced location.
The reason I took this approach is that if you import a managed Aperture Library into Capture One, I think Capture One points to the original files buried in the Aperture file. I see that as a problem as you move forward with adding new files through Capture One.
Best,
Tim
Thirty seconds is pretty amazing! Your suspicion about asking C1 to read a managed iibrary in order to load may indeed be the cause of the interminably long load times some of us are getting. In my case, I have about 28K images in a managed Aperture file and C1 takes close to 2 minutes to load. I’m going to try your step of relocating the originals out of Aperture to see if that will speed things up. Thanks for the tip.
Ron
Hi Ron,
I’m curious if you exported your originals from your Apreture library and noticed a speed improvement? Is you plan to have the images referenced or managed in C1?
ACS
Hi Alex,
I plan to use the C1 Catalog as referenced but I’ve not yet completed the process of relocating my all originals from Aperture. I’m extra cautious and so far just tried relocating a few specific folders. Everything worked fine so I’ll now go ahead and relocate all the originals in my Aperture Library to their own folder. I’ll make a post here when I find out if there has been a speed improvement in opening the C1 Catalog.
Ron
Ron
Hi Alex,
I finally completed relocating my originals out of my managed Aperture Library. My C1 catalog is now used as referenced only and there is a BIG improvement in speed of loading! I have 28.5K images located in a separate folder on an external drive and they load in 20 seconds. Before, when they were part of the managed Aperture Library, it took close to two minutes.
Ron
This is great information. Thank you for posting. I asked C1 support for different options. They suggested having the C1 catalog on my SSD, and have this relatively small catalog reference my large Aperture Library on my Drobo Thunderbolt. (previously I was referencing the Aperture library on my internal spinning drive which is slower than the external Drobo!) However, I think I prefer your method. Keeping my 40k images in the aperture library package doesn’t seem right. I think I should be working with these images completely outside of the Aperture Library package file.
I not sure how you exported/relocated the images out of Aperture while maintaining both the structure (Folder/Year–> Project–> Events–> Albums) and also the edits you’ve made in Aperture. How is this done?
Thank you!
ACS
I just followed the Capture One recommended method, i.e., File>Import Catalog>Aperture Library. It was a long, overnight process for my 28.5K images to migrate. Then, another long process for previews to build the first time I opened the C1 Catalog. The folder structure shows up under the User Collections section of the C1 Catalog. As Capture One forewarns„ all edits didn’t carry over exactly as seen in Aperture. Also, out of 28.5K images there were 355 “incompatible files” that did not get imported. I have not investigated thoroughly enough to see which ones they were. Hope this helps.
Ron
Ok… it looks like we all did exactly the same thing. We had a managed library in an Aperture Library Package (.aplibrary file) that we:
1) first cleaned up in Aperture getting the images in the right projects/albums/etc.
2) created a new empty catalog in C1 (mine is on my SSD)
3) used the “import catalog” command in C1 and chose Aperture Library
This action make C1 “REFERENCE” my Aperture Library which is a package (at container) holding all of my Aperture masters. It also preserves my photos in their Aperture organizational structure.
Here’s the thing….. all of my Masters are still in the Aperture Library package. They were not “moved” out. They were not moved out to an open file folder structure on my hard rive. They are still tucked away nicely in the .aplibrary package file.
(Please correct me if I’m wrong.)
So, this is my question. Do we want to be “referencing” an Aperture .aplibrary forever? Is there a problem with this?
ACS
At some point in time - in future versions of OS X - Aperture may not be launching reliably anymore. While this won’t “destroy” your package file containing all the masters (I assume), you would at least loose the powerful option to “relocate masters” out of Aperture with a folder structure of your choice. This could be quite the difficult task to get all your masters out of the package file manually and then re-establish all the links in your C1 catalog. So I would really think hard about that, since you don’t loose anything in your current Aperture setup if you just move out your masters to referenced folders. Aperture works the same as before, the relocate option is rock-solid. I had 10 years of images in a single, growing managed library and everything went super-smooth with the relocation.
What I did was move them out to a structure (on the same HD as the package) by Year>Month>Day (of shooting) in a folder called “Aperture masters” (which I write-protected in the finder), THEN import the library into C1 and from here on out put all my NEW images in a new folder called “Capture One masters”. So I have a clean cut between the old and the new and won’t get confused.
Also there seems to be some consensus here, that a C1 catalog referencing a managed Aperture package file is performing worse then one using masters directly from a flat folder structure.
Alex,
Maybe it was not clear that I moved my Aperture Masters into a new, separate folder on an external drive. That means both my Aperture Library and C1 Catalog can now reference that folder that I call Photo Masters. I suppose you could go on keeping all images in a managed Aperture Library indefinitely but it seems cleaner to me to have all images in a folder that is not “owned” by any application. A BIG advantage that I have seen so far is much faster loading of images in C1 now that they are free from Aperture.
Ron
Oh, I understand. Thanks for clarifying. How did you export your edited photos from Aperture? I have 40k pictures, and many many edited versions. I read in the Apple site that export master will not export versions of the masters. Is there a way to “bake” the edits in so they will export? Thank you!!
ACS
Someone else can probably provide better information on this than I can, but I believe what you need to do is:
1) Set up the folder that will become the location of your Masters (the one that will contain the migrants from your former Aperture Managed Library and will now be referenced by your C1 Catalog and Aperture Library.
2) Select the edited images you want to export.
3) Go to Aperture File menu and select Export>Versions.
4) Specify your new Master Photo Folder as the location for the export.
The “versions” you exported should have all the baked in edits but I suggest seeking confirmation of this procedure from others in the forum.
Ron
See my comment under the “Slow Loading Speed” thread about using the Verify Catalog command to improve loading speed somewhat.
Best,
Tim
Ron: I have been using C1 for about 18 months. It has worked well with every OX including the latest. It is an excellent RAW converter, if you shoot RAW, and has extensive features that they keep on improving and adding to. Great program and customer support.
Gerald Levy
Thanks for this very helpful testimonial. It gives me more confidence to continue on in trying to master C1. I really like what I have seen so far. Could you recommend any resources for learning to use it, other than the C1 You Tube videos?
Ron
They have an online newsletter, to which you should subscribe, and there are some good ideas in them. However, YouTube is about the best resource. I spent a lot of time using trial and error! Again, focussed questions put to their customer service are usually quickly responded to. Hope this helps. I don’t miss Aperture now.
Gerald Levy
Thanks, again. I’ll subscribe to their newsletter. It sounds like the effort at trial and error will have a payoff and be well worth the time.
Ron
To get a grip with C1 I HIGHLY recommend checking out their YouTube-Channel with lots of videos about working with C1 Pro 8. Especially the “Webinars” are very extensive and informative:
https://www.youtube.com/user/PhaseOneDK/featured
I found the Capture One Pro video series sold by the Luminous Landscape site to be quite useful. It is based on version 7 rather than version 8 but the major features are the same and it provides a good overview. David Grover from Phase One, who does their webinars, is present as “the expert”, and walks the hosts from LuLa through the details. I will say that I purchased at the recent sale they had. I think the full price of $60 (I think that is what it was,) is a bit steep. But I got a lot out of it.
Best,
Tim