flowreen91 wrote:
Sopheus wrote:

As a sidenote, I care about clear image more than FPS

To make image more clear by removing blur, click download zip here:
https://gist.github.com/igv/8a77e4eb827 … c1c50c317e
and put the .glsl file in a shaders folder like this:
"C:\Program Files (x86)\SVP 4\mpv64\shaders\adaptive-sharpen.glsl"

Then add this line in mpv.conf to enable it:
glsl-shaders="~~/shaders/adaptive-sharpen.glsl"

If you want to see comparison ON-OFF add this in input.conf:
CTRL+1 no-osd cycle-values glsl-shaders "~~/shaders/adaptive-sharpen.glsl" ""; show-text "AdaptiveSharpen ON-OFF"

That shader doesn't remove blur but the added sharpness can make the image look perceptually clearer. But Rife v4.25 and even that MPV config should look pretty good already. If that's the path he wants to take then there's a few different sharpness shaders to choose from. Plus you can change the sharpness settings inside the glsl file which is what I used to do.

Sopheus wrote:

Hey good folks, can anyone give me advice on improving SVP settings I have at the moment primary for 4K (3832x1920) files?

https://i.imgur.com/i6B10bN.png

You can't because RIFE you get what you get. It's been a while since I used Rife so I can't remember what IC Custom:100. But with v4.25 you should still be getting about the best image you can get outside of manually tweaking SVP settings. Your MPV config looks likes a typical Internet config but there's nothing there that should make things look less clear.

28

(2 replies, posted in Using SVP)

MAG79 wrote:

SVP Index must show N\A when you not playback video with smoothness.
But while playback video it must show value near to 1.
At your screenshot I see you just starting to playback. Just wait for changings.

Thank. I noticed this while a video had been playing for about 1 minute so how long do I wait?

29

(2 replies, posted in Using SVP)

SVP Index not showing any metrics. Just N/A. I'm not using RIFE, only SVP settings at 120fps.

The higher the number, then "in general" the better the model is with fewer artifacts. This is not always the case so you can search the thread or try yourself. Rife 4.25 is probably the best but you need a decent Nvidia GPU. Basically higher number models require more GPU power.

I remove that script on every re-install. I already have an mpv thumbnail process running with the main process. So adding this extra process just makes mpv very unstable.

lol

One card is clearly more powerful than the other so it's your choice depending on your needs. There is no simple answer to your final question but a quick search of these threads will give you more information including a thread dedicated to using LSFG and SVP. But short answer, SVP out of the box and LSFG are very similar.  If you decide to use SVP with RIFE AI then MadVR adds extra GPU overhead which might favor LSFG which will be lighter on the GPU. LSFG and SVP can be combined. But with some considerable work and a decent GPU then SVP by itself is best overall. 

But the end result might depend on your usage and tolerance for artifacts. I have a low tolerance so I put in the work to get the best results with SVP. Others on here are fine using SVP with RIFE AI (for example) for smoothness and accept the artifacts or are lucky enough to watch content like Anime that doesn't highlight them too much.

If others want to give you a more definite answer then good luck because there are too many variables for any definite answers to make sense. But you may only understand this after you make your decision and try things out for yourself.

34

(3 replies, posted in Using SVP)

flowreen91 wrote:

Nice, then try to make a request to SVP devs to update default mpv config to remove "-copy", enable blend frames by default
and to drop RIFE support since out of the box SVP config outperforms in smoothness and quality.
And maybe allow users to select from menu dropdown higher values than "Movie Frame rate x6" multiplier and 240 fps. xD
Constructive feedback is always welcomed.

Not sure how serious to take this. Probably not serious at all but the questions don't make sense, even as jokes so maybe you misread a little?
1. SVP doesn't outperform RIFE "out of the box".
2. RIFE or not, SVP still needs a good GPU for the most optimised real time processing of live action content.
3. But the very early artifact riddled versions of RIFE used by some (anime?) users suggests that RIFE is still useful with lesser GPUs.
4.Why would "-copy" be removed when it might be actually needed?
5. Higher multipliers than x6 don't make much sense.

I stopped posting my configs because I was told they were useless and at that stage they could have been better which is why I called this lessons learned. A key point was not following the trend of using stupid amounts of overrides. There's a lot of valuable information on this forum but it is spread all over the place in little bits and pieces. I'm grateful for that info because it has opened my eyes to the possibilities of not using RIFE. Just trying to pay it forward a little.

35

(3 replies, posted in Using SVP)

1. Integer interpolation multipliers seem to work best which might be why 60fps isn't quite as smooth as it could be.
2. Most SVP defaults work best and "overrides" should be used sparingly. Otherwise you end up trying to fix problems that you caused.
3. Consistent frame pacing means less stutters. 1% lows are more consistent with "-copy".
4. Recent mpv versions will fallback to "copy" if needed which might be adding to frame pacing inconsistencies.
5. The most consistent frame-pacing on Windows mpv is with hw d3d11/d3d12.
6. If you have smooth motion with occasional micro-stutters then "Blend Frames" can help smooth them out.
7. With the above, there should be no longer be a need to increase default scene.blocks.limit for the Hugo intro.

