51 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

flowreen91 wrote:
erriep2703 wrote:

# Deband filter. Always turn on for anime.
deband=yes # Default values are 1:64:16:48

I see that these settings are present in an outdated guide:
https://kokomins.wordpress.com/2019/10/ … fig-guide/
<meta property="article:modified_time" content="2024-02-08T06:53:17+00:00"/>

Probably we should use more recent configs from 2024:
https://kohana.fi/article/mpv-for-anime
https://artoriuz.github.io/blog/mpv_upscaling.html
https://iamscum.wordpress.com/guides/vi … /mpv-conf/
https://thewiki.moe/tutorials/mpv/

I know nothing about Anime shaders so I will leave that to the experts smile  But there's nothing wrong with his config as such, he's just using the default SVP mpv.conf. Yes the config is a little outdated but there's nothing there that will make his output look worse. Then he adds some custom deband settings which is personal preference.

Go to forum: Using SVP

52 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

I assume that SVP motion detection is the default now when using SVP and I would like to use it if it is useful. But is it possible to fix the garbage frame issue where it and NVOF behave identical to "disable" motion detection? As shown before, IC is still the only motion detect that behaves properly.

Go to forum: Using SVP

53 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Xenocyde wrote:
dawkinscm wrote:
Xenocyde wrote:

I haven't noticed any smoothness problems since I don't watch anime. I only tested with my usual football scenes
and 4.21 still has the same edge artifacts as 4.20 in those scenes.

BTW, 4.22 is out. Maybe they fixed it with this one. Testing now.

4.22 is the fix he's talking about. It's a little better than 4.21 but overall it has the same artefacts.

Ah thought it was a 4.21 update, they don't actually mention 4.22 in the comments.

The dev mentioned it.

Go to forum: Using SVP

54 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Xenocyde wrote:
flowreen91 wrote:
Xenocyde wrote:

Can confirm the edge artifacts are still there in 4.21.

The devs fixed the smoothness issue:
https://github.com/hzwer/Practical-RIFE … 2275333756

I haven't noticed any smoothness problems since I don't watch anime. I only tested with my usual football scenes
and 4.21 still has the same edge artifacts as 4.20 in those scenes.

BTW, 4.22 is out. Maybe they fixed it with this one. Testing now.

4.22 is the fix he's talking about. It's a little better than 4.21 but overall it has the same artefacts.

Go to forum: Using SVP

55 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

flowreen91 wrote:
Xenocyde wrote:

Can confirm the edge artifacts are still there in 4.21.

The devs fixed the smoothness issue:
https://github.com/hzwer/Practical-RIFE … 2275333756

Yes but it's still not as good as v4.18.

Go to forum: Using SVP

56 Reply by dawkinscm

(1 replies, posted in Using SVP)

exaltedtricky wrote:

Dear community,

I'm searching for a player that can send frame-packed 3D to SVP, then use an avisynth script to convert it to sequential 3D, and finally execute madVR upscaling while bitstreaming common audio formats like Atmos to a receiver.

Do you chance to know if this is possible? Which player should I check into for accomplishing this?

Thank you in advance.

If I understand you correctly then the only player that does something like this is mpc-be. It can play frame-packed 3D and convert it to SBS/TAB format while using SVP as an external filter and MadVR rendering. But you might need a good GPU to be able to run SVP and MadVR together. More mpc-be info is available if you Google it.

Go to forum: Using SVP

57 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

aloola wrote:

v15.2 gives me a tiny FPS boost
v14test3 ~150fps vs ~ v15.2 ~158fps, also fixed dynamic shape (Performance boost: off) bug

15.2 changelog:

    Upgraded to TensorRT 10.3.0.

    Fixed performance regression of RIFE and SAFA models starting with vs-mlrt v14.test4. This version may still be slightly slower than vs-mlrt v14.test3 under some conditions, however.

Thanks. I have been waiting for this. On brief testing I don't think I see anything obviously better than 9.2. Maybe I would see more advantages if I wasn't downscaling.

Go to forum: Using SVP

58 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

flowreen91 wrote:
flowreen91 wrote:
jdg4dfv7 wrote:

1) For me18.v2 is by far the best model regarding all things mentioned.

I agree, somehow v19 and v20 managed to break something and now they stretch the images instead of smoothly moving them vertically:
https://github.com/hzwer/Practical-RIFE … 2253162650

They fixed it in v21:
https://github.com/AmusementClub/vs-mlr … e_v4.21.7z

Nope. The dev says it's the same as v4.20.

Go to forum: Using SVP

59 Reply by dawkinscm

(7 replies, posted in Using SVP)

Kyuri wrote:

Hello,

I'm having a bit of trouble getting SVP to run with MPV with other scripts enabled. If I run SVP4 with just the "Open file with MPV", it works fine. But I wanted to add Anime4K script to MPV so I can upscale old anime to higher quality as I had done before. But whenever I install said script, SVP stops functioning and won't detect MPV, even if launched from SVP4. If I uninstall it, it works. Is there some kind of conflict between the 2?

Thanks in advance!

Did you follow these instructions https://github.com/bloc97/Anime4K/blob/ … ows_MPV.md?

Go to forum: Using SVP

60 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Xenocyde wrote:
dawkinscm wrote:

Rife v4.20 has been released. I didn't do a large amount of testing but I did check the few remaining artefacts I know of and there doesn't seem to be a clear  difference to v4.15/v4.18 on my system.

I can see a slight improvement for some interference pattern artifacts, but 4.20 introduces other artifacts especially on the edges of the video in fast moving scenes.

Yes I saw those too after I wrote my original message and went back to 4.18 smile

Go to forum: Using SVP

61 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Rife v4.20 has been released. I didn't do a large amount of testing but I did check the few remaining artefacts I know of and there doesn't seem to be a clear  difference to v4.15/v4.18 on my system.

Update: Apparently v4.20 is great when using 16x interpolation with Anime. I would be interested to hear if that is helpful for anyone.

Go to forum: Using SVP

62 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Blackfyre wrote:
dawkinscm wrote:

How are you using FSRCNNX because by default because it doesn't work unless there's at least 2x scaling required. Is it listed your in your mpv page 2 stats?

1080p to 4K content, such as Arcane (Netflix) when testing RIFE versions or when watching old content. Some old favourites like Everybody Loves Raymond, Friends, etc are all not 4K content too.

Yep that makes sense. I frigged the code so that it works on everything lol. It didn't make any difference to the normal stuff I was watching and a decent high end Sony TV from the last 7 years upscales DVDs and other low rez stuff better than any PC upscaler I've tried. But recently other TV manufacturers are catching up.


Blackfyre wrote:

Otherwise at 4K, mpv will automatically use the internal scaler, for example I have mine set to ewa_lanczos in the config, which btw:

I just use the High Quality profile default which is lanczossharp.

Go to forum: Using SVP

63 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Blackfyre wrote:
dawkinscm wrote:

As I said before, machine generated scores doesn't guarantee the best looking picture because human perception and preference isn't objective. The other thing I said is that much of this is designed specifically for Anime and that definitely applies to ArtCNN. So hopefully you are an Anime watcher smile

Also don't forget there are different levels to it, for example I would never use strongest FSRCNNX because it would introduce too much sharpness for non-Anime. However, the one I do use, is always very helpful in improving the sharpness just a little a bit because I have the TV sharpness set to 0 on the LG C2.

TV sharpness is much worse than these AI shaders btw, so actually using the shaders as an alternative and toning down the TV ones definitely helps.

In most cases though, I imagine people here use monitors, which automatically have sharpness set to 0.

It also wouldn't make sense to use these upscalers on a 27" or 32" 4K monitor, as again like @dawkinscm says, it would look too sharp.

However, watching on a 42" screen, and I have been using 42" and 43" screens for almost a decade now, I started using FSRCNNX in its very early days and have not looked back, it is great.

So, a lot of factors play a role, no harm in testing and seeing what you prefer.

For reference, I use FSRCNNX_x2_8-0-4-1.glsl, which is the 8- and it's very low sharpness compared to the 16- and 32-.

How are you using FSRCNNX because by default because it doesn't work unless there's at least 2x scaling required. Is it listed your in your mpv page 2 stats?

Go to forum: Using SVP

64 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

flowreen91 wrote:
Blackfyre wrote:

You can read more about them on their pages. But also, if you want an article explaining them, as well as better shaders that are more demanding which I cannot run with an RTX 3090 while using RIFE, have a read through this: https://artoriuz.github.io/blog/mpv_upscaling.html

I tried to download ArtCNN since it says here that it beats FSRCNNX:
https://www.svp-team.com/forum/viewtopi … 264#p84264

As I said before, machine generated scores doesn't guarantee the best looking picture because human perception and preference isn't objective. The other thing I said is that much of this is designed specifically for Anime and that definitely applies to ArtCNN. So hopefully you are an Anime watcher smile

Go to forum: Using SVP

65 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Xenocyde wrote:

