Jump to content


  • Content Count

  • Joined

  • Last visited

About HairyDalek

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
    Essex, UK

Recent Profile Visitors

711 profile views
  1. I tried it again, and not, couldn’t repeat it either using Metal. Is this something that needs to be traced from a new document? Do things “build up” over use, and cause problems (I don’t know how Affinity Photo works internally, so this is pure speculation).
  2. This is the file I was working on. Face.afphoto
  3. This image, when I load it into Affinity Photo, causes a crash. It’s a JPEG2000 image from what I can tell, and may be monochrome. Every time I load it, Affinity Photo on my Mac crashes. https://www.telegraph.co.uk/content/dam/radio/2017/05/05/3151783_Rex-Features_825926tg-Kenneth-Williams_trans_NvBQzQNjv4Bq5xq5nv8iaFaK36BUkx5Fvu7e3XZpZKPsZsEgdcIcEns.jpg?imwidth=1400 The link above is to the source of the image. 3151783_Rex-Features_825926tg-Kenneth-Williams_trans_NvBQzQNjv4Bq5xq5nv8iaFaK36BUkx5Fvu7e3XZpZKPsZsEgdcIcEns.jpg.jp2
  4. I’ve been munching about with some ideas in Affinity Photo, and I managed to cause this problem. As you can see, a lot of weird artefacts on the canvas. They seem to be transient - not party of the image, but they appear and shift around. What I have done is applied some envelope distortions to a layer, which has a mask, a blue filter and a recolour effect applied. When I shift the envelope distortion around, all these blocks appear around the image. They look wrong, bit I kind of like them in the spirit of the image and effect I’m aiming for. As well as the artefacts, you’ll notice rectangles of colour in the image. The face should be all red, and the background all blue. Instead, I’ve got this. I’m using Metal for this in Affinity Photo. Can't seem to reproduce on Open GL.
  5. Hi, every now and then, I get what appears to be odd flickering pixels in Affinity Photo (also, possibly Designer, but Photo is the one where I know I have seen it before). I’m seeing it on both my Macs - a late 2012 Mini and a 2013 MacBook Pro with a retina display. You can see the odd pixels in this screen shot - they flicker. It started this time when I had imported and placed another image in the file, and was dragging it to a larger size. I was using my Mac Mini for this. Those pixels are not part of the image - and they do go away after a while. Affinity is set to use Metal in the preferences. I have seen this before - areas become pixellated, or they flicker. The size/location of the flickering area seems to be random. I can’t knowingly trigger them either (if I could, I’d list steps to repeat).
  6. Oh, and I mean to add, an exported bitmap shows the problem too. It doesn’t seem to be a display issue, it appears to affect output.
  7. I found that, thanks. The numbers are still whole numbers. No decimals. However, if I nudge one element that is a x=9px and displays the problem to 8.955281 px, the antialiasing appears to go away.
  8. Hi, Done. I’ve uploaded a file called Truck 2.afdesign - if you zoom in on the right hand artboard, and switch on Pixel View, you should see the problem. It’s based on the file the screenshots were created with. Hopefully this problem can be repeated with this file at your end. Some elements are in groups, and if you manually move the elements just a little bit, the antialiasing vanishes, and the edges firm up to match pixel boundaries. The thing is, the movements needed are so slight that the numbers don’t change in the interface (zooming in is a big help here).
  9. HI, I’m using Affinity Designer, and using the pixel view option to make sure that there’s not too much pixel mis-alignment. I’m setting x and y coordinates to whole numbers to try to get rid of any vertical and horizontal antialisaing. The problem I have here is that an object of a solid colour seems to gain some vague transparency/antialiasing even when x and y coordinates are whole numbers. This is an dartboard, and the artboard’s coordinates are also whole numbers (I know this can have an effect on this as well). Screen shots show this, with an element butted up against the artboard left hand edge. The screen shots show the problem - look at the left hand column of blue/grey pixels. They should be the same colour as column to their right, but what seems to be happening is that something is making Designer antialias the edge, giving it a bit of a transparent look. In this case, there seems to be no way to solve this problem - dragging the edge out of the artboard bounds doesn’t fix this. I am also seeing a similar effect in other places - the coordinates are whole numbers (they have been typed in). I’ve have to manually drag the elements a little to the left or right (or up and down) to resolve the problem. It feels like there is some minor number rounding that’s causing elements to cross the pixel boundaries a little to just cause this. The second pair of screenshots shows an element at x position of 9px . There is some antialiasing to the left. If I just nudge the element a shave to the left, that antialiasing goes away. If I then type 9 into the x position in the transform palette, the object returns to the previous location and the antialiasing/transparency is back. Why is this a problem? Well, apart form not giving whole, solid, pixels, these objects are animated, and it seems that this small amount of transparency causes flickering as they move. I was hoping that if I typed a whole number into the transform palette that they would be bang on the pixel border, and not require manual adjusting.
  10. Thanks for the reply. EXIF data - the original image in this case doesn’t have much by way of EXIF data, as it was scanned. If I go to Edit>Resize Document, the correct DPI settings are there. It’s not in the EXIF panel. So, it seems that other than dimensions and the scanner manufacturer, there is little there to copy anyway. There have been instances where I have seen a transparent border on an image, but not just the left hand side, all of them. I’ve not been able to reproduce that today (always the way), but it was consistent and repeatable last week. The border looked about somewhere between 4-8 pixels across, and was added to the size of the image, so what was copied from the main document was correct, but extra padding added.
  11. HI, Got a 1200 ppi image that I want to crop down into smaller chunks. What I don]t want is the final documents retaining the full original image. So I’m trying the File>New From Clipboard option I have found some problems. 1 - Open an image (mine is a scan at 1200ppi) 2 - Using the Selection Tool, draw a marquee on the image 3 - Go to Edit>Copy (Make sure you have a bitmap layer selected) 4 - Go to File>New From Clipboard 5 >> First off, Affinity Photo reports this new image as 69dpi (should this be Pixels Per Inch?), not 1200 as the original is. The pixel dimensions seem the same, but clearly not all information is carried over. Secondly, if the image is already cropped: 1 - Open an image in Photo 2 - Use the crop tool to crop the image down a bit. Save, close, and reload the image 3 - Using the selection tool, select everything inside the crop window. 4 - Go to Edit>Copy (Make sure you have a bitmap layer selected) 5 - Go to File>New From Clipboard 6 >> You get a transparent border around the image.
  12. Done. I’ve uploaded some images from my Ricoh Theta, which takes equirectangular images. Of interest in those files is the Pitch and Roll data which can be used to level the photos. I currently do this via a script that uses Hugin’s tools, but if Affinity Photo could do that, it would be great.
  13. Weird, on my Mac Mini running Sierra, Metal is available. On my late 2011 MacBook Pro running High Sierra, Metal is greyed out. Turning on Integrated GPU doesn’t seem to make any difference. So grids work on the Mac Mini now, but not on the MBP.
  14. More experimentation, and I find this. If I change the angle of the y axis to -90, the grid lines up with the object drawn. Note - I’ve changed the x-axis to be 12 with two divisions, so I get a better idea of grid spacing. The problem still persists. Compare this to how the object appears when the angle is 90 degrees (it’s default state). The object top right was drawn using snap to grid, with the grid settings as the screen shot above. Notice that when the grid is at -90 degrees, things still do not snap to the lines (see yellow dot with the red marker). It’s almost as if Affinity is inverting either the drawing of the grid or the snapping each time! It’s starting to feel like a bug to me now.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.