Media

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.

Kdenlive 26.08.04 cores · 8 GBOpens in a browser tab
hub://kdenlive

$ dxflow workflow create --identity kdenlive hub://kdenlive --start --link

01Pick a machinecores, memory and a rate per hour
02Create the workflowpulled from the hub, once
03Run it, then stopstopped when the work is done
The application

Cut it,then let it render

The edit is interactive; the render is what the machine is for.

Multi-track timeline

Video, audio and title tracks, with effects and transitions keyframed.

Proxy editing

Edit against small proxies and render from the originals on the volume.

Export on the cores

Rendering uses every core the machine has, and you stop it when it is done.

How you run it

Every defaultis one override away

The session reads its settings from the environment, so you set them on the start line.

VNC_PASSWORDWhat the tab asks for. It ships as dxflow, and everyone reading this knows that.
PANEL and TASKBARBoth hidden, so the timeline has the whole screen. Show either one to get the desktop back.
AUDIO_RATE and AUDIO_CHANNELSSound is on here, since this is an editor. Raise the rate to 44100 for a mix you actually have to judge.
start it your way

$ 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 session

The timelinefills the screen

Streamed to your browser, with Kdenlive already maximized.

6082Browserin the tab, at /vnc.html
6100Audiothe sound, streamed with it
/volumeStorageyour files, kept between runs
The sound comes tooAUDIO is on for this one, so what plays on the machine plays in the tab.
Open it from anywhereStart with --link and the session comes back on an HTTPS address.
Set a password firstVNC_PASSWORD defaults to dxflow, and everyone can read this page.
Good to know

Rendering runson the cores

There is no card to hand the encode to, so the machine you pick is the render farm.

Cores, for a long timeline

Every effect and every transition is resolved on the CPU. More of them is the only thing that shortens a render.

Edit on proxies

Cut against low-resolution stand-ins and swap the originals back for the final render. Playback stays smooth over the stream.

Projects belong on the volume

Footage, the project file and the render output all under /volume, or the next start opens an empty timeline.

The image

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.

694Mamd64compressed, the way the registry counts it
666Marm64compressed, the way the registry counts it
20GOn diskunpacked, with room to work beside it
ghcr.io/dxflow-ai/kdenlive:latestPublished from the hub, pulled on the first start and kept for the ones after it.
Either architectureamd64 and arm64 are both published, and the machine pulls the one it runs.
What it asks for

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.

4 cores · 8 GBAsks forwhat the definition writes down
2 cores · 4 GBRuns onthe least the image comes up on
Not neededGPUit works on the cores alone
The ask is not the floorThe definition writes down what suits the work. The image itself starts on less, which is what the second figure is.
--fit caps it to the hostA start given --fit trims each step to what the machine actually has, for that start alone. The definition is never rewritten.

Machines that fit it

Kdenlive asks for 4 cores and 8 GB. Cheapest first.

E2 Standard-4
$0.168/ hour4 cores · 16 GBStart this machine
T4g XLarge
$0.168/ hour4 cores · 16 GBStart this machine
C7g XLarge
$0.181/ hour4 cores · 8 GBStart this machine
Run Kdenlive on your own machinePick a machine that meets it, and it opens about a minute after you ask.