I just had SVP trigger in "ignore HFR sources," but I'm not really sure why this happened. I'm watching S10 of the new Doctor Who series and all episodes appear to be encoded at 25 fps according to MPV. However, starting with Episode 6, SVP is triggering the ignore HFR sources profile after saying it is playing at 50 fps. How does SVP identify some videos as HFR and some as non-HFR if all are 25 fps? Also, if I raise the video frame rate threshold from 47 to 60 on the ignore HFR sources profile, the RIFE profile gets triggered with fixed 60 fps, but some videos exhibit strange microstuttering as if they are not truly running at 60 fps, probably because of the threshold conversion. Any way to fix this?

I've seen it do that a few times, but I usually ignore it because it only triggers on stuff I normally wouldn't watch with SVP. But if you regularly watch 4K with SVP then I see how it could be a problem.

Go to forum: Using SVP

66 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

donnieyeen wrote:

Did anybody try to manually update the TRT libraries to v15.1: latest TensorRT library? Any benefits over the standard TRT install from SVP?

Don't upgrade. Both myself (twice) and @Chainik have already explained why. The next version will hopefully be fixed.

Go to forum: Using SVP

67 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

flowreen91 wrote:
dawkinscm wrote:

Nowadays I mostly use in-built scalers.

I found this link with upscaler examples really useful:
https://github.com/LitCastVlog/Plex-GLSL-Shaders

the ultimate goal is to improve visual quality, so we will always try to pick the combination that makes it look better overall
can u please explain which in-built scalers combination u use so we can try that too?
i preffer to set max visual quality + resize down until GPU stops dieing, than watch pure image native 24 fps. xD

I've found that the key to the best picture quality is basic picture calibration. Get the brightness, contrast, saturation and gamma right and 90% of the work is done. You need a calibration disc like Spears & Munsil for this. Like @Blackfyre, my MPV config has evolved over time and is now much simpler. MPV has been around for years and its defaults are set after dev testing, discussion and years of user feedback, some of which I have read.

I set SVP downscale to Bilinear to remove any obvious sharpening done by SVP. Lanczos is a great default but even with the mildest MPV scaling algorithm I sometimes see bad effects like ringing when used with SVP sharpening. This is NOT a problem with SVP, just a consequence of double sharpening so I want full control over sharpening post downscale.

I use Lanczossharp which is the default scaler. For movies on a large screen it's not actually that sharp, but it might be the most natural of the sharp scalers. For additional sharpening I use Contrast Adaptive Sharpening because it gives more fine tune control. But you can get a similar affect with a lot less hassle using the Adaptive Sharpening shader and others. Maybe also SSIMDownscaler.

Go to forum: Using SVP

68 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

oriento wrote:

New version
4.19 (Add SportsSlomo) - 2024.07.12

Thanks. Not sure how to actually use SportsSlomo. But it is clearly worse than v4.15/4.18 and maybe even worse than v4.9.

Go to forum: Using SVP

69 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Blackfyre wrote:
Xenocyde wrote:

What are these for exactly?

Scaling methodology.

Dithering methodology.

The shaders at the bottom (which have to be downloaded and added into a shaders folder separately) improve quality. FSRCNNX is an upscaler, while KrigBilateral is a chroma upscaler, SSimDownscaler is for downsampling.

You can read more about them on their pages. But also, if you want an article explaining them, as well as better shaders that are more demanding which I cannot run with an RTX 3090 while using RIFE, have a read through this: https://artoriuz.github.io/blog/mpv_upscaling.html

First here's the appology I owe you. I must have been reading with old, assuming eyes smile

As for the shaders, just like Rife, a lot of this applies to Anime and results are based on machine generated scores. I've had almost every shader in my config at one point or another including the 3 above. Krig is technically it is better than default but visually speaking the difference myself and others have found is negligible. Since I read that it can generate also errors I stopped using it.  SSSimDownscaler might be great for Anime but when used with video content it's too sharp even for me, but especially when tested with calibration tools. FSRCNNX is a GPU killer for anything above 1080p. I've been using it to upscale low res poor quality content but i recently removed it because like the other AI based upscalers it made little visual difference. That's why I initially said that it's personal taste and machine generated scores.

Nowadays I mostly use in-built scalers.

Go to forum: Using SVP

70 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Blackfyre wrote:

