A timeline,and cores to render it
Kdenlive, on a Void Linux desktop of your own.Multi-track editing in the tab, and the export on a machine you rented.
$ dxflow workflow create --identity kdenlive hub://kdenlive --start --link
Cut it,then let it render
The edit is interactive; the render is what the machine is for.
Video, audio and title tracks, with effects and transitions keyframed.
Edit against small proxies and render from the originals on the volume.
Rendering uses every core the machine has, and you stop it when it is done.
Every defaultis one override away
The session reads its settings from the environment, so you set them on the start line.
$ dxflow workflow start kdenlive --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start kdenlive --override env.app.AUDIO_RATE=44100 --override env.app.AUDIO_CHANNELS=2 --link
The timelinefills the screen
Streamed to your browser, with Kdenlive already maximized.
Rendering runson the cores
There is no card to hand the encode to, so the machine you pick is the render farm.
Every effect and every transition is resolved on the CPU. More of them is the only thing that shortens a render.
Cut against low-resolution stand-ins and swap the originals back for the final render. Playback stays smooth over the stream.
Footage, the project file and the render output all under /volume, or the next start opens an empty timeline.
Pulled once,then it stays
Kdenlive arrives as one image. This is what comes down the first time, and what the disk should have free for it.
What it wants,and what it needs
The definition asks for 4 cores and 8 GB. The image comes up on less than that, and a start given --fit trims the ask to whatever the machine actually has.
Machines that fit it
Kdenlive asks for 4 cores and 8 GB. Cheapest first.