dawkinscm wrote:
oriento wrote:

the onnx file is available now

Yep. But it does not work properly with SVP. It might look like it is working but the engine parse crashes. Looking at the new vsmlrt script there are a lot of changes and I'm not sure which ones are relevant. Especially since SVP moved some functionality into helpers.py.

i suppose you must change 32 into 64

multiple_frac = 32 / Fraction(scale)

the onnx file is available now

dawkinscm wrote:
oriento wrote:

the onnx file is available now

Yep. But it does not work properly with SVP. It might look like it is working but the engine parse crashes. Looking at the new vsmlrt script there are a lot of changes and I'm not sure which ones are relevant. Especially since SVP moved some functionality into helpers.py.

i suppose you must change 32 into 64

multiple_frac = 32 / Fraction(scale)

another update (no changelog)
4.26 - 21M - 2024.09.21 | Google Drive 百度网盘

scb wrote:

4.25 seems good on performance!

yes, now it's 15% less fps than 4.22 lite v2 !

new release

4.25beta - 21M - 2024.09.19 | [Google Drive](https://drive.google.com/file/d/10RhXyy … share_link) | I am trying using more flow blocks, so the scale_list will change accordingly.

to test the performance you can use the transcoding feature

thanks for the update. I've tested and I don't see any performance gain or lose with rife 4.22 lite v2. Around 98fps for converting a specific video 1080

i ask here because it doesn't happen if I disable the vapoursynth filter (related to svp),sorry I should have mentioned that

edit :nevermind, it's a bug in madvr sorry smile

When enabling "smooth motion" on the madvr settings (which allow to smooth video when interpoling 24fps to 48fps, and then madvr interpolate to your refresh rate),
the video becomes almost desaturated, black & white.
Disabling smooth motion directly make it colored again.

i'm correctly using vapoursynth filter and avisynth is disabled. I'm using madvr beta 206
How can I fix ?

It wasn't happening with the stable madvr (which is really old)

redraiderj wrote:
dawkinscm wrote:
redraiderj wrote:

4.24 is out, anyone tried it?

Yep and and my advice is don't bother. v4.18 is still the best for live action and even the dev has updated the README to agree.

Thanks, but where can I see the readme?

https://github.com/hzwer/Practical-RIFE … /README.md

I don't know why this have been removed from the readùe, but it was described as this : 4.24 (Inherited from 4.18 and fine-tuned)

Blackfyre wrote:
oriento wrote:

I made a small test, 4.22lite show less artifact (on a specific scene with repeated patterns) than 4.16lite

I found the opposite, weird artifacts re-introduced in scenes that were previously fixed. Went back to 4.16_lite (v2) as it has been my main one since its release.

i only tested like 20minutes of video, I will test more later. 4.16 was having artefacts, 4.22 too, but a bit less.

what is your kind of artefacts you're seeing ? On what type ? Is it also on repeated patterns (like fence)

I made a small test, 4.22lite show less artifact (on a specific scene with repeated patterns) than 4.16lite

4.22 lite is out !

New version
4.19 (Add SportsSlomo) - 2024.07.12

Xenocyde wrote:

RIFE 4.17 is out with no lite version. Testing now.

L.E.: Not sure what this new version is supposed to improve... I'm getting quite a bit more more fast movement artifacts compared to 4.15 and 4.16.

4.17 - 2024.05.24 | Google Drive | 百度网盘 : Add gram loss from FILM, need to fully assess the impact.

i'm seing artifacts in 4.15 lite that i don't see in 4.15

is there any comparison for frame.resize ?
I mean if it downscale to 1080p, why then starting from 4k and not start with 1080p ? You're not really playing 4K then

it's strange because the wiki tells that the 4090 is capable of 4K 60fps
https://www.svp-team.com/wiki/RIFE_AI_interpolation

edit: he said that even 4.9 he can't reach more than x2, or I misunderstood

are you using v2 and "performance boost" enabled with your 4090 ?

dawkinscm wrote:

Rife v4.15 is out. It is a clear improvement over previous models for reducing double images in fast movement. I need to do some testing but I think it uses a little more GPU than previous models because even with v2 my GPU never drops below 100%. Packet drops sometimes happen when starting or when FF/REW but settles down quickly with no further drops during playback. No obvious regressions from previous tests.

where is it available ?

thank you smile

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

i don't have conditions for any of the profiles, and "automatic" (the default one ?) doesn't have  an option for conditions
adding "expert add score" to a negative value for rife fixes it, i don't know if it was there before and has been deleted by mistake.

maybe when the score is similar, use the last used one ?

Thanks

Chainik wrote:
Blackfyre wrote:

Any progress at all with Dolby Vision ...

MPC Video Renderer + Avisynth Filter can now play DoVi

Hello did you saw my previous message about what I  think is a bug ? :

"on windows, every time I restart svp, it switch back to rife, and I need to reset to automatic each time.
How do I avoid this ?"

on windows, every time I restart svp, it switch back to rife, and I need to reset to automatic each time.
How do I avoid this ?