ruffle VS ffmpeg.wasm

The memories…

I often wondered what would happen to those wonderful Orisinal mini games after Flash's death, without actually checking out the site. Would Ferry Halim find the time to port them to "HTML5"? Would they just… disappear forever?

It turns out that they know run in Ruffle[1], a Rust/WASM based Flash Player emulator I've never heard of (or forgotten about). The handful of them that I have tested work flawlessly.

[1] https://ruffle.rs/

shrug It finds its uses. It's just not that overstated.

sandspiel is quite popular and is built using WASM: https://sandspiel.club/

Google Earth - https://blog.chromium.org/2019/06/webassembly-brings-google-...

Ruffle (the "make Flash run safely" tool) - https://ruffle.rs/

Ableton's Learning Synths - https://learningsynths.ableton.com/

etc etc. It's just hard to tell when something is using WASM when it "just works" and is indistinguishable from optimized JavaScript

I was amazed that the site still runs, apparently still using the same engine.

But it seems that it was a flash site (of course), and archive.org seems to replace Flash Player with "Ruffle" [1]. Either that, or someone of Tobin's team replaced Flash with Ruffle >= 2019.

[1] https://ruffle.rs/

Out of curiosity a couple months ago I wondered if I could play my old Proximity flash game on Newgrounds from the browser within the Quest 3 VR headset, and it worked great!

That led me to do a little searching, and I discovered that originally the game didn't work in Ruffle, as I apparently did something with the play game button that wasn't normal. But someone put a fix in it back in 2020[1] in order to get my game working again. That was pretty neat. Felt kind of nice that people still cared enough about my old game to make sure it still works in an emulator.

Still working on a more in-depth sequel (using Monogame), and I'm way overdue to make a new web version of the original. Might knock that out once I get closer to getting the sequel out there.

[1]: https://github.com/ruffle-rs/ruffle/pull/1024

i believe it's using Ruffle[0] and that's already happened[1]

[0] https://github.com/ruffle-rs/ruffle

This is all using a really cool Flash emulator called https://github.com/ruffle-rs/ruffle

There's already ffmpeg wasm. I've used it in projects. Works great.

https://github.com/ffmpegwasm/ffmpeg.wasm

There's a low-hanging fruit that I think would make ffmpeg more helpful for regular people.

There's a million terrible websites that offer file conversion services. They're ad-ridden, with god-knows-what privacy/security postures. There's little reason for users to need to upload their files to a third-party when they can do it locally. But getting them to download fiddly technical software is tough - and they're right to mistrust it.

So, there's a WASM version of ffmpeg, already working and hosted at Netlify [1]. It downloads the WASM bundle to your browser and you can run conversions/transformations as you wish, in your browser. Sandboxed and pretty performant too!

If this tool a) was updated regularly b) had a nicer, non-CLI UI for everyday users and c) was available at an easily-Googlable domain name - it would solve all the problems I mentioned above.

[1]: https://ffmpegwasm.netlify.app/

As their github page says, based on https://ffmpegwasm.netlify.app ...

I'm guessing no one did GPU-optimizations? I saw a web app (not an ffmpeg transpilation) that went clever and used WebGL so it can access the GPU and use its parallel processing capabilities...

ffmpeg.wasm: The engine making all these happen. However, I’m a bit concerned about its current situation. The repo has not been updated for more than six months now, and that’s not a healthy sign for an open-source project. Clearly I was reading the commits wrong. The author mentioned “speed up x264 with SIMD intrinsics” in their roadmap (https://github.com/ffmpegwasm/ffmpeg.wasm/discussions/415), which, if landed, could make such on-device video editors much more competitive.

I use https://github.com/ffmpegwasm/ffmpeg.wasm and I want my FFMPEG commands to be hidden from others.

Possibly using this? https://github.com/ffmpegwasm/ffmpeg.wasm

You could try using something like ffmpeg wasm which is a way of using ffmpeg client side in browser. Unfortunately WebAssembly only supports files less than 2 gigabytes, which is a problem for videos. And I don't know if ffmpeg wasm contains ffprobe, so you might have to find another project or try to compile ffprobe to wasm yourself. This stuff is out of my wheelhouse so I can't offer much help.