Batch work and job history

Use Batch when several files need the same encoding settings. Use Jobs to watch everything Video Commander runs, whether it started from Batch, Convert, Delivery, or Analyze.

Build a batch

1. Open Batch from the workspace navigation.
2. Add the input files.
3. Configure the shared video, audio, format, filter, and output settings.
4. Review the files and resolved outputs before submitting.
5. Press Cmd/Ctrl+Enter to queue the batch.

Files become individual jobs, so one failure does not erase the completed outputs or logs from the others.

Follow running work

The status bar shows the active encode with progress, processing speed, and estimated time remaining. Open Jobs for the complete queue. A job detail contains:

• its current state and progress;
• input and output paths;
• the generated FFmpeg command;
• a timeline of queued, started, completed, or failed events; and
• the complete process log.

You can move to another tab while a job runs. A desktop notification can report completion or failure if notifications are enabled in Settings and permitted by the operating system.

Reopen completed work

Completed encodes can be opened in Player or loaded back into Convert. Analysis jobs retain their score summary, timeline, and frame comparison. Keeping the settings and log beside the result makes it possible to reproduce a run without reconstructing the command from memory.

When a job fails

Start with the explanation at the top of the detail, then check the final log lines. Common causes are an encoder missing from the selected FFmpeg build, an unwritable output folder, a source the build cannot decode, or a hardware encoder whose driver and FFmpeg build do not match.

Include the job log and app version when contacting support. Review paths or source URLs before sharing if they contain information you consider sensitive.