Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Professional video editing, right in the browser with WebGPU and WASM

tooscut.app

Post reply on HN
Print view View original

71–80 of 148 posts

Re: Professional video editing, right in the browser with WebGPU and WASM

#71

Post by mohebifar »

pjmlp wrote: post #70

This will only handle toy videos, given the browser limitations in sandboxing and 3D rendering. Not really sure why someone would use this instead of a proper native application.

The goal here is not to replace Premiere Pro across every professional workflow. But it is also not intended to be a toy editor.

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.

Re: Professional video editing, right in the browser with WebGPU and WASM

#72

Post by mohebifar »

esafak wrote: post #12
mohebifar wrote: post #2

Free and open source NLE video editor powered by WGPU, WASM, WebGPU, Rust, and Tanstack Start

Any plugin plans? In case you don't know, there is a standard for it: https://openeffects.org/ Would you like to share your development experience? I suggest creating a CONTRIBUTING.md and enabling discussions if you are open to PRs.

I added CONTRIBUTING.md. I also took a look at OpenFX. My current view is that supporting OFX in the browser would be hard, since the standard and its existing tooling are not designed around wgpu or browser execution. Tooscut would likely need its own plugin model rather than adopting OFX as is.

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

Re: Professional video editing, right in the browser with WebGPU and WASM

#73

Post by pjmlp »

mohebifar wrote: post #71
pjmlp wrote: post #70

This will only handle toy videos, given the browser limitations in sandboxing and 3D rendering. Not really sure why someone would use this instead of a proper native application.

The goal here is not to replace Premiere Pro across every professional workflow. But it is also not intended to be a toy editor. 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 product…

Except WebGPU 1.0 isn't modern, it exposes hardware capabilities from a decade ago, better than WebGL 2.0 sure, which is what mobile GPUs were in 2010.

And the sandboxing get up to 4 GB, which in most cases will kill the browser depending on how many tabs are open.

Re: Professional video editing, right in the browser with WebGPU and WASM

#74

Post by m00dy »

mohebifar wrote: post #71
pjmlp wrote: post #70

This will only handle toy videos, given the browser limitations in sandboxing and 3D rendering. Not really sure why someone would use this instead of a proper native application.

The goal here is not to replace Premiere Pro across every professional workflow. But it is also not intended to be a toy editor. 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 product…

A chrome tab still has 4gb max memory limit right ?

Re: Professional video editing, right in the browser with WebGPU and WASM

#75

Post by mashreghi »

pjmlp wrote: post #70

This will only handle toy videos, given the browser limitations in sandboxing and 3D rendering. Not really sure why someone would use this instead of a proper native application.

Photopea wasn't "Photoshop replacement" either, still massively useful.

Re: Professional video editing, right in the browser with WebGPU and WASM

#76

Post by mashreghi »

pjmlp wrote: post #70

This will only handle toy videos, given the browser limitations in sandboxing and 3D rendering. Not really sure why someone would use this instead of a proper native application.

Same argument was made about Figma vs native tools, didn't age well.

Re: Professional video editing, right in the browser with WebGPU and WASM

#78

Post by mohebifar »

bilekas wrote: post #58

Nice tool, but not a very useful license.. I would love to integrate something like this as an additive to users but if I'm not mistaken, that's completely off limits for this license type ?

Could you please tell me more about your use case. I've changed the license once today. I'm open to changing it again.

Re: Professional video editing, right in the browser with WebGPU and WASM

#79

Post by mashreghi »

pjmlp wrote: post #73
mohebifar wrote: post #71

Earlier quoted context omitted.

The goal here is not to replace Premiere Pro across every professional workflow. But it is also not intended to be a toy editor. 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 product…

Except WebGPU 1.0 isn't modern, it exposes hardware capabilities from a decade ago, better than WebGL 2.0 sure, which is what mobile GPUs were in 2010. And the sandboxing get up to 4 GB, which in most cases will kill the browser depending on how many tabs are open.

Most real-world edits aren't hitting those limits. Constraint ≠ useless, it just defines the target use case.

Re: Professional video editing, right in the browser with WebGPU and WASM

#80

Post by mashreghi »

m00dy wrote: post #74
mohebifar wrote: post #71

Earlier quoted context omitted.

The goal here is not to replace Premiere Pro across every professional workflow. But it is also not intended to be a toy editor. 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 product…

A chrome tab still has 4gb max memory limit right ?

Sure, and most social/video workflows fit comfortably under that. Not everything is 8K RAW timelines.
Post reply on HN