Greyfox

Seems to be working here also - Windows 10 Pro. Not nicely colored as with the Mac though.

I can confirm that if Windows 10 default application for TIFF is set to Affinity Photo, and the output of Vuescan Pro to TIFF, then at the completion of the scan, the image will automatically open in Affinity Photo. My preference however is to have Windows 10 default application for all images set to my DAM software, and to use Affinity Photo as an external editor from that.

Peter, I've downloaded both your .afphoto files. I've zoomed the "After _straightening" one 400% and I can't see what I would call jagged lines. Using the "Before_straightening" one, I've also done a straighten here using the straighten tool from the crop menu, and again at 400% zoom I'm not seeing the problem. My monitors are 1920 x 1080, and my graphics card is a nVidia GTX 1050ti 4GB. Windows 10 Pro (1903) Maybe I'm missing something, sorry.

It looks like you are painting with the Color Replacement Brush Tool in the left side screen shot, and the Paint Brush tool in the right side screen shot. I'm not sure whether that was intentional. If it was, then because you have the Color Replacement Brush hardness set to 0%, the initial stroke has soft edges. When you try to cross over that stroke, with the Color Replacement Brush tolerance set to 10%, it will not paint over the soft edge. If you set the tolerance to 100% it will.

Your screen shot is correct for the current version 1.7.2.471 Vignette is now found under New Live Filter Layer->Colours->Vignette

You could try a reset Hold down the Control key while starting Affinity photo. When the Clear User Data dialogue appears, the top three items should be ticked. Click on the Clear button at the bottom of the dialogue.

4EverMaAT, I don't know what operating system you are using, however if it is Windows, Arial Black has been a system font with all versions of Windows, so as DWright has said, it should be there, however all Windows versions since 3.1 have included "Courier New" (from The Monotype Corporation), not "Courier". If I remember correctly, "Courier" was a Postscript font used by Adobe and IBM, which Microsoft chose not to licence for Windows. Again, if your operating system is Windows, there were reports of some of the fonts, and in particular Arial variants, including Arial Black, not being present after upgrading Windows 10 from Windows 7. If your system is Windows 10, then check C:\Windows\Fonts, and see whether Arial Black is in the Arial folder. Are you by any chance using a font manager?

Chad, Does the problem occur if you work in RGB 8 bit instead of RGB 16 bit ? What are your renderer settings (Edit->Preferences->Performance->Renderer) ?

So having modified my test to exclude the export process, I've been able to get a reasonably clear comparison between a crop resample and a set of document resizes using the various resample methods, and that leads me to believe that the crop resample method might actually be Nearest Neighbour. !!! My test: My source image was a yellow filled triangle with a black outline on a 600px x 600px white background, produced in a vector drawing package, and exported as a 600px x 600px 300DPI uncompressed 24 bit TIF image. I've attached that image for reference In Affinity Photo I up sized the image by 10 to 6000px x 6000px leaving the DPI as 300 using each of the resample methods. I zoomed each resized image immediately after resizing to 122.2%, positioned the view so it showed the peak of the triangle and took a screen shot, then put the screen shots together for comparison. The simple triangle image makes it easy to see the difference in resampling methods on this type of image. The crop resize most closely matches the Nearest Neighbour resample. Triangle 600x600.tif

Yes, that would be helpful. Having done some tests, my thoughts are that it wouldn't seem to be Lanczos 3 Non-Separable, simply because using the same source image, a resize in Document Resize using Lanczos 3 Non-Separablen is taking far, far longer than the same resize using crop resize. I had thought a comparison would be relatively simple, just do the same resize to the same tiff source image using the different resampling methods in Document, Resize, and also a Crop resize, export each result as a non compressed tiff and compare the exported images at 100%. Unfortunately, it seems to me that the resample type used in the Export process is having an effect, even though I'm not making any changes to the pixel size in the export process. Not sure why that should be.

DWright, carl123, Thanks for the response. As a result I have now been able have my custom categories show at the top of the list when I open it. Thanks also for the information about the upsizing/downsizing method. Will be interesting to compare a resize using crop with a resize using one of the Lanczos options in Resize Document.

Possibly there has been an answer to these two questions. I've looked but so far haven't found. 1. When I use a Resample crop, what resample method is being used eg. Bicubic, Lanczos 3 Non-Separable, Lanczos 3 Separable or something else.. 2. Having created a couple of custom Crop preset cateagories, they appear at the bottom of the preset categories list, and I have to scroll down each time to get to them. Is there a way I can get my custom crop categories to appear at the top of the preset list. (I realize that if I just select None for each preset then theyt will appear at the top of the list)

The image in the .zip file appears to be a Motion Panorama image from a (Samsung Galaxy S7 ?) smart phone, rather than a standard static .jpg. It does indeed cause Affinity Photo to crash back to desktop when opening it, and it also has that effect on Topaz Studio 1 and Studio 2, so obviously they all have issues with that format. It can be opened by ACDSee Photo Studio and by FastStone Editor, but they display it as a static image, not a Motion Panorama.

As can be seen from the screen shots comparison below, it is removing a significant amount of the color noise here in Affinity Photo 1.7.2.471 on Windows 10 Pro. This particular comparison was made using Layer->New Live Filter layer->Noise->Denoise.

Chris, What I've found is that if I freehand down the line a short way, and then move left off the line and slightly back up (so the pink section looks something like a tick, (as shown in the screen shot attached), I can get the "hang" to occur nearly every time. The other thing I've found is that the "hang" is not actually terminal - if left long enough it does actually complete, but long enough has sometimes been in the order of 184 seconds.