Jump to content
You must now use your email address to sign in [click for more info] ×

Recommended Posts

I really have no good way to describe the issue that I am having other than uploading an image of the issue itself.  Basically, I am editing this photo and I keep finding random square pixels that become solid colors after I apply certain edits to the photo.  I started noticing the issue after applying some adjustments masks.  The issue became worse after I exported the image as a .jpg

Thank you for any help with this issue.

Screen Shot 2019-11-21 at 8.00.40 AM.png

Screen Shot 2019-11-21 at 8.00.48 AM.png

Link to comment
Share on other sites

21 minutes ago, markhartphotography said:

I started noticing the issue after applying some adjustments masks.

Which adjustments?

Can you provide the the .afphoto file (preferrably saved with the History), so we can see it for ourselves?

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

If you try to use the inpainting tool or the patch tool it will not patch over them, some of the squares also scale up and down as you zoom in and out. If you change the top layer to Hue you get to see a lot more.

Without the masks and adjustment layers it's hard to say why or what caused this, I think the only thing you can do is re process the original image and take notes as you apply each edit.

iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

18 minutes ago, firstdefence said:

If you try to use the inpainting tool or the patch tool it will not patch over them, some of the squares also scale up and down as you zoom in and out. If you change the top layer to Hue you get to see a lot more.

Without the masks and adjustment layers it's hard to say why or what caused this, I think the only thing you can do is re process the original image and take notes as you apply each edit.

That is a massive bummer. This looks like a big software issue to me. 
 

Link to comment
Share on other sites

@firstdefence

@markhartphotography

I too downloaded the file and have opened it multiple times in Affinity Photo.

Strangely the squares have not appeared here at all.

Out of interest, I saved it (saved as) to a new .afphoto file. The two files are not the same size. The original as downloaded is 1,067,703,979 bytes, the resaved file  1,060,711,600 bytes. I know "save as" will often reduce the size of the project file that has had repeated "saves", so the size difference probably doesn't mean much. More importantly, the squares don't show when the new file is opened either.

I using Windows 10 Pro  (1903, build 18362.476), Intel i7 processor, 16GB RAM, GTX 1050ti 4GB graphics card.

Affinity Photo 1.7.3.481.  Renderer set to Nvidia GeForce GTX 1050ti, Retina Rendering set to Automatic (Best)

 

 

Car.jpg

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Link to comment
Share on other sites

@Greyfox

Thank you so much for your help.  I also resaved the file, however Im still seeing the same distorted squares as the original afphoto file (see image attached).  The issue becomes worse when I save the image to a .jpg, as seen on the window in the post above.  

@Greyfox in the file that you saved do you see the issue on the front/grill as shown here?

