Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 7 hrs, 6 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 19 hrs ago - more...
aenbacka |
2010-10-11
, 20:27
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#321
|
One additional thing that could help: could you provide the output when starting yaspot from the xterm (by typing yaspot), and logging in?
Originally Posted by mattiasbäx
|
|
2010-10-29
, 06:49
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#322
|
I have spent time investigating the login problem (i.e., "client too old.." error message) that some users have experienced, and now I think I have found the reason. It seems that if the Spotify username and / or password contain Scandinavian characters the login attempt to Spotify will fail with the "Client too old, library will need to be updated" error message. I have already a fix available for this (so Scandinavian characters can be used), and it will be part of the next QSpot version, which I hope to release soon..
 |
|
2010-10-29
, 16:59
|
|
Posts: 7,075 |
Thanked: 9,073 times |
Joined on Oct 2009
@ Moon! It's not the East or the West side... it's the Dark Side
|
#323
|
only bug-fix release or any new features?
|
|
2010-10-30
, 11:45
|
|
Posts: 7,075 |
Thanked: 9,073 times |
Joined on Oct 2009
@ Moon! It's not the East or the West side... it's the Dark Side
|
#325
|
Possible to include a feature later on where I can change search result to "Most played" by pressing "m" character on keyboard?
|
|
2010-10-30
, 13:17
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#326
|
Well I think such a feature is possible to introduce already in the next version..
Originally Posted by Dave999
Possible to include a feature later on where I can change search result to "Most played" by pressing "m" character on keyboard?
| The Following User Says Thank You to aenbacka For This Useful Post: | ||
|
|
2010-11-08
, 04:30
|
|
Posts: 75 |
Thanked: 27 times |
Joined on Dec 2009
|
#327
|
Does anyone else experience a massive slowdown with the N900 when using qspot for a while? If I listen to one album or an hour, it takes forever to try to get the device out of the screenlock! Sometimes I have to remove the battery because the device is so slow the display won't turn on at all! The music keeps playing though...
|
|
2010-11-08
, 08:01
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#328
|
I assume that you are using the lastest version (0.1.0-7)? What buffer size value / length are you currently using (default value is 30secs)? And what bit rate have you been using? It seems that the problem could be caused by e.g., some heavy memory usage.
Edit: I tested playing a very long track (duration over an hour) without experiencing any significant slowdown. I also used a large buffer size (300 secs). Are you using the latest firmware (PR1.3)? It seems that changes to the PulseAudio backend introduced in the newest firmware could impact on responsiveness.
Last edited by aenbacka; 2010-11-08 at 09:45.
Edit: I tested playing a very long track (duration over an hour) without experiencing any significant slowdown. I also used a large buffer size (300 secs). Are you using the latest firmware (PR1.3)? It seems that changes to the PulseAudio backend introduced in the newest firmware could impact on responsiveness.
Originally Posted by Nozu
Does anyone else experience a massive slowdown with the N900 when using qspot for a while? If I listen to one album or an hour, it takes forever to try to get the device out of the screenlock! Sometimes I have to remove the battery because the device is so slow the display won't turn on at all! The music keeps playing though...
Last edited by aenbacka; 2010-11-08 at 09:45.
|
|
2010-11-08
, 14:23
|
|
Posts: 75 |
Thanked: 27 times |
Joined on Dec 2009
|
#329
|
Originally Posted by aenbacka
Using latest 0.1.0-7. I haven't changed the default buffer size so it must be the 30secs. I use 160kbit when on the move and 320kbit when at home. I'm using PR1.3.
I assume that you are using the lastest version (0.1.0-7)? What buffer size value / length are you currently using (default value is 30secs)? And what bit rate have you been using? It seems that the problem could be caused by e.g., some heavy memory usage.
Edit: I tested playing a very long track (duration over an hour) without experiencing any significant slowdown. I also used a large buffer size (300 secs). Are you using the latest firmware (PR1.3)? It seems that changes to the PulseAudio backend introduced in the newest firmware could impact on responsiveness.
It's not about playing one long track. I'm playing mostly my "misc" playlist with shuffle enabled. I have 195 tracks on that playlist at the moment. When I begin listening to the playlist and I put on the device's screenlock and open the screenlock right after, there's no delay. If I let it play couple of songs and then try to open screenlock I might need to wait couple of seconds. If I wait long enough I won't be able to open my device at all, it's so jammed.
I also have the same problem as someone else earlier mentioned. When playing my "misc" playlist with shuffle, the player might start exactly the same song again which just played but show the "next" song as playing song. If I press skip then it will start playing the song that previously was showed in the album art etc. and again there's the album art and song name of the "next" song displayed. Whoah, difficult explanation... I just listened to Madonna's Love Don't Live Here Anymore at the same time Qspot telling me that the playing song is Police's Murder by Numbers... close enough...
This slowdown problem has to have something to do with memory usage as you said. I just connected my N900 to an amplifier at my home and left it playing music at 320kbit as long as it can. It played duplicates, me skipping always when it did so. It didn't actually play a very long time, about 45mins perhaps. Then it stopped. When I opened my screenlock it opened straightaway showing that Qspot had crashed and had a system message in finnish language, my translation follows as: "Action temporarily prevented. Not enough memory."
And another problem that still occurs is when I log in to Qspot, I first have the message "Loading playlists" and then followed by "Timeout occured while loading playlists!". Qspot showing only some of my playlists.
|
|
2010-11-08
, 17:10
|
|
Posts: 564 |
Thanked: 693 times |
Joined on Apr 2010
|
#330
|
First, thank you very much for your long and detailed reply.. It always helps when trying to find the cause of a problem. It should (from an implementation point of view) be the same thing playing one long track, as playing several different ones in a row. I will, however, try with a long playlist to see if there is some difference. It is very likely that the problem you are experiencing is related to memory usage, as the underlying library at the moment delivers uncompressed audio data, which is buffered by QSpot. If also swap memory has to be utilized it will impact device performance. I will need to look into possible solutions to how buffering could be improved in this respect.
The problem you described with shuffle playback definitely seems like a bug; I will look into fixing it in the next version (which is very close now). I am myself using shuffle playback very rarely, so therefore I have not detected it.
The problem with playlist loading seems to be at Spotify's end (and in my case, the problem is mostly related to shared / collaborative playlists). When I have experience loading problems and timeout, I have also experienced the same problem with other clients such as yaspot and footify.
It always helps when trying to find the cause of a problem. It should (from an implementation point of view) be the same thing playing one long track, as playing several different ones in a row. I will, however, try with a long playlist to see if there is some difference. It is very likely that the problem you are experiencing is related to memory usage, as the underlying library at the moment delivers uncompressed audio data, which is buffered by QSpot. If also swap memory has to be utilized it will impact device performance. I will need to look into possible solutions to how buffering could be improved in this respect. The problem you described with shuffle playback definitely seems like a bug; I will look into fixing it in the next version (which is very close now). I am myself using shuffle playback very rarely, so therefore I have not detected it.
The problem with playlist loading seems to be at Spotify's end (and in my case, the problem is mostly related to shared / collaborative playlists). When I have experience loading problems and timeout, I have also experienced the same problem with other clients such as yaspot and footify.
Originally Posted by Nozu
Using latest 0.1.0-7. I haven't changed the default buffer size so it must be the 30secs. I use 160kbit when on the move and 320kbit when at home. I'm using PR1.3.
It's not about playing one long track. I'm playing mostly my "misc" playlist with shuffle enabled. I have 195 tracks on that playlist at the moment. When I begin listening to the playlist and I put on the device's screenlock and open the screenlock right after, there's no delay. If I let it play couple of songs and then try to open screenlock I might need to wait couple of seconds. If I wait long enough I won't be able to open my device at all, it's so jammed.
I also have the same problem as someone else earlier mentioned. When playing my "misc" playlist with shuffle, the player might start exactly the same song again which just played but show the "next" song as playing song. If I press skip then it will start playing the song that previously was showed in the album art etc. and again there's the album art and song name of the "next" song displayed. Whoah, difficult explanation... I just listened to Madonna's Love Don't Live Here Anymore at the same time Qspot telling me that the playing song is Police's Murder by Numbers... close enough...
This slowdown problem has to have something to do with memory usage as you said. I just connected my N900 to an amplifier at my home and left it playing music at 320kbit as long as it can. It played duplicates, me skipping always when it did so. It didn't actually play a very long time, about 45mins perhaps. Then it stopped. When I opened my screenlock it opened straightaway showing that Qspot had crashed and had a system message in finnish language, my translation follows as: "Action temporarily prevented. Not enough memory."
And another problem that still occurs is when I log in to Qspot, I first have the message "Loading playlists" and then followed by "Timeout occured while loading playlists!". Qspot showing only some of my playlists.
| The Following User Says Thank You to aenbacka For This Useful Post: | ||
 |
| Tags |
| premium account, spotify |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 00:48.