You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
> Подскажите, как проверить?
запустить, увидеть или ту же ошибку, или нет
> Запускать прямо из меню SVP ("Открыть видео в mpv...") тоже пробовал - не помогает.
"не помогает" - с той же ошибкой?
вы сегодня обновлялись, или вчера? вчера было окно в полчаса-час, когда можно было стянуть неправильную версию SVPManager.
в components.xml должна быть версия пакета "core.full" -- "4.7.2.325-1"
в правильной работает так:
- если есть SVP4/mpv/libvapoursynth.so -- то встроенный mpv ПРИ ЗАПУСКЕ ИЗ SVP будет использовать встроенный vapoursynth R72, который просто работает, безо всяких конфиг-файлов и переменных окружения.
- если есть SVP4/mpv/libvapoursynth.so, и запуск встроенного mpv откуда-то еще КРОМЕ меню SVP, то он будет использовать системный vapoursynth.
- если нет SVP4/mpv/libvapoursynth.so -- то встроенный mpv будет использовать системый vapoursynth.
у вас он, очевидно, тянет системный vapoursynth, с которым какая-то неведомая проблема.
/usr/bin/vspipe работает?
и кстати, если системный версии R80 и новее, то TensorRT работать (пока) не будет.
надо использовать встроенный vapoursynth.
не работает в ГДЕ?
во "встроенном" mpv или где-то еще? запускаемом из меню SVP или отдельно?
vapoursynth в самом SVP стоит, или только системный? VSSCRIPT_PATH в шелле прописан, или нет?
---
чо хочет vapoursynth.
он хочет этот .toml конфиг в $XDG_CONFIG_HOME/vapoursynth/ (если XDG_CONFIG_HOME установлена) ИЛИ в $HOME/.config/vapoursynth/
если его там нет, то он сам запускает 'vapoursynth config' и пробует еще раз
если всё-равно нет, то пишет вот эту ошибку
this is more like a pre-built mpv problem
recent update has x11egl built-in
> what does the update 4.0-5 contains ?
fix for rife/ncnn not working on recent AMD drivers
> Is there a plan to port this over natively
yes, but there's a lot of time before macOS 28...
right now there're absolutely no issues running x86 app
надо просто ставить и обновлять SVP инсталлером, там всё как надо
вер.4.7.0.325, 2026-09-23
Обновите еще раз.
Это история о том, как не надо гнаться за последними версиями всего подряд 
Ok, to be clear, the current state:
- svpflow libs updated to "API 4" and work with any Vapoursynth version
- vsmlrt IS NOT updated to API 4, and because of this SVP will install Vapoursynth R79.
There're NO performance gains in R81.
There're NO quality or whatever gains in R81.
Performance gains with TRT-RTX are ... questionable. At least it isn't better in ALL cases.
All flowreen91's AI builds are not officially supported and you use them on your own risk
> But the colors are a little more refined.
absolutely no idea how is that possible
the colors MUST be identical to the source colors (i.e. w/o vapoursynth at all) on each and every version used
it isn't the question of "colors are a little more refined" or not. IF they're not identical - it's just an error.
> I have tried using licence manager but same result.
"tried" how?
Open the License Manager and remove an old device activation.
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 )
> 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" 
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
какая умная скотина
я даже смог повторить то что она сказала
try to reinstall VC++ redists manually: https://aka.ms/vc14/vc_redist.x64.exe
dunno what else could be wrong
"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
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
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.