High Pass Filter bug perhaps?

[andersp5]

Not sure if this is a bug or not but it is very strange to say the least. 

Try this!

Develop a RAW (CR3 in my case) image in the develop persona but DO NOT apply any sharpening, but apply Colour and Vibrance, contrast and Brightness, to taste, some noise reduction but nothing else. Then develop the image.

In the Photo persona apply a high pass (live ) filter set to 0.5, monochrome ticked and choose Linear Light

Then duplicate the live pass filter which gives you two 0.5 filters. You should see a clear sharpening taking effect.

Keep the AFPHOTO file open

Now export the resultant image in JPG.

Then import the file you just exported back into AFPHOTO so you should have the original and the exported image showing in AFPHOTO.

Set both images with Control Zero so they are the same size and compare the two, switching from one to the other.

What I am finding is that the clarity and sharpness of the Exported image is noticeably less than the adjusted AFPHOTO image.

I thought it was because I was using JPG but I tried TIFF with no compression and then again with ZIP but the result was the same, there is a difference and I just don't understand why?

Shouldn't it save exactly the same sharpening that I am seeing on the screen? It doesn't appear to.

Anyone got any ideas why?

[Old Bruce]

6 hours ago, andersp5 said:

Set both images with Control Zero so they are the same size and compare the two, switching from one to the other.

This is most likely your problem. View at 100% instead.

[NotMyFault]

To say it in a more polite way: The effect of sharpening and noise filters (like unsharp mask, highness etc) needs to be reviewed at 100% zoom level (or integer multiples 200, 300, ...). Otherwise the rendering method mipmaps will produce wrong results, as it scales cached renders of pre-computed fixed zoom levels for performance reasons. This will exaggerate the effect of those filters when viewed at especially at zoom levels below 100%.

 

If you don't like this behaviour, add your vote here:

 

[Old Bruce]

@andersp5,

I just read what I vote and realized that what I wrote is rather insulting. I apologize, I didn't mean that it is something you are responsible for. Rather I meant to say that ... Not viewing at 100% is most likely the source of your problem. English is my only language so I cannot do anything other than offer my sincere apology for being sloppy with my wording.

@NotMyFault, Thank you very much for pointing out my misuse, or lazy use, of the language.

[NotMyFault]

You are welcome, @Old Bruce. Normally its me being lazy and using short and harsh statements. 

[andersp5]

17 hours ago, Old Bruce said:

This is most likely your problem. View at 100% instead.

 

13 hours ago, NotMyFault said:

To say it in a more polite way: The effect of sharpening and noise filters (like unsharp mask, highness etc) needs to be reviewed at 100% zoom level (or integer multiples 200, 300, ...). Otherwise the rendering method mipmaps will produce wrong results, as it scales cached renders of pre-computed fixed zoom levels for performance reasons. This will exaggerate the effect of those filters when viewed at especially at zoom levels below 100%.

 

If you don't like this behaviour, add your vote here:

 

Hi, thank you both for clearing this up for me.

@Old Bruce no offence taken

I didn't realise that the preview was not perfect and it did throw me somewhat. Having checked as you both say at 100% it does actually sharpen as the screen shows, which does solve my issue. 

So no bug as such but it would really be great if Photo did show an absolute preview but I suspect as you say it could compromise performance and that is something we don't want. I can live with this, now I know about it!......thanks again