-
Notifications
You must be signed in to change notification settings - Fork 0
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
New Snapclients are at 100% volume at first connect #37
Comments
Feature Request in snapcast project |
Possible solutions:
|
Success. The following
And this is the volume in percent a brand new snapclient gets assigned on initial connect (i.e. the snapclient is not known to |
|
Moved setting from |
PR has been merged in snapcast to I'll expand the current snapserver role to support the new parameter in |
And it's released in v0.27.0 🎉 |
I have not investigated yet if there is any possibility via command line / configuration files to set the initial volume to a certain level. I agree that for new setups it is easier to search for something to lower the volume than to start erratic debuging just to find out two hours later that it was just one (of the many) volume settings along the audio path set to 0...
But when you have a working setup and add a device (by simply adding a hostname to your
inventory
and running the playbook again) or rename the snapclient device name (add/edit some ansible variables...) it can get quite loud during the ansible run: At the moment the snapclient picks up the connection and starts to play music for the first time, you have 100% volume. Depending on what equipment you have connected (e.g. a hifiberry amp board with connected speakers), the only chance you have is to stop all inputs...The text was updated successfully, but these errors were encountered: