Documentation

TRNSCODE

A distributed video encoder that runs on your own machines. One master coordinates, any number of workers encode, and FFmpeg performs the encoding.

TRNSCODE splits a video into chunks, distributes those chunks to every machine on the network, and reassembles the result. A job that occupies one computer for an hour finishes in minutes across six. No data leaves the network, and there is no per-minute charge.

The system operates identically for a single editor with one spare desktop and for a facility with forty nodes on a wired VLAN. The only difference is the number of workers started.

Choose a starting point#

Both paths result in the same deployment. Choose according to the hardware currently available.

01 / GuideSingle machineRun the master and a worker on the same machine. Chunked parallel encoding still applies across the CPU cores, and machines can be added later without reinstallation.Install the master →02 / ConceptMultiple machinesReview chunking, scheduling and codec parity first, then bring up a master and connect the remaining machines to it.How it works →

Requirements#

Requirements are fewer than for comparable tools. The distribution is portable and self-contained.

Requirement	Detail
Operating system	Windows, macOS or Linux. Mixed fleets are supported; a Windows master can drive Linux and macOS workers.
Account	A trnscode.com account. A fresh master starts unactivated and does not accept jobs or workers until it is activated — see Licensing. The free tier covers a single-worker installation.
FFmpeg	Not required. A tested build ships inside the bundle, in `bin/`.
Python	Not required. The services are frozen single-file executables.
Database	Not required. SQLite is embedded and created on first run.
Network	A LAN the machines share. Workers find the master automatically over mDNS.
Disk	Scratch space on each worker for its chunks, plus room for the finished file on the master.

Note

No installer, service registration or administrator-only setup step is required. Unzip the folder and run the executable. The procedure is the same on every platform.

Intended audience#

This documentation assumes familiarity with video files and encoding. It does not assume prior experience operating a distributed system. Pages that cover facility-operator topics — colour management, QC evidence, MAM integration — state so at the top and can be deferred until needed.

Editors and prosumers — begin with Install the master, then Run your first job. The remaining documentation becomes relevant when a job fails or more throughput is needed.
Post-production professionals — read How it works first. It explains chunk boundaries, codec parity and what the verifier checks; these factors determine whether output is deliverable.
Facility operators — follow the same path, then consult the configuration reference for enrollment tokens, worker approval and fleet policy.

Worker approval requirement#

A worker that connects to the master is not immediately eligible to encode. It registers, reports its capabilities, and remains in pending_approval until approved. This gate is by design: it prevents an unknown machine from joining the fleet and receiving work without review.

Important

A worker that starts but never picks up a chunk is usually awaiting approval. Approve it on the Workers page. Add a worker covers the full procedure.