The factory installed internal SSD has 2,700 MB/s write/read speeds. The external SSD has a 1,800 MB/s write/read speeds. My C1P catalogues use referenced folders for my images which reside on a OWC Thunderblade 8TB Thunderbolt 2 connected external drive. I keep my C1P catalogues in the Picture folder on my internal SSD.
Photo supreme vs lightroom timelapse pro#
My main workstation is a 2 year old iMacPro 8-core with 64GB RAM, Radeon Pro Vega 56 8GB graphics card, and 2-TB internal SSD. This is the big drawback from switching to C1P. This keeps the speed up, however, I do miss the ability to search across my whole image library like I could do with LR.
My images from 2017 until today are kept in a catalogue for each year. I broke my LR library of about 130k images (Canon, Fuji and Leica RAW files) into years to keep the C1P catalog size to less than 20k images. Forget trying to import a 150k+ LR library in to C1P. What I discovered early on with my C1P journey was that if you get over about 20,000 images in a C1P reference folder library, the program gets sluggish and annoying. (Leica M10, M10-R and SL2 and a variety of lenses). I since sold off all my Fuji X gear (excellent system!) to invest in more Leica kit. Three years ago, I fulfilled a lifelong desire to own a Leica M with the purchase of a Leica M10. I switched to C1P from LR about 4 years ago after being continually frustrated with the mediocre quality of LR RAW conversions from my Fuji-X system. I´m quite curious on how someone else is working with C1 relating to browsing and DAM, where hyerarchical keywording is Paramount. I´ve tried C1 and found it´s a fantastic developer for my taste but its DAM is not able to handle my inceasing number of photographs in one catalog, and On1 and Luminar are still far behind LR (globally) or C1 talking about developing. In my case it´s holding around 150.000 photographys easily in one catalog, so I don´t need to change catalogs to browse among all of them at a time or start a selection of any kind. Maybe someone could shine a light on the advantages of working with developed files so that I could understand a reason for doing it this way.Īlthough I tried to escape from LR, I´m still sticked to it mainly because of its DAM. I’ with you that the DAM section of CO is a way behind others. But now I have my recipe versions in CO which is ok for me. But for searching Photo Supreme is more powerful than CO. So now I use Photo Supreme as a DAM and for getting all the metadata in the files and than import them to CO. I liked the recipes method and I found it in Capture One which is similar than in Aperture. Some of my friends like this but I can not get really warm with this method. You can do version to in Photo Supreme, but they are for “developed” files, so you have the original raw and a new Tiff for example. But the experience with the versions in Aperture which are “only” recipes I missed.
When I dropped Aperture, I started to use Photo Supreme for DAM. At the time looking Adobe started with the renting system and even when I choosed Aperture I couldn’t get warm with Lightroom. I have (maybe had) a similar problem, I came from Apple Aperture and was looking for something similar. That’s why I think the cataloging system in C1 has the capability I would like to have, but unfortunately most of it breaks when the catalogs get of any size. The problem is they are all rabbit holes to fall into and I spent way to much time “organizing” and not any near enough time producing imagery. In the past I’ve used iMatch, iView Media Pro and LR. I’m not looking for a ton of capability in a DAM. Digikam is a DAM as it uses a sqLite database, and I’ve just started playing with it, but it shows promise. xnView is not a DAM per se as it doesn’t have a database to speak of, but saves all the info and metadata into XMP files.
Per a posting on dpReview, I use a Session with no imagery imported and just browse around the drive.Īt present I’m using xnView MP and Digikam to see if either makes any sense for use as photo organization tool in conjunction with C1. I’ve played around with cataloging in other DAM’s and really not come up with a workflow that really makes sense. Frankly having a functional catalog system in C1 is a prerequisite for me before I send them any more money for an upgrade. I’ve got about 65k images in my catalog and that chokes a catalog in C1.
0 kommentar(er)
