You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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?
When controlling it with an remote it can happen that you press the volume down button too long accidently, and then it can take quite a while to get up again.
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: