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 my old GPU was 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 uou should post your mpv config on here because I suspect it's a meme config. If it's not, then you should completely remove SVP, reboot then retrying with my previous 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.

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

It's been an interesting balancing act trying to get the best out of all scenarios. RIFE like fast action smoothness & RIFE clarity are two separate things. Hugo intro style multiple types of complicated slow pans are another. The main thing I learned is that SVP default settings are mostly correct. I tried many of the other modifications and they usually make things subtly worse. But a small change in block percentage from 20 (the default) to 24 seems to be the last best mod I can make to my configuration The multiple complications of Hugo are dealt with better than ever, while not impacting normal slow and fast pans.

The good news is that GPU usage is almost halved. So CPU usage is now 2x GPU usage with peaks of 3x and rare peaks of 4x GPU usage.

raider10 wrote:

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

From a 3840x216op 3D MKV source, upscaled to 4K passing through SVP with resize disabled, my CPU normally runs at around 15%. But the full set of overrides you posted that increases another 10%. My GPU is pretty much unbothered by all of this which is how I learned about the SVP bottleneck lol. But my point is that those overrides seem to have a CPU tax as well as a GPU tax.   If you have the option to fully enable Resizable BAR then I would do that.

flowreen91 wrote:

If dawkinscm's config doesn't give good enough results, and tinkering with the profile settings might make it slower, i would also test with the default automatic profile + masking disabled (to confirm if it's better/worse).

I've previously suggested exactly this and I have posted settings based on augmenting the Automatic Profile. My current settings do the same thing, but taken to the next level with overrides.

flowreen91 wrote:

And lowering the monitor resolution a bit if it's already at 3840x2160 (but you only watch movies at 1920x1080).
You can also use the "Alter video frame size" button to lower the amount of pixels that get interpolated:
https://gyazo.com/92109d19b50e5eeb29a72123fc0ea5a8
But the quality loss is not worth it if u ask me.

Surely applying a combination of above will get u to stable 120 fps.

It depends on the size of the screen. On very large screens, just as upscaling to 4k can make the movie "appear" to be sharper and clearer. A reduction in resolution can also become noticeable in certain movie scenes.

As previously explained, going from 24fps to 60fps is one thing, but getting to 120fps is another. My settings provide a rock solid smooth 120fps and almost completely passes the Hugo test smile, but that's with the display already running at 120Hz. There are (let's say) more GPU efficient ways of achieving the 120fps goal. The issue isn't just the GPU though, SVP itself is part of the bottleneck. So I would not recommend using my latest settings on a 60Hz display. Looking at what the full set of overrides did on my CPU, @raider10 might be hitting both a CPU and GPU bottleneck. I do recommend using my previously posted settings as a baseline then using the appropriate overrides to reduce the possible SVP bottleneck.

raider10 wrote:

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!

My settings reduce artifacts to a bare minimum. But if you are mainly watching Anime then RIFE will do a good job. If RIFE 4.4 is working for then the overrides you posted are overkill and my settings are quadruple overkill wink

raider10 wrote:

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?

Oh I've improved it all right lol and I will post the settings. Also you may be right about the CPU because I heard my PC fans spin up and when I checked it was the CPU being hit a little harder than before. Are these settings better than RIFE? lol All my previous settings on this thread are better than RIFE. My settings on the other thread the same. The settings you provided are way better than all my previous settings but is specifically designed for 24fp to 60fps only, so it needs modding for different setups.

My attached settings are for my setup running at 120fps so you may need to add the multipliers in the original post to these settings. I mentioned before that I added estimation complexity and you will see this if you compare it to my other posts. Also, I'm going to re-emphasize that I can see the aura artifacts mentioned in the original thread as well as other fleeting artifacts that you don't see. I don't just see micro-stutters, I see nano-stutters. Finally I am very sensitive to interpolation drag or delay which literally make my eyes feel like they are being dragged in the same direction as the camera pan.  So some of these settings are going to be overkill . But you asked for it smile

raider10 wrote:

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;

I added these penalty overrides to my overrides and I have to admit that they make mostly a positive difference. The negative is that I can see a slight increase in artifacts , but I don't think these would e noticeable on a TV. There's also an occasional full stutter which I don't have with my settings, even with the Hugo intro. The main positive is that it increases SVP's responsiveness and significantly reduces SVP bottlenecking. I'm going to see if some of the other overrides "very slight" increase in artifacts and stuttering. Now I'm even more interested in reading the rationale behind these changes smile
-------------
As an update, I added most of the remaining overrides. One I've used before but in this case it doesn't work with this combination of overrides and my personal overrides.  With my settings alone, RIFE is no longer needed. But with these combined settings, it was never needed. There's still the very occasional major stutter which my settings don't have. But for this level of smoothness and responsiveness that's a very, very small price and maybe with some tweaking I can get rid of those too.
-------------
Another (final?) update: Using the settings above with some modifications combined with what were my current settings are the smoothest I've ever seen SVP run overall. But I watch on a very large screen so I see artifacts that most people won't. I'm also very sensitive to interpolation delays that I can't see, but it feels like something is literally pulling on my eyes. So I'm back to using my previous overrides but with your penalties and, m1,m2 limits. I'm guessing the penalties changes frees up SVP resources enabling me to to increase motion estimation complexity a little, leading to smoother motion and less visible artifacts. I'm not sure what m1 and m2 do, but they add a smoothness to my slow pans that I wasn't able to reach before.

