web-api VS LyricsGenius

I did some research and it seems that Chromecast Audio are not visible using Spotify Connect Api as discussed here: https://github.com/spotify/web-api/issues/787. Maybe it has been fixed since then though.

Slightly off topic, but it’s a shame Spotify’s web API doesn’t support (and they’ve said never will support [1]) playlist folders. I get that it’s a bit of a power user feature but it’s an essential one for me in any media player.

Makes me worry they’ll remove the feature from their app one day (they allude to it being a bit of a mess in the database) which would be the push I’d need to move away to either another service or a local collection only…

[1] https://github.com/spotify/web-api/issues/38

See GitHub issue: https://github.com/spotify/web-api/issues/157

Ah, that makes sense. There appear to be some specific workarounds: https://github.com/johnwmillr/LyricsGenius https://github.com/philipredstone/simple-genius-lyrics-scraper

this, I wanted to make a little utility for getting lyrics for whatever song is currently playing on spotify[1] and ran into the issue for getting the song name without using the API since that's just inconvenient for the end user. The most popular such project does go that way though.[2]

I ended up writing a small library that does that locally cross-platform by using the metadata from the app.[3] The approach is probably not as robust as the API, but much faster and works well.

[1] https://github.com/SwagLyrics/SwagLyrics-For-Spotify

[2] https://github.com/johnwmillr/LyricsGenius

[3] https://github.com/SwagLyrics/SwSpotify

It looks like there's also a couple of wrappers for this, including this python code: https://github.com/johnwmillr/LyricsGenius

A quick search lands on the LyricsGenius wrapper, and one that i personally used before is the Spotipy wrapper. Incorporate those in your project, start small by breaking it up into easy to achieve things like creating a function that searches on Genius and gives you something back etc.