Search options (Page 15 of 21)

I keep saying this but it's worth repeating. If you are new to this then don't do anything you see here because we are experimenting. SVP works out of the box.  Just uninstall everything, go to the SVP Rife AI page https://www.svp-team.com/wiki/RIFE_AI_interpolation and follow the instructions. All the information you need about the Rife, the DOS box and everything else is on that page. Once you have done that then have a look at the SVP Transcoding page https://www.svp-team.com/wiki/Manual:SVPcode. I don't transcode, but once you have followed those instructions there are others on here who can help you with any specific questions you have.

3840x2160 was watchable on the 4080, but with slow pan stutters. I updated the Nvidia Driver to latest version released yesterday and used the v14Test3 TensorRT library (Cuda 12.3) and the latest vslmrt.py with Rife 4.14v2 lite. It's still dropping frames but the slow pans are now mostly smooth. The 4090 should have no problem so you don't need to wait for a 5090.

I currently don't have any intention of using SVP with 4K but this should help to clarify your options.

I installed 537.58 and tbh it made little obvious difference. But the install tool was useful to completely fix some Nvidia driver issues I knew about but had only partially fixed. I just made another back up of everything. Thank you

Not necessarily. I would test 1.14 lite first because the 3080/3090 has a wider memory bus than even the 4070ti/4080 so the 3090ti might work better with Rife 1.14 lite than anything less than a 4090. Hopefully someone can help with other card comparisons.

It's OK. We were both talking about 1.14 lite v2 and it is very smooth

The new technique used for the "lite" versions is potentially a little more accurate than the normal versions but I suspect that GPUs with low internal memory bandwidth will have issues with v14 "lite". I'm keeping it for now and will see what happens further down the line.

Edit:
The figures from @aloola and @RickyAstle98 show that this is a heavy model. But now everything has kind of bedded in, Rife v1.14 "lite" (v2) is using a little less GPU resources than before, down from 94-100% with Rife v1.14 to between 86-92% with "lite" while "so far" retaining the same quality as before. It's also very smooth. YMMV on GPUs with limited memory bandwidth.

I've updated and I don't see any obvious differences. But I have thought about updating for the latest fixes to TensorRT and Cuda so thanks

Yep. That's where I got the last copy from too. It's configured for Catmull Rom. The ones I saw configured for Mitchell must have been local variations by other users.

Thanks. If you see a particular issue that you want fixing then this does make sense. Especially if you are saying that v14 fixes this issue for you. I still do testing of new models, changing code etc but I think SVP is stable and works well now so I would not recommend most people do this. Why fix something when it ain't broken ?

I use a number of videos highlighting different artefacts. But Alita might be the best because it has different types of fast movement and exposes a couple of minor artefacts. One of which has been fixed by Rife 4.14.

It's a change to the code in base.py. I got this from a previous post by @blackmickey1007 for completely disabling SC.

SVP4\script\base.py

input_m = input_m.misc.SCDetect(threshold= 0.1 or 0.2)

The threshold values are just suggestions. You will need to experiment to see what works for you. You won't find a pefect setting because when you fix double images from fast movement it will break slow panning. When you reset for slow panning you get double images in fast movement. But you can get a compromise which improves fast movement a little without breaking slow panning. I couldn't get even this minor improvement in 4.12/4.13 but 4.14 does seem to be better overall for fast movement so here it was possible.

I'm not going to comment on config for OLED. It's best you experiment for yourself. Here are some points to think about.
dither-depth=auto and spirv-compiler=auto is the default so not necessary
fbo-format is disabled in gpu-next so is not needed and won't work anyway.

KrigBilateral isn't really necessary and although I've never seen it myself it can apparently cause mistakes.
Is FSRCNNX_x2_16-0-4-1.glsl that much better than FSRCNNX_x2_8-0-4-1.glsl considering the extra processing power needed?
Do you need to use both FSRCNNX_x2_16-0-4-1.glsl and SSimDownscaler.glsl? That's a lot of processing and sharpening.
SSimDownscaler.glsl is configured by default for Mitchell but you are using ewa_lanczossharp. So that is not optimal.

You are sharpening in upscale, shader and downscale. Although FSRCNNX might not be doing anything because by default it only works when a x2 or greater upscale is needed. This might be why you can get away with running FSRCNNX_x2_16 and SSimDownscaler which are very GPU heavy.
Some shaders overwrite others so it's best to use append when you want multiple shaders to work at the same time.

Hope this helps a little.

Now that you have said it is obvious. I already knew what multi does in theory. But what I didn't realise was that in practice it directly relates to the fps which again is now obvious. Thanks