Originally posted by wizofoz I tend to use each of the tools to do a specific job. I'm thinking that as I really like the CO raw converter I would start there, make whatever adjustments I can do quickly and easily and then process and export a tiff to PS if it needs further refinement. In other words, use CO in lieu of ACR.
In very few cases I use PS Elements. For my purposes the local adjustment tool is mostly sufficient. I didn't test it until now, but COP8 now also includes local cloning and repair layer. Maybe this is another new improvement.
Originally posted by wizofoz DXO, On One and LR all have better cataloging/file retreival features than CO ( I still cant get my head around their sessions and catalogues) So i use one of them when browsing files, depending on my mood and purpose.
I think retrieval isn't that bad. You also have a tagging tool and you can create intelligent albums (collections based on tagging). But when you've reorganized and renamed folders on OS level it's a very hard job to adjust the image references within the catalog. Aperture 3 does a much better job in this respect. Another downside is that the meta data doesn't show the lens you used to take the image (in case of my K5 files - raw and jpg). Only the focal length is shown. On the other hand some lens correction profiles for pentax lenses are offered. The main reason I use COP is the high end quality of the raw converter and the flexibility of the user interface.
---------- Post added 2014-09-26 at 06:38 ----------
Originally posted by emalvick I've seen people's results using Capture One (not 8 yet), and I have to say that the results I see are usually quite impressive. I tried out 7 and could not get a grip on its file handling, so I gave up. I didn't want yet another RAW developer software insisting it should be a DAM software too. Capture One makes it really difficult to understand what it's library or sessions are doing with your files. If they work out a few things I don't like about it, I'd likely try it again.
Sessions are more dedicated to events. Creating a session yields to a specific file structure on operating system level. This fixed structure also includes the images. Catalogs can contain images, but they also can reference the images in the OS directory structure you defined (I use this feature). Before version 7 of CO Sessions were the only „organizational unit“. In my opinion it fits perfectly on studio/event situations. I sometimes use Sessions when stacking images. The resulting Helicon Focus images I import into my CO Catalog.
CO’s Catalogs are similar to Apertures Catalog structure - but not the same. They support intelligent albums based on the whole catalog image „universe“. Used with tagging it’s directly comparable with Aperture and also with LR (I think, no experience). I mainly take photos in the area of plants, animals, landscape, macro, … So most of the time I’m working subject driven and not event driven. This is the reason why I mostly use one Catalog. The images get their subject oriented tags, and using these tags I create my subject-oriented image collections (intelligent albums). By the way, CO Version 8 has a separate Keyword tool. In COP7 this was part of the general Metadata tool. Based on the collections I generate the appropriate jpg-albums.
If you want to include a Session into a Catalog, you can import it. Within the catalog it becomes a Project. The original Session stays unchanged. Changing things within the original Session doesn’t reflect in the catalog project. So Catalog and Session are completely independent.
Maybe the lines above help you to understand the difference between CO Catalogs & Sessions?! Starting with CO I had the same problems.