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
I've recently been working on developing mute/unmute functionality for my device and have encountered an issue.
Problem:
When the device is in the muted state, performing a "next track" or "seek" operation in LMS causes the device's volume to change from a negative value to a positive one.
However, the mute state reported via the HTTP API remains as "muted."
If I then send an unmute command, the device's volume is set to 0.
This issue appears to be caused by an inconsistency between the actual volume level and the reported mute state.
Hi
I've recently been working on developing mute/unmute functionality for my device and have encountered an issue.
Problem:
When the device is in the muted state, performing a "next track" or "seek" operation in LMS causes the device's volume to change from a negative value to a positive one.
However, the mute state reported via the HTTP API remains as "muted."
If I then send an unmute command, the device's volume is set to 0.
This issue appears to be caused by an inconsistency between the actual volume level and the reported mute state.
Used API:
System Information:
Operating System: Windows 10 (64-bit) - ZH_CN - cp936
Lyrion Music Server Version: 9.0.1 - 1736238071
The text was updated successfully, but these errors were encountered: