Flowframes Early Access Download: 1.37.2
🕑 Added 2022-06-01 17:14:29 +0000 UTCFractional interpolation now works fine with RIFE-NCNN, both scene detection and deduplication have been fixed.
Also, the RIFE 4.1 model has been added to RIFE CUDA and NCNN however the NCNN version seems to be broken and causes flickering. Stick to 4.0 for now.
Full changelog on Discord and in Flowframes.
Comments
Celestial Creator
before python was installed with installer up to 3.6? how to get that back in this version
Milica Zivanovic
Well, it turns out that unchecking the "Make Output Match Input Duration" option was a solution to make past generating the frame order step. Not sure why that option is an issue in this version, when in 1.35 did not pose an obstacle... In any case, now I just hope that audio will not mismatch in final mux, but it's a one frame of difference, how bad can it be...
Milica Zivanovic
I've just tried x5 interpolation with Rife 4.1 in this version (CUDA), and the error appeared in the step of generating frame order: "Error generating frame order information: Sequence contains no elements". Did any of you get this? How to solve. I am trying now to do the same with Rife 4.0, but expect the same will happen... I use the same settings as with free version that I had no issues with. Not sure what is going on?! Edit: Yeah, the same happened also with 4.0 and NCNN, but I think that version has nothing to do with it, as the issue seems to be before rife event starts...
jo
In general, does rife-ncnn use less gpu than rife-cuda? Over time in rife-ncnn the gpu load rate drops from 95% to less than 40%. The ai model is rife-4.0, and the gpu is Rtx 3070. The operating system is Windows 10. Does it any solution?
João Paulo PE
I am getting this error too
Michele Meschke
I am getting also the error that i should install Python/Pytorch. I am using RIFE (NCNN) 4.0 Tried 1.37.1 with no errors.
LTSM
Did you select "RIFE (NCNN)" in the AI dropdown?
LTSM
Did you select "RIFE (NCNN)" in the AI dropdown?
Kenneth Flournoy
also get error, darkmoon what is the solutoiopn?
Lukas
I am getting the same error message as Nika does with the latest version. The free version works just fine but as soon as I install the patreon build both versions give me this error.
Nika
I am getting this error message "Neither the Flowframess Python Runtime nor System Python Installation could be found! Either redownload Flowframes with the embedded Python runtime enabled or install Python/Pytorch yourself." Im not quiet sure what is missing as my previous installation of Frameflow worked just fine.
Jake
Gotcha, thanks for the info. I tested both and either one or the other is faster depending on video quality, but either way they're both fast. Look forward to future updates!
LTSM
Quality should be the same, nowadays I recommend NCNN because it's faster with 4.x models.
Jake
is rife NCNN or CUDA the higher quality one? And thanks for the help
LTSM
Only with RIFE-NCNN, and only when using fractional factors, yes
Jake
Just as reference, deduplication and scene detection was only broken on NCNN prior correct?
LTSM
Ping me on the Discord in the support channel. Also there's no real reason to use CUDA because NCNN is now faster, unless you want to test the 4.1 model.
LTSM
Ping me on Discord and I can take a closer look
Kenneth Flournoy
getting a no encoding error, reset settings to default, still getting the error...every version prior to this worked fine, any suggestions? on rtx 3070, 64gb ram, tried mp4, mkv, and mov...attempt to 4.1RIDECUDA
g90ak
Not sure if that was directed at me. The file import slowness occurs before you even select a custom model - simply opening the video file is where the issue is hit.
Kenneth Flournoy
can you please explain a little on how to you use custom models?
Kenneth Flournoy
deh wuhtid ih cuhh
g90ak
Bummer. Files seem to be compatible, they've imported immediately for all versions up to and including 1.35. Few others have reported this on Discord as well. Uncompressed video is a non-option for me past 1.35.
LTSM
It's not slow if the files are compatible. Nothing's broken right now from what I know.
EvilMadness
Hey thanks alot!!!!! Gonna try this.
Andrew
nice
Diego Chavez
thank you!
g90ak
Any plans to address the super slow import process for large files that was broken on versions after 1.35?