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
Can you advise if the same workaround that's required for Kodi would be required for Mopidy on a Pi running Raspbian Stretch? I see the correct events firing in evtest, but no change in effective or reported volume. Sound is output to bluetooth speaker via Alsa.
*Edit: alsamixer accurately reflects volume changes, but only to the default output, not the bluetooth output. "alsamixer -D bluealsa" displays the output volume for the correct device, but it remains static while the default device changes. Any advice on how to get it to affect the bluetooth / bluealsa sink instead would be appreciated.
The text was updated successfully, but these errors were encountered:
streff
changed the title
Mopidy compatibility (Raspbian)
Bluetooth compatibility (Raspbian)
Feb 15, 2019
I have no experience with mopidy, but essentially what this module does is provide keyboard input with volume up or down button presses, so you could see if anyone has had this issue with a normal keyboard and try any solutions that come up from there?
I'd like to try and help investigate but I just don't have the required bits (no Bluetooth audio) but if there is anything you think I might be able to help with please ask
Can you advise if the same workaround that's required for Kodi would be required for Mopidy on a Pi running Raspbian Stretch? I see the correct events firing in evtest, but no change in effective
or reportedvolume. Sound is output to bluetooth speaker via Alsa.*Edit: alsamixer accurately reflects volume changes, but only to the default output, not the bluetooth output. "alsamixer -D bluealsa" displays the output volume for the correct device, but it remains static while the default device changes. Any advice on how to get it to affect the bluetooth / bluealsa sink instead would be appreciated.
The text was updated successfully, but these errors were encountered: