My /comfy/ and less bloated spotify-tui setupPosted on Wednesday, 03 June 2020 Suggest An Edit
Hi! This time I will explain about how I setup my spotifyd + spotify-tui to enjoy music from spotify without their resource heavy app. It’s not Spotify’s fault, it’s Electron. Not that I hate it, I think it’s awesome. It just feels heavy on my machine. I still have 4GB of RAMs lol, so that’s reasonable.
Spotifyd is the daemon that is used to run spotify-tui. So, basically spotify-tui is just a front-end for spotify that needs some sort of daemon. You can use spotify-tui with any official Spotify client. For example, spotify-tui will read your phone as an available device but that will be a hassle having to open spotify on your phone to use spotify on your desktop.
Spotifyd provides a service that can be used to play spotify. It’s more lightweight and supports more platform than the official client. You can check their github page for more details.
I’m using Arch so I will use the almighty AUR to make my life easier. If you’re on any other distro, you can either take the binary or build it yourself. To install it on Arch (or any Arch based distro), you can use any AUR helper or download the
PKGBUILD and run
# yay $ yay -S spotifyd-full # trizen $ trizen spotifyd-full
I personally use
spotifyd-full from AUR. Spotify-full is spotifyd with all feature flags enabled. If you want a minimal install, you can use
spotifyd instead. If you don’t like to wait for it to compile, just take one with
-bin suffix. For more details on feature flags, you can refer to their github page.
Configuring spotifyd is quite easy actually, they gave you a default configuration to help you get going. Here’s mine.
[global] username = <your username> password = <your password> # password_cmd = command_that_writes_password_to_stdout # use_keyring = true backend = pulseaudio # device = alsa_audio_device # control = alsa_audio_device # mixer = PCM volume_controller = alsa_linear device_name = arch bitrate = 320 cache_path = /home/elianiva/.config/spotifyd no_audio_cache = false volume_normalisation = true normalisation_pregain = -4 device_type = computer
I’ll explain the configuration briefly.
Fill this field with your real username. You can get one from here and it’s roughly looks like 21zu9n5i8jtipipiwxrfyglhohmq. It’s NOT your usual username that you can change, this username is given by Spotify.
Fill this field with your spotify device password which you can make by visiting this link. If you want to put this configuration on github or something like that, DO NOT USE THIS METHOD. If you use this method, don’t include it on your repo.
Fill this field with a program that outputs your password through stdout.
passcan do this. For more details, you can check out their website. I personally don’t use this so I can’t give you any guide.
Fill this field if you want spotifyd to look up any password on your machine. I don’t have any experience with keyrings and such so I can’t give you any guide on this. It’s explained on spotifyd readme though, so you can check that.
As the name suggest, this field sets the backend used by spotifyd. I use pulseaudio because pulseaudio is able to set per-app volume. I know that ALSA can do that as well but it’s just way too much tinkering.
This field sets the device that is used for ALSA to stream audio to which can be listed by running
aplay -L. If you are using pulseaudio like me, just comment this section.
This field sets the controller that is used for ALSA to control its audio to. If you are using pulseaudio like me, you can comment this section as well.
This field sets the ALSA that is used by spotifyd. Again, you can comment this is you’re using pulseaudio.
This field sets the volume controller for spotifyd. Available options are
This field sets the device name for spotifyd. You can fill this with whatever you want.
This field sets the bitrate for your audio. Available options are 96, 160, and 320. I use 320 which is the highest option available cuz why not ツ
This field defines where to put the cached audio. It can’t accept
$HOMEfor home directory shorthand, so you have to fill the full path like
No Audio Cache
If this field sets to true, spotifyd won’t cache the audio. I set this to false because I want my audio to be cached so it loads faster and it saves a lot of bandwith.
This field set whether or not spotifyd normalize the volume of an audio that you’re playing. I enable this because I want all my song to be played with the same volume.
Basically, it sets how loud or quiet the song will be. The higher you set it, then it will be louder and vice versa. For example, if you set it
-10which is the default option then it won’t be as loud as if you set it to
-4. You might tinker around with this to get what you like.
This sets the device type for spotifyd that is displayed on Spotify clients. You can fill this whatever you want, but I set mine to
computerbecause it’s a computer. Other available options are
stb(Set-Top Box), and
Now that spotifyd has been configured, let’s move on to spotify-tui itself.
Spotify TUI is a spotify client or frontend based on Terminal User Interface written in Rust. It’s an awesome alternative for the official Spotify client.
I like this software because it’s lightweight and it’s based on TUI which can be controlled fully with a keyboard. I also like its UI, it’s simple and straight forward. For more details about this software, you can visit their github page.
Installing spotify-tui is pretty straight forward. I use Arch so I can just use AUR. If you’re on the other distro, check out their readme for installation.
# yay $ yay -S spotify-tui # trizen $ trizen spotify-tui
After installing it, the executable binary is called
spt. I got confused the first time I installed it because I missed the part where it says
The binary executable is
So don’t get confused when you type
spotify-tui and nothing happens.
Spotify-tui needs to be authenticated by spotify. Don’t worry though, it’s super simple. Just run
spt and fill out the needed field which are:
Your spotify client ID which can be acquired from Spotify Dashboard then click on
Create a Client iD. Then go to
Edit Settings, add
http://localhost:8888/callbackto Redirect URIs
Your spotify client secret which available on the same website as your spotify client ID.
After filling those out, you will get redirected to Spotify website that ask for your permissions.
There’s a lot of spotify-tui configuration which can make this post longer. I use the default configuration for it and satisfied enough. If you want to configure it yourself, please refer to their guide.
There we have it. Spotifyd + Spotify-tui. A Lightweight alternative for the official spotify client. Unfortunately, this setup doesn’t support offline mode yet. I would really like to see this feature implemented. Huge thank you goes to the developers of spotifyd and spotify-tui. Anyway, thanks for reading my post and have a nice day!