broadcast: configurable live transition retry delay

Trek Hopton

The two minute delay exists because our hardware generally used a 1 minute monitor period. This monitor period cannot be guaranteed since monitor period is configurable, therefore the delays in the broadcast pipeline should also be configurable.

These delays happen at three locations:

health.go lines 81 and 90. These wait for stop and start to take effect during a power cycle.

broadcast/youtube.go line 276. This waits for the camera to power down before trying another live transition after a failure.

It would be good if instead of another custom broadcast variable, the delays were actually based on the monitor period.

Note: There’s also other hard coded delays at broadcast/youtube.go line 328 but I’m uncertain if these should be changed in a similar manner.

2023-09-27T04:58:42+00:00

Comments (1)

Trek Hopton
The two minute delay exists because our hardware generally used a 1 minute monitor period. This monitor period cannot be guaranteed since monitor period is configurable, therefore the delays in the broadcast pipeline should also be configurable.

These delays happen at three locations:

health.go lines 81 and 90. These wait for stop and start to take effect during a power cycle.

broadcast/youtube.go line 276. This waits for the camera to power down before trying another live transition after a failure.

It would be good if instead of another custom broadcast variable, the delays were actually based on the monitor period.

Note: There’s also other hard coded delays at broadcast/youtube.go line 328 but I’m uncertain if these should be changed in a similar manner.
- 2023-09-27T04:58:42+00:00
Log in to comment