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 noticed the incorrect display of the "Mute" flag on the display.
This display is only true if the mute function is controlled by a rotary encoder.
On the contrary, in the case of using the remote control or the web interface, the display of the "Mute" flag does not correspond to the actual situation.
I could handle this problem myself, but I would like my code to be as little different from the official version as possible. I already have too many of those differences. Then it is very difficult to incorporate the news in the official version into my modified code.
I'm not even 100% sure (only 99%) that the described behavior also occurs on devices with the official version of the code...
If not, then I'm very sorry for reporting a bug that doesn't exist!
The text was updated successfully, but these errors were encountered:
In the end, I decided to solve it myself. It worked pretty well, but I found that it didn't really suit me.
I arrived at a completely different (actually completely opposite) solution:
Before, I didn't like that the word "Mute" was sometimes visible, sometimes not (even though the mute state was selected).
Now the word "Mute" (instead of the name of the station or track) is no longer displayed on the display at all. The mute status is sufficiently indicated by the volume indicator.
This is far more useful as it is immediately visible when a track or station change occurs during the mute state.
I noticed the incorrect display of the "Mute" flag on the display.
This display is only true if the mute function is controlled by a rotary encoder.
On the contrary, in the case of using the remote control or the web interface, the display of the "Mute" flag does not correspond to the actual situation.
I could handle this problem myself, but I would like my code to be as little different from the official version as possible. I already have too many of those differences. Then it is very difficult to incorporate the news in the official version into my modified code.
I'm not even 100% sure (only 99%) that the described behavior also occurs on devices with the official version of the code...
If not, then I'm very sorry for reporting a bug that doesn't exist!
The text was updated successfully, but these errors were encountered: