-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Set all faders to new client level" only affects current users #1420
Labels
feature request
Feature request
Milestone
Comments
I believe this is by design (there is a discussion about this point somewhere...), but I agree it feels like a bug. |
I think "Set all faders to new client level" should also remove all "storedfader" values in the ini file of not currently connected clients, In that way we can keep the inifile tidy and it will also apply the current new client level when an old client joins again. |
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 1, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 1, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 3, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 15, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 23, 2023
8 tasks
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 25, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 28, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 28, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 5, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 12, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 18, 2023
pljones
added
feature request
Feature request
and removed
bug
Something isn't working
labels
Sep 18, 2023
pljones
added a commit
to pljones/jamulus
that referenced
this issue
May 6, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jun 9, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jun 15, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jun 23, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jun 30, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jul 2, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jul 20, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Jul 26, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 4, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 4, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 7, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 26, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Aug 31, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 13, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 21, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 22, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Sep 22, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Oct 1, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Oct 25, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Oct 29, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Nov 2, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Nov 26, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Dec 10, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Dec 18, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Dec 20, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Dec 25, 2024
pljones
added a commit
to pljones/jamulus
that referenced
this issue
Dec 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When using "Set all faders to new client level" this only resets the faders of current users, if a previous user signs in it's level is still set to the previous level.
To Reproduce
Sign in to a server with multiple users.
Set all levels to i.e. max.
Sign out one user.
use "Set all faders to new client level".
sign in the previous user again and it's level will still be set to max. not the "New Client Level".
Expected behavior
Just like when using "Clear All Stored Solo and Mute Settings" also the stored levels should be reset to new client level when using "Set all faders to new client level"
Screenshots
Operating system
n.a.
Version of Jamulus
3.6.x, 3.7.0
Additional context
Maybe also an added option to delete all stored users?
The text was updated successfully, but these errors were encountered: