Search options (Page 2 of 21)

Oh I haven't tried speed up since I switched to RIFE, I did before RIFE and it was fine. I might give it a try, but I am very happy with 48FPS @ 48Hz

100% keep 4.6 as the default for everyone. Because then people will complain all of a sudden their RIFE is lagging if it changes the default with an update haha!

Most 'advanced' users already know how to change them.

Maybe you can add the 'extra options'. Such as Rife 4.16 Lite v2 and 4.18 in the drop down menu with 4.9 as well, but keep 4.6 as default.

Is it two times better? It depends, I have always been sensitive to artifacts, since old SVP days I used to always try to minimise artifacts haha

So to some of us, it is a lot more than 2x better.

In terms of 'smoothness', not much difference, very similar between all RIFE versions. In terms of artifact masking, much much better.

Edit: Information below is for 2x, running with a custom refresh rate of 48Hz at 48FPS.

3090 owner here. I hate downscaling so here are some tips to run 4K.

First of all, forget about 25 FPS or higher at full 4K with newer RIFE versions (hopefully they optimise better in the future). The source has to be 24FPS (which is most shows and movies anyway). You can create a profile for 25 FPS or higher to run old RIFE such as version 4.6 for example.

I use one profile which is: 4.16 Lite v2 for full screen 4K content, Performance Boost enabled. Scene change detection set to SVP motion vectors.

I have a second profile which is 4.18 v2 with Apply this profile IF "Frame Height" ≤ 1700

If you know how to overclock/undervolt, GPU memory overclock helps RIFE a lot, so for example I undervolt my GPU and run +1050Mhz overclock on memory (depending on your GPU, this might be unstable for you so try +700). I have this profile on MSI Afterburner for when I watch movies/shows with a custom fan curve to keep the GPU quiet too.

I use MPV to watch content and here are my current MPV Config:

Another thing I forgot to mention V2 versions perform better, if they do not work for you, there is a guide here in this thread about how to make V2's work.

25FPS to 50FPS (2X) is more demanding, a lot more than you would think compared to 24FPS for some reason.

For example, I always have to run 25FPS content with older RIFE models, such as 4.9, than the one I am currently using 4.16_lite (v2).

You can create a copy of your RIFE profile, rename it to 25 FPS for example, and set an "Apply this profile IF..." and choose "Video frame rate", then change to "greater than" and choose 25 FPS and for that you choose the model that works for it.

This IMO is horrible. But if someone prefers smoothness over quality, then 100% the correct method.

I don't have a 4090, but for my RTX 3090, the one and only model that works at 4K x 2 with the best quality = 4.16_Lite(v2) has been the primary one since it was released.

You're welcome.

Change hdr-compute-peak=yes to no instead. There is some HDR content that flickers with hdr-compute turned on for me on my LG C2. But maybe it depends on the monitor/TV, so keep it on, but if you notice flickering in some scenes, switch it to off.

If the colours, brightness, and black levels look good, and there is no banding, then Dolby Vision is working fine. But while using MPV, turn on CAPS lock, press i on the keyboard and it will show up the stats (information) which reveals what's being used next to colormatrix it should say dolbyvision. Turning on CAPS lock allows the information screen to stay up without fading away, pressing i again will make it go away. Without CAPS lock enabled, it comes on for a few seconds then goes away.

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

@Chainik changing hdr-compute-peak=yes to no in MPV config solves HDR flickering in problematic non-DV HDR content, for example the bluray of Ant-Man and the Wasp: Quantumania. Sending the HDR metadata directly to the display I guess instead of it being processed by MPV.

It has no impact on DV though, yes or no, it appears the same exactly (stutter instead of flicker now). Is MPV always processing DV metadata? Maybe that causes an issue, not sure, just letting you know in case you want to investigate it further.

No that was the cleaned up version and thanks for extra info.

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

Oh! Interesting, well it happens a lot with Mandalorian S3E4, it has become my torture test the scene at the start with a lot of panning shots (first 3 or so minutes).

Hopefully in the future you find a solution to the above as well, that would be amazing!

Also, for me I have been using "SVP Motion Vectors" for Scene Change Detection since the latest update and I'm happy with it.

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

Remove - updated in below post.

Regarding the below:

I will experiment myself, but any recommendations for 4K content only? I always just watch 4K high bitrate content now. So, I want highest quality if there are further improvements. I am happy with default, but always interested in tweaking haha

Artifacts do not change for me, all 3 show very little artifacts with the 4K Bluray quality. If anything, SVP Motion Vectors maybe shows least.

However you are right, Image Comparison at 99% for me does appear to be the "smoothest" out of the 3 options.

SVP Motion Vectors in those specific time stamps makes the creature ribbons and America Chavez look as though they are dropping frames (even though there are no dropped frames at all), similar to Image Comparison when its set to very low percentages like 6% for example. But with custom 99% it is the smoothest always.

Interesting, well I have tested it for a while as you know and I have documented here before as well, Dolby Vision has never worked with RIFE correctly. Blinking was always present. At least for my setup, RTX 3090 + LG C2 OLED.

Curious what mpv config do you use? Do you mind sharing yours.

Tested and 3090 not powerful enough to do 4K x 2, so I'm going back to 4.16_Lite_(v2) (most stable version for me in terms of performance). I will wait for 4.18_Lite_(v2) and see how it goes.

Interested for those who do tests to see if there are visual improvements with 4.18

I got so excited lol

Then I tested, and the blinking was still there, I assume this is not fixed for RIFE? But only for motion vector or NVOF methods? @Chainik

I tried with both my custom mpv config, and then I removed my config file to test with default, and both had heavy blinking with Dolby Vision exclusive files.