![]() ![]() This particular frame has a lot of fine detail in it, so it’s a good test for the idea. ![]() I’m holding most values at 0 so you can see the impact of the two antialiasing values. You need to test both negative and positive values on your content while holding other settings constant.įor example: Here is a frame comparison between two different Proteus settings. I recommend testing settings of 0 - 25.Īntialias / Deblur: This is one of the most important settings, and how you use it varies by source. Leave it low in any case, it’s damaging to detail. If you don’t have haloing problems, don’t. If you perform noise processing elsewhere, you may be able to leave this off.ĭeHalo: If you have haloing problems you can turn this up. Reduce Noise: I denoise with other applications and only use this option a little. Sharpen: I recommend keeping this very low to off. Below 20, and the improvement is quite small. When testing Proteus against content, you should use the following settings:Įnhance Detail: Test a range between 20 - 75. The auto tuner can be useful, but it does not give the kind of achievable quality boost that Proteus can. General advice to the group: Use Proteus, but ignore the auto tuner. No intention to plagiarize just to facilitate the discussion here. Here’s a copy of the post, as I could not generate a direct link to the great post by Joel Hruska. Took a while to find the post Richard mentioned. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |