Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 5 hrs, 56 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 18 hrs ago - more...
| The Following User Says Thank You to Joorin For This Useful Post: | ||
 |
|
2010-06-03
, 18:34
|
|
Posts: 148 |
Thanked: 484 times |
Joined on Nov 2008
|
#92
|
Originally Posted by Joorin
You can request to become the maintainer if you like. There have been some cases where package maintainership has been handed over.
There is already a despotify package for the library and some simple client. As far as I know, this has been patched with new client version identifiers but it still might not work.
Of course with libdespotify it's a bit complicated as the API changed between r488 and r508. Updating to r508 breaks the older (less maintained) clients or there needs to be some modifications to the library to support the old API.
|
|
2010-06-03
, 19:10
|
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#93
|
Originally Posted by tekojo
I have thought about that. As things are now, I'm not sure I've got the time to maintain two packages (even though I'll compile despotify as needed). Perhaps this changes over the summer.
You can request to become the maintainer if you like. There have been some cases where package maintainership has been handed over.
But, as an idea, I agree on it not being a bad one.
Of course with libdespotify it's a bit complicated as the API changed between r488 and r508. Updating to r508 breaks the older (less maintained) clients or there needs to be some modifications to the library to support the old API.
Backward compatibility feels like trouble since there is an old function that has changed.
| The Following User Says Thank You to Joorin For This Useful Post: | ||
|
|
2010-06-04
, 17:34
|
|
Posts: 30 |
Thanked: 5 times |
Joined on May 2010
@ @Netherlands
|
#94
|
Footify is getting better and better! no crashes anymore and very reliable. i thought about 1 thing. is it possible to create a save button to add a song you found using the search function to a playlist?
When this feature is there, i never need to start my pc for spotify anymore
keep up the great work!
When this feature is there, i never need to start my pc for spotify anymore
keep up the great work!
|
|
2010-06-04
, 18:11
|
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#95
|
Originally Posted by jacobkorf
Despotify has no functionality to add or remove songs from playlists.
Footify is getting better and better! no crashes anymore and very reliable. i thought about 1 thing. is it possible to create a save button to add a song you found using the search function to a playlist?
When this feature is there, i never need to start my pc for spotify anymore
keep up the great work!
An alternative would be to keep a list of "interesting" songs on the N900 but this playlist would not be available on your PC.
|
|
2010-06-05
, 09:15
|
|
Posts: 48 |
Thanked: 21 times |
Joined on May 2010
|
#96
|
Hi,
my client is very very slow somehow since version 0.0.4 (I think 0.0.3 worked better).
Having launched it in terminal, I see a constant output of:
pulse.c: pa_simple_write() failed: Invalid argument
I do have some large playlists, but that shouldn't be a problem, should it? I've been testing it with this playlist: spotify:user:topsify
laylist:1QM1qz09ZzsAPiXphF1l 4S
When I do finally get a song to play, it at most plays one.
Somehow the entire client becomes unresponsive.
my client is very very slow somehow since version 0.0.4 (I think 0.0.3 worked better).
Having launched it in terminal, I see a constant output of:
pulse.c: pa_simple_write() failed: Invalid argument
I do have some large playlists, but that shouldn't be a problem, should it? I've been testing it with this playlist: spotify:user:topsify
laylist:1QM1qz09ZzsAPiXphF1l 4SWhen I do finally get a song to play, it at most plays one.
Somehow the entire client becomes unresponsive.
|
|
2010-06-05
, 09:36
|
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#97
|
Originally Posted by florian
Are you using the latest, 0.0.6-1, now or some other version?
Hi,
my client is very very slow somehow since version 0.0.4 (I think 0.0.3 worked better).
Having launched it in terminal, I see a constant output of:
pulse.c: pa_simple_write() failed: Invalid argument
I do have some large playlists, but that shouldn't be a problem, should it? I've been testing it with this playlist: spotify:user:topsify
When I do finally get a song to play, it at most plays one.
Somehow the entire client becomes unresponsive.
|
|
2010-06-05
, 09:50
|
|
Posts: 48 |
Thanked: 21 times |
Joined on May 2010
|
#98
|
Originally Posted by Joorin
Yup, running 0.0.6-1
Are you using the latest, 0.0.6-1, now or some other version?
Originally Posted by Joorin
Right, but this seems to take 2 mins or more, per song?
The read loop that pumps data from despotify to PulseAudio has to be started at a certain time to make despotify start doing things (or that's how it looks to me). If despotify isn't ready to deliver data, you get this message. I have left it like this to be able to see that the read loop is still alive. At some time I'll make this go away and if it's a problem that this is sent to the console, I might do it sooner.
Please note: I'm testing this via WiFi on a 50Mbit/s line. So internet speed shouldn't be the issue here.
Originally Posted by Joorin
Right, login takes about 5 minutes, but I do have quite a few playlists. Can't these be cached?
How many songs are there in this playlist? footify asks for all saved playlists and all songs after logging in so if you have many playlists with lots of songs in them, startup will take some time.
Originally Posted by Joorin
No shuffle, no repeat ... all songs that should play back are playable. It behaves slow like this in every playlist.
This doesn't sound good. Are all songs in the playlist playable? Did you activate Shuffle? Does it behave the same way if you start another song in the playlist? How are you connected to the internet?
Originally Posted by Joorin
No other CPU hungry processes.
If despotify is busy waiting for data from the Spotify servers, things might get slow. Are you running any other CPU hungry processes at the same time?
|
|
2010-06-05
, 14:44
|
|
Posts: 726 |
Thanked: 345 times |
Joined on Apr 2010
@ Sweden
|
#99
|
Version 0.0.7-1 has been uploaded to the Extras-devel repository.
New features:
+ It is now possible to choose between high and low bitrate.
+ It is now possible to enable local cache of cover art, album information and playlists.
Changes:
* The debug message from the sound layer has been removed.
To think about:
The cache is located in /home/user/.cache/despotify and it's important to remember that this is in the 2GByte "program partition". If you'd like to allow for a bigger cache, you need to create a symlink to somewhere under MyDocs and hope it works. I have not tried this.
Please experiment with high and low bitrates and report if it changes the behaviour of the client. It's extra interesting to know if lots of big playlists still is a problem or not.
Playlists handling seems to be atomic in despotify. This means that if you change one playlist, all playlists will be downloaded again. This might be by design by Spotify.
If you change the settings for bitrate and cache, please wait a moment for the change to reach the gconf system before clicking Login. I have no idea why it sometimes takes a while.
New features:
+ It is now possible to choose between high and low bitrate.
+ It is now possible to enable local cache of cover art, album information and playlists.
Changes:
* The debug message from the sound layer has been removed.
To think about:
The cache is located in /home/user/.cache/despotify and it's important to remember that this is in the 2GByte "program partition". If you'd like to allow for a bigger cache, you need to create a symlink to somewhere under MyDocs and hope it works. I have not tried this.
Please experiment with high and low bitrates and report if it changes the behaviour of the client. It's extra interesting to know if lots of big playlists still is a problem or not.
Playlists handling seems to be atomic in despotify. This means that if you change one playlist, all playlists will be downloaded again. This might be by design by Spotify.
If you change the settings for bitrate and cache, please wait a moment for the change to reach the gconf system before clicking Login. I have no idea why it sometimes takes a while.
| The Following User Says Thank You to Joorin For This Useful Post: | ||
|
|
2010-06-05
, 15:57
|
|
Posts: 48 |
Thanked: 21 times |
Joined on May 2010
|
#100
|
Hey,
the client works a lot smoother now that the playlists are cached. How are they refreshed?
For playback: It still takes "ages" (anything between 30 seconds and 5 minutes) to start the first track. Once that one is started, the playing is fast. No long waits between tracks, even when skipping.
the client works a lot smoother now that the playlists are cached. How are they refreshed?
For playback: It still takes "ages" (anything between 30 seconds and 5 minutes) to start the first track. Once that one is started, the playing is fast. No long waits between tracks, even when skipping.
Changes and fixes as above with one extra smallish thread bug fixed and a minimal change to the startup graphics. Shuffle is still not perfect but it won't kill the application as soon as it runs into a corner.
If the playing stops while Shuffling, try to start another song and you'll get some more play-time out of it.