Mute on entry

[reinhardwh]

Would be great to offer

"Muted entry" for new participants in server settings

worldjam.vip recommend this

Or set as option for client

[dcorson-ticino-com]

Muting is not a server function.
You can set New Client Level to 0 if you don't want to hear new participants.
I would not want to because it would mean I need to pull up the level of everyone coming into a session.

EDIT: I do not see any mention of muting new participants on the worldjam.vip site. Where did you see that?

[reinhardwh]

Thats right - but sometimes - people forget...
Maybe good if after starting the client the "automute" is active (as a option)

[dcorson-ticino-com]

Thats right - but sometimes - people forget... Maybe good if after starting the client the "automute" is active (as a option)

The problem we see more often is that people don't realize they are muted and then they are missing in the mix.

[pcar75]

Muting is not a server function.

?!?! How can Muting (channels, not Mute Myself) not be a server function. Though, it is set by a (client) user muting/panning his or other(s) channels, it is definitely the server that is adjusting the mix for that user. My understanding is therefore that the server integrates and resends not individual tracks but personnalized mix to each and every participants ... the server does the job. Which may explain the wish : for large ensembles and choirs to send one same standard mix to each user (thus lessening the power/performance requirement on the server).

[dcorson-ticino-com]

The server does not know if someone is muted or not soloed or if the volume is just turned down.
The server mixes, but has no idea of why the volume multiplier is 0.

[pcar75]

EDIT : Apologies to any inconvenienced, it was not my intent to derail this topic.
I've opened "Better understanding Client vs. Server, #2530 " in the General category.

[ann0see]

I think I get your point: you basically want that everyone who joins is first muted to not disturb the session. I think a CLI option already exists.

Moreover, I think this has been discussed before but rejected by Volker/Community (?) due to the argument that it might cause confusion.

I think the real question is: why do you want to have everyone having mute myself on before joining?

• To ensure their audio setup is correct before joining —> implement something like a pre join sound check
• To prevent disturbances —> feedback protection might be improved
• Because Zoom does it (Jamulus should have basic zoom features) —> ???

[reinhardwh]

Ok, thanks for the discussion.

I understand your concerns and trust your experience.

[rdica]

If a user is going to go to the lengths of adding a cli option, they can more easily "Mute Yourself" before they join a session. Starting up the client doesnt automatically join a session, so what problem gets solved by this suggestion?

[pcar75]

You can mute, (...) And even then many forget, as we know.
(...) And even before the feedback protection we saw more problems with people inadvertently muting than crashing a session with noise.

Often, a session is paused to figure out the problems of someone and find that there is no problem just that one forgot to un'Mute Myself'.
EDIT : Apologies to any inconvenienced, it was not my intent to derail this topic.
I've added my comment to "Need Indication On Fader Panel That Someone Has Muted Themselves" #1025 UI Related category.

[wschell]

In my opinion it wouldn't help much if it is a client option. If I think of setting such an option I also think of mute myself before entering a server. I would vote for a server option - so the server tells the client to set the option on connect. So the server operator decides if people can only connect self-muted.

[reinhardwh]

Like the idea.
Some kind of "Open Stage Rule"

In server welcome message a info could be shown by server admin.

[pcar75]

I would strongly suggest a documentation section How to Use Jamulus ... recommending that users should first try their sound with loopback address before joining a public session just to make sure that they don't cause other musicians to stop and mute any ear-splitting noise they are generating !

Sadly, that may not prevent careless or *!&#"/?ole users from ruining a session.

[ann0see]

Can you draft a suggestion and put it on the GettingStarted page - if it isn't there already which I doubt.
Maybe a loopback check should also be implemented #1252

It would be great if you helped re-vive it (or draft an actionable issue)

[pcar75]

Oops sorry I had missed that

Before playing with others, we recommend that you connect to an empty server to test your setup, and make sure you are listening to the signal coming back from the server (if possible) and not yourself.

The loopback test bit could be added to this phrase but may burden the idea with unnecessary details. However, it might be more complete if

Before playing with others, we recommend that you connect to an empty server to test your setup, and make sure you are listening to the signal coming back from the server (if possible) and not yourself and that your signal has appropriate quality and volume.

For loopback check to be (semi?-) automatically implemented , one should be warned the ping and overall delays do not reflect what a public or private server elsewhere will provide, as evidenced in Ref. "3.8.0 on Windows 10 : problem with loopback (127.0.0.1)" #1855

[dcorson-ticino-com]

If people follow the getting started info it will not happen.
But if it is not clear there, suggestions for clarification are always welcome.

[pcar75]

@dcorson-ticino-com Sadly , anyone working around adult education will testify that contrary to what we tell our children to do, most adult do not read the manuals :-/
EDIT : ... but some may skim over a Getting Started section .