Search options (Page 203 of 359)

For the reference, the data from the logs, what's going on on the "spike":

06:09 - CPU usage drops to nearly zero
06:15 - SVP detects source frame rate change from 23.976 to 24.39 and resets the script
06:22 - CPU usage goes to 100%
06:27 - SVP detects source frame rate change back to 23.976 and resets the script again
06:30 - we're all good now

It's a good question
We should implicitly give this information somehow...

However you have a form to send reports/question via the Manager itself.

And yes, the address is support-at-svp-team-dot-com

имя файла - в кавычках!

> Why would I want that?  The site for that project forgot to explain why I'd want it.

yeah, right...

it may be fixed in the future when (or "if"?) VLC will be supported via the Vapoursynth engine
right now Windows users haven't even heard about mpv (unless they're using Plex)

> But setting up automatic resolution changing in MPV is a complete pain if you aren't into coding or command line stuff

haven't dived into mpv that deep yet o_O
could you describe the problem with more details?

Можно на колонки good / high смотреть, там чистый fps написан. Оно наиболее близко к реальной жизни.
Если сравнивать именно с упором на процессоры - то highest, он самый GPU-независимый.

Частота реальная для K-серии не определяется, да. Надежнее сравнивать по не-К. Ну или если в комменте реальная частота указана.

таблица SVPmark-а не отвечает на этот вопрос?

The fix will be in the next build.
The fix for the loop itself, not for "zero width via MediaInfo". It should normally fall back to mpv's provided information in this case.

> А со вторым что делать ?

ждать

если уже работает с амбибокс - то какие проблемы? он включает точно такой же remote API как в призматике
т.е. в SVP выбираем "Prismatik", запускаем Амбибокс, и вроде бы должно работать

===
Называется "Доп. настройки" - "Включить API сервер" - порт 3636

check that "svp-maintenance.dat" exists in the SVP 4 folder
if not - try to rename "svp-maintenance.dat.backup" to "svp-maintenance.dat"

> No matter whether I use mpv or smplayer, or disable frame rate conversion, as long as SVP is integrated to the player the audio immediately starts desyncing

I think I know the reason - it's a inconsistency between the actual video frame rate and the value written in the container and thus used as a base frame rate for the frc conversion.
This value is exposed by mpv to the Vapoursynth engine as a global variable called "container_fps". If the real fps doesn't match - we're probably screwed o_O

It turns out that there're a lot of problems with interlaced videos here...

1. SVP replaces the entire video filter chain with the vapoursynth filter, while interlaced videos need the yadif filter to be inserted before - luckily this's quite simple to fix

2. SMPlayer sets incorrect mpv option when using "Yadif (normal)" - it sets "--vf-add=yadif" instead of "--vf-add=yadif=frame", so both "Yadif" modes in SMPlayer now output doubled frame rate

3. Vapoursynth filter inside mpv can't properly handle video deinterlaced with doubling frame rate because the video IS actually 50 fps while the internal variable "container_fps" is still set to 25 fps.

So... to make interlaced video work with SVP we need:

1. Fix SVP Manager
2. Force SMPlayer to add "--vf-add=yadif=frame" to advanced mpv options