![]() So, the file structure is open to all other apps, no container like importing all files into C1’s catalog. The import settings are quite refined, as they use tokens to define folder and file names. So, no reason to not use a “workaround DAM” except maybe, that an external DAM can’t show any RAW edits In fact, the DxO archive was a structural copy of the C1 archive. Also, my catalogs are on SSD and only contain previews/thumbnails and links to nearly the same structures of folders and files (YYYY/MM) I also had in DxO PL. The most intresting is that a session is selfcontained and can very easy be moved if although I had my share of crashes during importing and applying a style for B/W “scans” (only RAWs from a Nikon Z 7 with a macro lens): Since version 22 of C1 (and 23 was introduced yesterday, but, welllllllll… nothing to go crazy about) and the replacement of my Intel iMac against a Mac Studio, simply no crashes anymore. Sessions also have other things going for them. ![]() That’s one of the main reasons to use session mode instead. I have a fast computer now but Photolab 6 has gotten so much slower rendering previews than I ever have seen before and that was really one of the most important reasons leaving it.Įven C1 has got a lot of bashing for it’s slow and unstable general catalog mode. Then Photolab wouldn’t need to suffer from the same compromises Lightroom has been suffering from for so long. Together with PM Plus it would be possible to inactivate the catalog for those using external solutions. A DAM like Photo Mechanic doesn’t need to scale previews and that is the main reason why it’s so much faster. It has never been a receipe for speed having to compromise between smaller previews in the catalog and the need for 1:1 previews in the converter. One of the main reasons leaving Lightroom before migrating to C1 was to get rid of that slow and single point of failure catalog. Photolab can’t still read the DNG-files I export from C1 after converting my Sony ARW to DNG - even from cameras that Photolab has profiles for. I have done so for years when I have felt Photolab wasn’t up to do the job but there is still that data interchange problems with DNG and the need to use these clumsy heavy TIFF-files. Or setting up one session you use for ad hoc jobs. It is to get access to them I have left Photolab. It has a lower learning curve than C1 but you will also find that some of the tools you have used is not there or a little bit less advanced. With this said it can for sure be reasons to migrate to Photolab. If you have used the XMP-metadata in C1 to tag your images, you also have to export the XMP-files and reindex them with Photolab. In fact, it´s far more convenient to index a straight folder hierarchy like the one in Photolab. It wasn´t an easy decision to go back again because I think the C1 sessions system is more complicated to use in a DAM-structure, since it relies on its own folder hierarchy. I also liked that Photolab is using the core filesystems folders straight on without any cumbersome import processes like Lightroom and C1. I did like Joachim and am back with C1 again after many years with Photolab but once I went the other way just like Joachim because at that time, I felt Photolab was more efficient and also had better denoise. Malcolm, is there any special reason why you are thinking of migrating? So far I haven’t regret both steps, it was interesting to see “how it’s done in another valley”, but comparing both apps I have no reason to continue with DxO products.Īnd I’m no subscriber of C1, I bought my licenses both in DxO as in C1 for one version. I also came from C1, tried PL and after the last version of PL didn’t improve what I missed, I went back to C1. If you’re using catalog functions of Capture One you need to prepare to do the image management with another tool as PL rather sucks in this area. Worse, once you eventually find out Capture One might be the smaller p.i.t.a., there’s also no way to get PL’s edits into C1. There’s no way to transfer C1 edits to DxO else than export all edited images and lose the abilities to re-edit. If a combination is not supported it can take extremely long (and sosmetimes long as in “never”) to get support for a certain combo. If you use PL trial version like suggests make sure to try out all your lenses and all your bodies as PL relies on “home-grown” sensor- and lens profiles.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |