Search options (Page 314 of 349)

I believe Daum PotPlayer is more customizable. Also it has built-in DXVA copy-back decoder so no need for LAV

The vote lacks one option - "I don't use MPC-HC" 

Vladdo
i've just spent the last hour trying to replicate the other 1440x1080i bug

I should ask for the error message first This's simple - just patch .exe file of progdvb with that tool and it should be OK. MPC-HC executable is already patched so it works.

I'm now using 3.06 so I can't replicate the bug as it doesn't appear to be affecting 3.06.

3.0.6 and 3.1.1 can easily live together in different installation folders
The main thinks that is different in 3.06 and 3.1.1 GPU processing is "Motion vectors interpolation mode" option so try to switch it from "bicubic" to "bilinear". Anyway I think it's some kind of driver bug for 7xxx chips 

What do you mean? 
Obviously 50 Hz screen is the best for 25 fps source. Some people believe it's the best for 23.9/24 fps sources too - they use motion interpolation 24*2 = 48 fps + ReClock up to 50 Hz.
I don't like ReClock cause I prefer to bitstream DTS sound to AV-receiver and for me 23.9 * 5/2 = 60 Hz mode is much better than 23.9 * (some_strange_value) = 50 Hz.

MAG79 внезапно выкопал гениальный пример "пользы упрощеннного поиска на грубых уровнях".
Выглядит это так, как в аттаче - ВСЕ вектора в кадре оказываются абсолютно не правильными, весь дом уезжает вниз.
Ирония в том, что при любом поиске, отличном от расово верных "шестиугольников", всё хорошо 

erik
can not find the automatic settings "reference system level 1-2-3 etc. etc."

it's determined automatically at installation time:

and you can change it from Start menu -> SVP 3.1 -> Reset profiles (run as Administrator)

Это чо, новую спецификацию BD принимать, и все имеющиеся сейчас проигрыватели на помойку? 

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.