Search options (Page 17 of 22)

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

Thanks but that's not what I'm trying to do. Or at least I don't think that's what I'm trying to do. Does changing the code in the way I mentioned do this?

I'm using my GPU heavily and can easily hit 100% usage with 4.12.4.13 but max out at 80% with 4.9. So maybe you don't see it under lighter loads?

Make sure you have a 4.13 onnx file in the "v2" folder. If you do then delete it and any files created by it, download the v2 onnx file again and put the new onnx file into the "v2" folder.

This is not necessary. In the SVP rife folder, just replace the onnx file for the model you want updated then delete the generated model and engine files. This will trigger regeneration. But if you are using model names that are different to the actual model being used then I don't know since I stopped doing this some time ago.

Don't worry about the Lite versions, at least not yet.  If Rife 4.9 v1 or v2 works for you then stick with that. if it's too much then use Rife 4.6 v1 or v2. But if you have a 3090 (or maybe 3080) or above then you can also try 4.12/4.13.

Maybe I should have said that hwdec off works better "for me".

Same here. My wild and totally uninformed guess might be that there's more GPU resources available to process RIFE when not using hw decoding. I did a quick check of CPU resources with hwdec on/off and there wasn't any obvious difference. For both hwdec on and off, a couple cores were close to max, a couple were about 50% and the rest were either idling or parked.

My test is visual. With hwdec off I get smoother playback. YMMV.

I just tried Heresphere and I will probably never touch it again. But thanks for the heads up

It doesn't cache in 15 seconds. None of them do.

Everything from 4.9 onwards was for anime, but they also work very well with live stuff. Rife 4.12/4.13 are better for fast motion which is why I now use them, but I'm watching on a very large screen. Rife 4.9 is the best quality/performance compromise for most people, followed by 4.6. I agree with your placebo tier.