there're different skins, one of them just like Media Player Classic ![]()
You are not logged in. Please login or register.
SmoothVideo Project → Posts by Chainik
there're different skins, one of them just like Media Player Classic ![]()
maybe SMPlayer can handle playlists better than plain mpv...
it's possible to add some logic to SVP Manager to launch every other mpv instance with a unique socket name, but not right now
after all it can handle multiple ffdshow instances at the same time in Windows
You mean running two mpv instances at the same time?
I'm not sure how they would share the same IPC socket o_O
ok, will try to 'fix' this in the next release
> i3 windows
oh, I see
consider controlling SVP Manager via wget from the console then ![]()
> Is there any way to fix this?
nope
why it bother you? how often do you need to "drag video to another monitor"?
> I can't figure out how to minimize it
just close the window and the Manager will remain in the tray? o_O
mickeekung
contact us via email to get the Pro license in case you still don't have it ![]()
despite evidently detecting the correct OpenCL device
hmm... this's interesting ![]()
This's not the case.
clGetPlatformIDs() call for some reason fails in both SVPManager and svpflow lib, BUT it works in clinfo.
The only difference is clinfo is linked with libOpenCL.so while SVPManager loads it dynamically at runtime.
Could it be that you have several different versions of libOpenCL.so installed?
In other words check that libOpenCL.so from "ldd clinfo" and the one from /proc/<SVPManager pid>/maps point to the same AMD's .so file.
clinfo output is fine, it's exactly like it should be
1st device is "GPU", 2nd one is "CPU"
you'd better post "events log" after trying to play some video with GPU acceleration enabled
> APT wants to pull mpv from the SMPlayer repo which doesn't have Vapoursynth support
yeah, it's a known "issue", just forgot to include it into the FAQ ![]()
gpuId=11 in this context means "1st GPU device on the 1st platform", so what's wrong?
the fact that built-in benchmark fails is interesting BUT even more interesting would be the actual Vapoursynth error (if any) when the filter script initialization fails
это вопрос не сюда
на сегодня аппаратное декодирование в mpv не совместимо с фильтром Vapoursynth
автомат рассчитан на аппаратный декодер
а тут его нет
так оно ж в /opt/qt55 поставило
LD_LIBRARY_PATH=/opt/qt55/lib ./SVPManagerМда... ну и для верности, "ls -l /usr/lib/x86_64-linux-gnu/libQt5*" ? Что бы я точно поверил в 5.5.1 ![]()
Just add --input-unix-socket=/tmp/mpvsocket to mpv args (or config file) and SVP should find it. Alternatively you can "open" video file via SVPManager - it'll execute mpv with the correct argument.
toroto
наверное Qt стоит какой-то старый
нужен 5.5
возможно (!) будет работать с 5.4, но это не проверялось
всё что раньше 100% не годится
конечно если здесь присутствующие до этого доживут
> Note : i never used SVP 3.
this's the problem ![]()
"1.5m" before the last update was equal to "Adaptive" plus
smooth.scene.limits.m1 = 0;
smooth.scene.limits.m2 = 0;in "override.js"
ну так зачем всю портянку сюда показывать?
libQt5Script.so.5 => not foundнайти пакет, в котором он содержится, и поставить
главное не понятно нафига
всё равно за один день новые версии всех скачивальщиков выходят
хотели бы радикально зарубить саму возможность - давно бы реализовали
ну значит не все зависимости стоят
#ldd ./SVPManager
покажет чего не хватает
например, libQt5Concurrent может отдельным пакетом идти, не стоящим по-умолчанию
SmoothVideo Project → Posts by Chainik
Powered by PunBB, supported by Informer Technologies, Inc.