Add warnings for bad audio values

[JulianGro]

Currently we have a couple of problems with the audio system being high latency or unreliable. In Dales case he had an extremely high Output Read latency. (over 3000ms) In Mr.Squarepegs case he had extremely high Jitter values, both upstream and downstream. (over 1000ms) Switching to a different wifi adapter fixed his issue. In both these cases there was something pretty obviously wrong with the values and the users had no idea. I feel like Interface should warn its users or at least write to log when something starts getting out of sane values like that.

Without knowing how every system and network behaves, I would suggest the following values:

Input Read = >200ms Input Ring = >50ms (my understanding is that that is the jitter between the local systems audio server and Interface) Network (up) = >400ms Mixer Ring = >200ms Network (down) = >400ms Output Ring = >200ms Output Read = >400ms

Upstream Jitter = not sure what this is

Mixer (upstream) Jitter = >350ms Mixer (upstream) Packet loss = >0.05%

Client (downstream) Jitter = >350ms Client (downstream) Packet loss = >0.05%

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[daleglass]

Dev meeting: In my case PipeWire seems to have fixed latency issues, but this would still be useful

[stale[bot]]

Hello! Is this still an issue?

[daleglass]

Still a good idea, though my original issue is gone

[stale[bot]]

Hello! Is this still an issue?