New RIFE filter - 3x faster AI interpolation possible in SVP!!! (Page 51 of 84)

I don't suppose this works with the newly open-sourced ZLUDA for running CUDA software on AMD GPUs?

https://github.com/vosen/ZLUDA
https://www.phoronix.com/review/radeon-cuda-zluda

One particularly key interesting point from the Phoronix review on page 3 is that Blender actually ran faster with CUDA + ZLUDA than its native HIP codepath, so it's within reason that ZLUDA could also be faster than Vulkan for AMD GPUs.

In my case my chinese 165Hz GSync monitor doesnt breaks VRR d3d11va hardware decoder, and cant be out of range because 24fps content synced to 48Hz auto, less/x3Hz hehe

Next time I install a new driver, I'll turn on GSync again and test it.

EDIT:

Also, this goes for everyone, instead of quoting a huge block of text, please just quote the section you want to reply to, or only the important part, and remove everything else.

It makes reading the forum a lot easier.

>Now that Nvidia launched the Nvidia App on latest update that turns SDR games into HDR:

HDR is too rare even here. Its basically OLED TV and 3-4 monitors. Below HDR 1000 its crap

https://www.youtube.com/watch?v=ZhDc8p_GsZ8&t=208s

The remaining issue I have with RIFE is the double images for fast motion. What I found is that the higher the frame-rate the less the issue occurs. At x3 frame-rate from the issue is reduced but then I get stutters. But turning on interpolation in mpv removes those stutters and I get the smooth motion back and better fast motion handling, but it still has issues with horizontal slow pans. I like it, but the issue with slow pans annoys me. Maybe if you have a 4090 this might be useful.

Referring to https://mpv.io/manual/master/

I believe video-sync=audio is the mpv default behaviour.

When i tried rife 4.14 v2 (i just copied the onnx file)
it gives an error on screen, and on a log file
[03/02/2024-21:34:57] [W] Could not read timing cache from: C:\Users\Attila\AppData\Roaming\SVP4\cache\Program Files (x86)/SVP 4/rife\models\rife\rife_v4.14.onnx.min64x64_opt1920x1088_max2560x1440_fp16_no-tf32_trt-8502_cudnn_I-fp16_O-fp16_NVIDIA-GeForce-RTX-2080_9c726c00.engine.cache. A new timing cache will be generated and written.
[03/02/2024-21:34:57] [E] Error[4]: [network.cpp::nvinfer1::Network::validate::3100] Error Code 4: Internal Error (input: for dimension number 1 in profile 0 does not match network definition (got min=11, opt=11, max=11), expected min=opt=max=7).)
[03/02/2024-21:34:57] [E] Error[2]: [builder.cpp::nvinfer1::builder::Builder::buildSerializedNetwork::751] Error Code 2: Internal Error (Assertion engine != nullptr failed. )
[03/02/2024-21:34:57] [E] Engine could not be created from network
[03/02/2024-21:34:57] [E] Building engine failed
[03/02/2024-21:34:57] [E] Failed to create engine from model or file.
[03/02/2024-21:34:57] [E] Engine set up failed

rtx 2080 driver 554.61

build in older versions of rife (like 4.4) works

edit : thank you, i missed that i should create a folder. Sorry for that. I have searched my error on the forum and this one wasn't listed ^^'

edit2: actually my 8gb rtx 2080 is not compatible with 4.14 or 4.14 lite, it tries to allocate exactly 8gb vram, but it can't as the vram already contains a little bit of something

[03/02/2024-23:38:14] [E] Error[2]: [virtualMemoryBuffer.cpp::nvinfer1::StdVirtualMemoryBufferImpl::resizePhysical::145] Error Code 2: OutOfMemory (no further information)
[03/02/2024-23:38:14] [E] Error[1]: [virtualMemoryBuffer.cpp::nvinfer1::StdVirtualMemoryBufferImpl::resizePhysical::132] Error Code 1: Cuda Driver (invalid argument)
[03/02/2024-23:38:14] [W] [TRT] Requested amount of GPU memory (8589934592 bytes) could not be allocated. There may not be enough free memory for allocation to succeed.
[03/02/2024-23:38:14] [W] [TRT] Skipping tactic 1 due to insufficient memory on requested size of 8589934592 detected for tactic 0x0000000000000001.
Try decreasing the workspace size with IBuilderConfig::setMemoryPoolLimit().

edit3: enabling "performance boost" fixes the memory problem

because of this bug https://github.com/AmusementClub/vs-mlrt/issues/72

if you use model v2 v4.7+ you need to turn performance boost on else you will get the error.

So after more testing I pretty much have a fixed mpv/SVP configuration for VR. Although knowing me, it won't stop me from tinkering. None of this is strictly necessary because SVP works pretty well out of the box.

For SVP I use Rife 4.13v2 with 12% SCT at 60fps fixed. I'm also using a later version of vsmlrt which has some extra code for playback buffering but this is not compatible with the default SVP helper scripts so I modified it to work.

For mpv the difference betwen using hwdec and not using it is about 1-2% in favor of not using it. YMMV. I also use interpolation with some motion blur. Overall motion was smooth enough before, but fast motion is now almost perfectly fluid so I am very happy with the results. Looking at the SVP manual, is it still the case that SVP runs after decoding but before rendering meaning that mpv is interpolating the output of SVP?

lol But as I said yesterday, I don't need interpolation to be enabled and it probably doesn't have room to do much. I now use it because it needs to be active in order to set up motion-blur.

Not unless they have OLED lenses because OLED has an issue with smooth movement. I'm not particularly susceptible to it myself but even I can see that the extra config reduces the OLED micro-stutters. LED doesn't have the same issues. The rest is mostly standard stuff from my Plex mpv config.

#start
input-ipc-server=mpvpipe
hwdec=no
vo=gpu-next
profile=high-quality

#This is standard stuff most of which is not needed because it's the default but I like to play around with them
gpu-api=auto
gpu-context=auto
linear-downscaling=yes
correct-downscaling=yes
dither=ordered
dither-depth=8
temporal-dither=yes
deband=yes
pause="no"
no-hidpi-window-scale

#This is config specific to my situation and as some have already seen, it can cause problems even for other VR users because they all use LED lenses.
video-sync=display-resample
interpolation=yes
tscale=sphinx
tscale-blur=0.65
swapchain-depth=1

#standard shader stuff
glsl-shaders="~~/shaders/CfL_Prediction.glsl"
glsl-shaders-append="~~/shaders/adaptive-sharpen.glsl"

After that there's shader stuff that won't work because they aren't designed to work the way I use them because I modified the code. So I haven't included them here because they are only used for special circumstances. I also haven't included any color settings because every display is different.