C1 22 - is it worth to "upgrade" ?
I wonder if there is something there that is worth to considering the "upgrade" and the extra payment or as usually just some cosmetic features and rather some problems ?
(Somebody commented on Youtube:
From a user perspective I have three main issues with C1:
1- they encourage you to make early purchases without actually telling you what new features will be added to the product.
2- eventually when they do reveal the features, it’s old features that competitors have had for years and they justify this as worthy of a new version instead of a minor dot update.
3- the new features (as behind as they are) are yet still not ready and full of flaws.)
Here is the youtube review and it sounds like the (ehm) super new "panorama" and "HDR" features are actually quite amateurish here comparing to the competitors https://www.youtube.com/watch?v=tkUY1jB5uFY
-
It's up to you whether you consider the new features useful to you. Are you likely to use the Panorama, or HDR features, do you have a new camera that older versions don't support? Now that version 22 is available, you could take a 30-day free trial and see how you like the new features - if you like them, upgrade, if you don't, don't.
Ian
0 -
the house of CO - greed, flaws and bugs...
this company has turned itself into a kind of cheap drama show. without the many bugs and problems c1 would be a good raw converter. unfortunatly do they think they need to have more LR features even when they are unable to bring them to the same level. a reasonable company would have delayed the release but not c1 they need to meet their deadlines to please their investors and they also have no problem to sell an unfinished tool and again a new version with a load of new and old bugs as with every release in the last years. their dehaze clone was already ridicules bad but the pano and HDR tool problems are so easy to reproduce that no spin can make them go away so they have their mr.grover say "oh yes this needs to be improved" like it was a surprise or marginally that a tool without automatic or manual ghosting correction is not acceptable today.
-1 -
Permanently deleted userOh look - CSP whining about Capture One again.
What a refreshing surprise that is...
0 -
Hello all; Just to say that when I first tried Capture One, Version 20, I immediately stopped using LR. Period.
Today I am returning to LR. I have to get work done. It's as simple as that.
In CO 22 my findings:
- Random previews take 4 or more seconds to generate, for both directly after completion of import + preview building (by random I mean no apparent visual significance to which images render slowly and which do not. additionally, it does not seem to matter if the image has been edited or not)
- most edit operations are now skewed so far from real time that I wait multiple seconds without any indication anything's happening till edit completion.
I honestly haven't investigated further issues because OMG. I have previously noted in another thread the same images render in LR in literally the blink of an eye. LR edit operations continue to be nominally swift. I'll also add the same catalog and edit functions are not slow in CO 21. My machine is an i9 2.4 MBP, mid 2019 32GB RAM, 4 GB VRAM, SSD,
In it's current state,CO 22 is unusable to me. Period.
Embarrassing
2 -
I dodged the v21 marketing, but unfortunately I bit on the v22; the thought of having an "all in one" HDR/Pano stitcher was just too enticing.
The bottom line, v22 HDR/Pano is not ready for prime time. During Beta testing I reported problems to which I never received an acknowledgement. I find it hard to believe that with all of the HDR and Pano software on the market, that C1 would choose to implement a package as poor as this one. The good news is that C1 will likely implement changes that will move it from blah to good. I hope they do it sooner rather than later.
Since C1 pano stitching will not work with Tiffs and until they implement the changes, I will be doing HDR merging with Photomatix and stitching in Affinity. IMO, better image quality is more important that easy workflow.
0 -
During Beta testing I reported problems to which I never received an acknowledgement
one might ask what is the point of beta testing when they show no real interest in solving issues but you are not alone with this experience. my impression is that they always run out of time and so even bigger problems got ignored and as a result c1 is in constant beta state. I think most user would be very happy if they would release a version which fixes most of the bugs instead of under developed new features.
1 -
If you are upgrading from Capture One 20 then YES.
I don’t do HDR or Panorama and everyone focuses on the new features. I shoot with Canon, Nikon and Sony so the greatly improved color profiles were worth the upgrade for me. The consistency and color is so good and so much better than LR.
The improved menus, interface and performance was a HUGE boost on my 2019 iMac. Not much was talked about this in the reviews but it is night and day difference for me. Everything just flows more nicely than version 20.
And the last big difference is the import interface and speed increases.
LR is more mature with many more features if that is what you are looking for. But if you want something that has the most accurate color, control and consistency, I can’t think of anything better!
0 -
I wonder if v22 uses Metal instead of OpenCL on Intel Mac.
It would be the only reason for me to upgrade. Even if I'm only an amateur, C1 slowness is somehow frustrating on my 2019 iMac 27' with 24Gb of RAM and 8Gb of VRAM...
(edit: typo)
0 -
I am on a 2019 iMac 27 with 16 GB and a Radeon 580x and I am not encountering any "slow" problems.
0 -
Michael,
If Capture One, Version 20 is better for you than LR, why did you return to LR instead of staying with C1 version 20 for the time being?
1 -
I had them both for a time. When I purchased Capture One 20 I still had 7 months on my Adobe subscription that I had paid up front.
This also provided me sufficient time to work between both products to make sure I Capture One could be the only program I would need.
What I discovered was the joy of photography. Making sure I chose my light more carefully, and nailed the shots in camera the best I could, instead of doing heavier post-processing. Like I had said, Capture One is not for everyone and where the additional post-processing is a priority you cannot beat the LR/Photoshop combo. I only made some references to LR in this post because others mentioned it in their posts.
0 -
...just out of curiosity for all of you who have performance issues with C1v22 (not talking about Pano or HDR for the moment). Are you placing the images you are editing inside a collection prior to editing, or are you editing your images directly in a folder with lots of images or even the "All Images" selected in the library window?
I am asking because the difference in performance when editing images inside a smaller collection is drastically different from editing images inside collections with several thousand images. So if you are experiencing dismal performance when editing images my suggestion would be to create a collection in the Library tab and drop the images you want to edit into it before starting to edit them. In my experience the larger the folder or collection, the slower the performance, for instance editing an image inside a +200,000 image folder will take several seconds for every edit, but inside a collection with maybe 200 images the same image will apply every edit instantly.
Can't say if this will work for everyone, but it certainly worked for me.
0 -
ruppert,
In my experience the larger the folder or collection, the slower the performance, for instance editing an image inside a +200,000 image folder will take several seconds for every edit, but inside a collection with maybe 200 images the same image will apply every edit instantly.
out of curiosity, do you mean "apply every edit" in the sense of copy & apply Adjustments from one image to another, or do you mean moving a slider e.g. exposure on a previewed image?
0 -
...I am not a software developer and it would be nice if one of the developers of C1 could chip in (though I guess they have other things to do), but from my experience with v22 so far it feels like it is using a lot more of the systems resources to deal with browsing and editing and indeed I do feel that browsing some of my larger folders of several thousand images is very smooth. Also the editing of very large DNG's (+200megapixels) is now as responsive as it is in Lightroom. But trying to do both at the same time (browsing and editing) results in dismal performance, particularly when editing. I would guess that the system resources attributed to the browsing are so massive when browsing large folders, that there are not enough resources left for the editing. It actually says something to that effect in the official release notes. I would assume that LR has similar limitations, but that they found a clever workaround by separating "Library" and "Develop" module altogether.
Again I am no developer, but this representation feels consistent with my experience so far.
0 -
Hi BeO
out of curiosity, do you mean "apply every edit" in the sense of copy & apply Adjustments from one image to another, or do you mean moving a slider e.g. exposure on a previewed image?
I meant the later, aka every adjustment made to the image, every slider, every speed edit every applescript, all just smooth as butter, as long as the image is not inside a massive folder, but in a smaller collection of maybe a couple hundred images (though the actual numbers might depend on your respective hardware/software combination).
0 -
maybe c1 is for some unknown reason regenerating previews or re-reading / synchronising meta data, I would monitor the processes with activity monitor. I do not see a difference in speed to the older version but I have also no folders containing more than a couple tsd. images.
0 -
maybe c1 is for some unknown reason regenerating previews or re-reading / synchronising meta data, I would monitor the processes with activity monitor. I do not see a difference in speed to the older version but I have also no folders containing more than a couple tsd. images.
...as I said I don't know what happens under the hood, but I doubt it's regenerating anything, since the behavior is the same, regardless on whether the drive with the actual source files is connected or disconnected (aka offline).
I am currently working on an archive with roughly 100,000 images each 61megapixels from a Sony A7RIV. The C1 catalog file is about 110GB in size and copying that catalog file from one internal ssd to another internal ssd (both measured at 2900MB/s read/write) will take about 5min, though the first 40sec are just spent with the finder "preparing to copy" not actually copying. If however you use one of those portable external SSDs like the popular Samsung T5, the actual speeds will drop to something around 300MB/s read/write and copying the catalog file will take closer to half an hour. So unless you only work on very fast internal SSDs and RAM upwards of 128GB on your computer, C1 will have to load and unload portions of that catalog file into your RAM depending on where your focus shifts to. And when viewing and editing at the same time C1 has no way of limiting its focus swiftly, so making a collection might help, that is all I am saying, at least until someone who actually knows what they are talking about (because they have participated in developing it) is chipping in.
0
投稿コメントは受け付けていません。
コメント
17件のコメント