Drakko01
> A version can have identical math performance but be fundamentally broken in stability, or introduce visual artifacts that completely ruin the output.

so, do you think that Vapoursynth R73 is "fundamentally broken in stability, or introduce visual artifacts that completely ruin the output", while R80 fixed this? really?
and given the "picture quality", "R31" and R80 are identical

IF there're no "fundamentally broken in stability, or introduce visual artifacts that completely ruin the output" then I personally don't see any reason for running for the latest versions of everything

> Do you honestly, truly believe that every single VapourSynth version works exactly the same?

in terms of performance of a complicated math running in its own native libraries - yes, sure

> why didn't you just freeze the whole thing at r31 and call it a day.

because other open source components depend on newer versions, even if there're no real benefits
this is how open source world works
for example, on macOS mpv should be installed from Homebrew repo, which provides only the latest versions of everything (right now R80) even if it breaks things

> I was finally able to use the R79

so, is it any better?
(hint: no big_smile)

> With 1.6.1 the odd-size crash is fixed and the speed is 261.8 vs 267.4 fps at 1080p and 60.0 vs 62.8 at 4K (model 4.6, x2).

is it possible that 5090 is not a bottleneck in your case?
what is the GPU load?

flowreen91

> About it being slower: that was half a year ago.

dunno. just tried on a laptop with 2060:
TRT: 33.7 fps
TRT-RTX 1.4: 23.9 fps
TRT-RTX 1.6: 21.6 fps

----------
btw, instead of "fixing" generate.js, just add a "rife_rtx" profile option via "user defined options" wink

for me _rtx is significantly slower (on the 4070), last time I tried was ~half an year ago
plus, it doesn't need "slow engine compilation", yes, BUT it's much slower at initialization. TRT runs instantly after the initial engine compilation, TRT_RTX needs some time at every run and every seek.

у вас версия - откуда? из google play что ли?

вторая попытка

rollback svp 4\plugins\svpflow2_vs.dll from there

какая умная скотина big_smile
я даже смог повторить то что она сказала

11

(35 replies, posted in Using SVP)

try to reinstall VC++ redists manually: https://aka.ms/vc14/vc_redist.x64.exe

dunno what else could be wrong

12

(509 replies, posted in Using SVP)

"supported" means:
Device Profile = FULL_PROFILE
Image support = yes
Device Extensions = contains cl_khr_byte_addressable_store

you may check with clinfo what's missing and ask GPT how to add/fix this in your specific case

13

(35 replies, posted in Using SVP)

are we still talking about running mpv from SVP's menu ("open file via mpv")?
and that mpv crashes at the point where SVP kicks-in?
in All settings, put "--log-file=d:\mpv.log" into main.setup.player_args (enter "player" into the search field first)
replace "d:\" with some writable location you actually have

then run playback and send the generated mpv.log file

обновилось

вроде никто вчера не обновлялся
или это про какой-то конкретный очень нужный коммит на гитхабе?

люди вот жалуются что не работает без свежих кукисов
а со свежими - работает

16

(35 replies, posted in Using SVP)

there's no PATH variable on Screenshot (45).jpg

17

(35 replies, posted in Using SVP)

> I'm not sure what you mean, as I said earlier, I have limited software engineering abilities

- Open the Start menu, type env, and choose Edit the system environment variables.
- Click the Environment Variables... button at the bottom.
- Under User variables, find the row named Path and click Edit.
- Click New and paste the exact file path to your target folder (e.g., C:\Program Files\SVP 4\mpv64).
- Click OK on all open windows to save your changes.
- Close and reopen SVP for the change to take effect.

what SVP version? what vapoursynth version?
right now SVP installs pre-built R72

19

(35 replies, posted in Using SVP)

run 'set env. variables for vapoursynth' again

20

(35 replies, posted in Using SVP)

there's no "path" in the user variables section on your screenshot, which is kinda strange

are you sure it's not created after running 'set env. variables for vapoursynth'? hmm maybe you deleted it later?
anyway you can add it manually

21

(35 replies, posted in Using SVP)

don't you see that mpv64 folder is not here?

22

(35 replies, posted in Using SVP)

win+R, cmd, 'echo %PATH%'

you said "checked that the PATH was pointing to SVP/MPV" BUT all I can see now tells that the path ISN'T in the PATH

23

(35 replies, posted in Using SVP)

and the log still tells "Main: PATH doesn't contain mpv64 folder, Vapoursynth Filter and libmpv players may not work"
run cmd, exec 'echo %PATH%'

when you double click "vapoursynth filter" in MPC-HC's "External filters" list - what happens?

24

(35 replies, posted in Using SVP)

> I'm way past that

then show the correct logs of everything, because all I can see from the logs attached - you're running mpv bundled with SMPlayer

regarding "RIFE only works via Vapoursynth!" - again, the log! this message shouldn't appear with "Vapoursynth Filter" at all.

25

(35 replies, posted in Using SVP)

> SVP works with MPC-HC but when I try to engage the RIFE engine, I get a warning sign in the lower right of the screen that says, "RIFE only works via Vapoursynth!"

this means RIFE/TensorRT works only via Vapoursynth Filter set in MPC-HC. Not via Avisynth Filter. Go to View -> Options -> External filters, uncheck Avisynth Filter, check Vapoursynth Filter.

> As far as my mpv not being from the SVP bundle, I'm not sure what to do about that.

choose mpv bundled with SVP as described there - https://www.svp-team.com/wiki/SVP:SMPlayer