Search options (Page 5 of 12)

I think it's the problem of driver instead of W10. I've heard the driver already broken even in W7/8.1

That's more like "lack of memory"? DXVA copy back is memory intensive since they're copying back the memory so it can be processed further. And does NVIDIA CUVID really works with SVP for NVIDIA newest driver?

Hmm, is that always happening? I never notice this. I'll check it later with CPU usage log info. If that's not happened in my PC, maybe you should check your PC in case of some malware.

Yeah, I didn't really realized until you mentioned it.

I tried TimeStretch but ffdshow_source() only contains the video not the audio, so TimeStretch complains the clip has no audio.

While what I could think of is to use DirectShowSource to load audio only in complement to ffdshow_source(), I prefer to load it using ffdshow too as Mystery mentioned above.

For reference, this is part of my last used script which generated from SVP 3.1.7

global crop_params=""
global resize_string=""
global super_params="{scale:{up:0},gpu:1,rc:true}"
global analyse_params="{block:{w:32,h:32},main:{search:{coarse:{distance:-10}}}}"
global smoothfps_params="{rate:{num:5,den:2},algo:13,mask:{area:50},scene:{}}"

It equivalently by changing value in "override.js" to

levels.gpu = 1;
levels.scale.up = 0;

analyse.block.w = 32;
analyse.block.h = 32;
analyse.main.search.coarse.distance = -10;

smooth.rate = 5;
smooth.den = 2;
smooth.algo = 13;
smooth.mask.area = 50;

So in short, you should look for your "last used script" which generated by SVP 3.1.7, and use that for reference to change the value of "override.js" in SVP 4

To tweak the "generate.js", you should have any experience with JScript and/or Javascript. The "override.js" is supplied to make it easier to tweak the values that will be fed to SVPFlow.

In the end, you still need to refer this page https://www.svp-team.com/w/index.php?ti … ow_options to tweak it. So I'm sorry I can't advise furthermore.
When you're tweaking the "override.js", you're on your way

Yes, makes the interpolating as multiple of exact integer is the definite way to reduce artifacts.

Don't change any values or expression in "generate.js". You only need to compare the value it generates and comparing it with the values from 3.1.7.
You should look for "override.js" instead of "generate.js". The necessary values are defined in "override.js".
Don't forget to remove the commenting sign in front of each expression (the "//")

Refer to this page, https://www.svp-team.com/wiki/SVP:Techn … AVS-script

The FPS usually floor-ed, e.g 59.94 usually only 59, 23.97 only 23, etc, so stick with 60Hz refresh rate.

If by chance you want to manually override or manually change those available value, you'll have to change those values in override.js.
This will help you to know what those values mean https://www.svp-team.com/w/index.php?ti … ow_options

For the mode, this will explain those (scroll to the bottom of page) https://www.svp-team.com/wiki/SVP:Technical_insights

Actually, it's about profile setting.

The "optimal" setting which marked as "default" is from SVP Team.
Clearly your "default" setting doesn't give you what you prefer, so you tweak it to the point which the balance that you prefer.

I would suggest you to search around because this issue (the balance between smoothness and artifacts) already asked many times, nonetheless, the setting that you need to look out are:
1. Artifact masking, set that to higher value to mask the artifact, in exchange of smoothness.
2. Change the target framerate to be exact multiple integer of the frame rate, such as the target frame rate to 2x.
3. Decrease grid step, this refinement could help to filter the bad calculated vector motion, in exchange of heavier CPU usage.

There are many others, but those 3 could be the starting point before you tweak the profile further.
This page from SVP wiki should help you, https://www.svp-team.com/wiki/SVP:Profile

Those are known as artifacts.

To quote from SVP wiki:

https://www.svp-team.com/wiki/SVP:Profile

MAG79
He meant it's like "demo mode" in SVP 3 but with target-able frame rate for each panel, and with 2-3 panel picture.
If the "demo mode" in SVP 3 it's the difference between SVP on and off, and that's only two panel.

CMIIW.

Not sure this is related or not.

When I was experimenting with various SVPFlow setting, there was a time that the performance got better after making the "Buffer back/ahead" in ffdshow bigger.
I'm using 20/20 now, the default was 10/10.

Of course, the problem could be incorrect thread value, like Keis' problem, http://www.svp-team.com/forum/viewtopic … 587#p54587

MAG79

It would be nice if SVP Manager stop nags me about using x64 player
Is there something that I need to set to stop it?

Even disabling the "Show OSD messages" doesn't work. For now, the only workaround is to exit SVP Manager altogether.
I'm still using SVP 3.1.7