log_interval as a non global setting

[henkwiedig]

As far as i can see log_interval is a global setting.
It might make sense to set it:

• per client (cli or json)
• per stream

Some streams or clients might prefer faster/slower updates then others.

[svpcom]

For which cases do you need per stream log_interval setting?

[henkwiedig]

For OpenIPC, we currently use an adaptive link to adjust the link parameters during flight. To ensure this happens reasonably fast, we use a 100ms log_interval at the moment.
However, when using wfb_cli or Pixelpilot_rk to display RSSI statistics on an OSD, such a fast update interval is not desirable.
The human observing this data will likely not be able to keep up with the high update rate. Additionally, rendering the data in rapid succession keeps the CPU load unnecessarily high.

[henkwiedig]

An more, adaptive link currently only handles the video stream. Other streams like mavlink or tunnel do not need the fast update as well which would also lower cpu load on wfb-server.

[lida2003]

@henkwiedig Sorry for cut-in the discussion here.

@svpcom If wfb-ng monitor packet drops, which might be due to CSMA/CA, but we're not entirely sure. However, we have observed packet drops in /proc/net/dev.

Regardless of whether these drops are caused by CSMA/CA or other lower-layer factors, they undeniably impact video transmission.

• Enhancing Packet Loss Handling in FPV Scenarios with Increased FEC OpenIPC/adaptive-link#21