why the hell so many people have "native interface" active?
where is that f**ing guide that told you to enable it? o_O

302

(8 replies, posted in Using SVP)

it's not similar, your mpv doesn't start at all

303

(2 replies, posted in Using SVP)

nobody knows, SVP 3 isn't supported for years

304

(1 replies, posted in Using SVP)

classified information

граждане, давно пришло время удалить ffdshow из фильтров, и заменить его на Avisynth Filter

если же вам ffdshow настолько мил, что вы не хотите его удалять, то следует вручную поставить Avisynth 3.5 (вместо 3.7)

306

(1 replies, posted in Using SVP)

it's not clear why you set refresh rate to 30 Hz?
SVP won't help much in this case.

you either didn't set "prefer" for the Vapoursynth Filter, or didn't even run 'set env. variables for Vapoursynth' from SVP's menu
and you definitely didn't read the manual - https://www.svp-team.com/wiki/RIFE_AI_interpolation - which is kind of annoying big_smile

> Everything seems to be so complex.

then you don't need to "update to the latest version of RIFE"
stick to what is provided with SVP

why the hell you have ffdshow enabled?

https://mpv.io/manual/stable/#video-filters-vapoursynth

you're using Avisynth Filter and RIFE/trt doesn't work with it

show your video profiles here
plus the log...

don't you know that SVP works via vapoursynth filter? hmm

how exactly "a library that leverages NVIDIA RTX architecture for accelerating large language models (LLMs)" is connected with us?

где появилась? hmm

both profiles match any interlaced video regardless of its resolution

source frame area = A
framerate = R
interlaced = I

now you have: (A and R) or I
while you probably wanted: A and (R or I), which is equal to: (A and R) or (A and I)

please update now, 12_lite will work w/o renaming...

update now

> The SVP script needs to be updated to work with 4.12 lite.

the way vsmlrt authors work with file names is just ... ridiculous big_smile
if tomorrow there will be "4.12_super" then the script won't work again

320

(4 replies, posted in Эксплуатация SVP)

не надо все фильтры добавлять
или один, или другой

если не работает - смотреть в лог

321

(4 replies, posted in Using SVP)

if something is going wrong with transcoding, the first thing to do is reading the log

in this case you'll see a lot of vapoursynth errors there, meaning the video was converted w/o interpolation script active

errors are PROBABLY because the video size after lavfi doesn't fall into the size range provided for RIFE: min_shapes=[2560,1440],max_shapes=[3840,2176]

a workaround for this is enable "perf. boost" in the RIFE proifle

----
there's another problem here, not sure what could be a workaround for this one...

RIFE/trt wants frame size divisible by 32, thus SVP crops 16 px from the bottom (2160 -> 2144 px)
and it do so even after your lavfi transformation, making (1920;896) -> (1920;880), which is NOT divisible by 32 again

if you somehow will make (1920;912) in the lavfi - it will work

322

(1 replies, posted in Using SVP)

not possible

323

(4 replies, posted in Using SVP)

it's more like the source video is broken cause it shows 2682 fps in the MediaInfo

324

(2 replies, posted in Using SVP)

black bars _detection_ doesn't work for transcoding
cause it _detects_ bars in a run time

this log is with an old helpers.py