Search options (Page 312 of 347)

badrange=-24 will use exhaustive search regardless of "search" value

Maken1
i dont know if i need this

Yes you do   The second fixed bug is about motion vectors accuracy => picture quality.

ddragon
It's just that 3.06 used a lot less CPU for me.

you can't compare them in this way cause the settings and their default values are very different

the tearing on the left-hand side of the screen

i've got no idea what do you mean  "tearing" is a frame break caused by wrong vertical sync
could you make a screenshot of this?

There's a chance that it'll be better with the latest SVPflow libs (today's build 1.0.3) but they need some adjustment in scripting code.

You could test it
- unpack DLLs from there to SVP_install_dir/Plugins
- replace SVPMgr.wsf with attached one

... or just wait for SVP 3.1.2 update

See the first message!

Now we know that it's a bug (or a "feature"  ) either in 301.10 OpenCL compiler for GTX680 or in SVP code.
I hope the next WHQL release will show the answer.

ddragon

Your CPU is to close to "reference system 3" (4 cores Phenom @2.8 GHz) so 80% CPU load at default settings is normal. If you think it's too much just install "level 2" video profiles from start menu shortcut called "reset profiles".
Also 3.1 assumes that you're using hardware video decoder (LAV filter, for example) and I know nothing about HW decoding and .FLV format so it may be some splitter/decoder issues there.

smoothness doesn't look good

Some people think that 3.1.1 has too high threshold for scene change detection. Though I don't agree with them you still can adjust it by yourself by uncommenting "smooth.scene.limits.scene" line in overrride.js file.

these profiles are for "source video resolution"

sergioleon
Нет уж, что бы можно было что-то с чем-то сравнивать, поставь и там и там блоки 16*16.
Кроме того, мелочь конечно, но 23-й с выключенным подавлением контурных = 11-му , а 3.1.1 у тебя честно пашет на 23-м.

Ну как-то примерно так:

SetMemoryMax(1024)
SetMTMode(3,11)

# Наверное это всё хозяйство само по себе многопоточное
LoadPlugin("C:\Program Files\MeGUI\tools\dgindex\DGDecode.dll")
DGDecode_mpeg2source("r:\Сакура.d2v", cpu=4, info=3)
LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\ColorMatrix.dll")
ColorMatrix(hints=true, interlaced=true, threads=0)
LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\TomsMoComp.dll")
TomsMoComp(1,5,1)
#crop
#resize

# Сюда суём СВП
LoadPlugin("C:\Program Files\SVP\plugins\svpflow1.dll")
LoadPlugin("C:\Program Files\SVP\plugins\svpflow2.dll")

SetMTMode(2)
analyse_params="{block:{w:8,h:8,overlap:0},main:{search:{coarse:{distance:-10},bad:{sad:2000}}},refine:[{thsad:250}]}"
smoothfps_params="{num:6,den:1,algo:13,cubic:1,mask:{area:100},scene:{}}"

super=SVSuper(super_params)
vectors=SVAnalyse(super, analyse_params)
SVSmoothFps(super, vectors, smoothfps_params, url="www.svp-team.com")

# Вот тут не знаю, как оно работает с MT
SetMTMode(3)
LoadPlugin("C:\Program Files\MeGUI\tools\avisynth_plugin\UnDot.dll")
Undot() # Minimal Noise

Ну правда "num:6,den:1" это, наверное, перебор

В скрипте надо править, или в файлике override.js - параметр "smooth.scene.limits.scene".

Domas4

I think it's better to incorrectly detect a scene change sometimes than do not detect the actual change at all.
Though detection in 3.1 is much better than in 3.0.x we'll continue to improve it

порог смены сцен выкрутить вверх