In this particular case 0.35 - 0.37 isn’t really having much of an effect. Although my demonstration is static I tested extensively and tried many different combinations of values before deciding to report an issue.
My ultimate goal for Turbo Duo/Grafx16/PC-Engine is to have the “m” and other fine point fonts legible without being blended while at the same time having all checkerboard dithering blended without seeing any temporal artifacts and flickering.
In the older iterations, circa 2024, I was able to achieve this with various levels of compromise of blending/bluriness of the “m”.
In 2025-11-11-r1, I seemed to have gotten results that looked better than my previous efforts with the added benefit of NTSC Artifacts and Fringing being on the table.
It was always hard to strike a balance between increased font legibility via increasing the Artifacts value and visible flickering/noise in the blended areas.
I found that to make the flickering less noticeable, I needed to lower artifacts to at least 0.80.
Anything higher and I know that I would have to accept some visible noise/movement in the blended formerly dithered areas.
Thanks for your hard work on this. I have confidence in your abilities but if it isn’t able to be resolved or improved at least the implementation in 2025-11-11-r1 is there for me to fall back to.