> My gut feeling is that the NVidia Optical Flow algorithm in SVP4 is set to very low.

Unfortunately it's set to high.

You can play with the "grid size" value. 4px will give you the raw NV's output...

according to ffmpeg's log - all ok, there must be two streams (videos + audio) in the output file

10:42:34.055: Output #0, mp4, to 'C:/Users/Tim/Videos/bankruptcy.SVP.mp4':
10:42:34.056: Stream #0:0: Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709/unknown/unknown, progressive), 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 60 fps, 60 tbr, 16k tbn, 1k tbc (default)
10:42:34.056: Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 125 kb/s (default)

2,478

(1 replies, posted in Using SVP)

> Why?

Depends on the error.

2,479

(33 replies, posted in Using SVP)

"10-bit output in SVP" is for mpv and VLC, it does nothing for MPC-BE

2,480

(1 replies, posted in Using SVP)

It's better to ask such questions via email

yep, ffdshow can't decode h265

2,482

(1 replies, posted in Using SVP)

Nope, it can only switch SVP shaders based on the current frame "quality" - which is "adaptive" rendering mode.

2,483

(33 replies, posted in Using SVP)

> Is this still an issue?

at least much less than before

not sure... you'd better wait for the next build of VLC plugin
it's not about raw CPU power

2,485

(1 replies, posted in Using SVP)

check %APPDATA%\SVP4\logs\active.log

https://www.svp-team.com/wiki/FAQ#SVP_M … .27t_start

Если речь конкретно про HDR, то попробовать выключить "восстановление цвета" в настройках SVP и посмотреть есть ли разница.
Если есть, то включить назад "восстановление цвета", а в окошке "все настройки" найти frc.color.hdr.adaptive и сделать его false. И опять проверить есть ли разница.

> прилетело обновление на potplayer

Поставить обратно предыдущую версию?

2,488

(1 replies, posted in Using SVP)

try again later

> Can quality improvements be made on the NVOF front?

yeah, theoretically, by post-processing motion vectors received from the NVOF

* added file tag "hdr=on|off" or "transfer=hdr|sdr|2084|709"

Indeed hmm Still all it has is 8-bit color data and no HDR meta info (neither dynamic nor static) at all.
And I can't check right now if it still switches TV to the HDR mode.

> Пункт ClearMotion TM сразу над MiraVision TM

На прошлой странице же ещё обсосано. Всего 5 лет взад big_smile

works on my 2070...
it can't be more stuttery than "software mode" with NVOF off, considering the same video, same player and same SVP rendering options used

but if you're hoping for "even in really fast paced scenes or with scenes with a lot of moving people or objects without artifacts" - then no, current implementation is overall worse than a good old "software motion estimation"

FYI

2,494

(128 replies, posted in Using SVP)

Finally, VLC audio sync problems fixed in rev.168!

Только сегодня, только один день!
Мгновенное исполнение желаний! big_smile

обновитесь...

2,496

(1 replies, posted in Using SVP)

> There will be discount in the future ?

there's kind of "backdoor" on the Chinese site wink
https://www.svp-team.cn.com/wiki/Purchase

2,497

(3 replies, posted in Using SVP)

ffmpeg doesn't have MVC decoder

madVR is a renderer - i.e. it renders video onto the specific screen
you can't encode anything "with the settings of madvr"

"Black bar lighting" will eat a lot of bitrate and will look awful after the encoder, this's why it's off in encoding mode

> Is this a Mandala effect

there was a memory leak somewhere in-between ffdshow x64 and Avisynth+ x64 in early AVS+ builds
let's think pinterf fixed it (probably unintentionally)

> As for HDR content, AFAIK madVR renders that properly.

madVR's HDR doesn't work with ffdshow in front of it

> MPC x64 was always stuttering with 4K HDR for me

seems like NV CUVID in LAV decoder is the key to success wink