Additional statistics/client settings

[DominikSchaller]

Hi,

As a chorus director/band leader/tech person for a larger group I would like to be able to see the settings of each client. This would make it easier to get a more uniform sound or to help less tech-savvy users.

While it would be possible to have this in the server, a lot of servers run in headless mode. So I would prefer to have it in the client.

I see two options:

1. An additional dialog for this. In addition to the settings per client this dialog could also include statistics, e.g., server version, session length, number of dropouts, recording on/off etc. This option would have the benefit to see all clients in one page so that it is easier to identify outliers.
2. The information is added to the tooltip (currently Musician Profile) per client. At the moment, the tooltip wastes a lot of space by have everything vertically spaced. If the tooltip were to be expanded horizontally, a lot more information would fit in.

I would like to see the following information:

• Client Jamulus version
• Audio channels (mono/stereo)
• Audio quality
• Overall delay
• Reverb

[alexbuckland]

This is a great idea and would really help where you have one member of a group leading the on boarding for a group that has less tech experiences users. In my experience this is always the way, where one person wants to make it work remotely and has to drive everyone else. This could really speed the adoption of jamulus with larger groups!

[Zaidcrowe]

1+

Aside from Volker, and the other contributors, the ‘other’ hero’s involved with Jamulus are those onboarding everything from bands to choirs with 30+ members.

Giving the this kind of visibility to group leaders would be awesome, if possible!

On Sun, 7 Feb 2021 at 12:01, Alex Buckland [email protected] wrote:

This is a great idea and would really help where you have one member of a group leading the on boarding for a group that has less tech experiences users. In my experience this is always the way, where one person wants to make it work remotely and has to drive everyone else. This could really speed the adoption of jamulus with larger groups!

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jamulussoftware/jamulus/issues/961#issuecomment-774662787, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXXXG4KBSUCLG62AB2YBPLS5Z6JTANCNFSM4XGNWMOA .

[hoffie]

I intend to work on this as time permits. I'm therefore assigning it to me and moving it to the Backlog. If someone wants to take over, just do it and comment here. :)

[gene96817]

I am most interested in stats regarding underruns, overruns, and lost audio packets.

[ann0see]

Related to: https://github.com/jamulussoftware/jamulus/discussions/2440

[ann0see]

@hoffie already worked on this and JSON-RPC gives some benefit. @DominikSchaller maybe you two can agree on an implementation together?

Note: I will unsubscribe from this issue and won’t receive responses from any new comments. If you have any questions concerning maintenance, feel free to ping me.