RickyAstle98 wrote:

NVOF : good (smoother than SVP)
SVP : normal
RIFE : good/normal (weird changes depends on threshold but perfect with newer models)

I think we're talking cross purposes here, the image comparison list in SVP has the following options
* Disabled
* SVP motion vectors
* NVOF motion vectors
* Image comparison

It's the differences between these four options that I'm looking for clarification on. Can you help?

Chainik wrote:

different scene change detection methods work differently big_smile

I'm sure smile

How would those differences be described, to allow an end-user like myself to know what might be reasons to pick one over the other?

In context of using the RIFE filter, can anyone explain the differences between selecting (for 'Scene change detection'), 'Image comparison', 'NVOF motion vectors', 'SVP motion vectors', and 'disabled'?

4

(13 replies, posted in Using SVP)

Any idea when 0.39 will come down via SVP?

Is there any guidance on which type of scene detection to use and when?

Is it an advantage using NVOF if you own an NVIDIA card?

4.25 seems good on performance!

RickyAstle98 wrote:
Insindro wrote:

Could someone let me know how I’d be able to change my builder optimization level?

Line 137
Line 1179
Line 1297

Please do elaborate.. what is the impact of this? What are my options and how does it help? smile

Now that ffmpeg 7.0 is out, has anything changed?

Xenocyde wrote:

Tried 4.16 V2 Lite with the new MPV update a few days ago and it looks like the fast movement interference artifacts are almost gone now.

I noticed there is only a 'Lite' version available for 4.16. Does anyone know if that's how things will be from now on, just 'Lite' versions?

What does Lite even mean in practice?

oriento wrote:

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

I think that will be with earlier versions of RIFE (<=4.9); later versions just need more horsepower.

flowreen91 wrote:

We should either use "video-sync=audio" like Blackfyre's configs or nothing at all.

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

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

So should I be using auto-copy rather than auto? SVP appears to work either setting.

This is good to know, but what are the differences between the models? When should one pick a particular one? What are the different models best at? What are the quality differences?

Guys,

I still haven't seen a full explanation about the different between the 'normal' and 'lite' models of the same versions? What situations should I pick the 'lite' version over the 'normal' version of a model?

aloola wrote:
hvs wrote:

I hope someone can guide me in getting Soap Opera effect using RIFE in SVP.

currently, the best quality that almost gets rid of the soap effect is models 4.12 and 4.13.

4.0->4.6: about the same quality and same performance
4.7->4.9: about the same quality and same performance, the performance cost +20% than 4.0->4.6
4.10->4.13: about the same quality and same performance, the performance cost +20% than 4.7->4.9
4.12lite, 4.13lite: performance between 4.7->4.9 and 4.10->4.13

my recommended models are: 4.6, 4.9 and 4.13


Sadly I cannot afford the performance decrease of 4.13 however 4.9 V2 is a great compromise for me.

So what about 4.13v2 lite, how does that rank?

Could anyone fully clarify the difference between the regular models, the V2 models and lite models please?

e.g. 4.13 vs 4.13 lite vs 4.13v2 vs 4.13v2 lite.

It would help solidify my understanding!

When MPV 0.37 arrives in SVP, will it impact performance of RIFE?

Is it likely we'll see optimisations to improve performance, or is this pretty much going to stay the same even if quality improves?

Hello,

I'm fortunate enough to have a laptop with a 12GB 4080 in and I've been using SVP to playback 4k HDR videos (resized to 1440p) in real time @ 48fps with RIFE, which like another poster has said, looks smoother than 'Automatic @ 120fps'.

I've been exploring using SVPcode to do all the calculations up front. SDR colour space content works fine, but I notice that with HDR sources, SVPcode arranges a tonemapping rather than preserving the HDR colourspace. Is this an innate limitation of SVPcode?

I was hoping that because SVP could do the HDR processing in realtime, that SVPcode could essentially do the same thing in batch for watching on other devices later?