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.

▲

pjmlp 8 hours ago | parent | next [-]

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.

▲

mashreghi 8 hours ago | parent [-]

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

	▲	pjmlp 4 hours ago \| parent [-]
		Depends on the target audience.

▲

m00dy 8 hours ago | parent | prev [-]

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

▲

mohebifar 8 hours ago | parent | next [-]

Much of Tooscut's heavy data lives outside the V8 heap. We use WASM linear memory which is not counted against V8 heap. GPU buffers is in VRAM. Bitmaps are also native allocations.

Also, video files are never fully decoded. We use the browser's native WebCodecs on demand. Only a small buffered window gets decoded and sent to the compositor. So it can even handle long 4K videos.

	▲	m00dy 6 hours ago \| parent [-]
		good info, thanks.

▲

mashreghi 8 hours ago | parent | prev [-]

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