New version of SVP? (Page 4 of 7)

where is my favorite "facepalm" picture?

http://forum.doom9.org/showthread.php?t=164554

1.0 * 1.2 * 1.15 = 1.38

Wait. Are you saying we can update SVP right now to get all these improvements by replacing the DLLs without having to wait for a new package to be built on the main website?

Which DLLs in the SVP program folder are these?

(assuming I don't find it myself first...)

EDIT: Whelp, found them.   They're in "Program Files\SVP\Plugins"

I'm definitely going to look into this and use it as a baseline for performance in my undervolting.

And for the record - it's up to 38% faster. Which means from zero to 38%.

There's a reason I used the words "could" and "maybe".

Besides, I got a wierd shimmering and/or flickering when using the exact same settings I've always used that doesn't seem to occur on the official 3.1.6 + hotfixes, so for actual video use I'll continue using that.   For reference, said shimmering/flickering seemed to be greatly reduced when I enabled "by two with global refinement" if that makes any difference.

Yup, setting 6 threads or less on my dual-core Pentium G3258 works well; by comparison setting 7 threads or more causes the flickering/shimmering effect that I saw with "Auto".

I'm guessing this is a known bug?

EDIT: And now I get to pick on you Chainik with your Doom9 post, what kind of software developer doesn't use ISO 8601 for version dating, that is YYYY-MM-DD? And you're not allowed to pull the American card because both of my parents and myself have lived in northeast Ohio our entire lives.

Where did you get the latest 1.1.14 cause I don't see it here http://www.svp-team.com/wiki/Plugins:_SVPflow

P.S. Mystery, Avisynth 2.6?

Want even more of a boost?  Use the newest trunck revisions of LAVfilters (if you're not already).

For two smaller CPU utilization reductions (more noticable on weaker hardware), if you're not using madVR, you can use "D3D Fullscreen" . Also if you're using MPC-BE, then select the "MPC Audio Renderer"; if you're using MPC-HC, then you can download the MPC-BE standalone filters and add it to MPC-HC's "External Filters" list manually (make sure you set it to "Prefer!".)

In total, if you were using a stock copy of the MPC-HC that came with SVP, you could see a 10-20% CPU utilization decrease by doing all three things.

Yup, that's it.

And Chainlink, Microsoft is a corperation, not a software developer.  You really think they don't use yyyy-mm-dd in-house?

Does LAV Filter 0.65 include these optimizations?

I tried reproducing the high CPU usage problem the next day and couldn't reproduce it. I'll let you know if I see that happening again. I had tried both with AVS 2.6 and + and saw the same high CPU usage for both when using the new DLLs, and lower when using the previous DLLs.