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

Distortion from use of whibal dropper after lens correction

Bill
I've found an interesting anomaly with C1 5.0.1, P65+ and the new Schneider 80 mm LS lens.

If I use the lens correction tool and choose the 80 mm LS, all is well and one can see the correction take place. If I then use the dropper tool to select a neutral area for white balance correction, severe pincushion distortion occurs!

However, if I select the white balance first, and use the lens correction second, there is no problem. So the moral is - correct white balance first and the lens later.

I'd be interested in anyone else's experience. I'm using Mac computers and it's the same on each of them.

Bill
0

Comments

6 comments

Date Votes
  • Drew Altdo
    Bill,
    We haven't heard from anyone else in regard to this issue.
    Have you created a support case and can you provide us examples?
    0
  • Bill
    Drew, I have informed my dealer, Walter Borchenko, who has replicated the problem and is apparently taking this up with your colleagues.

    If you have one of the lenses listed in the Lens Correction Tool, I'm sure you can replicate the problem too. Just use the tool first, and then go to the White Balance Dropper and use it on the frame you've just corrected. The frame distorts quite severely.

    However, the problem does not occur if you correct WB first and then use Lens Correction.

    Happy New Year!
    Bill
    0
  • Drew Altdo
    Bill,
    Please create a support case so the issue can be addressed and logged properly.
    0
  • Bill
    [quote="Drew " wrote:
    Bill,
    Please create a support case so the issue can be addressed and logged properly.


    I have done so, Drew!
    Bill
    0
  • Drew Altdo
    Bill,
    Thank you. We've looked into the issue and there is certainly something there. We will bring it to the programmers attention and hope to address it in the next release.
    0
  • Bill
    I'm pleased to note that 5.1 has successfully addressed this issue!
    It is an issue no more - thanks, P1!
    Bill
    0

Post is closed for comments.