Vint: Realtime Video Interpolation and CRT Emulation is now Available. What are your feature requests?

[William Sokol Erhard]

I wonder how Vint with the Rife model would handle interpolation of this video to 120fps. This footage features screens with a large number of point-like LEDs. And LSFG interpolates them poorly. There are a lot of artifacts and little detail on these elements.
https://www.youtube.com/watch?v=BEfOGyvyfFY

Hi radeko,

Thanks for asking. I tried out this video with the 4.9 model and it seems to work quite well. There's a small amount of artifacting around the singer's hands at about 1:35 but it's brief and not particularly obtrusive.

A large consideration for repeating patterns like grids or lines is the risk of temporal aliasing below the Nyquist frequency. In the same way that a wheel or helicopter blade can appear to rotate backwards with a low framerate recording, interpolation can assume incorrect directionality or speed of movement.

That all said, this video is far from a worst case scenario and Vint's RIFE holds up quite well here. I want to make a head to head comparison but frankly it's not super high on my dev priority list.

[radeko]

Is it possible to use manually downloaded rife models? Or is that not possible and can only models already in the program be used?

[William Sokol Erhard]

Is it possible to use manually downloaded rife models? Or is that not possible and can only models already in the program be used?

Yep.

You can plop them in the right folder in the directory and they'll pop up in the dropdown list.

[William Sokol Erhard]

Just released my 1.3.1 update: https://store.steampowered.com/news/app ... 9014162988

Added JS runtime as recommended by yt-dlp: https://github.com/yt-dlp/yt-dlp/wiki/EJS

Updated TensorRT-RTX to version 1.2 and fixed bugs.

Fixed bugs related to transcoding.

Added rounding feature for framerate targets so that you can get better performance while using a VRR display if you are okay with targeting a few fewer frames.

Other fixes.

[William Sokol Erhard]

Vint has been available on Steam for a year today!

Thank you to all of my great customers who help support my work on this software.

In this last year, I've added new platforms, major features, and regular updates.

Next on the roadmap is Linux.

For the anniversary, Vint is now 30% off on Steam.

[kyube]

How viable is 24→96FPS interpolation with your software? Can you quantify / estimate the GPU load such a setup would entail?
Is there a specific metric a GPU needs to have to push such performance easily? Or even more specific, what GPUs would be capable of such performance?
I assume 30→240–480FPS is impossible to do on any consumer single-GPU setup?
Is it possible to hook onto browser videos?

[William Sokol Erhard]

Hi kyube,

I personally use 24/25/30 -> 120 for most of my usage on an Ampere GPU.

Vint's RIFE interpolation is going to be computationally expensive generally but the quality is just so much better than other solutions.

The important parts for performance boil down to pixels per second (interpolated frames made * pixel count of those frames) and the convolution operate rate or essentially how many tensor units you have. I also add convenient scaling options to lower resolution before interpolation and upscale it after.
This means 4000 and 5000 series RTX GPUs are way faster for Vint than 2000 and 3000 series. Far more than raster perf would indicate and the real improvement from Ada -> Blackwell.

You might be able to get 900p/1080p 24->96 FPS on a high end Ampere card depending on the RIFE model used. I think 24->72 (3x) would be a safer bet.
Again, Ada and Blackwell will run much better to the point where an RTX 5060 TI can do 4k interpolation well.

The "AI TOPS" metric is a decent indicator of relative performance. https://www.nvidia.com/en-us/geforce/gr ... s/compare/

I can do 24 -> 240 FPS on Ampere if I drop my resolution to 540p.


Vint does hook into yt-dlp so everything it supports can be piped into Vint's process:
https://github.com/yt-dlp/yt-dlp/blob/m ... edsites.md


I also should add that Vint has a good offline transcode system so you can interpolate whatever high resolution video to whatever output framerate on whatever hardware as long as you're willing to wait a bit. Ironically the CPU encoding is considerably slower than the interpolation but at least you can split the workload between both devices simultaneously and the quality is way better than GPU encoding which is also supported.

[7bhsq]

Vint stopped working for me for some reason. It doesn't seem to start that cache generation process when I try to play a new video or switch to a different RIFE model. Any idea what could be causing this? Also, is there any documentation or resource on what the differences are between all the different RIFE models?

[William Sokol Erhard]

Hi 7bhsq,

I'm sorry you're having issues with Vint.
I take it you had the cache generate before but it stopped doing so? What hardware are you using? Did you update your GPU drivers?
Deleting the Vint install and verifying the steam installation might fix the issue if there are invalid caches.

Have you selected an appropriate 'Acceleration Library' for your platform?
What happens when you try the offline transcoding with the "transcode log window" option in the advanced settings enabled? Is there any useful information in the log?

I have a little documentation here that might help troubleshooting: https://www.willse.me/p/vint-docs.html

If you want to follow up and troubleshoot what might be causing the issue, you can email me at [email protected].

As for the different RIFE models, those are fairly similar by and large. There are differences in performance and specific artifacts but it's really more of a trial and error thing for the content you're using it for. Newer models tend to generally be better.
I don't have a specific guide I can point you towards but I will say there are numerous forum discussions about the specific RIFE versions that might help you figure out which one is best for you.

[7bhsq]

It turns out that a driver update got it working again. I rolled back to an earlier driver from last year to test something but I guess that driver was too old for the acceleration library or something.