Hi team, (also posted in the '3rd party sofware and development' section in more detail).

I’d like to suggest an enhancement to the vMix HTTP API (and scripting interface) to allow dynamic control over the output filename when starting a recording.

Current behaviour

At present, the recording filename can only be defined globally under Settings → Recording → Filename Format. While that’s useful for consistent patterns, there’s no way via API or scripting to specify a custom filename per recording session.

Proposed enhancement

Add support for a new API parameter or function, for example:

Function=StartRecording&Filename=MyCustomName_2025-10-08.mp4


or alternatively:

Function=SetRecordingFilename&Value=MyCustomName_2025-10-08.mp4


This would allow integrations to:

Automatically name recordings based on metadata (client name, project ID, timestamp, etc.)

Avoid post-recording rename scripts or folder watchers

Maintain consistent linkage between recording files and automation systems (Salesforce, scheduling, broadcast logs, etc.)

Why it matters

Many professional workflows (including automated broadcast playout, live-event capture, and cloud upload systems) rely on predictable, programmatically generated filenames. Currently, we need to rely on post-recording scripts to rename files after vMix finishes writing them, which adds complexity and timing issues due to file locks.

Adding filename control via API would make vMix far more automation-friendly and align it with the same flexibility offered in other areas of the API.


Thanks,
Mick Paul

+1