Skip to content
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

Open
pgScorpio opened this issue Apr 1, 2021 · 2 comments · May be fixed by #3151
Open

"Set all faders to new client level" only affects current users #1420

pgScorpio opened this issue Apr 1, 2021 · 2 comments · May be fixed by #3151
Labels
feature request Feature request
Milestone

Comments

@pgScorpio
Copy link
Contributor

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?

@pgScorpio pgScorpio added the bug Something isn't working label Apr 1, 2021
@gilgongo
Copy link
Member

gilgongo commented Apr 2, 2021

I believe this is by design (there is a discussion about this point somewhere...), but I agree it feels like a bug.

@pgScorpio
Copy link
Contributor Author

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 pljones added this to the Release 3.11.0 milestone Oct 5, 2022
@pljones pljones added this to Tracking Jun 17, 2023
@github-project-automation github-project-automation bot moved this to Triage in Tracking Jun 17, 2023
@pljones pljones moved this from Triage to Backlog in Tracking Jun 17, 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 1, 2023
@pljones pljones moved this from Backlog to In Progress in Tracking Aug 1, 2023
pljones added a commit to pljones/jamulus that referenced this issue Aug 3, 2023
@pljones pljones self-assigned this Aug 12, 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
@pljones pljones linked a pull request Aug 23, 2023 that will close this issue
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 pljones moved this from In Progress to Backlog in Tracking Sep 18, 2023
@pljones pljones removed their assignment Sep 18, 2023
@pljones pljones moved this from Backlog to Triage in Tracking Sep 18, 2023
pljones added a commit to pljones/jamulus that referenced this issue Sep 18, 2023
@pljones pljones added feature request Feature request and removed bug Something isn't working labels Sep 18, 2023
@pljones pljones modified the milestones: Release 3.12.0, Release 4.0.0 May 3, 2024
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
Labels
feature request Feature request
Projects
Status: Triage
Development

Successfully merging a pull request may close this issue.

3 participants