System overview

Rust-Srec monitors configured channels, records live video and chat, and runs post-processing workflows. The web interface and API control the same backend.

Recording lifecycle

1. The backend checks a streamer's live status using its effective settings and schedule.
2. When recording is allowed and capacity is available, a download engine writes video files. Enabled danmu collection writes the matching chat files.
3. Size or duration limits can split a recording into segments. Segment workflows process completed files; paired workflows wait for video and chat from the same segment.
4. When the session ends and earlier processing finishes, its session-complete workflow runs.
5. Notifications report subscribed events. Sessions and outputs remain available in the interface.

Deployment and storage

The standard installation uses one backend and one SQLite database. Docker packages the backend and frontend separately; desktop runs its recording services locally. Recorded files live on the filesystem, while the database stores configuration, sessions, jobs, and file records.

Back up both the database and files. A configuration export is not a recording backup, and deleting a database record does not necessarily delete the file. See Backup and restore and deletion behavior.

Configure and operate the recorder

• Configuration layers: defaults, templates, and overrides.
• Recording engines: compatibility and engine options.
• Workflows: processing triggers and file routing.
• Monitoring: health, logs, and recovery actions.

For service boundaries, event delivery, database transactions, and Rust interfaces, see Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.

This section is now in Runtime architecture.