> В MPEG-TS сидят 2 видеопотока с разными PID: первый 2D (допустим, кодек H264 High L4), и второй анаморфная стереопара (кодек H264 High 4.1).

ссылку на пример в студию wink

> для меня исходные коды менеджера помогли бы написать

не помогли бы big_smile

> есть проблемы. Классический вариант: видео с 2-мя видеопотоками - 1-й - 2D, 2-й - 3D

и что там не так? почему бы не решить в рамках SVP 4?
вариант с двумя видеопоками в 3D-MVC уже работает, кстати, если речь об этом

http://www.svp-team.com/forum/viewtopic.php?id=3226

5,104

(7 replies, posted in Using SVP)

SVP itself can't produce BSOD.
If you have BSOD it's because either overheating or some driver instability (usually the video driver)

5,105

(2 replies, posted in Using SVP)

MPC-HC has built-in LAV filter as well
Standalone LAV filter is just for other player, you don't have to install it from SVP's setup.

> May I spam "next" on setup?

yes

5,107

(19 replies, posted in Using SVP)

please post a report just after this thing occurs

5,108

(138 replies, posted in Using SVP)

mpv updated to that version
(hopefully will be in the mpv's master branch soon)

replace "input-unix-socket=9911" with "input-ipc-server=mpvpipe"

requires SVP Manager 4.0.0.73 to work correctly

Starting from SVPflow ver.132 (SVP Manager ver. 4.0.0.72) the legacy Avisynth 2.5 interface is not supported any more.

This means you'll see that error message in case the video player is using Avisynth 2.5 dll:

Legacy Avisynth 2.5 is not supported, please use either Avisynth 2.6 or Avisynth+


What to do?

Open "Information" -> "Events log" and find out the path of the wrong avisynth.dll.

The most common case is when you also have SVP 3 installed and you're using MPC-HC bundled with SVP 3:

23:25:20.415 [i]: Avisynth: 2.5.8.6, AvisynthMT 2.5, C:\Program Files (x86)\SVP\MPC-HC\avisynth.dll
23:25:20.415 [E]: VideoPlayer: Avisynth 2.5 isn't supported

Now you've three choices:
1. delete this 'avisynth.dll' and use the system-wide one from C:\Windows\SysWOW64
2. replace this .dll it with any other version you like
3. stop using MPC-HC installed into SVP 3 folder (or just use exclusively with SVP 3)

> Пусть сразу VapourSynth к madVR прикручивает, чо уж там.

я ему предлагал big_smile

5,111

(206 replies, posted in Эксплуатация SVP)

Ну я даже не знаю... прямо в тексте написана ссылка на Qt 5.5 для убунты 14.04, ставящийся в /opt.
И тут 10 сообщений подряд про это же.

> в журнале SVP выдает вот такое предупреждение 16:46:04.713 [W]: Video: OpenCL subsystem isn't available, try to reinstall video drivers,
> драйвер на видеокарты 7970 на днях переустанавливал. интеловский вообще виндой обновляется сам

Значит что-то плохо встало.

5,113

(4 replies, posted in Using SVP)

BTW SMPlayer ships with built-in youtube-dl

5,114

(122 replies, posted in Using SVP)

sounds like a fucking magic! big_smile

>  It's definitely interlaced, if that matters.

this could be the problem...

5,116

(138 replies, posted in Using SVP)

> Do I need to enable hwaccel?

hwdec=dxva2-copy
vo=opengl-hq

is a good point to start with

5,117

(138 replies, posted in Using SVP)

> I wish I could use madvr to improve picture quality

https://mpv.io/manual/master/#video-output-drivers

prescale-luma=<filter>
- superxbr
- nnedi3

scale=<filter>
- spline36: Mid quality and speed. This is the default when using opengl-hq.

a part of SVP's log starting from "VideoPlayer: mpv ..." could be helpful wink

> --input-file=/dev/stdin

мда?

5,120

(138 replies, posted in Using SVP)

"official" mpv.exe won't work!

...cause it was built w/o Vapoursynth AND doesn't support "input-unix-socket" feature

5,121

(121 replies, posted in Using SVP)

according to the sources such a loop can only be if MediaInfo returns zero for the "Width" attribute

> SMPlayer после замены mpv.exe и mpv.com на аналогичные из папки C:\Program Files (x86)\SVP 4\mpv64 работать отказался.

не надо менять
надо в настройках SMPlayer-а указать путь к SVP 4\mpv64\mpv.exe

а если уж именно менять, то надо позаботиться о путях к vapoursynth.dll и прочим питонам

5,123

(138 replies, posted in Using SVP)

> I assume the SVP setup program installed vapoursynth

It uses the "portable" versions of both Python and Vapoursynth, so mpv.exe should work from the mpv64 folder only.
BUT those "portable" versions lack VC++ 2015 libs - this' why it have to be installed separately. SVP setup should do this automatically - but, well, "shit happens" big_smile

В логе написано где именно находится старый avisynth.dll 2.5. Надо его оттуда убрать.

5,125

(121 replies, posted in Using SVP)

again - what's in the log?