Search options (Page 9 of 17)

Is that for build_optimization or running at 72fps?

BTW Thanks for the reminder. The last time I tried this I remember seeing warnings generated, possibly because it was running out of workspace. Now I get no more errors and I think it does help a little.

Yeah I just tried it and if it is making a difference, it's at the margins and maybe pushing 4.15 lite closer to 4.15. But I will need to test with 4.15 to be sure. Also I'm not used to waiting this long for engine build anymore lol.

Nope. But YMMV.

That's why I said:
Quality: Rife v4.15 > v4.15 lite > v4.16 lite.

For artefacts it may be a little better than 4.9 but it's definitely not the same as 4.15, not even close. But I have access to a large number of movies and over time I've worked out which ones stress the models. Also I'm watching on a big assed cinema sized screen So if you don't see any of the issues I and others can see with the "your" movies then it does not matter

[deleted]

Yeah it's one of a number of things on the Rife pages that needs to be updated.

The default AV is Windows Defender which is not terrible, but also not great. But I think in your case you are using Edge browser which probably means it was being blocked by Microsoft SmartScreen which is cloud based.

Rife v4.15 is out. It is a clear improvement over previous models for reducing double images in fast movement. I need to do some testing but I think it uses a little more GPU than previous models because even with v2 my GPU never drops below 100%. Packet drops sometimes happen when starting or when FF/REW but settles down quickly with no further drops during playback. No obvious regressions from previous tests.

     RTX 4080 > 4.14 (lite)

lol But as I said yesterday, I don't need interpolation to be enabled and it probably doesn't have room to do much. I now use it because it needs to be active in order to set up motion-blur.

Not unless they have OLED lenses because OLED has an issue with smooth movement. I'm not particularly susceptible to it myself but even I can see that the extra config reduces the OLED micro-stutters. LED doesn't have the same issues. The rest is mostly standard stuff from my Plex mpv config.

#start
input-ipc-server=mpvpipe
hwdec=no
vo=gpu-next
profile=high-quality

#This is standard stuff most of which is not needed because it's the default but I like to play around with them
gpu-api=auto
gpu-context=auto
linear-downscaling=yes
correct-downscaling=yes
dither=ordered
dither-depth=8
temporal-dither=yes
deband=yes
pause="no"
no-hidpi-window-scale

#This is config specific to my situation and as some have already seen, it can cause problems even for other VR users because they all use LED lenses.
video-sync=display-resample
interpolation=yes
tscale=sphinx
tscale-blur=0.65
swapchain-depth=1

#standard shader stuff
glsl-shaders="~~/shaders/CfL_Prediction.glsl"
glsl-shaders-append="~~/shaders/adaptive-sharpen.glsl"

After that there's shader stuff that won't work because they aren't designed to work the way I use them because I modified the code. So I haven't included them here because they are only used for special circumstances. I also haven't included any color settings because every display is different.

Isn't this a separate issue to the TensorRT bug you refer to?  I don't think the use of dynamic shapes reduces the memory footprint enough to help @oriento who is literally running out of memory. Using performance mode reduces the amount of memory being used. Lower number Rife models also use less memory. Maybe for a 20 series card a user should do both by using the SVP default Rife 4.9 which works almost as well as later Rife models but is less taxing on the GPU.