skiletro
commented
1 year ago Can confirm I'm having the same issue with spotify (+ pretty much any other single player I tested). Was wondering if there are any updates on this issue?
Open bvergnaud opened 1 year ago
skiletro
commented
1 year ago Can confirm I'm having the same issue with spotify (+ pretty much any other single player I tested). Was wondering if there are any updates on this issue?
Hello,
I use Plexamp to play music. I'm using
playerctlin a waybar custom module to show what song is playing. And rather than poll every second, I'd rather use the--followflag which seems perfectly suited.So I crafted this little command which works almost as expected:
I say almost because if I close Plexamp,
playerctlseems to not know what to do about it. It prints a blank line, stays open, and won't resume following any new Plexamp I open or any other player.Here's an example:
It just hangs there until I
killit /^C.Here's a more detailed example with debug mode enabled:
So it does catch the new instance, and new status / metadata changes. However it just does not output them to stdout. Before the blank line, you can see the output after each
Plexamp: metadata changedline. After the blank line, no output. I did the same test with spotify, which works better, there's a few half-empty lines when the player restarts, but switching to a new track works as expected.In my case it's a problem because even though waybar gives me a
restart-intervaloption to restart the module after some time, sinceplayerctlnever exits, there's nothing to restart, the thread is still considered active.I'm happy to provide more details if it can help.