Preload Streams

[seydx]

This PR adds a preload feature that allows streams to be initialized at go2rtc startup, which is particularly useful for cameras with slow startup times.

Changes

• New preload package: Implements a consumer that keeps streams active without requiring active viewers
• Configuration support: Added preload section to YAML config for specifying streams to preload
• Stream integration: Extended streams package to support preload consumers with query parameters
• API endpoints: Added REST API for dynamic preload management

Usage

Configure streams to preload in go2rtc.yaml:

preload:
  camera1:                                     # default: video&audio = ANY
  camera2: "video"                             # preload only video track
  camera3: "video=h264#audio=opus"             # initialize transcoding pipeline

streams:
  camera1: 
    - rtsp://192.168.1.100/stream
  camera2: 
    - rtsp://192.168.1.101/stream  
  camera3: 
    - rtsp://192.168.1.102/h265stream
    - ffmpeg:camera3#video=h264#audio=opus#hardware

API Endpoints

Dynamic preload management via REST API:

# Add/update preload for a stream
PUT /api/preloads?src=camera3&video=h264&audio=opus

# Remove preload from a stream  
DELETE /api/preloads?src=camera3

Benefits

• Eliminates cold start delays when accessing streams
• Maintains active connections to prevent camera timeouts
• Supports codec filtering and audio configuration
• Dynamic control via REST API for runtime management

The preload consumer acts as a permanent viewer that keeps the stream pipeline active while consuming minimal resources.

Closes/Addresses/Resolves: #1444 #605 #1344 #530

[gtxaspec]

yes! thank you!

[AlexxIT]

@gtxaspec Looks like you've been waiting a long time for this.

[gtxaspec]

@gtxaspec Looks like you've been waiting a long time for this.

I wait patiently =D