Search options (Page 28 of 354)

> я правильно понимаю что SVP для векторов использует далеко не только несколько соседних кадров

для каждого отдельного кадра использует только два соседних, но этих кадров одновременно считается _много_, по "количеству потоков"

there is no point in using VapourSynth instead of AviSynth <=> there is no point in using Avisynth instead of Vapoursynth

Avisynth is easier to install and use cause it doesn't need all these "environment variables", this's why it's the default engine
however if you already have Vapoursynth stuff up and ready then just use it

I really don't know what to do to get this error

grobalt
> but then SVP does not recognize the player. do you need logs or screenshot ?

if something is not working then looking through the log is a good idea!

jcflores
>  the result will always be black & white video

https://www.svp-team.com/wiki/RIFE_AI_i … n#Problems

still, TensorRT WON'T WORK VIA AVISYNTH!!!

if any additional mb/s of data transferred can break things then everything is possible

DragonicPrime

try this, will it improve a little bit? (replace in SVP 4\plugins64)

> when I try to do this, access violation error appears and the player close

SVP menu -> Utilities -> Set environment variables for Vapoursynth

constasmile
> please try implement new ai scene detection

dunno, I don't see any real problem with the current simple and fast method
another neural network just for a scene change detection looks like an overkill to me

24 to 60
"uniform": 1nnnn3nnnn5....
"2m": 11n22n33...
"1m": 1nn2n3nn4n...
something like this
"n" - interpolated frames, numbers - source frames

what exactly you'll get after enabling 1m/2m in any other XX fps to YY fps conversion - is a kind of mystery

> Can someone integrate the script in MPC Player to add MadVR in the pipeline ?

what do you mean? just run MPC-HC with 'Vapoursynth Filter' instead of 'Avisynth Filter'

because others have different hardware?

aloola
btw:also maybe it a bug? every time black bar detection was on, the TRT CMD pop out again.

with black bars removed the frame size changes, obviously, and it'll need to generate cache for the new size
that's the problem, 3-5 mins waiting is not exactly a smooth experience
BTW it can generate a "multi-resolution" cache, for example one cache for "1920*1080 and below" but then the speed drops by ~30%