At the risk of stating the obvious, going to "power options" and changing the setting to "high-performance" makes for a clear improvement. I don't remember this making much difference way back when, but with Windows 10 and my lowly 430 watt power supply, this seems to really up the performance. To save time if you want to switch back and forth, just pin the "control panel" icon to your taskbar and when you hover your cursor on top of it, it will give you the option to directly open "power options".

2

(7 replies, posted in Using SVP)

If FFDshow raw filter is your only hindrance, then maybe try using Potplayer, the 64-bit version. It requires the LAV filter, but not the FFDshow raw filter to work with SVP. As I recall, you have to go into SVP settings somewhere (maybe "all settings"), and go half way down the list and find the "Potplayer" settings area and delete "false" and type in "true". Then restart SVP, and you're good to go.

In my experience, the 32bit version of Potplayer freezes with CUDA and SVP running. The 64bit version does not.

4

(6 replies, posted in Using SVP)

My guess is that you're using MadVr and you need to lower your settings. Your "average stats rendering" is too high at 17.34ms. You need to drop it below your vsync of 16.67ms.

Come to think of it, I had a couple of rainbow flashes on starting something up with SVP, but it passed in a millisecond and then played normally. 99.9% of the time, I've had no problem. Maybe it's the version of Win 10 I'm using: Build 15019

For what it's worth, I'm running an i5 3570k with a GTX970

Hi: I already applied the changes to generate.js and it works fine. But I am happy to undo the changes.

However, how do I apply the modified settings in override.js ?

Somewhere in here?

/***** SVAnalyse options *****/

//analyse.vectors            = 3;
//analyse.block.w            = 16;
//analyse.block.h            = 16;
//analyse.block.overlap    = 2;

Hi: When I set Motion vectors grid to "24px. Large 2" I get practically no artifacts. At "16px. Average 0" I start to get noticeable artifacts but better smoothing of course.

How do I set up something like "20px. Average 0"  ?

Presumably I go to the Javascript file called "generate" and add a new entry to the following:

    case 32: analyse.block.w=32; analyse.block.overlap=0; break;
    case 28: analyse.block.w=32; analyse.block.overlap=1; break;
    case 24: analyse.block.w=32; break;
    case 16: analyse.block.overlap=0; break;
    case 14: analyse.block.overlap=1; break;
    case 12: break;
    case 8: analyse.block.w=8; analyse.block.overlap=0; break;
    case 7: analyse.block.w=8; analyse.block.overlap = profile.mv_refine ? 0:1; break;
    case 6: analyse.block.w=8; break;

Basically the same as here: https://www.svp-team.com/wiki/SVP:Daum_PotPlayer

Except that I set LAV hardware acceleration to NVIDIA CUVID because I have a GTX970 and it's totally safe to do so on the 64bit version. The rest of what I do is pretty much contained in the previous post.

Also, following another contributor's advice, I've reduced artifacts on the documentaries I watch to nearly zero by setting SVP as follows:
Motion vectors grid: 24px. Large 2
Decrease grid step: By two with global refinement

Doing this produces much the same effect as setting the first to "12 px. average 1" and the second to "disabled" but has the aforementioned advantage of almost completely eliminating artifacts for me.

No problems here using SVP with GPU acceleration enabled and the new Nvidia driver on Win 10 (build 14986).

Maybe the following thread has your answer:
https://www.svp-team.com/forum/viewtopic.php?id=2797

Been using 64bit Potplayer for months. No "slowdowns", though I didn't have slowdowns with the 32bit version either. Doesn't need (nor can it use) ReClock and works great with or without FFDshow (so you don't need to install that either if you don't want). And, to my eyes, the built-in video options (i.e. VMR9/EVR scaler options (I use Shader(2-Pass) Lanczos) plus the Resize options (I use Bicubic and set the multiplier to 2 times)) enable you to approximate MadVr quality (i.e. in MadVr setting all scaling algorithms to Jinc w/o activate ringing filter and not touching upscaling refinement) at half the GPU usage. So, even though I'm using a 55" 4K TV to watch documentaries with SVP, I don't use MadVr either. PotPlayer has more built-in options for audio playback than MPC or anything else I've seen (I have a 4.1 audio system). To my ears, sound quality is better on the 64bit version compared to 32bit if you have a decent sound system.

