101 Reply by flowreen91

(10 replies, posted in Using SVP)

lurker wrote:

https://disk.yandex.ru/d/SSe9CAsvUmDW4w

Only difference i see compared to my logs is that your TensorRT enables:
[08/05/2024-01:30:54] Preview Features: kFASTER_DYNAMIC_SHAPES_0805 [ON],
and then crashes:
[08/05/2024-01:31:01] [W] [TRT] Using kFASTER_DYNAMIC_SHAPES_0805 preview feature.
[08/05/2024-01:32:17] [E] Error[2]: [deconvolutionV2Builder.cpp::nvinfer1::builder::CaskDeconvolutionBuilderBase<class nvinfer1::builder::CaskDeconvolutionV2Builder,class nvinfer1::rt::task::CaskDeconvolutionV2Runner,-2147483603>::createDeconvolution::759] Error Code 2: Internal Error (Assertion isOpConsistent(deconvolution.get()) failed. Cask deconvolution isConsistent check failed.)
[08/05/2024-01:32:18] [E] Error[2]: [builder.cpp::nvinfer1::builder::Builder::buildSerializedNetwork::751] Error Code 2: Internal Error (Assertion engine != nullptr failed. )

this page mentions that it was removed eventually:
https://github.com/NVIDIA/trt-samples-f … /issues/65

I would suggest to try and update your TensorRT from 8.5.1 to 9.1.0 using these instructions:
https://www.svp-team.com/forum/viewtopi … 674#p83674
No clue if this will fix anything.
Maybe SVP devs have encountered that error before...

Go to forum: Using SVP

102 Reply by flowreen91

(10 replies, posted in Using SVP)

lurker wrote:

(copied the folder and replaced the script)