[
I'll post the latest config here as a quote:

ontop
fullscreen=yes
d3d11-exclusive-fs=yes

volume=100
volume-max=100

vo=gpu-next
gpu-api=d3d11
hwdec=auto-copy
hwdec-codecs=all
gpu-context=d3d11

hdr-compute-peak=yes
tone-mapping=bt.2446a
target-colorspace-hint=yes

scale=ewa_lanczos
cscale=ewa_lanczos
dscale=ewa_lanczos
tscale=ewa_lanczos

dither-depth=10
dither=error-diffusion
error-diffusion=burkes

glsl-shader="C:\Users\USERNAME\AppData\Roaming\mpv\Shaders\FSRCNNX_x2_8-0-4-1.glsl"
glsl-shader="C:\Users\USERNAME\AppData\Roaming\mpv\Shaders\KrigBilateral.glsl"
glsl-shader="C:\Users\USERNAME\AppData\Roaming\mpv\Shaders\SSimDownscaler.glsl"

To be fair this is a very much cleaned up version. I'm curious if this different to the one I commented on because if it isn't then I owe you an apology smile

On this cleaned up version, you don't need  hwdecs-copy=all and you are not using tscale. On my setup, Error-diffussion in general isn't required for gpu-next coz Ordered works as well or better and costs almost zero resources. Again on my system, if error-diffusion is used then Burkes is worse than Floyd. After that the shaders are personal preference.

Good job big_smile

Go to forum: Using SVP

71 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Blackfyre wrote:

For anyone interested, this is my mpv config now - you can scroll up and down in the code below to see the full config:

ontop 

dither=error-diffusion 
error-diffusion=burkes

Thanks for this. There's nothing in your config that makes a difference for SVP and we've already had the discussion about config lines that essentially do nothing or are even contradictory. But if you are happy with the picture then I suppose it doesn't matter big_smile However I am interested in the error-diffusion you chose so I will try that out. Thanks smile

Go to forum: Using SVP

72 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Xenocyde wrote:
dawkinscm wrote:
Chainik wrote:

dawkinscm
> One minute you are saying that I'm seeing garbage frames with IC.

you said you have "very sharp cut" with MVs, while it's not that sharp with IC
meaning you saw frame repeating with MVs and some kind of "soft" mixing with IC
dunno how I supposed to understand this in opposite way

I was going to say that this was probably a language misunderstanding but I felt you might be insulted by me saying that. But you still don't understand so that's clearly the issue. The key words "sharp" and  "jarring" used together like this is always bad. SVP and NVOF have "jarring" cuts means they have bad scene cuts.

I think what Chainik is trying to say is it seems counterintuitive to have sharp and jarring cuts with "garbage" AI blended scenes on SPV and NVOF, while IC has no sharp and jarring cuts with no "garbage" blending.

Except he regularly made jokes about me "preferring" garbage AI frames while I was using IC. But ironically, it was SVP and NVOF that had the garbage frames, not IC. Anyway that's in the past, let's move forward.

Go to forum: Using SVP

73 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Chainik wrote:

dawkinscm
> One minute you are saying that I'm seeing garbage frames with IC.

you said you have "very sharp cut" with MVs, while it's not that sharp with IC
meaning you saw frame repeating with MVs and some kind of "soft" mixing with IC
dunno how I supposed to understand this in opposite way

I was going to say that this was probably a language misunderstanding but I felt you might be insulted by me saying that. But you still don't understand so that's clearly the issue. The key words "sharp" and  "jarring" used together like this is always bad. SVP and NVOF have "jarring" cuts means they have bad scene cuts.

Go to forum: Using SVP

74 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Chainik wrote:

> Is there anything we can do to increase NVOF and SVP algorithms strength

yep
smooth.scene.limits.scene
smooth.scene.limits.blocks

the bad thing is that values that work good with resizing to 720p doesn't seems to work with 1080p and 4K

What are the values that work well with 1080p and 4K? That could be of use to many of us on here.

Go to forum: Using SVP

75 Reply by dawkinscm

(2,112 replies, posted in Using SVP)

Chainik wrote:

> IC is properly processing that scene.

with a threshold value <=15
making a lot of false SC detections in other scenes

dawkinscm
> The only "garbage" Rife frames are with SVOP and NVOF which explains why I didn't like what I saw.

but you said the opposite thing - "With both NVOF and SVP this is a very sharp and jarring cut" big_smile

When something is "jarring" it is bad which is why "I didn't like what i saw". I can't even begin to understand where you are coming from when what you are saying is contrary to what I have said, but more importantly it is also contrary to what we are seeing. One minute you are saying that I'm seeing garbage frames with IC. Then when it's clear that myself and others are not seeing the same thing, now you are saying something else.

So let's just get back to the point I have been making since the start. There is an issue with SVP and NVOF and @flowreen91 has kindly demonstrated it. We all want SVP to be better so if it can be fixed then great. If not then we will continue to use IC.

Go to forum: Using SVP