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
When setting the volume with either player.set_volume or player.props.volume = .., the volume gets changed correctly on the player, but the player volume property does not update to the new volume. Here are steps to reproduce it:
Have a player (cmus) open
Follow volume changes using playerctl volume --follow
Use the following code to change the volume of the player using the Python library
fromgi.repositoryimportGLib, Playerctlmanager=Playerctl.PlayerManager()
player=Playerctl.Player.new_from_name(manager.props.player_names[0]) # Make sure cmus is the only open playerplayer.set_volume(0.8) # Set to a different volume
Notice how the volume changes correctly in cmus, but it does not change in player.props.volume nor are there updates from the --follow command executed in step 2
Edit: I also see very similar issues with the shuffle and loop_status properties (shuffle events don’t even work at all). This could be a problem with how cmus integrates with MPRIS.
The text was updated successfully, but these errors were encountered:
However, I wonder why playerctl detects volume updates when using playerctl volume 0.1 compared to not detecting volume updates when using player.set_volume(0.1). I’ll reopen this issue due to this inconsistency.
The player I am using is cmus.
When setting the volume with either
player.set_volume
orplayer.props.volume = ..
, the volume gets changed correctly on the player, but the player volume property does not update to the new volume. Here are steps to reproduce it:playerctl volume --follow
player.props.volume
nor are there updates from the--follow
command executed in step 2Edit: I also see very similar issues with the
shuffle
andloop_status
properties (shuffle events don’t even work at all). This could be a problem with how cmus integrates with MPRIS.The text was updated successfully, but these errors were encountered: