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.

Let me clarify: I don't watch movies in real-time; I transcode and save them. I’ve just seen that this is actually possible, but it seems it either doesn't work correctly or only works with certain models. Since I have an RTX card, it makes sense that DLSS could be applied to any image, especially if it's a static one—which is essentially what Topaz does with some of its models. Let's see if I can find a way to make it work.

This: scale = 0.5

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.

I don't watch anime, only live-action movies in 4K on an LG OLED. I'll keep testing, but I can see it's impossible to go over 45 fps in 4K (RIFE and AUTO). Also, it's linear: if I do 1080p videos I reach 180 fps, and 2K is around 87-90 fps. It's clear to me that it's a hardware limitation, but I don't know what CPUs you guys are using. Anyway, thanks for the help—I'm learning a lot through this. smile

That's not possible for the time being. DV (Dolby Vision) is created frame by frame, and with SVP you are creating new frames for which no DV information exists. The best way is to create the video to your liking and then add DV using DaVinci Resolve; that’s how I do it, and it looks great.

After running some tests, I am seeing artifacts now with a new video I'm watching, especially in the CGI intro scenes. With RIFE and the 4.4V2 model, this doesn't happen and it looks perfect. I think it depends a lot on the scenes, but I've noticed that in computer animations (not the movie itself, but in production company intros, text, etc.), there are visible artifacts—sometimes even quite large ones. It's just a matter of trial and error. Thanks again!

Great! With your experience, I'm sure you'll manage to improve it. If you succeed, would you be so kind as to post your config so I can try it out myself? Thanks!

I use a 65-inch screen and I honestly find it hard to spot any artifacts; maybe I'm just not paying enough attention. When I have more time, I'll be more thorough while watching to find any flaws. Compared to RIFE, is it better?

Well, definitely, I must have some kind of issue. In automatic mode with your settings, I'm not going over 63fps (which is already pretty good for me). I don't see any noticeable artifacts, but the movie I tested—aside from some vegetation and very fast movements—doesn't have many challenging scenes. However, I do have a config added to the override.js file; I'm not sure if that's a good thing or just a coincidence."

"I think my bottleneck might be the CPU, an i5 12400f with only 12 threads; I can't think of anything else. I'm leaving my override settings here—I got them from a thread on this forum, but I don't remember which one

levels.pel = 2;
levels.scale.up    = 2;
levels.scale.down    = 4;
levels.full     = true;
analyse.block.w    = 32;
analyse.block.h    = 32;
analyse.block.overlap    = 1;
analyse.main.levels    = 4;
analyse.main.search.type   = 4;
analyse.main.search.distance = -24;
analyse.main.search.coarse.type  = 4;
analyse.main.search.coarse.distance  = -5;
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.rate.num = 5;
smooth.rate.den = 2;
smooth.algo = 21;
smooth.scene.mode = 0;
smooth.mask.cover = 10;
smooth.scene.limits.m1 = 3600;
smooth.scene.limits.m2 = 7200;
smooth.scene.limits.scene = 10400;
smooth.scene.limits.zero = 10;
smooth.scene.limits.blocks = 90;

OK, I'll try those settings without touching anything else anywhere or in any other file. I'll see how the artifacts look; with RIFE, it's very rare to see any, even in complicated sequences. Thanks, I'll let you know how it goes.

I'm going to test this configuration in automatic mode. Do I need to do anything specific in the override.js file?



dawkinscm wrote:

These are my current settings for running at 120fps. I am no longer overriding PEL for quarter pixel accuracy as half a pixel is enough. I've found that Average Artifacts masking with the Standard SVP shader is the best combination for removing even the more difficult fast motion vertical artifacts. The other settings are down to your GPU capabilities, but this is the smoothest and most artifact free results I've had using SVP. The remaining difficult to get rid of double images can be reduced fuirther by overriding the main search algorithm to use SATD instead of SAD. However the SVP manual says that it is Extremely slow and do not use it! plus it's not even listed when you select "All Settings". But it does work if you want to try it.

I tried using these settings at 60fps. Fast motion and clarity are more or less the same, but slow pans are not quite as smooth and would require more work. I didn't check for artifacts but I doubt there would be any major difference. But at 120fps, these settings should provide smooth motion for problem slow pans and clarity for difficult to track fast action. Same as RIFE but without many of the problems, including vertical fast motion artifacts and occlusion errors. There may be other artifacts I have yet to find. But the most difficult ones I have previously listed with timestamps are fixed using these settings.

Small update:Mvg 12 px seems to be the SVP default, it's better so I'm using it. 8 px does the best job but at the cost of small artifacts with some edge cases.

@Chainik said in another thread that SVP Pro is the best. He's not wrong.

Chainik wrote:

raider10
> PCIe 4.0 is OK

are you sure? what do you see in NV control panel -> System information -> Bus ?

I think it's okay


https://i.ibb.co/R1M5DHz/Captura-de-pantalla-2026-01-02-144504.png


Ans vsmlrt.py archive.

Everything looks correct: memory is in dual channel, PCIe 4.0 is OK. No issues in games or under extreme load in DaVinci. This is odd, though: the GPU is at 99% usage, drawing 300-320W. CPU 45%. i5 12400, 32GB RAM.
Anyway... no big deal. It might be something weird, but it’s always worked like this for me. It’s nothing new.

47fps 2X

I really don't understand what could be wrong, transcoding won't go past 35 fps. This afternoon I did a clean install of SVP; I only kept the vsmlrt file where I had tweaked some settings for Nvidia.

I hope someone can help (I'm transcoding full videos to save and watch later, not for real-time playback, though I assume that makes no difference).

oriento wrote:

a 5090 cannot do 120fps for 4k

edit: i have tested right now, and rife 4.25v2 gives me 85fps at transcoding 4k with my 5090


I have an RTX 5080 but I can't get past 32 or 35 fps. Do you have any special settings? Have you changed anything to make it run faster?

I know I won't reach 80 or 90 fps, but I'm aiming for at least 50 or 60 fps for transcoding. Right now, almost everything takes double the video duration to finish, and the card is maxing out at 320W.

Thanks

https://i.ibb.co/7dRkwCwL/Captura-de-pantalla-2026-01-01-195351.png
https://i.ibb.co/8gPC4P6f/Captura-de-pantalla-2026-01-01-195605.png

16

(12 replies, posted in Using SVP)

For now the tests with VC1 are all good and without problems, the only thing is that it creates it at 59,940, but when editing it must work at 60fps, the NVENC codecs all give 59,524, it is clear that the problem is with the codecs, I don't know if it could be forced but with VC1 you can work without desynchronizations, I will continue doing tests if I discover something else, I will let you know, in case it helps anyone else. aid.

Thanks for everything.

17

(12 replies, posted in Using SVP)

Chainik wrote:

dunno, can't reproduce

but this's not about "RIFE", but more like encoder behavior
try software x265 mode

try software x265 mode?

H.264 NVENC, H.265 NVENC, Same results when encoding.

Testing AV1 NVENC.

They're the only ones that support bt2020 for HDR.

The truth is that it is very strange.

18

(12 replies, posted in Using SVP)

Chainik wrote:

transcoding - last transcoding log

Sorry, this...

Clean installation.

19

(12 replies, posted in Using SVP)

Chainik wrote:

dunno, got 59.94 as intended...
please show the transcoding log

20

(12 replies, posted in Using SVP)

Chainik wrote:

"always" with any source video or "always" with this particular one?


Always, with all the videos I've tested so far having a frame rate of 23.976, even if I use the fixed 60fps option, I don't know if you can check it yourself.

Thanks.

21

(12 replies, posted in Using SVP)

MAG79 wrote:

Try the Automatic profile to save your video at a 2.5 ratio.
Will you also get the wrong framerate of 59.524 fps?


Always, in automatic mode, on Rife models. I don't know what else to try to fix it.

Thanks for your reply.


General
ID única                                 : 99170183349980451301876673947111376407 (0x4A9B7B89BC00E553D6D0E21EC1DDC617)
Nombre completo                          : D:\Para montaje\Alicia en el país de las maravillas (1951) BRemux1080.SVP.mkv
Formato                                  : Matroska
Formato de la versión                    : Version 4
Tamaño de archivo                        : 42,5 MiB
Velocidad de fotogramas                  : 59,524 FPS
Aplicación de codifición                 : Lavf61.1.100
Librería de codificación                 : Lavf61.1.100
ErrorDetectionType                       : Per level 1
Conformance errors                       : 2
0x8538067                               : Yes
  General compliance                     : Element size 72057594037927935 is more than maximal permitted size 44564428 (offset 0x34)
Matroska                                : Yes
  General compliance                     : File size 44564480 is less than expected size at least 72057594037927987 (offset 0x34)

Vídeo
ID                                       : 1
Formato                                  : HEVC
Formato/Info                             : High Efficiency Video Coding
Formato del perfil                       : Main@L5@High
ID códec                                 : V_MPEGH/ISO/HEVC
Ancho                                    : 1 920 píxeles
Alto                                     : 1 080 píxeles
Relación de aspecto                      : 16:9
Modo velocidad fotogramas                : Constante
Velocidad de fotogramas                  : 59,524 FPS
Espacio de color                         : YUV
Submuestreo croma                        : 4:2:0
Profundidad bits                         : 8 bits
Código tiempo primer fotograma           : 00:59:59:00
Default                                  : No
Forced                                   : No
Rango de color                           : Limited
Coeficientes matriz                      : BT.709

I’m encountering an issue where RIFE always outputs a framerate of 59.524 fps, which causes problems in editing software like DaVinci Resolve. Resolve automatically converts this to 59.940 fps, resulting in audio desync because the video duration changes.

My question is: Is there any way to force RIFE to output 59.940 fps directly? I don’t understand why it defaults to 59.524 fps, since multiplying the source framerate (23.976 fps × 2.5) should result in 59.940 fps.

Thanks in advance for your help!

I find that the best thing is always to transcode the video with rife and then watch the file directly on the chosen player, USB TV, Plex, etc... zero problems and it looks great.

Today I received my RTX 5080 and SVP has stopped working, while with my previous RTX 4070 it works perfectly. I have seen that some components need to be updated, but the application does not show any updates. Will SVP be updated? Can anyone describe step-by-step how to do it manually if necessary? Sorry, I don't speak English, I'm using Copilot to translate.

RickyAstle98 wrote:
flowreen91 wrote:

Guys, can anyone check if they made any significant improvements since last time by testing the 20x frame generation on 4k videos?
https://www.reddit.com/r/nvidia/comment … n_30_with/

LSFG3 vs LSFG2 on any multipliers - smoother and better! Quality increased, same fast transitions now look more accurate, not just a fluid!

Im using RIFE x3 + LSFG x2 for 24>144 movies conversion, usually GPU usage looks like RIFE x4 with 6x real FLUIDITY rate!

On videos with LSFG3 only, looks pretty normal, conversion from 24FPS is less accurate, but smooth enough!


Do you do it with lossless scaling?