Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Automatic (idiosyncratic) Lens Correction

Comments

66 comments

  • Paul Steunebrink
    Hi Ralph,

    I have seen this question here in earlier threads. I have experimented with a preset (or style) with the Distortion slider set to 0 (zero) and applied the preset on import or during tethering.
    0
  • ianmac
    Hi

    This is a really annoying behaviour - CO 7 should not apply corrections itself by default, this should be an option that the user selects if required.

    Now I am forced to create a Style that sets all the Lens Correction settings to zero (basically to cancel out any auto corrections that have been applied) and I have to remember to do this every time a batch of images comes into CO 7.

    More annoying is that when CO 7 does apply it's own corrections, it affects the output file size (even if you output at 100%) so you really can't afford to forget to cancel out the settings each time or your client could end up with different file sizes from the same shoot on the same camera...

    It seems a ridiculous way to have to work, Lens Correction should be OFF by default for all lenses and ONLY selectable if the user prefers..

    I have posted this to Support as a request for future versions.

    Ian
    0
  • Ralph Eisenberg
    I believe that I have as well quite a while ago but apparently to no avail. It is a regrettable and time consuming aspect of the program.
    0
  • Ralph Eisenberg
    Permit me to reiterate just how annoying, troublesome and wasteful of time this aspect of Capture One Pro is.
    0
  • Dave241
    [quote="Ralph" wrote:
    Permit me to reiterate just how annoying, troublesome and wasteful of time this aspect of Capture One Pro is.


    I think the obvious solution would be to have a "CHOICE" let the user decide if they want it on or off, I actually want it it on as a default, I don't like distortion 😲


    Dave...
    0
  • SFA
    I have no way to test this (No V7) but is there any potential for simply deleting the lens profiles (or renaming them or renaming the folder containing the profiles?)

    I appreciate it might cause problems so would need testing - or someone may already have tried this and have the answer - but for those who never want lens corrections it would seem like an obvious immediate solution to consider and put to a test.

    Later an on/off option would seem like a useful option to have.

    Currently I don't mind either way since my preferences, when it's an issue with any of my cameras, are variable and I tend to set values about "half way" between full correction and none. So neither on nor off would be ideal.

    (I could probably get used to "random" so long as I could set some upper and lowere limits that avoided all and nothing.

    😉 )

    Grant Perkins
    0
  • Ralph Eisenberg
    Resurrecting this thread as I feel this problem needs to be addressed sooner rather than later. If anyone concurs, please establish a support case with the suggestion that the default setting should be lens correction "OFF" and allow the user the option of instituting this feature as needed.
    0
  • ianmac
    Hi Ralph

    +1.

    I've already put in a Support Case and did get a response that they are aware of this issue.

    It HAS to be that Lens Correction is Off by default and only available if you specifically want it. To have it On by default seems crazy as you have to remember to remove the auto corrections - every time - before you even start working on the images. Extra work for nothing.

    Ian
    0
  • Ralph Eisenberg
    Hi Ian

    +1 to your +1 as well as to your addendum
    0
  • Nick64
    I've done the same thing and got a short reply that they have acknowledged the request. No guarantees I guess.

    -Nik

    [quote="ianmac" wrote:


    I have posted this to Support as a request for future versions.

    Ian
    0
  • Ralph Eisenberg
    Lets hope that our words are heard!
    0
  • Edward Caruso
    i too consider this a bad oversight on Phase One's part. there should be no auto correction going on - especially of any lens corrections. architecture and still life photographers usually shoot multiple frames of a shot to layer later in photoshop. any auto correction could possibly make those images out of register.
    0
  • Ralph Eisenberg
    Hello Edward51,
    It would be helpful if you would register a support case voicing your opinion as an increasing number of tactfully formulated requests might lead to an implemented response or at least an enhanced probability of some-such.
    0
  • Edward Caruso
    that's why we need a feedback tracker like I requested:
    viewtopic.php?f=46&t=13972&p=64682&hilit=feedback#p64682

    but not too many people helped to support it . . .
    0
  • Ralph Eisenberg
    Well it looks like automatic lens correction is still obligatorily imposed by the program (with its great demands on processing power) whether or not it is wanted by the user. I do have regrets that Phase One is not more responsive to user requests for what are considered workflow enhancing features which up to now had been a hallmark of the program. At present I would be inclined to add that sadly CO Pro v 7.1 is quickly becoming obsolescent in my Raw processing workflow, and I have been using it (although less and less by now) since v 1.
    0
  • Christian Gruner
    [quote="Ralph" wrote:
    Well it looks like automatic lens correction is still obligatorily imposed by the program (with its great demands on processing power) whether or not it is wanted by the user. I do have regrets that Phase One is not more responsive to user requests for what are considered workflow enhancing features which up to now had been a hallmark of the program. At present I would be inclined to add that sadly CO Pro v 7.1 is quickly becoming obsolescent in my Raw processing workflow, and I have been using it (although less and less by now) since v 1.


    I'm sorry that you think we don't listen to user request. I can tell you that we really do, also if we don't respond here on the user-to-user forum. However, changing something like the concepts of the lens distortion model is not something done in "no-time". There are a lot of steps that a change of this magnitude needs to go through.

    Please trust that we are intensely listening to all feature/change-request, but given our resources, we still have to prioritize.
    0
  • Ralph Eisenberg
    Thank you for replying. Making this feature optional (and off) by default has been a request submitted since automatic lens correction was first erratically and inconsistently deployed. There was no implication in this thread, or in a thread that appeared many months previously, either that members of the CO development team should immediately implement user feature requests or that they should get wind of these requests by constant reading of these forums.
    0
  • Christian Gruner
    [quote="Ralph" wrote:
    ... since automatic lens correction was first erratically and inconsistently deployed.


    I can assure that it is not inconsistently applied. We are using the distortion information from the lens profile coupled with a lot of other factors like focal length, sensor size and so on, to decide whether or not a given picture has too much distortion.
    So what seems random to some, is a very conscious decision based on hard facts.

    We are aware that the automatic applying of the correction is not ideal for some, and we are looking into possible solutions. That said, I can't say how or when for the time being.
    0
  • Ralph Eisenberg
    Thank you for your response.
    While I did not wish in any manner to diminish the extent of continuing work that goes into the development of CO Pro, the request for an optional preference setting allowing the user to determine whether or not the deployment of lens correction is to be carried out automatically or by user choice, has been voiced since the initial implementation of this feature.
    Your reply does highlight, however, another broader albeit tangential issue. A systematic, in-depth, user-paid third party program of instructional videos, much as Michael Reichmann has done for Capture One (but in greater detail) and especially for Lightroom, perhaps along the lines of Lynda.com, would be helpful. I've requested this for some time, regrettably to no avail. I'm quite sure that I would benefit from such an instructional program and become better acquainted with the many facets of CO Pro with which I'm insufficiently familiar. This would precisely allow me to have a greater appreciation of the extent of the work that has gone into CO Pro's development.
    0
  • Ralph Eisenberg
    Has there been any headway on this question ?
    0
  • oscarmeyer
    [quote="Ralph" wrote:
    Has there been any headway on this question ?

    Would really like to know that aswell..!
    0
  • Ralph Eisenberg
    This is just a respectful reminder that this issue would really benefit from Phase One's attention. I really would like to be able to use CO Pro as I have for the past decade (and then some), but this issue is an obstacle that has made such usage impossible. It has become all the more pressing with Adobe's new Cloud policies and their implications for end-users.
    0
  • Christian Gruner
    [quote="Ralph" wrote:
    Has there been any headway on this question ?


    This subject is still fresh in mind, but we cannot give any ETA's.
    0
  • Ralph Eisenberg
    Thank you for responding. While it is good to learn that remedying this issue is under consideration, it is not entirely clear to me why disabling lens correction and subjecting its implementation to user control as an option is so difficult to introduce into the program. Is it now almost 2 years, or perhaps more ?
    0
  • Paul Steunebrink
    [quote="Ralph" wrote:
    Thank you for responding. While it is good to learn that remedying this issue is under consideration, it is not entirely clear to me why disabling lens correction and subjecting its implementation to user control as an option is so difficult to introduce into the program. Is it now almost 2 years, or perhaps more ?

    Less. CO7 was released end October last year. Requests for change came in some time after that. Few months pending now.
    0
  • Ralph Eisenberg
    Hi Paul,
    Didn't this "feature" exist prior to V.7 ? Either way, it seems like a long, very long time since it should have been made optional.
    0
  • Paul Steunebrink
    [quote="Ralph" wrote:
    Hi Paul,
    Didn't this "feature" exist prior to V.7 ? Either way, it seems like a long, very long time since it should have been made optional.

    Hi Ralph,
    You could say that CO6 had a similar feature. However, only a few lenses were detected (Phase One/Mamiya stuff) and I am not sure that it was detected and applied automatically (indeed, CO6 seems a long time ago, while CO7 was introduced 25 Oct 2012).

    CO7's lens profiles for DSLRs was the trigger that brought the feature the attention of a larger audience, of which a part dislikes the automatic application.
    0
  • Ralph Eisenberg
    It does seem that, given the manner in which this feature had been implemented elsewhere, that the example of making it optional, with its application when desired under user control, might have been a more judicious path to follow. There is of course nothing critical implied in the above remarks about the sophisticated quality of its implementation in CO Pro.
    0
  • Ralph Eisenberg
    It would be worthwhile to have the application of lens correction as an optional feature under user control rather than automatically applied.
    0
  • Ralph Eisenberg
    Just a reminder that it would be nice to have this matter addressed !
    0

Post is closed for comments.