You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
1, 2. if you've a small samples or an URL from where I could download such a videos please share it
3. we still don't known what "video output" value is the best for 1920*1080@60
I was under the impression that it is not necessary to manually set environment variables with a non-portable installation.
yeah, it seems that Vapousynth setup doesn't copy vapoursynth.dll to the system32 for some reason
MistahBonzai
The same setup as needed for the VLC: http://www.svp-team.com/forum/viewtopic … 313#p59313
Either install full Python and Vapoursynth packages with their own setup files
or add SVP 4\mpv64 to both PATH and PYTHONPATH environment variables
And yes, vapoursynth.dll should be in the PATH.
I'm not sure why the official installer doesn't copy it to the system32 (while it copies vsscript.dll here)
frc.target.max во "всех настройках"
> mpc-qt
check this out: link 
(a mingw-64 build with Qt 5.5 + mpv-1.dll with vapoursynth + "input-ipc-server=mpvpipe" option hardcoded into mpc-qt sources)
потому что в системе уже стоит Qt5, но более старой версии
и для старого дистра официального обновления до 5.5 нет
поэтому надо поработать руками и покурить маны
переходите на 16.04, там всё "из коробки"
===
а еще можно выпилить все libQt5* из /usr/lib, а в /etc/ld.so.conf добавить /opt/qt55/lib, таким образом перевести всю систему на 5.5
тысячи способов...
definitely "no"
It should work...
OK, lets double check all those stuff.
- reboot PC
- Win+R, type "cmd"
echo %PATH%do you see "C:\Program Files (x86)\SVP 4\mpv64" in the list?
- in the same cmd window type
vspipewill it run?
You may need to restart SVP Manager after modifying PATH value.
Wrong:
12:29:23.468: Playback: starting up...
12:29:23.468: Playback [ee8]: Frame server (64-bit) NOT FOUNDRight:
12:29:23.468: Playback: starting up...
12:29:23.468: Playback [ee8]: Frame server (64-bit) C:\Program Files (x86)\SVP 4\mpv64\vapoursynth.dllACE кстати, может быть, будет работать, надо бы попробовать...
За VLC идём туда - http://www.svp-team.com/forum/viewtopic.php?id=3298
====
Что-то он какой-то старый (на VLC 2.0.5), и 64-бит версии нет.
Тогда пока что не взлетит...
> А что там за проблема, стало интересно, я бы понаблюдал?
Теперь подсветка работает только с первым файлом, а дальше "нет подключенных dll". В общем, требуется перезапуск SVP перед каждым новым запуском фильма.
Windows specific
1. Install "VLC support" package via the SVP's Maintenance tool
2. Install VLC 64-bit
3. Make Vapoursynth installation usable by other apps (see below)
4. Run SVP and exec the Utilities -> "SVP in VLC" via the main menu
5. Run VLC and ensure that "vapoursynth" is in the video filters list.
The tricky part is correct Vapoursynth / Python installation
"Portable" way - assuming you DON'T have system-wide Python installation:
1. add SVP 4/mpv64 folder to the PATH environment variable
2. add new env variable called PYTHONPATH, containing the same SVP 4/mpv64 path
System-wide way:
1. Install Python 3.5.1 64-bit: https://www.python.org/ftp/python/3.5.1 … -amd64.exe
2. Install Vapoursynth 64-bit: https://github.com/vapoursynth/vapoursynth/releases
3. Either add C:\Program Files (x86)\Vapoursynth\core64 to the PATH env var OR copy C:\Program Files (x86)\Vapoursynth\core64\vapoursynth.dll to C:\Windows\System32\
> Теперь подсветка работает только с первым файлом, а дальше "нет подключенных dll". В общем, требуется перезапуск SVP перед каждым новым запуском фильма.
Исправлено в вер.1.9.0.76
Починено в версии 1.9.0.76.
починены и Лайтпак, и Пейнтпак
с пейнтпаком вроде как другая проблема
дойдут руки перешить наш экземпляр обратно в пейнтпак - исправим...
It's completely up to you to install any 64-bit video player.
64-bit players are supported but NOT recommended for SVP.
> What about the GPU acceleration though?
I remember...
> unable to init GPU-based renderer
clean all the GPU drivers and re-install them from the scratch
"processing threads" should be set to "auto" and works fine - this why it's called "auto"
IF it isn't working fine then it's a question to the "auto" algorithm.
I mean that adding new manual options just to workaround some bugs is not a good idea.
It's much better just to fix those bugs.
Я тут чувствую какое-то недопонимание...
Если взять крайнюю версию SVP 4, поставить SVPlight, и заменить файл extensions/svplight.dll на тот, что находится в архиве вон там - http://www.svp-team.com/forum/viewtopic … 506#p58506
то работает, или нет?
Если "да", то к чему замечания про "еще одни выходные", если "нет", то зачем отвечать "правильно" на вопрос "работает ли версия 69-1"
???
Т.е. до этого Призматик вобще не стоял?
Ок, еще раз: "69-1" из сообщения выше работает, "74" обех версий - нет?
Правильно?
The problem with that "Baka" is it's statically linked with libmpv.
So if someone wants to use it with SVP - he will need to ask Baka devs to build it "the right way" first - e.g. with the Vapoursynth enabled.
And then they will refuse to do it cause they will fail to statically link with Vapoursynth and Python
From SVP's point of view:
- mpv executable just works (this includes SMPlayer)
- players dynamically linked with libmpv can work after some manual PATH adjustments and file replacements (see Plex)
- players statically linked with libmpv won't work at all
There's a little mess with SVP libs versions and MT mode 1 support.
- all pre-Vapoursynth libs are MT mode 2 only
- builds 128 - 132 are compatible with MT mode 1 BUT there's a mysterious memory corruption somewhere in svpflow2 which gives us that error
- as a temporary fix we released svpflow2.dll .135 as an old (pre-VS) version upgraded for the latest SVP Manager, so it is NOT compatible with MT mode 1
The script with SetFilterMTMode("SVSmoothFps", 1) using svpflow2.dll ver.135 will definitely freeze on start.
However I really don't see any improvement in using MT mode 1 with build 132 libs.
Here's how it works:
"old" Avisynth-only libs in MT=2: N instanes of AVS's VideoFilters running at the same time.
"new" multi-platform libs contain a platform-independent thread-safe "cores"
- Vapoursynth: 1 thread safe VS filter uses 1 "core"
- Avisynth MT=2: N single-threaded VideoFilters share 1 thread safe "core"
- Avisynth MT=1: 1 thread safe VideoFilter uses 1 "core" - just like in Vapoursynth version
The point is there's just one "core" is all cases.
а вот если на такой файлик заменить, не поможет ли?
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.