Reference
Reference
Section titled “Reference”Configuration comes in two forms, and they are not interchangeable. One is the file a service starts from. The other is a message that changes it while it is running. This section covers both.
Static configuration — the file a service starts from
Section titled “Static configuration — the file a service starts from”| Service | Reference |
|---|---|
| input-processor | input-processor config |
| output-processor | output-processor config |
| phrame-webrtc-session | phrame-webrtc-session config |
These pages are generated from each service’s JSON Schema, so they cannot drift from what the service actually accepts. Every field, its type, whether it is required, and its default.
Live control — changing a running system
Section titled “Live control — changing a running system”| Reference | Covers |
|---|---|
| Real-time control | Transport, cuts, mixes and controller-mode config, over MQTT |
A word on what is not here
Section titled “A word on what is not here”Several services are configured entirely by environment variables, with no schema to generate a table from: the TAMS components, the orchestration services, and the platform services. Where those matter operationally the values are described on the service’s own page rather than duplicated here, because a hand-copied field table looks exactly like a generated one and rots without anybody noticing.
If a field you need is not written down, the service’s configuration handling is the authority — not this section.