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
Disable Audio Controls #789
Comments
An alternative approach would be to take a page out of Android's book with how they handle max volume when using headphones. It prompts that the volume is too loud for extending durations, but doesn't block it after the prompt. Basically it is a 'soft' limit. Also worth considering is other mechanisms that control volume (Snapcast integration for instance), as well as keyboard shortcuts. There are a few moving parts to making this a complete feature. But indeed, I think gauging demand is the first step. |
I'd also like this functionality. |
@loryanstrant the other option btw would be to write a mopidy mixer plugin to control sonos volume, and then iris' volume control would work. In theory it's just an api call/upnp message, but I've not tried it. |
I have achieved something similar by using Iris Commands. This allows you to set up arbitrary API calls that can be triggered by buttons within the 'Outputs' panel in the Iris UI. In this screenshot you can see + and -, those trigger a HTTP request to my infrared blaster, and on to my lounge amplifier. Not perfect, but perfectly capable. See more in Commands |
Problem to solve
I'd like to add a config that would allow you to disable the volume control. I have a fairly expensive audio setup, but like to let my friends and family play music through their phones. I just don't want someone to accidentally turn the volume to max and blow my speakers out.
Proposed solution
Add a config value for iris, I'm thinking something like
disable-volume-control
that could be set to true to hide the volume control.Additional info
I'm planning on implementing this to my local build, but wondering if anyone else would like to see that be a feature.
The text was updated successfully, but these errors were encountered: