9 comments

[ 0.23 ms ] story [ 35.4 ms ] thread
Does it supports keyframing?
looks like you could do this via API. Not sure though, it's not in the UI and according to the company it's on the roadmap.
Thanks for your interest, currently not but keyframing is on the roadmap for next year!
> We do not support video editing for your current browser right now.

> While we are working to support every major browser, please use a supported browser like the latest Google Chrome, Microsoft Edge, or another Chromium-based browser.

Hello IE....how ironic is to see the anti-IE generation making the same mistake all over again.

I’ve found javascript is much better than wasm for lots of this stuff

https://bwasti.github.io/mebm/

Interesting tool. But looking at the code when you load a video it simply decodes all frames into memory. If you deal with 1080p footage at 30 fps you will hit 4 GB with just ~23 seconds of video.
Can video clips be larger than 2GB or 4GB? because there is a mem limit for each browser tab.

does using this violate the h264 patent?

Sadly, videos can't be larger than that. For one there's a memory limit per browser tab. Secondly, wasm32 is not able to address more than 4 GB of memory.

Editing feature length movies is certainly out of scope for this editor. It's meant for editing short 10-30 second video clips that are well within the limits of 2 GB. We keep compressed video in memory and only deal with a few decompressed frames at a time.

We avoid H264 patents by not shipping an H264 encoder/decoder. We leverage the browser's WebCodecs API which in turn uses the platform's native codec API. It's the OS and the hardware vendors that license H264 patents because they're the ones providing the H264 implementation.