flowframes VS Avalonia

Yeah, sorry, I didn't see your replies until after I posted. But in case you haven't tried them, in Video AI, the Stabilization function really helped me a lot with my Deforum animations, so you might want to try it, if you haven't. Here's a Deforum video I used it on, but my video was way wilder than yours, so this feature might not be needed. It's so smooth already, I'd personally just run yours through Flowframes maybe.

I am using Flowframes which does the interpolation in between each change. ✌ https://github.com/n00mkrad/flowframes

I have a troubleshooting request for the Flowframes frame interpolation application. If there is a more appropriate subreddit for this question, please let me know.

RIFE 4.0 was used for interpolation an implementation of which can be found in Flowframes.

Check out FlowFrames It's interpolation software to increase framerate.

Huh, I'll have to look into that keyframe string generator, that looks handy. As for interpolation DaVinci Resolve was okay for me, I ended up switching to FlowFrames for most of my interpolation workflow for a while, but the diffusion_cadence in Deforum gives me a smoother result on its own. Haven't tried using both but, I imagine diffusion_cadence of 8 and interpolation of 2x and 2x slowmo could be pretty good at slowing down an animation that plays too fast.

6-10 frames per second should be enough for a smooth animation as long as you use an interpolation or morphing technique, for morph someone recommend me DiffMorph and for interpolation i like Flowframes , these are by no means your only options but simply what i like

For frame interpolation I messed around with quite a bit of software and eventually ended up on Flow Frames

You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.

[0] https://github.com/AvaloniaUI/Avalonia

Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].

The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.

See my comment [2]

[1] https://github.com/AvaloniaUI/Avalonia/issues

[2] https://news.ycombinator.com/item?id=39246988#39249128

Yes, but the portable GUI frameworks by Microsoft themselves are generally not very good, and they tend to be abandoned after a couple of years.

Avalonia is developed outside of the Microsoft corporate madness and seems to be slowly becoming the defacto cross-platform framework because it is expected to last a bit longer than a manager's attention span: https://avaloniaui.net/

Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."

(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )

It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.

Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.

[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup

[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)

For desktop, Avalonia, hands down.

https://avaloniaui.net/

Open source, powered by Skia, backed by JetBrains, and quite battle-tested at this point for small to medium-sized apps. In theory perfectly capable for enterprise as well, since it's basically a spiritual successor to WPF, which has been an industry standard for about 15 years.

They're diving into mobile and WASM well, but that's more of a recent effort and I haven't tested that yet.