Search options (Page 196 of 356)

Я тут чувствую какое-то недопонимание...

Если взять крайнюю версию SVP 4, поставить SVPlight, и заменить файл extensions/svplight.dll на тот, что находится в архиве вон там - http://www.svp-team.com/forum/viewtopic … 506#p58506
то работает, или нет?

Если "да", то к чему замечания про "еще одни выходные", если "нет", то зачем отвечать "правильно" на вопрос "работает ли версия 69-1"
???

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.

brucethemoose
> We have SMPlayer, but it doesn't add any GUI for configuring MPV.

SMPlayer is in active development so there're good chances if someone will post a feature request...

> Is SVP rendering the video at a different frame rate possibly cause this slight stutter?

It is.
Try to start with "D3D Fullscreen" option in MPC-HC -> Playback -> Output.

The ultimate solution for syncing video with the screen refresh rate is ReClock but I personally won't recommend it unless you know what and why you're doing.

- All settings -> find your custom profile under "profiles"
- set "fi_target" to "144" or whatever you want
- see the changes on the "Video profiles" page

4.0.0.76

Added VLC support (beta) - see there

Check SVP's events log:

20:09:34.645 [I.]: Main: module 'plugins/libsvpflow1_vs64.dylib': 4.0.0.132
20:09:34.646 [I.]: Main: module 'plugins/libsvpflow2_vs64.dylib': 4.0.0.132
20:09:34.652 [I.]: Main: VLC filter: 0.9.0.76

The magic: we need to remove VLC's "deinterlace" filter and place SVP's "vapoursynth" filter into the VLC plugins folder.

1. remove VLC/plugins/libdeinterlace_plugin.dll (or .so, or .dylib, depending on the OS)
2. choose one of the SVP/plugins/libvapoursynth_plugin.20 or libvapoursynth_plugin.30 (depending on VLC version  - 2.2.x or 3.0)
3. copy it to VLC/plugins/libvapoursynth_plugin.dll (.so, .dylib)

To help with this you can just run
SVP menu -> Utilities -> SVP in VLC
and choose the VLC executable (or an .app on OS X)

Note that SVP Manager needs write access to the VLC's plugins folder!

If you want SVP to start automatically just set deinterlace to "always on" in
VLC preferences -> Video -> Deinterlace = On

> is 'support@svp-team.com' the right email to contact regarding this issue?

yes it is!

> A delayed start option would be extremely handy nonetheless!

SVP 4.0.0.76

All settings -> main.setup.start_delay  = 0 by default