Older sessions will not often be updated to match new versions since they are sitting in what are effectively archives. Older sessions had multiple copies saved as backups to multiple external drives. They are often moved form where they were to somewhere else - most recently to a NAS. I work almost exclusively in Sessions - I prefer that concept and have always disliked Catalogue constraints since LR V1 was released. Would the ability to synch cos and comask have real value for a mass of users? Lightroom is okayish now and I am sure C1 will eventually get there as well. But for most day to day use of pano stitching an all raw workflow would still be very desirable. 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. 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 are really curious about it you could look up Helmut Dersch vs IPIX, or GoPro kills Kolor. 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. 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. 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. 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. have you ever heard of the Pareto principle and how it applies to the development of software? I don't think the distinction between professional and non-professional is all that helpful in photography.Ī 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).īut 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. Six month ago, I ask on the forum what's the core business of CO1 ? Public or Professional. Let's hope this is not the case for HDR and pano. Yes, even open-source app darktable has a catalog AND (optionally) sidecar files.Ĭ1 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. But Catalog is a very fine DAM ! And working with session is very reliable and fast ! 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.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |