Search the Community
Showing results for tags 'sharpness'.
Found 3 results
I’m sorry for the very long story, but I didn't find the way to shorten the description of noticed problem. My final steps of jpg image processing are cropping, usually to 16:9 proportions, resampling to 1920:1080 and sharpening using the filter best suited to the photo. Next I export the picture to disk again as jpg, using export command and don’t change the picture size during export. Unfortunately I noticed, that sometimes the saved pictures looked in Faststone (or any picture viewer) are softer, than before export, viewed in AP. It is particullary obvious on pictures containing many tiny, sharp details. The difference is not big, but noticable. It is annoying, because the final result is a bit unpredictable in terms of sharpness and can differ from what I got in the edition. I assumed, that as long as I don’t change the picture size on the export, the choice of the algorithm displayed in the export dialog box is irrelevant and it was left “Bilinear” by default. I was wrong. In most cases the results were the following: nearest neighbour – sharpest, bilinear – softest, Biqubic and Lanchos 3 Separable between them; Lanchos 3 Non-separable very oversharpened; What is weired, there are photos, which are not suffer from this phenomenon, but I could’t find any regularity. Trying to better understand it I did some additional tests: 1. I prepared exactly 1920:1080 picture in another software and opened it in AP, than exported it as is, choosing all algorithms from nearest neighbour to Lanchos 3 Non-separable. There was no difference between exported files - as expected. 2. I opened the jpg picture 4928x3264 (the original size from 16 Mp camera) and resampled it to 1080 high, getting 1630,6 width and: a. Exported it with no any change, getting different looking pictures, depending on the algorithm set in the export dialog box, as described above. I can eventually understand it: the width of the final picture (displayed in the export dialog box) is 1630 instead of the initial 1630,6, so perhaps there can be any role of the resampling algorithm. For confirmation I did the following: b. In the Resize Dokument dialog box I changed 1630,6 to 1630 (1080 hight left unchanged) and repeated steps from 2a), this time getting identical results for each exported file, despite of the algorithm. It can confirm the conclusion from the point above. It seems there is nothing wrong in the results of these tests, contrary to the normal workflow, described above. I hope I’m right posting this description in the Bug section, because there is something wrong from my point of view. I hope you will find the way to fix the problem and I will be able to stop worry about the final result of my processing. Best regards, Andrzej
Hi I am using Capture One for RAW, export either JPEG or TIFF and then further edit in Affinity (since yesterday - I am new to Affinity). However, when I edit perspective in Affinity to make verticals vertical , and then export as JPEG as 100% there is a significant loss of sharpness on the entire image. This happens regardless if TIFF or JPEG is edited. Any ideas why?
HI All, Curious if anyone has tried using the new 1.5 version with Fuji's X-Trans Sensor... I know sharpness is an issue with Lightroom. Is AP same, worse, or better with fuji raw files versus the big boys like Lightroom or Iridient Developer? Pros Cons? Thanks for the help.