The .afphoto has the issue on the front/grill of the car, when I export it to .jpg the issue is worse.  :(

 

 

Screen Shot 2019-11-21 at 5.40.47 PM.png

Screen Shot 2019-11-21 at 5.48.02 PM.jpg

Link to comment
Share on other sites

I don't think you've said what OS you're using, @markhartphotography, and (if Mac) what kind of computer and what performance options you've chosen in the Affinity Photo Preferences. That could be relevant information.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

16 minutes ago, walt.farrell said:

I don't think you've said what OS you're using, @markhartphotography, and (if Mac) what kind of computer and what performance options you've chosen in the Affinity Photo Preferences. That could be relevant information.

Thank you for your help @walt.farrell I am using a MacBook Pro. See attached stats.  I have not changed any performance preferences in Affinity photo.  I just downloaded it and started using it.  Also see attached performance settings from Affinity Photo. 

 

Screen Shot 2019-11-21 at 6.21.49 PM.png

Screen Shot 2019-11-21 at 6.24.15 PM.png

Link to comment
Share on other sites

I am definitely seeing the square glitches reported by @markhartphotography They are less prominent in the original .afphoto file, but in an exported .jpg they're glaringly obvious. This is a grab from my . jpg export:

208792353_Screenshot2019-11-22at00_52_55.thumb.png.e3dd34e50753a7dbaba766c233d2e598.png

 

I'm on a 2018 MacBook Pro, 32GB RAM, MacOS 10.15 Catalina, with an AMD Radeon Pro Vega integrated GPU (though I don't believe Affinity Photo is actually using the card - that's another issue...)

All very odd - the green glitch on the wing mirror in the export is red when I view all layers of the .afphoto file; some of the glitches in the .afphoto file appear and disappear depending on which layers are made visible. Converting to CMYK produces even more horrible results - dark blue squares all over the image. I've also tried merging all the layers down to one and exporting, but the problem persists.

I fear though that because of the way the original has been edited, there's little or no chance of working out when, why or how these glitches were introduced. There's no history, and all the edits on the individual layers have been made destructively (or flattened). There are basically five different images in one .afphoto document, and no way of telling which derived from which, or what edits were done on which. 

Hopefully someone from Serif will have an idea...

 

 

 

 

 

Affinity Photo 2.0.3,  Affinity Designer 2.0.3, Affinity Publisher 2.0.3, Mac OSX 13, 2018 MacBook Pro 15" Intel.

Link to comment
Share on other sites

9 minutes ago, markhartphotography said:

I want to know what to try differently to avoid this issue

It's worth taking some time to learn how to use adjustment layers. Apply these to the base image, using masks on specific areas if need be, rather than creating different versions of the same image in different layers. The official Affinity tutorial videos are excellent on this.

It might also be worth posting the original image out of the camera for others to take a look at...

Affinity Photo 2.0.3,  Affinity Designer 2.0.3, Affinity Publisher 2.0.3, Mac OSX 13, 2018 MacBook Pro 15" Intel.

Link to comment
Share on other sites

2 hours ago, markhartphotography said:

@Greyfox in the file that you saved do you see the issue on the front/grill as shown here?

If I zoom the image to around 430% then I can see the one below the grill, but nowhere near as pronounced as in your screen shot. It becomes pronounced if I untick the top Mural/Background layer.

However if I convert the format to either RGB/16 or RGB/8 then the issue becomes really obvious. Lots of colored squares (Red, Green, Blue, as well as what I could call a light magenta) all over the car and quite visible at 100% zoom.

 

 

Intel i7-10700 Gen10 CPU, 32GB RAM, Geforce GTX 1660 OC 6GB
Windows 10 Pro 22H2, 1x 1TB M.2 NVMe, 1 x 2TB M.2 NVMe. Affinity APh, APu, ADe

Link to comment
Share on other sites

There are numerous "invisible" NaN pixels in your APhoto file that correspond to the artifacts that appear in an exported JPG file and also relate to the respective RGB colour channel.

 

nans.jpg

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

*EDIT* Ah, of course. NaN pixels. I forgot about those. Thanks FirstDefence and Carl123.

Since the original image is unaffected, to me it seems Affinity added these when the original layer was copied and edited, or during another layer action. It seems to affect the darkest values, which leads me to think Affinity buggered up the conversion somehow. It is the first time I see these caused by a regular image editor.

 

Link to comment
Share on other sites

There are multiple apps that attempt to fix these NaN (Not a Number) pixels, generally they will fix single Nan's by using pixels around them, one such app is Blackmagicdesigns Fusion studio app, it has a node based method for processing images and video and in this post: https://forum.blackmagicdesign.com/viewtopic.php?f=22&t=35915 they talk about detecting Nan pixels with a tool called Detect gremlins the code for that is below.
 

{
   Tools = ordered() {
      INPUT = BrightnessContrast {
         NameSet = true,
         ViewInfo = OperatorInfo { Pos = { 176.206, 274.766, }, },
      },
      Detect_Gremlins = Custom {
         NameSet = true,
         Inputs = {
            LUTIn1 = Input {
               SourceOp = "Detect_GremlinsLUTIn1",
               Source = "Value",
            },
            LUTIn2 = Input {
               SourceOp = "Detect_GremlinsLUTIn2",
               Source = "Value",
            },
            LUTIn3 = Input {
               SourceOp = "Detect_GremlinsLUTIn3",
               Source = "Value",
            },
            LUTIn4 = Input {
               SourceOp = "Detect_GremlinsLUTIn4",
               Source = "Value",
            },
            Intermediate1 = Input { Value = "min(min(min(r1/r1, g1/g1), b1/b1), a1/a1)", },
            RedExpression = Input { Value = "i1", },
            GreenExpression = Input { Value = "i1", },
            BlueExpression = Input { Value = "i1", },
            AlphaExpression = Input { Value = "i1", },
            ShowNumber1 = Input { Value = 0, },
            ShowNumber2 = Input { Value = 0, },
            ShowNumber3 = Input { Value = 0, },
            ShowNumber4 = Input { Value = 0, },
            ShowNumber5 = Input { Value = 0, },
            ShowNumber6 = Input { Value = 0, },
            ShowNumber7 = Input { Value = 0, },
            ShowNumber8 = Input { Value = 0, },
            ShowPoint1 = Input { Value = 0, },
            ShowPoint2 = Input { Value = 0, },
            ShowPoint3 = Input { Value = 0, },
            ShowPoint4 = Input { Value = 0, },
            Image1 = Input {
               SourceOp = "INPUT",
               Source = "Output",
            },
            Comments = Input { Value = "Detects render errors (pixels with \"infinite\" float values). They are tinted red for debugging and the alpha channel is an error mask.", },
         },
         ViewInfo = OperatorInfo { Pos = { 301.735, 273, }, },
      },
      Detect_GremlinsLUTIn1 = LUTBezier {
         KeyColorSplines = {
            [0] = {
               [0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
               [1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
            },
         },
         SplineColor = { Red = 204, Green = 0, Blue = 0, },
         NameSet = true,
      },
      Detect_GremlinsLUTIn2 = LUTBezier {
         KeyColorSplines = {
            [0] = {
               [0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
               [1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
            },
         },
         SplineColor = { Red = 0, Green = 204, Blue = 0, },
         NameSet = true,
      },
      Detect_GremlinsLUTIn3 = LUTBezier {
         KeyColorSplines = {
            [0] = {
               [0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
               [1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
            },
         },
         SplineColor = { Red = 0, Green = 0, Blue = 204, },
         NameSet = true,
      },
      Detect_GremlinsLUTIn4 = LUTBezier {
         KeyColorSplines = {
            [0] = {
               [0] = { 0, RH = { 0.333333333333333, 0.333333333333333, }, Flags = { Linear = true, }, },
               [1] = { 1, LH = { 0.666666666666667, 0.666666666666667, }, Flags = { Linear = true, }, },
            },
         },
         SplineColor = { Red = 204, Green = 204, Blue = 204, },
         NameSet = true,
      },
      BrightnessContrast1 = BrightnessContrast {
         Inputs = {
            Alpha = Input { Value = 1, },
            ClipBlack = Input { Value = 1, },
            ClipWhite = Input { Value = 1, },
            Input = Input {
               SourceOp = "Detect_Gremlins",
               Source = "Output",
            },
         },
         ViewInfo = OperatorInfo { Pos = { 411.735, 271, }, },
      },
      OUTPUT = BrightnessContrast {
         CtrlWZoom = false,
         NameSet = true,
         Inputs = {
            Alpha = Input { Value = 1, },
            ClipBlack = Input { Value = 1, },
            ClipWhite = Input { Value = 1, },
            Input = Input {
               SourceOp = "INPUT",
               Source = "Output",
            },
            EffectMask = Input {
               SourceOp = "Bitmap1",
               Source = "Mask",
            },
         },
         ViewInfo = OperatorInfo { Pos = { 415.353, 350.34, }, },
      },
      Bitmap1 = BitmapMask {
         Inputs = {
            Invert = Input { Value = 1, },
            MaskWidth = Input { Value = 2048, },
            MaskHeight = Input { Value = 1556, },
            PixelAspect = Input { Value = { 1, 1, }, },
            ClippingMode = Input { Value = FuID { "None", }, },
            Image = Input {
               SourceOp = "BrightnessContrast1",
               Source = "Output",
            },
         },
         ViewInfo = OperatorInfo { Pos = { 415.353, 317.34, }, },
      },
   },
}

The app accepts PSD files.

iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.