Professional video editing, right in the browser with WebGPU and WASM
https://tooscut.app/It violates point 1,5 and 6 of the open source definition https://opensource.org/osd
I did a poll on this on a Discord server a while ago
What does open source mean
You can view the source code: 0 votes
View + use + redistribute for any purpose: 14 votes
So no, your version of it is not the common usage
As far as I know the most restrictive open source license is the AGPL, with a CLA that allows for commercial dual licensing.
Restrictions on usage type are not commonly accepted as open source by any community that I'm aware of.
Sadly, things like this just put a bad taste in my mouth about the whole concept of running code in a browser like this. It's buggy as hell. It doesn't run in all browsers. And I really have to ask why we think the browser is the place to run this. We've moved from Java and now to WASM in a browser, but only some browsers.
Kdenlive is much better imho for basic edits
They are absolutely not anything like oracle.
This is a big barrier if you want cross-compatibility and making Linux usable for everyday people. My whole interface is a terminal and a browser. I could use/pay for something like this in the same way I use figma. I don't need an app and when I open my iPad I can access whatever I was working on.
The browser should have been the place to run all of this from the very start; but Apple/Google decided to create walled gardens for their systems.
Look at something like the Hashicorp BSL [1] for inspiration on crafting a license that forbids specific commercialization of the software itself.
Would you like to share your development experience? I suggest creating a CONTRIBUTING.md and enabling discussions if you are open to PRs.
The current poc still has significant performance overhead, and that overhead grows as the plugin system becomes more powerful. If plugins are only allowed to apply a WGSL shader, the performance impact is almost negligible. But features that require broader access to timeline data, such as time shifts, speed ramps, or full timeline transformations, become much more expensive and make zero-copy architectures harder to reason about.
That said, I would be very interested in hearing your thoughts if you are open to contributing or discussing what a practical plugin system should look like in this environment. Please file a GitHub issue if you can
Not really sure why someone would use this instead of a proper native application.
Modern browser and GPU capabilities are already sufficient for a large category of practical video editing tasks. We are not targeting blockbuster scale 8K movies at least for now, but we are targeting real jobs people do every day across social, commercial, and non-commercial video production.
it's for this:
https://ubernaut.github.io/recordMyScreen/
which uses a the wasm build of ffmpeg.
Is there similar project for image editing?
Just basic features:
- cropping
- rotating
- brightness & contrast
https://shithub.us/slashscreen/ricket/HEAD/info.html
I'd love to have nethack/slashem, the terminal version, ported to it. No, not HTML+JS, VT220 output with colour at least, usable in any VT emulator with Ricket.
That way I would play Slashem everywhere without even needing to have an ANSI C+POSIX compiler with tons of Unix dependencies. 9front has some compat but the game looks like a maze of ifdefs for different Unix systems. GLHack can be compiled with NPE (a small POSIX+SDL2/3 wrapper) and TinyGL but for these games I'm faster with the terminal output.
I have used Remotion for years because the DX is great, but the performance and overhead is significant. Even something like attaching subtitles to a video can take around 10x more time and resources than bare FFmpeg because of the chromium layer.
A headless version of this wgpu renderer with a clean API and eventually a nicer DX layer such as a react renderer could be a strong replacement for that kind of workflow.
It doesn't take much functionality to make jump cut videos and silly zooms an other non-traditional editorial styles that are the new normal for content.
However, as a professional editor, I laugh at these attempts using professional in the description when you're telling me to edit in a browser. <face_palm> It's great that they want to create a new thing and try some experimental stuff, but it's not going any where near my use of professional. Also, the landing page is dry as can be and not really informative. It's the visual equivalent of bullet points. What codecs does it support? What level of audio features are available. The lame video is just some panning shot. There's no editorial features being demoed at all. Does the timeline behave like FCP elastic or a more traditional timeline? What professional tools are available? Hmm, no data available, so I guess we'll have to just play with it. Oops, browser not compatible. Thanks for playing.