It uses ffmpeg (compiled to WASM) and currently only Chromium browsers support SharedArrayBuffers.

SAFs were disabled on all major browsers after the Spectre exploit iirc. Slowly but steadily they’ll patch and bring the feature back, and it’ll automatically be compatible with those browsers then.

Edit: Apparently Firefox does have SharedArrayBuffer support[0], but needs special headers.

[0] https://caniuse.com/sharedarraybuffer

I made a similar site and it works fine in firefox after the headers are added: https://editclips.online/

hey... is your product foss licensed or proprietary?

I haven't published the source yet but I plan to do it in the future.

cool. this idea came up when i saw your website. Peertube would be much better if it had on the fly editing tools like yours. They could build from scratch but that's not really efficient. If you do go GPL or something, please come to peertube github. the software needs something like this

Uuuh, can you add a feature to mirror videos - that would really be useful to create some choreo practive videos

Firefox does support SharedArrayBuffers again https://caniuse.com/mdn-javascript_builtins_sharedarraybuffe...

Quick question, what’s the difference between the SharedArrayBuffers you linked and the ones I linked in my edit

One of them was imported from MDN (and is more accurate, at least in this case.)

https://hacks.mozilla.org/2019/09/caniuse-and-mdn-compat-dat...

Chrome needs the same headers too since Chrome 91, as it was violating CORS without requiring them.

It does not require CORS (cross origin resource sharing), it requires COEP/COOP.

Yes, but because it did not require COEP/COOP, it allowed websites to break CORS policies through Spectre.

This is top priority. In theory it should work, but there are few bugs still preventing it from working.

Ah, so it's a Chrome-based video editor, not a web-based one.

Ah, so it's a sarcasm-based comment, not a thoughtful one.