Description: This plugin allows you to easily control Spotify using KRunner. The plugin uses Spotipy to interact with the Spotify Web API. Using only a handful of words the user can control Spotify in a straightforward manner, even if Spotify does not run on the same device as KRunner is running on. Whether you are playing Spotify on your phone, Chromecast(Audio), Smart TV or anyother device, you are able to control it using this plugin!Last changelog:
v0.3
The following new features have been added:
- Podcasts are now supported - Progress of track can be controlled - Playback style can be changed - Better volume control - General bugfixes
Hey, could you please mark the install script as executable? Otherwise the installation does not work automatically when installing this using KNewStuff .
other two things that came to my mind today while using the add-on are:maybe shorter keywords could helpful (for speed i mean), the next and previous commands could take an integer value for the number of song skiped (if none default could be 1), and ,probably the most important thing, an album function (i am an album listener).
ty for listening and il stop trowing shit at you now
Don't worry, I can handle some criticism.
The keywords can be configured in the config file located in: ~/.config/KRunner-Spotify/KRunner-Spotify.config. They can thus be made as short as you want. After editing, don't forget to run the: ReloadConfig command in Krunner for the changes to take effect.
To be honest, I do not see the use case for skipping multiple songs.
Regarding the album feature, it has been on the backlog since the beginning, but as I am not an album listener I haven't worked on it yet.
pretty good add-on overhaul useful and fast, i have some suggestions tho.
I think that the double volume function is a bit of a repetition, u can do a single vol function that takes as input the percent of volume to set, instead of 2 functions for increase and decrease the volume,another thing that bugs me is that when u pause a song for a bit after some time u can't resume it or even play another song cause the program says that there isn't an open instance even if there is solid 8 stars, solve those problems and they can be 10
good job keep it up
8pretty good add-on overhaul useful and fast, i have some suggestions tho.
I think that the double volume function is a bit of a repetition, u can do a single vol function that takes as input the percent of volume to set, instead of 2 functions for increase and decrease the volume,another thing that bugs me is that when u pause a song for a bit after some time u can't resume it or even play another song cause the program says that there isn't an open instance even if there is solid 8 stars, solve those problems and they can be 10
good job keep it up
Hi,
First of all thanks for the feedback, regarding your points:
* I do agree that a single volume command is beneficial, I've put it on the back log.
* I, unfortunately, cannot do anything about the fact that there is no open instance available. Spotify automatically "unregisters" a device after it has not played a song/track for a certain amount of time, lets say 15 minutes. After those 15 minutes, the Spotify API is no longer able to communicate with the device running Spotify. As I am writing this comment I might have a solution for this but I am not a 100% sure if it is going to work.
Ratings & Comments
9 Comments
7 7 good
Hey, could you please mark the install script as executable? Otherwise the installation does not work automatically when installing this using KNewStuff .
Hi, I'll do that within a few days.
It has been fixed.
other two things that came to my mind today while using the add-on are:maybe shorter keywords could helpful (for speed i mean), the next and previous commands could take an integer value for the number of song skiped (if none default could be 1), and ,probably the most important thing, an album function (i am an album listener). ty for listening and il stop trowing shit at you now
Don't worry, I can handle some criticism. The keywords can be configured in the config file located in: ~/.config/KRunner-Spotify/KRunner-Spotify.config. They can thus be made as short as you want. After editing, don't forget to run the: ReloadConfig command in Krunner for the changes to take effect. To be honest, I do not see the use case for skipping multiple songs. Regarding the album feature, it has been on the backlog since the beginning, but as I am not an album listener I haven't worked on it yet.
pretty good add-on overhaul useful and fast, i have some suggestions tho. I think that the double volume function is a bit of a repetition, u can do a single vol function that takes as input the percent of volume to set, instead of 2 functions for increase and decrease the volume,another thing that bugs me is that when u pause a song for a bit after some time u can't resume it or even play another song cause the program says that there isn't an open instance even if there is solid 8 stars, solve those problems and they can be 10 good job keep it up
8 pretty good add-on overhaul useful and fast, i have some suggestions tho. I think that the double volume function is a bit of a repetition, u can do a single vol function that takes as input the percent of volume to set, instead of 2 functions for increase and decrease the volume,another thing that bugs me is that when u pause a song for a bit after some time u can't resume it or even play another song cause the program says that there isn't an open instance even if there is solid 8 stars, solve those problems and they can be 10 good job keep it up
Hi, First of all thanks for the feedback, regarding your points: * I do agree that a single volume command is beneficial, I've put it on the back log. * I, unfortunately, cannot do anything about the fact that there is no open instance available. Spotify automatically "unregisters" a device after it has not played a song/track for a certain amount of time, lets say 15 minutes. After those 15 minutes, the Spotify API is no longer able to communicate with the device running Spotify. As I am writing this comment I might have a solution for this but I am not a 100% sure if it is going to work.