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

antialias clone brush


Recommended Posts

I have a clean pixel image with flat colours. In the blend options the coverage map is flat-top, antialiasing set to force-off.

Yet when I use the clone brush with a new brush- hardness set to 100% opacity and flow to 100% - I get antialiased result.

Is there any way to get rid of this? Like in Photoshop you can set your general settings to always use nearest neighbour.

Thanks,

Onno

Schermafbeelding 2024-01-22 om 12.24.41.png

Link to comment
Share on other sites

Garry, 

I was hoping for a quick answer too.

The original file is client work, but I have another file, same setup, same results.

My guess is that it has something to do with the application. Or the tool.

Antialiasing also occurs when you have one-colour (say black)  pixel shape as a layer. 

Once you rotate that 90 dgs. there is the antalias again. Shouldn't be with this 90 dgs rotation.

camouflage-test.afphoto

Link to comment
Share on other sites

Thanks for the file.

I can see what you mean now – even with the “64 Round Brush” from the “Basic” Category, the edges always seem to have some kind of ‘smudging’ or blending/transparency.

I tried adding a new Pixel Layer, setting the Antialiasing for that layer to “Force Off” and trying again with the Source set to “Current Layer & Below”, but the same effect is there, although to a lesser extent.

I tried different Blend Options for the new Pixel Layer but can’t seem to get anything much better.

I also tried making my own brush from a rectangle of black pixels, just to see what happened, and still get the same thing.

I don’t know what to try next – there’s a chance that the Clone Tool simply wasn’t designed to do ‘entirely whole pixel cloning’ like this if it was created for photo touch-up where an amount of ‘smudge’/blend is normally wanted.

Link to comment
Share on other sites

Thanks Garry for the extensive answer. Every possibility covered!

The default idea behind Affinity Photo might indeed be photograpy.

Image creation goes beyond that. Too bad!

Thanks,

Onno

Link to comment
Share on other sites

1 hour ago, GarryP said:

if it’s not in the design of the software

If it's not a bug, then it's a major conceptual flaw:
All brushes should respect Force pixel alignment much like objects do. And in fact, they do, except for the brush border. 
Only the Pixel Tool does reliably and absolutely snap to integer pixels by definition, regardless snapping settings.

I was pulling out my hair on similar stuff before, already in v1. :/ 

1 hour ago, GarryP said:

a ‘trick’ that can be used.

  1. clone onto a new layer
  2. erase borders with the Pixel tool

or:

  1. clone onto a new layer
  2. Select → Alpha Range → Select Partially Transparent
  3. delete

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

Layer anti-alias settings impact vector layers only, and have no impact to pixel layers.

Pixel based brushes and tools always have forced anti-aliasing. You cannot deactivate it.

So when you use pixel brushes, you will get multiple levels of antialiasing and resampling atop of each other:

  • pixel brush anti-aliasing for every brush stroke inside any bitmap layer
  • Vector layers have anti-aliasing settings in blend options 
  • resampling settings (in performance settings for in-canvas rendering, in export settings for export, enforced with no method to avoid when using rasterize) like bilinear for rendering and export

 

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

8 hours ago, onno-r said:

Is there any way to get rid of this?

Instead of using the clone brush, you may use alternative methods:

  • make a gross selection of the rough area (larger) 
  • copy/paste the area
  • have snapping on with fore pixel alignment on, move by whole pixels off, other snapping off
  • add a mask layer to clone layer
  • use pixel brush to paint in mask or remove unwanted areas
  • Check that the mask is 100% hard (isolation mode)

 

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Another observation: on iPad, the clone brush has a fixed hardness setting of 80% which cannot be adjusted in the regular numeric input fields. 

Even when you choose a fresh square brush.

You need to enter the (formerly) „more“ settings by clicking the small brush preview icon in top row.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

In cas you are using the non-destructive workflow, you can repair the clone brush behavior:

  1. add a new pixel layer
  2. activate clone brush
  3. select a square brush. Set the brush to 1px size, 100% hardness (in „more“ / brush icon, not the numeric settings, set wet edges to off)
  4. set brush source to current & below
  5. choose source position
  6. paint in clone area
  7. when done, add levels adjustment to clone layer (masking position)
  8. choose alpha channel
  9. set black level to 50%
  10. set white level to 50%
  11. now the result is hard, the former soft edged get „repaired“ to hard edges. 

This works reliable as the brush anti-aliasing is only applied to outer edges.

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

Forgot to mention: on M1 based Mac, Levels on alpha is broken (unfixed bug). Use curves adjustment instead, choose alpha, set left node to 0.5/0.0, set right side to 0.5 / 1.0

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

42 minutes ago, NotMyFault said:

on M1 based Mac, Levels on alpha is broken (unfixed bug)

M2 too, obviously…

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

50 minutes ago, NotMyFault said:

Levels on alpha is broken

Speaking of which:
It's apparently only broken on Pixel layers.
If you convert the cloned layer to an Image layer, Levels alpha works.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

10 minutes ago, loukash said:

Speaking of which:
It's apparently only broken on Pixel layers.
If you convert the cloned layer to an Image layer, Levels alpha works.

Interesting, I did not spot that detail

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

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.