Selur's Little Message Board

(08.05.2024, 16:08)Selur Wrote: [ -> ]Are you using the Gaming or Studio drivers?

Studio drivers, v552.22

Same I use here.
Hmm,.. try to clear your temp folder, maybe there is still some incompatible engine file or something similar.
Also, make sure the Vapoursynth preview is closed while you run something with RIFE.

You can also try whether it helps to use older versions like librife_r9_mod_v6 from https://github.com/styler00dollar/Vapour...n/releases

Cu Selur

(08.05.2024, 19:39)Selur Wrote: [ -> ]Same I use here.
Hmm,.. try to clear your temp folder, maybe there is still some incompatible engine file or something similar.
Also, make sure the Vapoursynth preview is closed while you run something with RIFE.

You can also try whether it helps to use older versions like librife_r9_mod_v6 from https://github.com/styler00dollar/Vapour...n/releases

Cu Selur

Tried clearing temp - no change. Vapoursynth preview is closed. Tried replacing librife.dll in 'C:\Program Files\Hybrid\64bit\vsfilters\FrameFilter\RIFE' with the one from the  librife_r9_mod_v6 and still no change.

Is there another GPU-heavy filter I can test to see if it's a GPU utilisation issue?

Using the torch- and/or vs-mlrt addons there are a lot in normal Vapoursynth, not really.
Cu Selur

(09.05.2024, 05:49)Selur Wrote: [ -> ]Using the torch- and/or vs-mlrt addons there are a lot in normal Vapoursynth, not really.
Cu Selur

I'm now using the addons with the VapoursynthR68_torch_2024.05.11 no-basicvsr++ version and it's working fine now - maybe my PC was having some issues with the version of VS used? Whatever the case, it seems to be working now - if it happens again I will try and get some more information to debug.

Also try the Vapoursynth_torch_2024.05.11 to know whether it is related to the Vapoursynth&Co version.
(new Hybrid comes with the previous changes I made)

Cu Selur