Search options (Page 5 of 8)

Try with these:
https://drive.google.com/drive/folders/ … SzUp1SAzbx

For minimum loss of quality we should not use RIFE and just go with the SVP's Automatic interpolation because it's not a resource hog.

@Chainik would it be possible to downgrade the out of the box SVP MPC Video Renderer from current version which is MPC VR 0.7.3.2210 down to MPC VR 0.7.1.2172 ?

Pensioner discovered that all newer versions hard cap the frame rate of MPC-HC at ~160 FPS even at 240p:
https://gyazo.com/b843d14264fb4539fe8be37dd94c9c69
while the version he found working seems just fine:
https://gyazo.com/39f0b09b4c266914d9fe57780343a475

You can try it out by downloading it from here:
https://github.com/Aleksoid1978/VideoRe … /tag/0.7.1
and unzipping the contents of it in "C:\Program Files (x86)\SVP 4\mpcVR"
and selecting in Options->Playback->Output MPC Video Renderer https://gyazo.com/7be0464a7540355c1716fa6699c0d6a4

This makes the average user believe that their PC is not strong enough, when actually developers broke something in the video player.

We'll still be able to use the amazing RTX Super Resolution so it should be OK.

Or should we ignore this issue cause MPC-HC guide does not recommend using that specific Playback Output?
https://www.svp-team.com/wiki/SVP:MPC-HC

Hmm maybe Drakko can explain here what to do.

67% GPU sounds good. Don't think it's a resource issue then.
V2 models give much better fps than V1 models. So u should see significant improvements from using them.

Try to set rife_sc to 100 in SVP so it will not cause microstuttering from repeating frames when a scene change is detected.

Xenocyde, could vsync syncing cause microstuttering then? Cause every time i try to test with video-sync=display-resample it breaks the soap opera effect on panning scenes.
Try to test with it temporarily disabled by adding these in mpv config too:

# D3D11 renderer (default) is required for the HDR playback
gpu-api=d3d11
# disable VSync
video-sync=audio
d3d11-sync-interval=0

Removing vsync wait times from the equation should allow the RIFE generated frames to be displayed realtime. Even if u set it to 120 fps on a 60 fps capped monitor. xD

Please share where you found this information.

It's easy, to upgrade to the TensorRT version 9.2 from here:
https://github.com/AmusementClub/vs-mlr … /v14.test3
you just have to download this big archive:
https://github.com/AmusementClub/vs-mlr … 4.test3.7z
and then copy pasta these files in "C:\Program Files (x86)\SVP 4\rife\"
https://gyazo.com/53e859fd5306eb8ce5f896bd87b22bd8

You can find some helpful settings here:
https://www.svp-team.com/forum/viewtopi … 352#p83352

You can add stuff called "shaders" to mpv & mpc-hc to enhance/upscale remove blur/remove noise/debanding like:
https://www.svp-team.com/forum/viewtopi … 264#p84264
that enhance your viewing experience while you watch.

Give a link where other guys can download such an example to compare if they see anything unusual.

Yep, that's a rife presentation video. Latest rife neural engine models have less interpolation issues. But never zero. It's still one of our best options for conversion on-the-fly while you watch the video.
You can try to follow this small guide to download latest models, and then resize the video down until you can test 120 or 240 fps smoothness.
https://www.svp-team.com/forum/viewtopi … 352#p83352
(if you tell the AI model to generate more frames, then it will improve the accuracy of the interpolation and your eyes won't notice any interpolation issues unless you spam pause every 0.5 seconds lol)
Have a look what it generated and compare:
https://drive.google.com/drive/folders/ … CKnKGieUtb

I think it's easier to test if u go to line 222 from generate.js and delete the following:
    if(profile.rife)
    {
    if(profile.rife_sc==6) rife_sc_algo = 1;
    else if(profile.rife_sc==8) rife_sc_algo = 2;
    else rife_sc_algo = 0;
    }
    else rife_sc_algo = -1;
then replace with following line for "scene change based on SVP's motion vectors"
    rife_sc_algo = 1;
or replace with following line for "scene change based on Nvidia Optical Flow's motion vectors"
    rife_sc_algo = 2;
or replace with following line for "scene change based on dumb frame comparison"
    rife_sc_algo = 0;

(manually editing the file this way allows u to use your own rife_sc value therefore removing that slight difference between rife_sc 6 and 8, thus making it easier for u to see the changes xD )

Yes, if that didn't fix it, it means you forgot to add the minus in front of the value.
Go to Application Settings, search resize and add:
-19201080
or
-12800720
or
-9600540

In some scenarios using fixed fps will make it go slower, so make sure you uncheck "Force the exact value"
For example setting a 240 fixed fps on a 23.976 video will make it generate 239.76 + 23.976 frames frames instead of rounding itself down to only 239.76 frames

Maybe try to select madVR in MPC-HC options and see if issue persists?
https://gyazo.com/509b01a01eb6dd413667b4dd3f6d819a

Don't think it's caused by a badly encoded HEVC[x265] file. Try to download other versions of the same video encoded in [x264] and compare.