Capture One 22
The pano/stitching feature is just amazing.. I was always using PTGui and now what the C1P developers have done blows me away.... As per David Grover's statement, no more ping-pong with other pieces of software.. Same can be said for the HDR merge and Photomatix....
Took 43 RAW shots with my Canon 5DIII in Brenizer style and the stitching was perfect... No Pano "Nodal Ninja" on tripod were used..All free hand..
Just love what I have seen..
-
I understand, so don't upgrade to Monterey Mac OS, that's even worse and Apple is in business for quite some years..This is what software is all about..
C1P is a very good and reliable platform and these improvements will come.. I have done a lot of stitching tests and the overlapping is very important, more so than with PTGui, well I have to get used to it and will..I am now changing the way I am taking the sequential shots..0 -
It’s all in the eye of the beholder..
0 -
EtMRS:
Look at the Catalog : It's not possible to work with Catalog AND Session because catalog can't export adjustment in a session sidecar like metadata. But Catalog is a very fine DAM ! And working with session is very reliable and fast !
Yes, even open-source app darktable has a catalog AND (optionally) sidecar files.
C1 sometimes seem to develop a feature (here: catalog in addition to session) to 80%, and add another 5% on top in upcoming releases, never reach 100% of what would be a well-designed and fine-tuned solution.
Let's hope this is not the case for HDR and pano.
Six month ago, I ask on the forum what's the core business of CO1 ? Public or Professional. Now, with V22, I have the answer
I don't think the distinction between professional and non-professional is all that helpful in photography.
A bus-driver is a bus-driver is a bus-driver, maybe there are multi-day tour bus-drivers and local bus-drivers, but they all have somewhat similar requirements to their working equipment (bus, seat, aircondition).
But the photography business is very diverse I think, sport event shooters need to get jpgs quickly out of the door, real estate and wedding requirements differ a lot too I think, print or online, landscape or product, art reproduction, company employe portraying, forensic photography, journalists, war reporters, etc., I think you pro's might know this better than me, and also the indiviudal requirements of non-professionals vary a lot, and there might sometimes be more overlap between one amateur to one pro than there is between two pros.
0 -
Not PM+ anymore? Maybe I mix this up...
0 -
C1 sometimes seem to develop a feature (here: catalog in addition to session) to 80%, and add another 5% on top in upcoming releases, never reach 100% of what would be a well-designed and fine-tuned solution.
...have you ever heard of the Pareto principle and how it applies to the development of software?
It's often referred to as the 80/20 rule and in software development it states that the development of the first 80% of any given piece of software will take about 20% of time whereas the remaining 20% will take an additional 80% of time to develop. So if we assume that it took C1 a year to come up with the current version of HDR and pano stitching, you should expect this to be perfect in about four years. In fairness it took Adobe also about the same amount of time from their first implementation of pano stiching to something that was even remotely usable, though still not as accurate nor flexible as dedicated programs like the afore mentioned PTGui or the unfortunately now defunct Kolor Autopano.
The other thing that is rarely mentioned is that the history of panorama stitching is a tale of patent wars and corporate speculations and maybe the lackluster implementations seen in PS, Lightroom and now C1 are also in part due to some patents owned by other companies still blocking any further development.
If you are really curious about it you could look up Helmut Dersch vs IPIX, or GoPro kills Kolor. It might give you an idea. As a frame of reference: I first bought Kolor Autopano in 2010 and to this day it is still the fastest, most accurate and most flexible tool to stitch panoramas and it has none of the limitations found in LR or C1 regarding file sizes or possible geometry corrections. If you want to create a panorama in a rectilinear projection, a field of view of 160º and pixel dimensions of 80,000 x 120,000 pixels you could do that in Autopano without breaking a sweat. But for most day to day use of pano stitching an all raw workflow would still be very desirable. Lightroom is okayish now and I am sure C1 will eventually get there as well.0 -
Hm, if you're shooting companies and they want a picture of their building, and a wide-angle or shift/tilt lens won't cut it, you might be able to get a good enough pano handheld, or on a regular tripod, or with a drone, then stitch, edit and downsize so it fits into their brochure or on their website. And if you charge money for it you are a pro, in my definition at least.
I fully agree with what you said about Session AND Catalog, e.g. not much work to synch cos and comask files as they do with xmp.
0 -
BeO,
Would the ability to synch cos and comask have real value for a mass of users?
I work almost exclusively in Sessions - I prefer that concept and have always disliked Catalogue constraints since LR V1 was released.
I very rarely revisit a session. It happens sometimes, but its rare. So they are in effect an Archive. They are often moved form where they were to somewhere else - most recently to a NAS . Older sessions had multiple copies saved as backups to multiple external drives.
Older sessions will not often be updated to match new versions since they are sitting in what are effectively archives. New edits - especially from a Version updated Catalogue to a non-updated Session may not be appropriate - even if there is mechanism in place to somehow track the location of the session or vice versa.
In my case - especially where backups of whole session are concerned, any synch activity to a referenced original image file would not be relevant to synching FROM a catalogue. If I have moved the entire session off an internal drive to the NAS and happen to do some work on an image there the current image location it may well no longer be relevant to referenced files the catalogue is using.
So although the synch itself might be easy - not too dissimilar to exporting from catalogue to session I suppose - keeping track of enough information to make it all work over time to the expectations of users could be a bit more challenging.
So what benefits are we really looking for here?
What is the real benefit of being able to edit in both catalog AND session and synch between them? Where does the implementation of that benefit set limits to avoid over-complexity and missed user assumptions and expectations?
Is it a one-way thing - allow edits in a session that can then be uploaded to a catalogue? To replace the edits (????) of the shared image (where known) or, if not "matched" to a known image for some reason, re-import?
Pareto principles for refining what is available and enhancing the experience are fine. Opening an entirely new can of worms in order to fulfill "expectations" is best avoided. In fact I would suggest that avoidance is imperative.
0 -
Hi SFA,
My more recent shoots or trips reside in a session, I work on them (culling, keywording, editing) etc.,; some I finish, some I don't finish yet, some may be untouched for more than a year, but after some time let's say a few months, I want to incorporate them into my catalog. I will continue to select some and edit in the catalog.
Thing is, I still would like to be able to edit them in my session e.g. on the notebook and easily synch the later edits to the catalog. And maybe vice versa, from the catalog to the session, which can be easily done if all edits resided in sidecar files as they have a modification date and have small file sizes.
In addition, I don't trust catalog databases too much, and especially not the C1 catalog.
EDIT:
It keeps forgetting one or the other folder with images on occasion, I have had a look into the database a few years back to solve an issue and it looked like made from a developer who has no glue about database design, and there is still a bug mentioned in every release notes from C1 since half a decade or so: quote: "Importing a catalog can result in the last picture not getting imported."
I trust sidecar files though. And I need catalog functionality. And I work on older images across several years, e,g. for a series of prints or a photobook.
And, even the open source software darktable has a catalog but edits are stored in sidecar files. Sounds straight forward, no?
Not in the world of C1, two concepts unlovingly connected with an import function. Once imported the connection is broken.
If you see the sessions only as archives, fine, my way to work differs, and sessions with a catalog on top would serve my purpose, I cannot speak for other users (as you cannot either).
0 -
SFA, my last sentence might have sound a little harsh, which was not my intention.
0
Post ist für Kommentare geschlossen.
Kommentare
9 Kommentare