Uuuh i think the script from that link is outdated.
Use the script from here for TensorRT9 instead:
https://drive.google.com/drive/folders/ … SzUp1SAzbx
Press ` in mpv to see if any error text appears.

Go to forum: Using SVP

103 Reply by flowreen91

(2,609 replies, posted in Using SVP)

jdg4dfv7 wrote:

1) For me18.v2 is by far the best model regarding all things mentioned.

I agree, somehow v19 and v20 managed to break something and now they stretch the images instead of smoothly moving them vertically:
https://github.com/hzwer/Practical-RIFE … 2253162650

Go to forum: Using SVP

104 Reply by flowreen91

(2,609 replies, posted in Using SVP)

chesley96 wrote:

Can anyone give any insight to the scene change detection?

There was a weird scenario recently where only "image comparison" algorithm detected a specific scene change:
https://www.svp-team.com/forum/viewtopi … 102#p85102
You can compare the scene changes yourself by pressing the < and > buttons in mpv.

Go to forum: Using SVP

105 Reply by flowreen91

(2 replies, posted in Using SVP)

Sach wrote:

RTX 4090

The settings from UI are enough.
But you can play around with other relevant settings if you're really really bored:
https://www.svp-team.com/forum/viewtopi … 352#p83352

Go to forum: Using SVP

106 Reply by flowreen91

(2,609 replies, posted in Using SVP)

Blackfyre wrote:

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

I tried to download ArtCNN since it says here that it beats FSRCNNX:
https://artoriuz.github.io/blog/mpv_ups … ng_results

When starting a video on my RTX 4080, it froze my mpv for 120 seconds to create a cache somewhere. Once it finished, it loads instantly every time.
Try to get it from here and wait for it to finish caching ArtCNN_C4F32_CMP for 3-6 minutes and it should probably run ok:
https://www.svp-team.com/forum/viewtopi … 264#p84264

Go to forum: Using SVP

107 Reply by flowreen91

(2,609 replies, posted in Using SVP)

donnieyeen wrote:

Did anybody try to manually update the TRT libraries to v15.1: latest TensorRT library? Any benefits over the standard TRT install from SVP?

According to Chainik, we should not upgrade yet cause we only get "10-15% performance drop":
https://www.svp-team.com/forum/viewtopi … 612#p84612
For now i would recommend to upgrade with TRT 9.2 from here which fixes a pixels shake issue on rife (v2) models (IF you are using those):
https://www.svp-team.com/forum/viewtopi … 795#p84795

Go to forum: Using SVP

108 Reply by flowreen91

(2,609 replies, posted in Using SVP)

dawkinscm wrote:

Nowadays I mostly use in-built scalers.

I found this link with upscaler examples really useful:
https://github.com/LitCastVlog/Plex-GLSL-Shaders

the ultimate goal is to improve visual quality, so we will always try to pick the combination that makes it look better overall
can u please explain which in-built scalers combination u use so we can try that too?
i preffer to set max visual quality + resize down until GPU stops dieing, than watch pure image native 24 fps. xD

Go to forum: Using SVP

109 Reply by flowreen91

(2,609 replies, posted in Using SVP)

Chainik wrote:

flowreen91
> When trying to transcode ... to see the difference between scene changes

Hint: press '.' key in mpv to step frame by frame. Or "Ctrl+right" in MPC-HC.

By spamming '.' in following example we can see that the cape scene frames are correctly repeated only for the Image comparison algorithm:

SVP motion vectors:
https://gyazo.com/e72e6ff3a090edd396057d0b26eee3f7
NVOF motion vectors:
https://gyazo.com/1b5a7afb1ceabf2ecd0f4a9c6b250de8
Image comparison:
https://gyazo.com/050c30df626410bde53291b9d8c47f76

Is there anything we can do to increase NVOF and SVP algorithms strength in order for them to correctly detect it and not interpolate that cape scene change?

Go to forum: Using SVP

110 Reply by flowreen91

(2,609 replies, posted in Using SVP)

Chainik wrote:

it's clearly a scene change and SVP do everything right - see f1.jpg before SC and f2.jpg after SC

When trying to transcode with following settings https://gyazo.com/219cab646d448fdd8b58d99d07504a2d with Repeat Frames to see the difference between scene changes i'm getting the following:

DoctorStrange2.SVP_sc06nvofmotionvectors.mp4 and DoctorStrange2.SVP_sc99nvofmotionvectors.mp4 have same file sizes
meaning changing rife_sc value doesn't increase the scene detection strength and they both can't detect the cape scene to repeat it.

DoctorStrange2.SVP_sc06svpmotionvectors.mp4 and DoctorStrange2.SVP_sc99svpmotionvectors.mp4 have same file sizes
meaning changing rife_sc value doesn't increase the scene detection strength and they both can't detect the cape scene to repeat it.

DoctorStrange2.SVP_sc15imagecomparison.mp4 doesn't detect the cape scene to repeat it.
DoctorStrange2.SVP_sc06imagecomparison.mp4 detects the cape scene and repeats correctly the frame to skip interpolating it.

Questions:
1. is that cape scene not detectable by nvof and svp motion vectors? cause it always tries to interpolate it, creating 10 frames of rife.jpg
2. or since they are new functionalities they aren't correctly passed to transcoding functionality?
3. if works ok, is there a way to increase/decrease scene detection strength for nvof/svp motion detector until it detects the cape scene as a scene change to be able to repeat those frames?

Thanks!

You can check the examples here:
https://drive.google.com/drive/folders/ … tb3OOUgkz7

Go to forum: Using SVP

111 Reply by flowreen91

(5 replies, posted in Using SVP)

SamE wrote:

If i try to uninstall and reinstall the whole SVP thing, will i lose all my setting and profiles then?

My local SVP4 settings and profiles are located here:
"C:\Users\username\AppData\Roaming\SVP4\settings"
Try to make a backup of it first.

Go to forum: Using SVP

112 Reply by flowreen91

(2,609 replies, posted in Using SVP)

dawkinscm wrote:

Doesn't setting it to 100% effectively turn it off.

Scene change 100% allows rife to interpolate everything all the time.
Scene change at 99% and below enables the selected scene change detector to compare the frames
if a scene change is detected then it will prevent the interpolation by repeating the same frame and creating a "microstutter" in order to prevent visual issues that happen when camera teleports around.

Go to forum: Using SVP

113 Reply by flowreen91

(2,609 replies, posted in Using SVP)

dawkinscm wrote:

I tested using an MPV build from this week with the latest SVP update.

With the MPV update, your mpv.conf file reseted, probably you should apply your previous mpv optimizations to get back to the old performance (if u had any).

New Rife 4.18 here:
https://github.com/AmusementClub/vs-mlr … nal-models

Go to forum: Using SVP

114 Reply by flowreen91

(2,609 replies, posted in Using SVP)

This is soooo cool!
https://gyazo.com/cd0cc66a7e77fc893d0d3cc4e8298b89

Go to forum: Using SVP

115 Reply by flowreen91

(29 replies, posted in Using SVP)

gerappa wrote:

Before the topic started i used avisynth

SVP devs please provide the avisynth rife.dll too with same fix applied. Maybe it won't have the seek crash.
Thanks!

Go to forum: Using SVP

116 Reply by flowreen91

(29 replies, posted in Using SVP)

Chainik wrote:

.dll attached

gerappa's reaction:
https://gyazo.com/a7a6cfd662e826dac89d6b08adf9bd4c

Go to forum: Using SVP

117 Reply by flowreen91

(29 replies, posted in Using SVP)

Chainik wrote:

why exactly you want this?

We want this:
1. to just keep stuff up to date whenever possible
2. to see if gerappa can use 2 threads if that line was turned into a warning:
more specifically it mentions on this commit that they changed the crashing "gpu_thread must be between 1 and 1 inclusive" into a warning:
https://github.com/styler00dollar/Vapou … r9_mod_v14
3. maybe u can recompile the old SVP compatible vs_rife.dll file with that fix so gerappa can check if it unlocks that extra thread?

Go to forum: Using SVP

118 Reply by flowreen91

(29 replies, posted in Using SVP)

gerappa wrote:

Change the DLL also didn't worked at all (actually froze the video completely).
just the stupid driver not allow it/limit it (if i understands well). But why?

@SVP devs, for us to correctly use the latest rife_vs.dll file from https://github.com/styler00dollar/Vapou … n/releases do we need to update something else too?

Go to forum: Using SVP

119 Reply by flowreen91

(29 replies, posted in Using SVP)

gerappa wrote:

Is there anything i can do about it?

Refund the Radeon RX 7900 XT and get any cheap RTX.
Or downgrade the driver like gerappa managed to fix it here:
https://www.svp-team.com/forum/viewtopi … 001#p84001

According to this video it says that installing "Driver Only" prevents issues:
https://www.youtube.com/watch?v=xCX3acP3At4&t=128s
Does the GPU thread issue persists even in this case?

gerappa try to go to
https://github.com/styler00dollar/Vapou … n/releases
and download each windows .dll from recent releases, rename it to rife_vs.dll and replace the initial "C:\Program Files (x86)\SVP 4\rife\rife_vs.dll"

more specifically it mentions on this commit that they changed the crashing "gpu_thread must be between 1 and 1 inclusive" into a warning:
https://github.com/styler00dollar/Vapou … r9_mod_v14

not sure if it would actually fix anything, but please take a look.
Thanks!

Go to forum: Using SVP

120 Reply by flowreen91

(2,609 replies, posted in Using SVP)

jdg4dfv7 wrote:

@flowreen91
Made the line change ("True"), nothing works.

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

Go to forum: Using SVP

121 Reply by flowreen91

(2,609 replies, posted in Using SVP)

jdg4dfv7 wrote:

So I understand it was the correct way to do?

Sounds like you made it work, well done!

From what i see if i revert the following step, the old SVP vsmlrt.py file still works for all models including latest 4.17_lite.

Step 5: Edit helpers.py replace line 52
old TensorRT 8.5:
return RIFE(clip,multi,1.0,None,None,None,model_num,backend,ensemble,implementation)
new TensorRT 10.1:
return RIFE(clip,multi,1.0,None,None,None,model_num,backend,ensemble,True,implementation)

And i didn't see any signficant improvements if i replace it with latest vsmlrt.py file from last week:
https://github.com/AmusementClub/vs-mlr … /vsmlrt.py

So for now we can continue using the old file until somebody notices something.

Go to forum: Using SVP

122 Reply by flowreen91

(2,609 replies, posted in Using SVP)

RAGEdemon wrote:

With RIFE ~4.4/4.6, you can easily get 2X - this will up 24fps to 48fps

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.

Go to forum: Using SVP

123 Reply by flowreen91

(2,609 replies, posted in Using SVP)

Xenocyde wrote:

Unfortunately I can still see microstuttering

I noticed that if i exit specific background apps like TeamViewer, i suddenly get 20-30 extra fps with SVP.
I believe TeamViewer reads the memory and causes a bottleneck even when it's minimized in taskbar.

Xenocyde try to close your 200 Chrome tabs and other background apps and see if u find the specific app that causes that microstuttering. It's good to know.
Try it with the 4.17 lite version cause it's easier on the GPU:
https://github.com/AmusementClub/vs-mlr … nal-models
Or... nevermind, try with other models.

Go to forum: Using SVP

124 Reply by flowreen91

(2,609 replies, posted in Using SVP)

pensioner600 wrote:

If you plan to melt above 160 fps, then I recommend version 0.7.1.2172 of mpcVR. Here (and in the following messages) it’s clear why.  The developer does not fix this error and wants a high-frequency monitor))
https://mpc-be.org/forum/index.php?topi … 18#msg8818

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

dlr5668 wrote:

I like MPC-HC with super res and built-in switching monitor hz.

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

Go to forum: Using SVP

125 Reply by flowreen91

(2,609 replies, posted in Using SVP)

pensioner600 wrote:

The developer does not fix this error and wants a high-frequency monitor))

Poor developers, they haven't heard of 60 fps yet.

Go to forum: Using SVP