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

[InstigatorX]

Yes, please merge this. Would help load times in frigate for live view.

[felipecrs]

Yes, please merge this. Would help load times in frigate for live view.

Are you sure? Frigate already maintains a connection to the stream active during all the time, unless the camera is deactivated.

[InstigatorX]

It only maintains if it's being requested. Otherwise, it terminates. This is the default behavior and in the README. This PR makes it a configurable option. So you can take it or leave it depending on need.

…

On Thu, Jul 10, 2025 at 6:14 PM Felipe Santos ***@***.***> wrote: *felipecrs* left a comment (AlexxIT/go2rtc#1762) <#1762 (comment)> Yes, please merge this. Would help load times in frigate for live view. Are you sure? Frigate already maintains a connection to the stream active during all the time, unless the camera is deactivated. — Reply to this email directly, view it on GitHub <#1762 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANJ2YGT5BDRUU5OQPIUPET3H3QV5AVCNFSM6AAAAAB6OT6FT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANJZGI4DINBTHA> . You are receiving this because you commented.Message ID: ***@***.***>

[felipecrs]

It only maintains if it's being requested. Otherwise, it terminates. This is the default behavior and in the README. This PR makes it a configurable option. So you can take it or leave it depending on need.

Where did you take this from? That's not how Frigate works. Frigate maintains a 24/7 stream with the camera even if all features like motion, detection, and recording are disabled.

[felipecrs]

That's one of the first issues I ever opened in Frigate:

• Do not maintain a connection to the camera if not required blakeblackshear/frigate#4325

And it was decided that it will not be addressed/changed.

[InstigatorX]

Not sure what your point is. This PR is a go2rtc enhancement (not frigate) that gives flexibility to those that want a stream ready to go when called. It’s purely optional and has no downside.Why’re you questioning my support for adding this? There’s literally no downside. On Jul 10, 2025, at 6:27 PM, Felipe Santos ***@***.***> wrote:felipecrs left a comment (AlexxIT/go2rtc#1762) That's one of the first issues I ever opened in Frigate: blakeblackshear/frigate#4325 And it was decided that it will not be addressed/changed. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[felipecrs]

I am not questioning your support for this PR. I couldn't be more in favor of this PR: I was the one who asked for it.

I am questioning your reasoning because you said Would help load times in frigate for live view.

[felipecrs]

I just want to set your expectations right. If you expect this PR to improve loading times for live view in Frigate: it won't.

[InstigatorX]

It will absolutely improve load times. I use the same high res RTSP stream for record and detect. However, the live view (in my setup) I use is the sub stream. Since it’s not being used actively the load times on my live view dashboard take a few moments to load. If I use the main stream, it loads instantly. I’ve proven this out by changing the order of the live stream configuration to use the high res stream (already preloaded by record/detect) for live dashboard. Since it’s already preloaded my dashboard renders immediately. On Jul 10, 2025, at 10:17 PM, Felipe Santos ***@***.***> wrote:felipecrs left a comment (AlexxIT/go2rtc#1762) I just want to set your expectations right. If you expect this PR to improve loading times for live view in Frigate: it won't. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[felipecrs]

Got it. You're absolutely right. Thanks for explaining, and sorry about the confusion.

[hprombex]

Nice! Tested and working very well :)

[kieslinger]

Same here! Using this to preload a mjpeg stream to my loxone bell. Before it takes up to 10 sec to connect. Now it's almost instantly. Hope to see it in the next release.

[AlexxIT]

I hope so too :)