-
Notifications
You must be signed in to change notification settings - Fork 48
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
Configurable limit for Volume filters #226
Comments
@HEnquist This is set as completed, but where can I set the clamp limit? |
This was not implemented as described here. Instead I added a limiter filter. It's a different but not equivalent solution to the problem of limiting the max volume going out. I should have added a comment about that when I closed this issue. And I probably should not have closed it. I'll reopen and implement this for 3.0. |
@HEnquist Would you consider adding a lower limit as well? |
Adding a lower limit won't help with that. The limit does not limit what values the websocket interface accepts, it only clamps what the volume control actually applies. |
Volume filters should have min and max parameters. If the volume is set to a value outside the allowed range, the actual applied value should be clamped at the nearest limit.
The text was updated successfully, but these errors were encountered: