Originally posted by MetteHHH I read the thread here about the new version of CaptureOne, googled around and found some very reassuring pages about switching from LR to CaptureOne
I used to recommend Capture One but I don't anymore, at least not for the time being.
The reason is that they don't really know what they are doing with respect to the user interface (and in terms of creating a robust). This may or may not have to do with the fact that Capture One has separated from Phase One. In the past, one received the great combined support but nowadays Capture One operates as a separate entity with far worse support and bad development decisions.
Capture One had a great brush system: One brush for every layer type. Same keyboard shortcut, no matter whether one needed to paint a mask in an adjustment layer or a heal layer. By associating the eraser brush with the same shortcut key but a modifier (such as "Alt"), one could easily change between brushing and erasing, using just one button on a controller (or keyboard).
In version 13.1.0 (Capture One 20), they not only introduced the ability to use an arbitrary number of source points on heal layers, but also changed how one needs to use brushes. Now there are four shortcuts to contend with. This decreased usability dramatically, as it then required the conscious use of one of four buttons on a controller or keys on the keyboard, plus there were forced changes to the layer selection which were so confusing to users that the problems had to be at least partially addressed in the next release. The whole design was poorly thought out and should never have made it past beta testing. The fact that it did and that they at least partially corrected it in the very next release, tells you something about quality control at Capture One.
In version 13.1.1 they partially fixed the huge step backwards in usability, by reducing the number of forced layer selections (a problem that required David Grover to intervene when Joe McNally was demonstrating the software). However, it is just a partial fix, usability problems remain and in the latest 13.1.2 release, the issue has still not been addressed (I'm just talking about making it as good as it was before, not making it better).
This tells me that in the future, more is likely to go wrong. If they listen to a limited number of focus group users but are deaf to objectively sound arguments -- anyone having done a HCI 101 course would agree to them without thinking -- then that doesn't bode well for the future. It's the same kind of dumbing down of the interface, but making it harder for users who know what they are doing, that Adobe started when they made everything in LR "smart". That was the time I left Adobe/LR and, very unfortunately, the signs for C1 don't look good, AFAIC.
If you add to that there are the kind of bugs I left Lightroom for; the latest release notes state "
Importing a catalog can result in the last picture not getting imported.", relocating folders on storage is bound to leave an inconsistent state behind, independently of whether you move images within Capture One or ask it to relocate them afterwards, the keystone correction does not work properly, etc. then, given the high price tag, it isn't that attractive as I once thought it was (before they heavily messed with the brush interaction design).
The is a bug, even in the most current release, which
causes layer masks to be lost that hasn't been fixed for three whole months (and counting).
Lightroom users should know that while importing LR catalogues is technically possible, almost none of the adjustments are transferred. Crops seem to be the one adjustment one can rely on making it into a C1 catalogue (a bit more is supported, but that's a statement I recently read from an LR looking at C1). Users also frequently complain about C1 being poor regarding DAM. I never missed this, but heard this argument many times.
LR users should also know that there are no image histories in C1, so among other downsides, "before/after" comparisons are pointless.
There are no proper "virtual copies" either. C1 has "image variants" but they are forced to stick together so it is, e.g., not possible to have one album with B&W versions of colour images in another album. One can work around this limitation by using "smart albums" and manually assigning metadata to one subset of the variants, but this clearly a workaround for missing flexibility. Think of C1 variants as "LR stacks" and realise that there are no proper "virtual copies".
LR users should also know that C1 previews can be rather mushy sometimes, depending on image properties. For the sake of efficiency, some image operations like noise reduction are not performed properly at low magnification levels (e.g., when the image just fills the screen and one does not zoom in). Sometimes you'll think that the image is out of focus, only to find that it is completely fine after zooming in. The same issue (cutting corners for the sake of efficiency) can dramatically affect colour rendition as well. The problem has been known for a long time and while previews are more often than not tolerable, users should have been given a better option a long time ago already.
There are other annoying things like the inability of being able to overwrite files in an export folder. Either you have to manually delete existing previously exported images or C1 will create duplicates and then duplicates of duplicates, etc. by automatically renaming the new files (if it at least renamed the old files...). Things like that are a real productivity brake and could be implemented with almost no effort, but despite being requested for years and years, are still not available.
That's what kills me about the worse brush interaction design: They could leave it as it as, I don't care, all they would have to do is add one additional (universal) brush type (the one they had before), and everyone would be happy. Everyone. Implementing this additional brush type (that automatically adapts to the selected layer type) could be done with a trivial amount of implementation effort. But no, they only did a half-hearted fix to the completely inefficient and confusing design they debuted in 13.1.0.
There are many more no-brainer improvements which would be trivial to implement but help users quite a bit. For instance, one can use the mouse scroll wheel to zoom in and out of viewed images. Inexplicably, the same approach is not available to resize the thumbnails in a browser window. Instead one either has to use a scrollbar (that is best hidden most of the time and would have to be unhidden whenever required) or keyboard shortcuts. To add insult to injury, some of these keyboard shortcuts don't work properly. I reported this and many more issues but more often than not the same issues persist from release to release.
There have, of course, been many great additions to the functionality over the years and many of my feature suggestions ended up being implemented. Still, that small easily fixable but nevertheless productivity impacting issues persist for so long is anything but optimal.
Originally posted by MetteHHH Capture One does not prioritize Pentax, so a lot of the specific lens presets are missing.
You won't get any special colour profiles from them either.
They sometimes used plain wrong colour profiles (for the K-5 and K-3) instead of the "custom-designed profile process" they claim in the marketing literature. The K-1 profile is not good, in my view, I'd recommend using one from another camera or making one your own (which is not as easy as it is in LR).
Nor will you see the lens name of a Pentax lens in the metadata panel. They cannot be bothered to pull the information from the right location (LR does it). No PixelShift support either, BTW, not even the limited support LR provides.
No tethering support for Pentax either. Again, LR does it.
Originally posted by MetteHHH Being able to edit in masked layers is simply a revolution to me.
The so-called "layers" in Capture One are not comparable to regular PS layers at all.
You get the same local adjustments with LR -- instead of layers you get adjustment pins -- and LR users had access to radial mask and proper linear gradient masks much, much earlier than C1 users.
Having said that, C1 is really great in practically supporting all kinds of adjustments when using local adjustments. To the best of my knowledge, LR still only offers a subset of the adjustments.
Originally posted by MetteHHH Colour editing is absolutely stunning.
I agree. That is really a highlight of C1.
However, I want to look at Darktable to see what the colour editing support is like.
Regarding retouching, for instance, Darktable is superior by offering a very sophisticated frequency separation approach.
I'm sorry for the rant, I don't want to dampen the joy you will no doubt have with Capture One. I'm just utterly disappointed that they didn't manage to completely fix a major usability problem in the last two releases; a problem that I find so aggravating that I won't consider any future upgrades anymore unless the problem has been fixed.
I'll probably keep using my old C1 13.0.4 version (it is a "Capture One 20" version, just not broken yet) for a while but will certainly not update to the version with the worse brush selection design and by implication never spend money on an upgrade again. This means, I'm forced to miss out on the improved healing support (healing and clone layers actually lost functionality in the 13.1.0 revamp, but the added multiple source point functionality would be really nice to have), i.e., have rather bad support for retouching, but at least I'm not forced to waste buttons on my controller and stupidly make multiple key/button presses and unnecessarily, when revisiting adjustment layers.
C1 was great and had great potential but I lost trust in their product design.