search

jamulussoftware / jamulus

Jamulus enables musicians to perform real-time jam sessions over the internet.
https://jamulus.io
Other
997 stars 222 forks source link

suggest having an indicator of other musician's Xruns. #549

Closed kezzy1966 closed 3 years ago

kezzy1966 commented 4 years ago

Sometimes on a jamming session a musician's audio is 'clicking'. Displaying an indicator of their xruns (red =high etc) might help identify them quickly.

gilgongo commented 4 years ago

This is interesting (although I've no clue about the technical feasibility of it) because it's about "telemetry" in Jamulus and the issue of what you would you do differently if you did or did not have a piece of information about something (What I call "the behaviour modification test" for UI, although I'm sure it's got a real name.)

So if, for example, you see some Xruns happening, I suppose you might investigate whether there's another app on the machine that's spiking the CPU, is that right? Or you might choose a larger buffer size? This would be as opposed to, say, investigating whether there was something hogging bandwidth (which I don't think would cause Xruns, but I could be wrong).

All this fits into the concept of a nicely formatted "diagnostic mode" in Jamulus that might (for example) show Xruns, delay, ping times, buffer sizes, etc. for you and other people over time so that you can spot patterns (the time of the event being an extra data point).

However, we would still be left with the issue of about what to do about it.

This makes the idea of displaying other people's Xruns interesting because it implies somebody more knowledgeable might know instead.

Overall though, I think it would be better to have a table of problem/action suggestions somewhere which lists typical troubleshooting measures against different states of the telemetry/sound quality - if you are to display data at all.

See also #164 #548

gilgongo commented 3 years ago

Hi - this is essentially a duplicate of https://github.com/jamulussoftware/jamulus/discussions/1032 so I'll close this now but make a cross-reference to that discussion. If we get to agreement on how to action this we can raise a work Issue for it. Thanks!