Repository navigation
v0.10.34: keep the stream fed
The stream no longer stays silent while the tunnel comes up.
Fixed
- go2rtc publishes a stream only once its demuxer has carried media, and it does
not answer RTSP DESCRIBE before that. With the doorbell asleep the tunnel
takes tens of seconds, and until then the producer had written just the header
and one silence frame, so a viewer waited about thirty seconds (ffprobe
printed nothing within eight). - A goroutine now writes G711A silence every 20 ms while the tunnel is being
established, and stops right before the real frames start, so there is never
more than one writer.
Verified
TestAudioTrickleKeepsWritingchecks that it writes continuously and that
after stopping it writes nothing more, and that stopping twice is harmless.TestTrickleIntervalcoversWIBOX_TRICKLE_MS(default 20, 0 disables).gofmt,go vetclean, full suite green in 8.0 s.
Not verified
- The real RTSP start time against the add-on: the measurement needs this
version deployed with the doorbell asleep. If it still waits, the trickle is
not what go2rtc is waiting for and the next step is serving RTSP ourselves.