Skip to content

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

Open

Description

@pgScorpio

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?

Activity

  1. gilgongo commented on Apr 2, 2021

    @gilgongo
    Member

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

  2. pgScorpio commented on Jan 13, 2022

    @pgScorpio
    ContributorAuthor

    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.

  3. added this to the Release 3.11.0 milestone on Oct 5, 2022
  4. moved this from Triage to Backlog in Trackingon Jun 17, 2023
  5. added 2 commits that reference this issue on Aug 1, 2023
  6. moved this from Backlog to In Progress in Trackingon Aug 1, 2023
  7. added a commit that references this issue on Aug 3, 2023
  8. self-assigned this
    on Aug 12, 2023
  9. added a commit that references this issue on Aug 15, 2023
  10. added 2 commits that reference this issue on Aug 23, 2023
  11. 43 remaining items

  12. added a commit that references this issue on Sep 22, 2024
  13. added a commit that references this issue on Oct 1, 2024
  14. added 3 commits that reference this issue on Oct 25, 2024
  15. added a commit that references this issue on Nov 26, 2024
  16. added a commit that references this issue on Dec 10, 2024
  17. added 5 commits that reference this issue on Dec 18, 2024
  18. added a commit that references this issue on Sep 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    • Status
      Triage

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions