n00mkrad patreon

Flowframes Early Access Download: 1.37.1

🕑 Added 2022-05-04 15:16:56 +0000 UTC

Comments

GamingCanBeFun (YouTuber)

Under the gear icon settings, under Export Options, just leave "Maximum Output FPS Encoding Mode" and "Make Output Match Output Duration" at default values. So keep Maximum Output FPS Encoding Mode to "Only Create Output with Limited FPS" and keep Make Output Match Input Duration UNchecked. That's what fixed it for me. I haven't gotten the Auto-Encode encountered an error message ever again. I don't have enuff karma to post on Reddit

Kenneth Flournoy

can you please also share it to reddit? I try to avoid discord as I fucking hate it

LTSM

Use RIFE-NCNN

BonEte

I'm running into errors saying the Python runtime can't be found. It suggests I redownload flowframes with the embedded python runtime or install python myself. Python is installed already, though :)

GamingCanBeFun (YouTuber)

I fixed it. Thanx anyway. I put the screenshot of what I did to fix the error in the same Discord channel for future reference to help with any development ;)

GamingCanBeFun (YouTuber)

I DM'ed "flowframes-support" in the Discord channel n uploaded both my ffmpeg log and session log. I'm under the name "GamingCanBeFun"

LTSM

DM me on Discord with the error and logs

GamingCanBeFun (YouTuber)

Ty, but no matter what settings I use with RIFE, it keeps coming back to me saying "Auto-Encode encountered an error" then interpolation cancels automatically... I'm trying to turn a 4K 60FPS video to a 4K 240fps video. It worked in the free version on RIFE 3.1 just fine with HEVC, H.265 and H.264... So I know my hardware supports that interpolation frame rate. I'm gonna have to go back to the free version until this is fixed. I haven't tried it in ur older paid ones yet tho

Kezo

Cool, thanks for the info, I hate relying on assumptions as I never make decisions with them in mind!

LTSM

Yeah pretty much, it's the sensitivity of the detection

Kezo

Thanks for the update, I love the prog, I just need to know about the dd settings, does the 2.0 setting represent the amount by which the prog finds dupes? As in, the higher the number, the higher the percentage of dupes found, vs lower numbers that represent lower percentages of dupes?

LTSM

It does not work yet, so 24>60 should only be used for content without scene cuts or duplicates, for now

Pewburrito

Hi, thank you for this amazing program and work! I had trouble understanding your sentence: "so initially I wanted to fix deduplication and scene detection for fractional factors" <-- does that mean you did actually fix it, or, that's still something presently being worked on and probably fixed in the next version? I'm one of those weirdos doing 24>60fps, lol. TIA

LTSM

Not at all, CPU encoding is always better, it just takes longer

Jake

Last question, is H265 NVENC the optimal encoding method speed/quality wise, assuming you have a high end computer.

LTSM

Deduplication should work fine fine for non-fractional factors but I recently encountered a bug where it detected dupes on a video that did not have any. But if it does have dupes it should work normally.

Jake

I was using dedpulication recently, so it's fine for normal use right? What was being fixed specifically if you don't mind me asking?

LTSM

4.0 is my go-to, it's fast and quality seems to be good if not the best.

mynamejeremy

Is there a comparison between the different models to find out which one is best for which use case? Do you have a go-to model you mostly get the best results from? Love your work btw! <3