spotify-tui VS Mopidy

It was at this point I was getting a lot of joy out of writing command line applications. I had also just learnt of the existence of spotify-tui and wanted to explore more I could build such applications. So building interfaces for APIs felt like a good way to try this out.

If you are handy with a terminal, spotify-tui is my favorite Spotify controller I’ve ever used. No bullshit at all.

I switched to linux recently and iam loving it the speed and CLI tools that linux provides are amazing you can do anything imaginable in the terminal i use Spotify in the terminal navigate very very fast using auto-jump and its just easier than navigating all those uis and using the keyboard for everything is way faster and easier on your hand than the mouse and keyboard combination especially if you use a window manager

I dont know if it counts but I have used spotify tui on my pi400 a while ago link

November 2019

For example, there's a couple reddit clients, YouTube viewers, Spotify clients and many many more.

If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices there.

Lots and lots of FOSS music players use libspotify or can otherwise connect to your Spotify account.

Here's just one. It's BYO frontend. https://mopidy.com/

Probably a good time to give a shout out to Mopidy: https://mopidy.com/

Though as for myself, I'm still running Squeezebox - nothing like being able to SSH into your smart speaker and mess around with the Perl system that's running it.

Have you tried Mopidy or MPD daemon? There's even a mopidy-party extension that is

I've tried several times to get mpd working over a network. The only way I got it to work was with mopidy. At some point it broke and I moved on to jellyfin instead. Too bad, because I love ncmpcpp as a client.

I have a music library on my home server that I use mopidy to play via the iris plugin integrated into my home assistant UI. It plays over Snapcast which streams over the network to multiple devices in the home with independent volume control. I can fire up the Snapcast client in my phone to get it going there as well, which does work over vpn if I'm away, though I generally just fire up the files from my phones SD card for out-of-home listening. I recently started using whipper on Linux to extract audio from craigslist cds.

https://mopidy.com/

https://mopidy.com/ext/iris/

https://github.com/badaix/snapcast

https://github.com/whipper-team/whipper

Could instead use Mopidy as the music player, which has plugins for Spotify and Airplay support.

Thanks! I use it on a daily basis, but I don’t think it’s ready for a wider adoption yet — for example, a pause button is still missing ... I’d be curious to know your experience with it though! For something more stable, you might like Mopidy.

Right now I'm reading about mopidy and iris (I have a server with some docker services and it would be nice using it as a Spotify connect device), I think this setup could be extended with extra algorithms, maybe they already exist as modipy extensions. I've never gone into detail about these but I'll do it!