New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Playerctl is too restrictive in matching a media player instance #198
Comments
For multiple instances, there's a part of the mpris specification for that kdeconnect should be using here. They should be specifying their instances with https://specifications.freedesktop.org/mpris-spec/2.2/
Make an issue with them asking to implement this part of the spec. As for your suggested solution, this is already implemented with the special player name
There's also With all of these options to select players, I don't think general globbing is useful when players follow the instance spec. |
I answered my followup question by searching the code for
Thanks for that as well. |
I was looking to open the bug against KDEConnect, but I realized the specification doesn't require |
Oh ok I think it would be safe to drop the |
I use KDEConnect, which permits me to remotely control media in-between my laptop/desktop/phone.
However, the player names reported by playerctl are like the following:
It is unwieldy to specify the full strings for these players. Multiple players from a single remote host will show up as multiple
kdeconnect.mpris_[hash]
on the local host. Also, Firefox uses something likefirefox.instance[num]
.Suggested solution:
Implement glob matching for player lists. Interpret
playerctl -i 'kdeconnect.*,firefox.*'
to ignore all matching players.This kind of matching could also be useful in
-p
to specify preferences but allow any player to be controlled:Is this in-scope, or is scripting on the output of
playerctl -l
preferred?Thank you!
The text was updated successfully, but these errors were encountered: