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. ⚠️

Can I disable auto lens correction?

NFGphoto
Since I picked up C1 I've done all my shooting with primes. Last night I took my 24-70 out for an event, and to my great dismay, C1 is auto-cropping and auto-correcting all the shots taken at the wide end. The correction I can probably live with, but the auto-cropping is driving me insane. Instead of:

1. Select picture
2. drag crop region
3. goto 1

I've now got to:

1. Select picture
2. Navigate to half invisible (dark night-club images) crop area corners, or tiny slivers or pixels on the outside edges
3. resize or draw new micro-crop area
4. draw the crop area I really want
5. goto 1

It's maddening, and I can't figure out how to make it stop. I've got several hundred images to tweak, and this is a pretty serious hit to my productivity.

Any suggestions?
0

Comments

8 comments

Date Votes
  • Ian Wilson
    Moderator
    Top Commenter
    Does it work to select all the images, make sure that the button for edit selected variants rather than edit primary variant is selected in the toolbar, then on the lens correction tab select Generic in the profile tab? I presume that would turn of the lens correction for all the images in one go.

    Ian
    0
  • SFA
    In terms of editing out the auto corrections I assume that V7 is much like V6 in temrs of the core tools, so ...

    Select your problem images and go to the Crop tools tab.

    You probably don't have any Keystone corrections in place but they can be contolled form the tools in the tab anyway if necessary.

    You can undo the crop and any rotation settings directly in the tool involved, either for a single image or all selected according to the toggle Primary/All variants previously mentioned above.

    In terms of visibility you can also change how the crop mask displays. Making it lighter for your dark images may help not matter how you are processing them - auto or manual. Maybe save the settings to a specific Workspace for future re-usability?

    Does this help at all as a production aid?


    Grant Perkins
    0
  • NFGphoto
    The lens correction does not seem to apply to multiple shots when more than one is selected, regardless of the primary/all button status. I selected two images and changed the lens between generic and the 24-70mm I used, and only the active image changed appearance, the other selected image did not. I clicked the one/all button and tried again, but the results were the same.

    Alas. =/
    0
  • Paul Steunebrink
    In the Lens Correction tool, you can the Distortion slider to 0% to remove the crop.

    If this works successfully for you, you can make a preset. I made one named "Distortion 0%". Next, you can apply the preset to all selected images you imported or opened earlier. Next, you can apply the preset during import to have this applied always automatically (Import dialog, Adjustments section, Styles drop-down field).
    0
  • NFGphoto
    Ah, a preset might be the go next time. Thanks for the suggestion Paul.

    I wouldn't mind the anti-distortion being applied, I just wish it wouldn't crop for me. It's already hiding the lost areas from view, the cropping is unnecessary.
    0
  • SFA
    NFG,

    I used to think (CO6) that the auto crop suggestion was annoying but in fact decided that if I was about to crop anyway it made no real difference to me whether I modified the suggested crop or started a new one.

    There is a setting (that I hardly ever use) in the CO6 crop tool to Crop Outside Image. Intended, I believe, for use when sending to PS or some other application that can "fill" the empty areas. Is this 'sticky' in a preset? I have not checked, maybe Paul will know.

    Even if it is I guess you still have a "crop" to deal with since the application, logically, needs some way of outlining the edges of the (now modified for screen presentation) file. The alternative would be to leave the output as some sort of random shape I suppose.

    I would still encourage you to investigate the options available to you in the preferences for the crop tool to find an enhanced way of working with the tool as it presents itself currently n order to gani immediate improvement for you needs.


    Grant Perkins
    0
  • NFGphoto
    [quote="SFA" wrote:
    I used to think (CO6) that the auto crop suggestion was annoying but in fact decided that if I was about to crop anyway it made no real difference to me whether I modified the suggested crop or started a new one.


    Except that, as I stated, it's a massive hit on my speed. Dragging a new crop where I want it is massively faster than adjusting an existing one. I've taken to clicking outside the cropped area, dragging a tiny crop and then doing the real one. It's stupid.

    [quote="SFA" wrote:
    There is a setting (that I hardly ever use) in the CO6 crop tool to Crop Outside Image.

    Possibly, but it won't have any effect on current behaviour, nor will it solve the problems I've described. Mostly this would be handy after a rotation. In my case the lens corrections are very minimal, so the area I'm losing to it is tiny.

    [quote="SFA" wrote:
    Even if it is I guess you still have a "crop" to deal with since the application, logically, needs some way of outlining the edges of the (now modified for screen presentation) file. The alternative would be to leave the output as some sort of random shape I suppose.

    Well, this is sort of an extra layer of irritation. C1 already hides the introduced areas resulting from the distortion correction. ie: when it has to bow the edges inwards, it fills them with white and hides them from view. You CAN view them with the appropriate checkbox, but normally you don't see it, and it's not important for the purposes of this discussion. C1 crops well within this adjusted, hidden area so that I'm losing more pixels than the adjustment itself would require. 30 pixels on the long side are lost, 50 pixels on the short side. That's 127k pixels on the long side, 141k on the short side.

    So the failures here are starting to cascade:
    - It's correcting something I don't want corrected
    - it's adding a crop I didn't ask for (and which isn't strictly necessary if it's already removing from view the adjusted areas, let's just assume these are removed from 'develop' as well)
    - this crop is not maximized to the newly corrected image (for what reason I cannot even guess)
    - it's slowing me down having to adjust the crop I didn't want

    If any devs are listening, I'd be very happy if I could choose some options here. They should apply from the program level (ie: set once and it's always configured that way by default)

    1. Auto correct (or not) the lens distortion
    2. Auto hide (or not) the empty spaces created by this correction
    3. Auto crop (or not) the image at the edge of the corrected area or whatever mad logic is being used currently, since I guess it's probably the result of a logical decision making process. 😉
    0
  • SFA
    [quote="NFG" wrote:
    [quote="SFA" wrote:
    I used to think (CO6) that the auto crop suggestion was annoying but in fact decided that if I was about to crop anyway it made no real difference to me whether I modified the suggested crop or started a new one.


    Except that, as I stated, it's a massive hit on my speed. Dragging a new crop where I want it is massively faster than adjusting an existing one. I've taken to clicking outside the cropped area, dragging a tiny crop and then doing the real one. It's stupid.

    [quote="SFA" wrote:
    There is a setting (that I hardly ever use) in the CO6 crop tool to Crop Outside Image.

    Possibly, but it won't have any effect on current behaviour, nor will it solve the problems I've described. Mostly this would be handy after a rotation. In my case the lens corrections are very minimal, so the area I'm losing to it is tiny.

    [quote="SFA" wrote:
    Even if it is I guess you still have a "crop" to deal with since the application, logically, needs some way of outlining the edges of the (now modified for screen presentation) file. The alternative would be to leave the output as some sort of random shape I suppose.

    Well, this is sort of an extra layer of irritation. C1 already hides the introduced areas resulting from the distortion correction. ie: when it has to bow the edges inwards, it fills them with white and hides them from view. You CAN view them with the appropriate checkbox, but normally you don't see it, and it's not important for the purposes of this discussion. C1 crops well within this adjusted, hidden area so that I'm losing more pixels than the adjustment itself would require. 30 pixels on the long side are lost, 50 pixels on the short side. That's 127k pixels on the long side, 141k on the short side.

    So the failures here are starting to cascade:
    - It's correcting something I don't want corrected
    - it's adding a crop I didn't ask for (and which isn't strictly necessary if it's already removing from view the adjusted areas, let's just assume these are removed from 'develop' as well)
    - this crop is not maximized to the newly corrected image (for what reason I cannot even guess)
    - it's slowing me down having to adjust the crop I didn't want

    If any devs are listening, I'd be very happy if I could choose some options here. They should apply from the program level (ie: set once and it's always configured that way by default)

    1. Auto correct (or not) the lens distortion
    2. Auto hide (or not) the empty spaces created by this correction
    3. Auto crop (or not) the image at the edge of the corrected area or whatever mad logic is being used currently, since I guess it's probably the result of a logical decision making process. 😉



    In my case I decided that, mostly, I lost nothing in terms of speed from modifying a pre-set crop compared to adding a new one. However I don't expect everyone to have the same experience.

    Sounds like you would be best advised to open a Support Case for the request, that being the preferred way of managing some things within the C1 development and support teams. (Bear in mind that the forum, at least in theory, is for user to user interaction and it should not be assumed that suport and development people are active and responsive to the post here, even though sometimes they are.)
    0

Post is closed for comments.