Jump to content

Matt H

Members
  • Content count

    9
  • Joined

  • Last visited

  1. Gotcha, thank you! I guess I had missed the earlier discussions.
  2. Normally I use the Extreme level of the denoise filters to add a certain subtle effect to some of my photos. Anyway, it will be missed...
  3. Ah, this is on a v1.6 afphoto file, indeed. However, I also do see the massive screen glitch for a brief moment before the crash. (I left Metal compute enabled.) Also, can you say what happened to the Extreme denoise sliders? They seem to max out at 100% now in 1.7.
  4. First question: What happened to the "extreme" denoise sliders? Second question: I am able to cause Affinity Photo to crash repeatedly by loading a file, selecting a nested (?) layer, then Filters -> Noise -> Denoise..., then selecting the parent layer. AP immediately crashes. *boom* I've attached a macOS diagnostic from one of the crashes. bug_report.txt
  5. I'm also experiencing slowdowns when using inpainting and selection refinement. Isn't Metal supposed to be faster? Why does turning it off improve performance?
  6. Matt H

    [APh] Content aware crop!

    I'd like to +1 this suggestion. Not every tool is always useful (even inpainting or clone) -- I think seam carving can be useful sometimes. In fact, I have quite a few photos that would benefit from it. Here's a new implementation of it in Go: https://github.com/esimov/caire -- and goes to show that there is still demand for and interest in this algorithm. And remember that this isn't just for cropping: it's also for expanding, which is the part I would find exceptionally useful. Little anomalies could be fixed up with clone or inpainting tools and similar. I do hope you'll consider adding this Affinity Photo. It would make it a highly competitive feature.
  7. That does work! It only took about 10 seconds that time. Thank you. Do you know why my initial attempt was causing it to go on forever? (I finally killed it after 45 minutes.) Even when I rasterize the layer and do a smaller selection, the bug still manifests (either it goes on forever or it doesn't do any inpainting). It seems the trick is to select the entire transparent area. Another quick question: why is rasterizing a layer that's already a pixel layer necessary? Thanks again, and sorry for the trouble, if this wasn't in fact a bug. (I bought Affinity Photo yesterday and am quite happy with it in every other way so far.)
  8. Sure thing; however, because it's a production photo, I will send you the link privately, including a screenshot of how to trigger the bug (please do not distribute the files). I will be happy to send this to any Serif staff who are looking into this. Just let me know. Thanks!
  9. Really enjoying my trial so far, and looking to buy in the next day or so if we can fix this. I'm following the video in this post: Unfortunately, going to Edit -> Inpaint results in spinning all CPU cores for about 5 minutes, then spinning 1 core after that for... well, it's still going about 15 minutes later: I'm on macOS 10.13.2. I tried it on small regions of about 1000 sq. pixels and it finishes quickly but leaves the area unchanged. Is this a bug or am I doing it wrong? Thanks, Matt Edit: Okay, so on smaller areas the best I've gotten is this (I would expect the selected region to be entirely filled by extending the blue part on bottom - look at the weird shape):
×