I've said all this before, but 99% of the nasty RIFE artifacts are gone. Leaving only the occasional fast motion artifact which can be removed, but at the cost of slow pan smoothness. So unlike with RIFE, there is a choice because there are almost all artifacts can be removed. But the trick is to find the balance between zero artifacts and ultimate smoothness.

Bottom line is that if you have a good GPU and a 120Hz display then RIFE is dead.

36

(2 replies, posted in Using SVP)

rosetisha wrote:

What is "Force the exact value" under FPS change option? Does it do good or bad? It force 120fps if on and 119.88 when of. Which one  is better?

Should I use 5x or 120fps for better smoothness?

What is "Width of top coarse level" ?

"Exact value" is useful for VR devices because they have fixed frame-rates.  If you hover over each SVP option, a tooltip will come up explaining what each option is for. Or you can Google it and get even more detailed explanations. I can never understand questions for "better smoothness" without even trying anything yourself first.

P.S. I took my own advice, did more searching and found new information. Bottom line as I have said before is that the SVP defaults are mostly correct. But depending on your GPU and CPU they can be tweaked to produce optimal results smile

Just a reminder for those of you with Nvidia cards. Remember to set the Power Management Mode to Prefer Max Power. I forgot to set this on a different computer and although SVP still worked well, I wasn't able to optimise it to the fullest. In "Normal" power mode with SVP running, my GPU "rests" at about 103w. But in "Prefer max power" it hovers around maximum and never goes below 120w. The extra 20w removes any remaining artificial SVP bottleneck.

Sophiasm wrote:

Hi everyone, when I enable SVP frame interpolation for HDR videos (HDR10) played via MPC-HC + madVR, I notice a slight color shift (especially in skin tones) compared to playback with SVP disabled. Is this expected behavior, and which SVP or madVR settings should be adjusted to preserve accurate HDR color while using SVP?

"Additional Options" -> "Allow Output in 10bit color depth".

raider10 wrote:

Interesting... we need to get SVP to do DLSS, downscale the frames, then create the intermediate frames, and then upscale again to 4K to save the video, just like it does in video games. I don't know if it's possible, but I don't think it's impossible. I'm talking about transcoding, not viewing in a player, so I think the changes need to be made in the app, or on Steam, or wherever. wink I'm not an expert on this, but the app developers might have an answer that would speed things up considerably.

Now we don't need that as I explained in your thread and it is practically impossible to do a good job with SVP which unlike DLSS is an external interpolation technology.

Chainik wrote:

> I used to use RIFE to watch at 80fps on a 60fps display

and there're must be 20 dropped frames per second in this case, regardless of the player settings and even regardless of what the stats prints big_smile
I can imagine that with vsync off the player won't report any dropped frames
however the monitor will still update at 60 times per second

Yeah if I remember correctly I usually turned off Vsync or at least I played around with various timing options.

raider10 wrote:

A question for the experts here: would it be possible to make RIFE work like DLSS does in games, by first downsizing the image to 1080p or 1440p and then upscaling it back to 4K? I don't think this is far-fetched, and I'm sure it would provide an extra speed boost during re-encoding. If this option exists, where should I set it up?

Greetings to everyone.

RIFE doesn't do anything. It's just an engine. SVP has the option to downscale.  By default any downscaled output will be upscaled if run on a higher resolution display. Or you can control the upscale yourself with a media player. Check the SVP manual for details.

matiasflyhigh wrote:
dawkinscm wrote:
flowreen91 wrote:

Ooh SVP updated to latest mpv version so it probably reseted your mpv.conf configuration file
and since it's newer mpv version, slight chance that it works slower than old version and might trigger this error in console:
https://gyazo.com/2cfe3723f732a057a8a838249d01320c (you can confirm by pressing ` in mpv)

Try to play around with mpv.conf settings and see which removes the stutter:
hwdec=auto
or
hwdec=no

add this too if slowdown persists:
profile=fast

If you think it's caused by bad SVP settings, then go to your SVP profile -> Automatic options selection -> and select one of the default profiles to reset it to recommended settings, and restart SVP.
This should fix the recent performance issue.

It's a more recent mpv version but not the latest, and it's not slower. Profile=fast will make some difference, but not enough to stop major packet loss. With this GPU, changing to hwdec=no will almost certainly perform worse than hwdec=auto.  I also wouldn't use those SVP settings as some of them could be causing problems for your CPU as well as your GPU. Better off using Automatic after SVP checks performance, then start to tweak from there.

Also it's worth restarting SVP every so often otherwise performance will begin to suffer (possible memory leaks?).

It's nothing related to SVP; no matter what configuration I'm currently using, this problem occurs. It didn't happen a few days ago. I imagine it's some command in mpv.conf that I forgot to reset; I thought it was "display-sync=resample" or something similar. I tested them all, but nothing solved it... the lack of a backup cost me too much, hahaha.

