Search options (Page 84 of 363)

There's no need to "implement ffdshow", they (Renderheads) could just give more control over the DirectShow fiilter chain to the developers

I believe Whirligig author will be glad to help us but he is just unable to do it.

===
> the new whirligig 4.821 beta

Where? The last one on Steam is 4.78 from 7 Nov 2019

> Is there a solution to it?

Unfortunately no.
They all share the same video engine - Renderheads AVPro Video, which doesn't allow the DirectShow filter chain configuration except the video decoder selection.
https://github.com/RenderHeads/UnityPlu … issues/230

this is why SVP doesn't see Kodi

4K/10 bit at very high frame rate is not a CPU perf problem but more like mpv's internal issue with rather slow copying of huge amount of data
60 fps should work. Ryzen 3xxx may also work at higher rates due to higher IPC and memory copying speed

you must have SVP Manager running (it can be completely disabled) to use the latest svpflow libs

please update SVP now

---
the video was encoded with a strange timecodes at frames ~90-95 and svpflow plugin didn't handle those negative and zero values correctly

Avisynth should work fine, Vapoursynth interface has performance issues.

если выбирать поток БЕЗ значка "V+A" то звук будет в любом плеере
если выбирать поток C значком "V+A", то звук будет ТОЛЬКО в mpv, VLC, MPC-HC, PotPlayer

если вы знаете как передать SMPlayer-у через ком. строку отдельную аудио-дорожку - можете сказать, тогда в след. версии SVPtube будет работать и для SMPlayer

> Как объяснить, что все опробованные, разные версии smplayer, работают идентичным образом

Путаницей среди вас

> youtube-dl + smplayer + svp

Что именно вы делаете и как?

> Как подружить svp и smplayer?

RTFM уже наконец , а там прямо так и написано

> VLC: unsupported color format, switch to software video decoder

do what it tells

> Video: error launching C:\Program Files (x86)\SVP 4\mpv64\mpv.exe

no idea how you managed to put this path into main.setup.player, but just clear it

try to update SVP - you'll see an updated Vapoursynth package, ver. 50
from the changelog:
> fixed regression in r49 where the python dll could only be located when in the PATH on windows

probably it's related