BTW I found the original post you got the settings from. They do mention the artifacts around bodies that I have been seeing and the block changes they suggest are similar to mine.

raider10 wrote:

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;

My settings are mostly made in the SVP Manager with only a couple of overrides as I've explained in earlier posts. Just by eyeballing it, I see it's mostly defaults. But with a quick check I see settings outside recommended values, some will cause more stuttering, others just plain wrong. I left the majority of the settings alone because I didn't understand them enough and some of those settings seem to be the ones that have been changed. I get the rationale behind the algorithm change but from personal experience this will increase stuttering.  But to be fair, now that I've looked up the new multiplier and it does make sense but not for me running with my display running at 120fps. So I am interested in reading the rationale behind these changes. Especially the penalties.

As for the bottleneck,  you know what your CPU and GPU stats are. But your settings might be making SVP the bottleneck which is what I've been talking about with my most recent posts.

raider10 wrote:

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.

If you are not seeing artifacts with your content then you could probably get away with using something like RIFE v4.18 or earlier which should work on most GPUs without issue.

raider10 wrote:

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.

I've corrected and updated my reply to you with more information.

raider10 wrote:

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.

It depends.  I've improved upon Motion vectors settings since then so I would advise playing with them after trying the above because what worked for me might not for you. As for overrides, I modified the block size as I outline here:https://www.svp-team.com/forum/viewtopi … 119#p88119. Check the manual page for the options. In that same post I also changed the main search algorithm. But I no longer do that for the reasons I mentioned in my most recent post just above yours on this thread. But in summary, if you are not careful then SVP becomes the bottleneck.

If the GPU is no longer the bottleneck when using SVP then my natural inclination is to turn everything up. All my previous settings were mostly based on turning most SVP settings up to get better results than even RIFE v26 Heavy. it works well enough, until it doesn't for something more difficult like the intro to Hugo. Adding more advanced settings or turning everything up to the max just shifts the bottle neck from the GPU to the application. The trick is actually to turn off unnecessary SVP settings so that it does just enough processing to remove artifacts and smooth motion, but not so much that it  struggles to process frames. For my setup that involved changing the vector block sizes and using quarter pixel motion pixel accuracy (which the manual says is "not recommended" so YMMV). But I also turn off Wide Search and reduce the size of the top course level.

RIFE puts uses so much GPU resources that this aspect of SVP goes unnoticed. But to repeat myself, SVP Pro with the right settings uses substantially less GPU while clearly working better than RIFE so it really is no longer necessary. It just requires a bit of reading and a lot of trial and error smile Unless of course you are just watching Anime then an earlier RIFE engine which uses relatively few GPU resources might be perfect for you.

SATD really smooths motion and helped a lot with Hugo. But it caused other issues which I'm certain wouldn't be a problem on a TV but are apparent on a large screen. Basically SVP becomes the bottleneck. So I removed SATD from main search, reduced the vertical block size back to default and tweaked the other settings to get as close as possible to SATD smoothness. But this still left the Hugo intro a bit choppy. The final piece of the puzzle was using merge adjacent frames to smooth out the stutters. This combination gives me SATD like smoothness but without SVP showing subtle signs of being a bottleneck.

With my previous non RIFE settings I forgot to test the intro to Hugo which is a brutal test of difficult scene changes and slow pans. If you have a large screen then you might not see the nano stutters, but with the wrong settings you will see the micro stutters. My settings failed the Hugo test but it taught me that I turned up almost every setting up to max increasing complexity, making SVP more likely to be the bottleneck. I also came across another artifact in Alita that I haven't noticed before.  The main fix seems to be increasing vector block sizes to 32 which also reduces complexity but is potentially less accurate. I had already overridden the main search to SATD but I also returned the PEL quarter pixel override.  Both of these increase computation complexity but they also increase accuracy. Then I reduced the complexity of the ancillary settings including removing SATD from the search radius. More smoothness was achieved from using SADT in the main SVPAnalyze than making changes to the lesser settings.

The new settings are shown below. If you have seen my other settings then the changes will be obvious. Even with these settings the Hugo intro still has some nano stutters but I don't think most people will see them. For the "advanced" changes I have attached the relevant sections from the manual below the main SVP manager window. PEL is not included but it's on the same manual page. These settings are very advanced so anyone trying them should be careful.

RAGEdemon wrote:

The later models are progressively heavier by 20% each iteration since 4.4 but offer very little improvement. The later models are mostly trained on anime.

4.4_v2 is literally 2x the performance (half the GPU usage) of 4.25. It doesn't make sense to use later versions after 4.4_v2 except mostly placebo.

Yes RIFE has been almost exclusively trained on Anime. But RIFE v4.25 and 4.26 Heavy are definitely not placebo for smoothness when watching on a larger screen. Also later versions have less noticeable artifacts, unless you are lucky enough to be watching content not affected by them. If you must use RIFE (which I don't think you should) then v4.18 might be the best compromise for performance vs smoothness and artifacts. I think RIFE v4.7 or v4.9 were also pretty decent but it's been a while since I tried those.

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.

raider10 wrote:

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.

You're right, this is odd. On the 4080 I get 99% because I'm using VR. Turn off VR then GPU goes down to 90%. The 5080 has more Cuda cores, higher base and boost frequencies and more memory bandwidth. The only thing I can think of is if somehow you have run out of PCIE lanes because of a motherboard limit. I would suggest trying the normal Rife version and not the v2 version just in case.