I'm going to end up uninstalling and giving up on movies/series. I can't watch them in 1x speed; I find it too slow, and buying a product I can't use is a real shame.

I used to use RIFE to watch at 80fps on a 60fps display so what you are saying is possible, although that was on a 4080. SVP isn't the issue because no one else is suffering from this. Your SVP config could be an issue depending on your CPU which you haven't mentioned yet. Also you should post your mpv config on here. In the mean time, you can completely uninstall SVP, reboot then reinstall and retry with my previous Automatic profile suggestion.

flowreen91 wrote:
matiasflyhigh wrote:

Hello everyone,
a performance issue with the integrated mpv on SVP that hasn't occurred before. Recently

Ooh SVP updated to latest mpv version so it probably reseted your mpv.conf configuration file
and since it's newer mpv version, slight chance that it works slower than old version and might trigger this error in console:
https://gyazo.com/2cfe3723f732a057a8a838249d01320c (you can confirm by pressing ` in mpv)

Try to play around with mpv.conf settings and see which removes the stutter:
hwdec=auto
or
hwdec=no

add this too if slowdown persists:
profile=fast

If you think it's caused by bad SVP settings, then go to your SVP profile -> Automatic options selection -> and select one of the default profiles to reset it to recommended settings, and restart SVP.
This should fix the recent performance issue.

It's a more recent mpv version but not the latest, and it's not slower. Profile=fast will make some difference, but not enough to stop major packet loss. With this GPU, changing to hwdec=no will almost certainly perform worse than hwdec=auto.  I also wouldn't use those SVP settings as some of them could be causing problems for your CPU as well as your GPU. Better off using Automatic after SVP checks performance, then start to tweak from there.

Also it's worth restarting SVP every so often otherwise performance will begin to suffer (possible memory leaks?).

Also the dropped frames rising counter doesn't always mean that you see actual issues on screen. Partially because, good displays are can hide such issues and partly because just opening the mpv overlay is a minor tax on the system which can cause mpv to drop packets if you are already at the limit.

AutumQueen92 wrote:

Nope, not useful.

Shame though coz now I've worked out how the original settings were created I was able to make more sense of what should actually be changed. Most of the changes in the OP are not unecessary at 120hz and with some tweaks probably not needed at 60Hz either. But no problem. Cool smile

My previous settings were very good, besting RIFE in almost every way. But using the OP settings as a baseline, I have been able to improve on my previous settings. I also have a little better understanding of how SVP actually works. So this was my pay it forward. But with no feedback it was difficult to tell if it's even worth continuing this. But maybe this is enough. I hope it's been useful smile

I think I understand how the previous list of settings were created. Once that clicked, it made it easier for me to make some changes and revert a couple of settings back to default. Short version; remove the pnew and pzero penalties. I also set lambda penalty to 4.0 but this is pure guesswork. But with these changes I was able to revert Decrease grid step from local, back to global. I also disabled Artifacts masking but I assume this was overridden anyway.

redraiderj wrote:

Please find attached

Different codec and bitrate, but both are within normal parameters. It might be the weird aspect ratio that SVP is struggling with?

I see a few people have downloaded the config and I would love some feedback. I'm particularly interested to hear about smoothness or lack of and CPU/GPU type and usage. I'm thinking about modding this for 60fps but not sure if that would be interesting since I'm sure others have already done that.

KnightRiderKARR wrote:

levels.pel = 1;
levels.scale.up    = 1;
levels.scale.down    = 1;
levels.full     = true;
analyse.block.w    = 32;
analyse.block.h    = 32;
analyse.block.overlap    = 2;
analyse.main.levels    = 4;
analyse.main.search.type   = 8;
analyse.main.search.distance = -8;
analyse.main.search.coarse.type  = 4;
analyse.main.search.coarse.distance  = -16;
analyse.main.search.coarse.bad.range  = 0;
analyse.main.penalty.lambda   = 1.0;
analyse.main.penalty.plevel   = 4.0;
analyse.main.penalty.lsad   = 800;
analyse.main.penalty.pnew   = 5;
analyse.main.penalty.pglobal   = 5;
analyse.main.penalty.pzero   = 10;
analyse.main.penalty.pnbour   = 5;
analyse.main.penalty.prev   = 0;
analyse.refine[0] = {thsad:2000, search:{distance:2, type:4}};
smooth.algo = 23;
smooth.scene.mode = 0;
smooth.mask.cover = 20;
smooth.mask.area = 8;
smooth.mask.area_sharp = 0.70;
smooth.scene.limits.m1 = 3600;
smooth.scene.limits.m2 = 7200;
smooth.scene.limits.scene = 10400;
smooth.scene.limits.zero = 10;
smooth.scene.limits.blocks = 60;

Try and tell me if its good or not smile

As suggested by @AutumnQueen, I've deleted the "not useful" configs. Some of you downloaded the attachment. Others hopefully found some use too smile