Search options (Page 5 of 18)

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

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-.

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?

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

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

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 

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

> 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"

dawkinscm wrote:

Chainik wrote:

it's clearly a scene change and SVP do everything right - see f1.jpg before SC and f2.jpg after SC

> what you call "garbage" might simply the AI doing it's job1

see attached rife.jpg
for the 3rd time - if you OK with this - then OK, "SC = disabled" is right for you
and I'll continue thinking that proper SC detection is a must for every frame interpolation algorithm

So I just checked I do get the same before and after frames as shown in f1.jpg and f2.jpg, but for IC.  When I use either SVP or NVOF SC, I get the same issue as shown in Rife.JPG. It would be interesting to see what others are seeing here because I checked and rechecked using SVP SC to be sure,  so something strange is happening here. This might explain why I didn't like the look of what I see when using SVP SC.

For me the frame between F1 and F2 are much better that the rife.jpg and all methods look almost the same.

> But an example of why IC is slightly better is in Dr Strange 2 where he throws his cloak to catch the girl. At the point she is caught the scene changes to show her being carried back.

what is the timecode?

> At the point she is caught the scene changes to show her being carried back. With both NVOF and SVP this is a very sharp and jarring cut. With IC there's still an issue but it's less jarring and looks more natural.

So MVs see the scene change while IC doesn't, and still it's "better". OK then

Update:  My VR headset also has increased CPU and decreased GPU usage effectively spreading resource usage across both CPU and GPU. I checked my Nvidia settings and there are still no changes. So this might be some kind of Microsoft/Nvidia optimisation.