11

(70 replies, posted in Using SVP)

For what it's worth, I use SVP with Windows 10 (on build 14986 at the moment, as 15002 and 15007 are nightmarish) and I have not found it to cause unusual crashing or freezing.

Sounds like my 60Hz Samsung TV which can only handle 24FPS and 30FPS videos. 25FPS videos are unwatchable without SVP.

13

(6 replies, posted in Using SVP)

Hi, I don't use MadVr anymore but I used to. According to your screenshot, your vsync is 16.68ms whereas your average rendering time is 17.52ms, which, if I remember correctly, is too slow and will cause frame drops, choppy play, etc.
Average rendering time needs to be below 16.68ms, I believe.
Beyond that, you might try using PotPlayer, which is what I use (the 64bit version, works perfect without ReClock).
My rig is kinda like yours, i5-3570k (but no overclock and my card is a GTX970 which approximates yours anyway)

14

(6 replies, posted in Using SVP)

I use ffdshow audio decoder too because MPC-HC and MPC-BE don't seem to output 4.1 audio. Neither does SMPlayer.

Which is why I primarily use PotPlayer, which does support 4.1 audio output.

15

(3 replies, posted in Using SVP)

If I remember correctly, you have to close the target program before you patch it.

If I set main.setup.potplayer.prefer_avisynth = false
when SVP runs I get stuttering playback too.

Quick question: Which is smoother?
SVP + VLC (vapoursynth)
or
SVP + PotPlayer (avisynth)

18

(14 replies, posted in Using SVP)

If MPC-HC becomes too much of a hassle, you might try the 64bit version of PotPlayer. Doesn't crash using Nvidia Cuvid  (so I haven't used a 32bit player in months.) Its built-in "VRM9/EVR scaler" can be adjusted to achieve much the same effect as MadVR but uses less than half as much GPU processing power. So I haven't used MadVr in months either. I don't know if it will solve your other problems, but it's an option to keep in mind.

19

(15 replies, posted in Using SVP)

HorribleSub's 23.810 fps releases play back smooth on my 60hz screen if I set the frame rate conversion to Moviex2.5

Maybe try that?

Thanks James D for the heads up on the update: http://www.videohelp.com/software/VapourSynth

Don't know if you updated to build 14946, but doing so totally crashed something on my computer (i5 3570k, GTX970, 16g of RAM). For some reason video would stutter when using vapoursynth with Potplayer (my CPU would run at 100% for some reason). I changed back to avisynth and soon video started to flash on and off. Then finally my whole screen reverted to black and white at a display of 360 x something, even without using SVP. After some mucking around, I gave up and did a clean install of 14946, which fixed the problem. Lately builds have also caused issues with MadVr too. Updating Windows 10 is worth it for the regular benefits I see on my 4k screen display and to audio quality too, but once in a while it cause serious issues with video playback.

Recent builds of Windows 10 are not always compatible with MadVr. The result is identical with your description: "occasional, very slight stuttering which is very distracting." Have you tried switching to EVR Custom?

A new x64 version of Potplayer is out and seems (as far as I can tell) to work well with vapoursynth: http://www.videohelp.com/software/PotPlayer

Hi, I'm using the latest build of Windows 10 (i.e. build 14936) and found MadVr's maximum rendering time had increased to approximately ten times normal, which caused video slowdowns for me too. I solved the problem by using another video renderer: EVR custom present.

Still no good. I guess I'll just have to wait a bit longer. Thanks for the help.