Almost any format,straight onto the timeline
Shotcut, on a Void Linux desktop of your own.FFmpeg underneath, so the file you were sent opens without converting it.
$ dxflow workflow create --identity shotcut hub://shotcut --start --link
FFmpeg,with a timeline on it
If FFmpeg reads it, Shotcut edits it — no import step first.
Hundreds of containers and codecs, including 4K and 10-bit, read natively.
Colour, audio and transform filters, animated over the clip rather than fixed.
Render to a preset or your own FFmpeg arguments, written to the volume.
Every defaultis one override away
The session reads its settings from the environment, so you set them on the start line.
$ dxflow workflow start shotcut --override env.app.VNC_PASSWORD=something-long
$ dxflow workflow start shotcut --override env.app.AUDIO_RATE=44100 --override env.app.AUDIO_CHANNELS=2 --link
The timelinefills the screen
Streamed to your browser, with Shotcut already maximized.
MLT underneath,FFmpeg behind that
The format list is FFmpeg's, which is most of why Shotcut opens whatever a camera or a colleague hands you.
Containers and codecs come from FFmpeg rather than a plugin list. There is rarely a conversion step before you can start.
Export time tracks core count. Pick the machine for that, and let it run while you do something else.
Footage, the project file and the export all under /volume, or the next start opens an empty timeline.
Pulled once,then it stays
Shotcut 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
Shotcut asks for 4 cores and 8 GB. Cheapest first.