Skip navigation
Currently Being Moderated

Weird Crop tool behaviour with 16-bit files

Jun 1, 2012 2:38 AM

Tags: #image_rotation #photoshop_cs6 #background_noise #crop_tool #16-bit

Shadow areas of my 16-bit files show strange patterns if I use the Crop tool to rotate. I can also replicate the problem by doing the following:

 

Make a new empty 16-bit file in PS6 in RGB mode (File>New). Fill it with 100% black. Use the Crop tool and rotate to taste. Press Enter to accept the crop and zoom in to enjoy the black and grey noise patterning reminiscent of a man's suit. The Straighten tool will achieve the same result. Your suit pattern will vary according to the degree of rotation.

 

The problem goes away if you subsequently convert the file to 8-bit, or convert to any other mode (Greyscale, Lab, CMYK).

 

This patterning is easily visible at 100% view or less, and appears whether the View>Show>Pixel Grid option is on or off. It is decidedly NOT the pixel grid I am seeing.

 

This effect can be created with files from both my Canon and Hasselblad cameras.

 

I'm using a Mac Pro with OS10.6.8.

 
Replies 1 2 3 Previous Next
  • Currently Being Moderated
    Jun 1, 2012 9:39 AM   in reply to erickellerman

    Which version of Photoshop are you using?

     

    And which options for the crop tool?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 4, 2012 10:18 AM   in reply to erickellerman

    Which GPU are you using?

     

    We'll have to investigate a bit more to isolate the cause.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 25, 2012 5:53 PM   in reply to erickellerman

    We have not been able to reproduce this problem.

     

    But it could be something about your video card or driver version.

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 25, 2012 6:08 PM   in reply to erickellerman

    It would be good to get more detail about what version of the driver you have.

     

    In Photoshop do Help - System Info, copy, then post the info here.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 1:24 AM   in reply to erickellerman

    I'm using a Radeon 4870 here at home, with MacOS 10.6.8 -- and cannot reproduce those artifacts.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 7:19 AM   in reply to erickellerman

    I assume I'm the affected user Eric is referring to with the Radeon HD 5800. I am running Windows 7 64x on an 17-2600 machine with 12GB RAM. The video-card driver is version 8.961.

     

    This problem has rendered the crop and tilt function on CS6 more or less useless to me at present. It seems to be some kind of interference effect, because, for me, the patterning is remarkably uniform - long, intersecting lines very much like a ghost tartan watermark on the image. The attached image shows the patterning at 500%. This occurred on a 16-bit image after a minor crop and tilt. It is only really visible when zoomed in, but is definitely burned into the image. I use GPU acceleration in Normal mode.

     

    Peter ReesCS6 crop pattern.jpg

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 7:47 AM   in reply to erickellerman

    Here's a weird thing:  I just opened the file http://www.erickellermanphotography.com/pattern.psd on my PC in Photoshop CS6 and it is perfectly black.

     

    I even added two extreme curves adjustment layers above the background.  There is no pattern there.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 7:50 AM   in reply to erickellerman

    Do you see a difference when you choose different settings in the Crop tool for [  ] Delete Cropped Pixels?

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 8:15 AM   in reply to Noel Carboni

    I don't know about Eric, but I don't have a Mac. Eric's pattern is certainly there on my screen, though. Oddly, when I select the pattern with the eyedropper, the info palette shows no difference in colour between the pattern and the background - both register as R0G0B0.

     

    The issue occurs whatever you select under Delete Cropped Pixels. Here's another weird thing though - I just noticed on a layered image (multiple image layers) that the pattern wasn't visible until I deselected the top layer - in other words, it only affected the background layer, although the two layers are nearly identical (one is sharpened).

     

    Peter

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 8:52 AM   in reply to erickellerman

    Seems to me it's a video driver issue then, and it may only be affecting your display when pixels extend beyond the boundary of the visible canvas.

     

    • I have an ATI Radeon HD 5670 with Catalyst 12.2 drivers (internally numbered 8.950.0.0) and don't see the problem.

     

    • Eric has an ATI Radeon HD 4670 with the drivers shipping with Apple's OSX 10.6.8 and DOES see the problem.
    • Peter has an ATI Radeon HD 5800 with Catalyst 12.4 drivers (internally numbered 8.961) and DOES see the problem.

     

    My conclusion is that it's a problem recently introduced by ATI.  This is not surprising, their recent driver versions have not worked well with Photoshop.  The last good version was Catalyst 12.2.

     

    Eric, you pretty much need to wait on Apple to provide new drivers with an OS update.

     

    Peter, you could either uninstall Catalyst 12.4 and drop back to 12.2, or you could move forward to ATI's 12.6 beta version.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 12:32 PM   in reply to Noel Carboni

    The artifacts are in the transparency channel, not the color channels.

    Layer -> Layer Mask -> From transparency to get them into a visible mask

     

    They do look like interpolation artifacts (like something used low precision math for the transparency channel).

     

     

    But I still can't reproduce that on my system with Photoshop CS6 (10.6.8, Radeo 4870).

      Chipset Model:          ATI Radeon HD 4870

      Type:          GPU

      Bus:          PCIe

      Slot:          Slot-1

      PCIe Lane Width:          x16

      VRAM (Total):          512 MB

      Vendor:          ATI (0x1002)

      Device ID:          0x9440

      Revision ID:          0x0000

      ROM Revision:          113-B7710C-176

      EFI Driver Version:          01.00.318

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 2:30 PM   in reply to erickellerman

    You PSD is what I was referring to -- it's an example of artifacts in the transparency channel.

    The artifacts are already present in that file, so I can't use it to reproduce anything.

    I need to know how to get the artifacts to start with.

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 2:46 PM   in reply to Chris Cox

    Chris, when I look at the pattern.psd file Eric posted, there are no artifacts.  Not even in the transparency channel.

     

    Honest!

     

    It must be something that's happening to the file when being opened on your particular system.

     

    I did a Layer - Layer Mask - From Transparency, copied the mask, and pasted it as a new layer.  It's pure white.  The histogram says so and two layers of extreme curves adjustments say so.

     

    The artifacts are NOT present in that file!

     

    Edit:  Scratch that.  I went through it again and saw something different.  Eric, did you update the file at the link posted above?

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 2:52 PM   in reply to Noel Carboni

    It's a 16 bit file, and the errors are small.

     

    Open patterns.psd, Layer -> Layer Mask -> From Transparency, option/alt click on the layer mask to show it, Levels and change the black point to 245, commit the levels adjustment, now repeat the same levels adjustment and you should see the artifacts.

    The errors appear to be in the least significant 2 bits of the result.

     

    But resampling solid white should always result in solid white -- so something when wrong before we saw that document.

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 2:58 PM   in reply to Noel Carboni

    I probably made a mistake the first time somehow in processing the image.  Here's what I see.  The curves layers are as extreme as they can be.  Looks like maybe a 1 or 2 level error in the 16 bit data.

     

    PatternShowing.jpg

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 3:00 PM   in reply to Noel Carboni

    And that's exactly what I'm seeing.

     

    The file is already dirty because of those artifacts in the transparency channel.

    Something happened to the file before we saw it to cause the artifacts.

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 3:16 PM   in reply to Chris Cox

    Chris I've been able to reproduce the issue in a new document.  Here's how:

     

    • File - New, 400 x 300 px x 96 ppi, 16 bits/channel, Transparent
    • Set foreground color to pure black
    • Bucket fill
    • Choose Crop Tool
    • Uncheck [  ] Delete Cropped Pixels
    • Click the Straighten Button
    • Drag a line across the image right and upward until 5.0 degrees is indicated.
    • Complete the crop.

     

     

    This reproduces the problem whether a Grayscale or RGB image is created.

     

    I'm thinking another inaccuracy is making this ultra slight transparency error visible on some GPU-accelerated modes with some drivers.

     

    -Noel

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 3:06 PM   in reply to erickellerman

    Eric, normally you would not expect to see a 1 or 2 level (out of 32768) transparency difference on-screen.  I suspect your particular drivers are showing that where others are not because of an error unrelated to the transparency channel glitches.

     

    There are just bugs all over this windshield! 

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 26, 2012 3:18 PM   in reply to Noel Carboni

    It looks clean because the error is very small (4 / 32768).

    But something is making it more visible on your system, and so far I haven't gotten it to be visible without using two extreme levels or curves adjustments.

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 26, 2012 3:26 PM   in reply to Chris Cox

    FYI, the transparency channel gains the same minor transparency glitches with just Image - Image Rotation - Arbitrary.

     

    Note that these glitches don't really look like what Eric and Peter are seeing.  That *could* be another issue entirely.

     

    -Noel

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 27, 2012 6:06 AM   in reply to Noel Carboni

    I will add my observation on the unexpected behavior of the transparency channel. While I do not see the behavior noted in the original posting, I do see the transparency error reported by Chris and Noel. It is only present in 16-bit mode and only with  my graphics processor turned on ( Nvidia 9600 GT, CS6). 

     

    In my case I see someting not yet mentioned. I can readily see the error on the display, which should be displaying pure black (Fill canvas with black, crop tool, rotate). It appears to be an error of a few percent on the display so if the calculation error is in fact only two LSBs in the mask data, then it appears as if the higher & lower order bytes are switched in writing the transparency channel ....... or some other error.

     

    Paulo

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 27, 2012 10:47 AM   in reply to Paulo Skylar

    Paulo - can you get a screenshot of what you're seeing?  I'm starting to suspect this is a display pipeline error, but it may only happen in certain circumstances (which I haven't yet reproduced).

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 27, 2012 11:06 AM   in reply to Chris Cox

    Here are  screen shots at 100% magnification.  The canvas was 100 x 100 pixels and using the crop tool I "straightened" the image by 40 degrees (if I remember correctly) - different angles yield different patterns, of course.

    Capture.PNG

     

    Here is another view with a levels adjustment

    Capture3.PNG

    I had a medium, blue transparency  grid, which can be resolved.

     

    Paulo

     
    |
    Mark as:
  • Noel Carboni
    20,917 posts
    Dec 23, 2006
    Currently Being Moderated
    Jun 27, 2012 11:16 AM   in reply to Paulo Skylar

    I'm only barely seeing the pattern you are seeing in the first of the two images you posted, Paulo - it looks almost perfectly black from here.  If I work at it I can just barely see the pattern, especially if I zoom in.  Looks like just a 1 or 2 level shift above pure black in that image.

     

    It occured to me the appearance / absence of this might just be differing responses to very dim level changes with different display systems, so I purposefully reproduced the issue and did a screen grab, but nope - I'm still getting a perfectly black display.  I think Chris must be right - something not right in the display pipeline on only some systems.

     

    -Noel

     
    |
    Mark as:
1 2 3 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points