Search options (Page 3 of 4)

If anyone is interested in much, much better quality than RIFE interpolation I will write about it soon, here on this forum. Please give me another week, maybe two weeks, until I update my repository on GitHub.

Hello, so I've wanted to try the rife engine, the vulkan version works fine, but I sure want the tensorRT version, so when selecting rife after opening a movie, a cmd window pops up and mpc-hc crashes, it just goes to shit and it doesn't really say that there's an error or something, try to search the problem on google and this forum and no luck. Here is a gif of all that happening -> https://imgur.com/a/VHVCvBZ

Any ideas on what's happening? The vulkan one works.

Thanks

dawkinscm wrote:

I've been trying for a while now to get RIFE running smoothly with my 3080 with MPC-BE. I've given up on that so instead I tried using MPV and there was an instant improvement. It still needed a bit of work and I had to learn about MPV config files so that I could configure it to match the scaling used in my MadVR config. Now it looks great and runs very smoothly.

Nvidia should release soon https://www.youtube.com/watch?v=XA-tQpQqD7U Perfect match for Rife

On tensor rife 4.6 %15 scene change threshold i get lag on fast panning scenes just like on vulkan 4.4 with %10 scene change threshold. My gpu usage is around %50-55. Is there a solution for this ?

Chainik, please try implement new ai scene detection from https://github.com/styler00dollar/VSGAN … detection. I use this fragment from Mad Max for tests how scene detection algorithms working https://drive.google.com/file/d/1f7zZ_A … share_link and this new thing performed almost perfectly.

SVP updated, added TensorRT (no need for doing anything manually), fixed (??) possible audio desync after RIFE transcoding (both Vulkan and TRT versions)

Either select the checkbox at install time, or install an additional package called "TensorRT" via SVP menu -> Utilities -> Additional programs and features.

----
It uses "dynamic shapes" by default, i.e. only ONE optimization pass for all resolutions below 2560*1440. And if/when you open a 4K video then it'll do another pass for resolutions from 1440p to 4K.
BUT! this can be a little bit slower than optimization for a specific resolution, like 5% in my case. This is why there's a "performance boost" profile option - it forces its own opt. pass for each resolution.

another finding: model 4.6 needs more than 8G of device memory for 4K res, so if you're on a 8G card and want 4K then choose model 4.4.

----
Also installation scripts fixed so the Vapoursynth Filter must be registered automatically.

edit this line

clip = RIFE(clip=clip, multi=interpMulti, model=RIFEModel.v4_6, backend=Backend.TRT(fp16=True, device_id=GPU, workspace=WS_size, use_cuda_graph=True, num_streams=GPU_t))

I think 2000 is enough for 4k

Chainik wrote:

>
dunno, I don't see any real problem with the current simple and fast method
another neural network just for a scene change detection looks like an overkill to me

Just try transcoding that clip from Mad Max. SCDetection works very bad. To avoid freezes, you need set more than 15%, I set 20%. At 15%, there are still freezes. But at high values,  ends of scenes are no longer detected at all and they simply flow one into another. It looks bad. I just want quality, not just work. I think I'm not the only one. By the way, when I tested, the difference with and without this system was no more than 10%. Fast scenes go with fading, part of scenes flow into one another, this is all work that does SCDetect.

I deleted SVP and startet from scratch, just to check if the inscructions are complete and everything is working.
There is a step missing.
After replacing generate.js and base.py, start SVP4, add the new option TensorRT etc.

Then the missing step:
Copy the Rife AI profile and select the AI Model "rife"
Enable the new Option TensorRT On