/api/streams?src=[streamname]&video=all&audio=all&microphone aka probing the camera streams what impacts speed?

[bagobones]

What happens behind the scenes when go2rtc runs the prob call? Is performance camera dependent?

This call sometimes takes over 14s for some of my cameras.

I ask because it is used in frigate and not everyone seems to encounter the slowness.

The slowness is also present when using the go2rtc UI and selecting prob on a stream. I would think in particular if a stream is already active in go2rtc this call should be cached or fast?

[AlexxIT]

It's usual request for getting all data from all sources of the stream. It depends on your settings and on the implementation of protocols in your specific cameras.

[bagobones]

It's usual request for getting all data from all sources of the stream. It depends on your settings and on the implementation of protocols in your specific cameras.

Any idea why the request would sometimes take less than a second but more than 14s sometimes? Is it purely waiting on the camera or is this go2rtc gathering its internal info?

Edit:

Also if go2rtc is probing the camera for this info, is this info actually expected to change WHILE go2rtc already has an active connection to the camera?

I did some more testing and noticed specific cameras are MUCH slower to probe than others.