Why I am still on 2.6.4

And it is not only because of no AviSynth support in v.3.+
Here is simple screenshot comparison
https://powerserv.sourceforge.net/sc/BW/
Source: 1080p BDRemux
Preprocess: resize to 75% with Spline64Resize using same .avs file
Upscale: 200%
2.6.4 - directly loaded .avs file
5.2.1 - loading .avs in CLI using avs2pipemod64
Resize to 1920x1080 after upscaling
Params - in top-right corner

So, as you can see, only Iris is more or less close to old proteus from v.2.6.4
Speed on my 4060Ti:
2.6.4 Proteus - 4.4 frames/s
5.2.1 Proteus - 5.7 frames/s
5.2.1 Iris - 5.2 frames/s
5.2.1 Rhea - 3.1 frames/s

1 Like

You can pipe avs into ffmpeg. Looks like you need to try more setting in Proteus 4. Unlike 3, Proteus 4 does not need the noise cleaned out beforehand to get good results.

Once I was able to bypass the GUI with their ffmpeg filter, I have loved working with TVAI. 2.6.4 was a pain and had some deal-breaking issues for me.

Anyway, last time I double checked how Proteus 4 compared to Proteus 3, 4 had more detail and was more true to the original.

I am not that good with 3+ versions… So, can you recommend any settings for proteus in 5.2.1?
Here is my recoded file that I used for tests (just to bypass avisynth stuff)

I think I misunderstood what you were doing when you said “Resize to 1920x1080 after upscaling.” That tricked me into thinking your source was something more like a DVD than a Blu-ray—even though you had already said what the source was.

You’ve been upscaling to 4K and then downscaling back.

For all my Blu-rays, I have just been using the Nyx model. But, I know great things can come out of using the Fix Focus settings when the video needs more sharpening.

The Proteus 4 settings that I start at with for DVDs, and are often good enough to keep, are:
image
If it creates spot-patterns on trees, gravel or grass, set sharpen to 0 and Anti-alias/deblur to 20.

Everything changes when you do 1080 to 4K though. Those settings might be terrible. Nothing I own fits 4K needs, so I have never tried to upscale to that—except to see if it comes out better. It never has yet.

Thanks - going to test it