Skip to main content
D
Dewcal
Known Participant
February 15, 2012

P: 16 bit calculated masks show artifacts

  • February 15, 2012
  • 7 replies
  • 272 views

16 bit calculated masks - issue of random squares on mask that destroy effectiveness.

Am using CS5 v12.0.4 64bit ona Win 7 64bit Ultimate PC with 12Gb RAM. I do not believe the problem is only one of display.

I started with a 16bit RGB image and my detailed workflow was - I only had a background layer -

Image | Calcuations | Source 1 channel = Gray | Source 2 channel = Gray | Blending | Screen (Overlay also shows issue but this image was too dark for good demo) | Result = selection

I then

Image | Calcuations | Source 1 channel = Selection | Source 2 channel = Selection | Blending | Screen | Result = selection or new doc or new channel

If you choose new channel, you see an alpha channel witht hese random squares where the mask is not applied correctly.

However, if you "result" the first calculation as a "New Channel" and then recalculate you do not see the issue.

    This topic has been closed for replies.

    7 replies

    J
    J453
    Legend
    February 4, 2015
    Fixed in CS6 or later.
    F
    FeedbackCommunityMember
    Inspiring
    February 21, 2014
    That would be Photoshop CS6.
    D
    DewcalAuthor
    Known Participant
    February 15, 2012
    Thanks Chris, any idea on timing or is that a state secret?
    F
    FeedbackCommunityMember
    Inspiring
    February 15, 2012
    This will be fixed in the next major release.
    D
    DewcalAuthor
    Known Participant
    February 15, 2012
    Brett, Chris,

    Many thanks for such prompt response - will be appreciated. My objective with double calculations is to try and refine the masks - possibly could do similar with levels but find multiple calculations easier to fit into actions etc.

    Assuming fixed code passes testing, how will users get this update / fix?

    Thanks again.

    Dave
    F
    FeedbackCommunityMember
    Inspiring
    February 15, 2012
    Yep, there were code paths where the depth of the selection, source, and destination weren't all matched.
    I just fixed it and sent it off for testing.
    Brett N
    Adobe Employee
    Brett N
    Adobe Employee
    February 15, 2012
    I've tested your workflow and see the same behavior... very strange. I'll let the engineering team know.

    By the way, out of curiosity, what are you trying to accomplish with this workflow?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices