Skip to content
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

Spotifyd or other media player support #8

Open
haley-yung opened this issue Aug 26, 2020 · 2 comments
Open

Spotifyd or other media player support #8

haley-yung opened this issue Aug 26, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@haley-yung
Copy link

This is a great application and adds some beauty to my desktop

However, as the Spotify's client is RAM and battery heavy, I switched to using Spotifyd + Spotifytui
Is it possible to config the UeberPlayer to detect tracks/audio input from alternative players other than Spotify and still be able to show the cover art/ name?

@noatpad
Copy link
Owner

noatpad commented Sep 21, 2020

Hi there, pardon for the late reply. I put this lil' side project on the side for a bit, ahah.

But it should be possible if I implement the Web API as a fallback option to run with, which would allow that combination and any other software that uses that API. Not sure how much I have to add to implement that, but I'll see what I can do

@noatpad
Copy link
Owner

noatpad commented Sep 27, 2020

So here's the thing. It is possible, but the problem is that it's tricky for a few reasons:

  • I'm not sure how to authenticate a user in a user-friendly manner, because you need to authenticate it through a browser and it has to make a callback somewhere (I can't do that directly back to the widget to my knowledge). My thought was to have the user do a small process to self-serve a pre-made .html file using Python (since that and the required function comes pre-installed with every Mac) to get the access token and the refresh token easily and plug those into the main widget.
  • The other thing is security since from what I can tell; the client ID, secret ID, & access token are all kept in the same directory. It's probably not a big deal, but it might not be the best practice.
  • And finally, AppleScript and JSON responses don't go well together, haha. It's definitely doable (I could maybe make a custom bash script for that instead), but that'll take a bit of figuring out on my end.

For now, I think I might put this on the backlog since I'm not quite sure how to take this just yet

@noatpad noatpad added the enhancement New feature or request label Sep 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants