Active Topics

 



Notices
Page 43 of 112 « First 334142 43 444553 Last »
Reply
Thread Tools
aenbacka is offline aenbacka
2011-01-04 , 07:07
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#421
Originally Posted by punto View Post
What is the implication of changing audio to Mafw (apart from enabling volume control when screen locked)?

I find the N900 audio frustratingly obtuse at times, although it appears to be very powerful on paper. High-bitrate FLACs sound 'off' although they play, there appears to be distortion in Media Player audio at times, and there's occasional channel-swapping (once again in Media Player) for what appears to be no good reason - which also affects QSpot.
As Mafw is the native multimedia framework used by Maemo 5, using it would allow QSpot to integrate as closely as possible with it (instead of using the pulseaudio backend directly, which is the case currently; however also Mafw uses pulseaudio in the background). Switching to Mafw will require significant changes to the QSpot implementation, but such a change could be considered at some point.

I have also noted distortions in audio now and then, and it seems that it is related to the current pulseaudio implementation; I also somehow think that the distortion has slightly increased in PR1.3.
 

The Following User Says Thank You to aenbacka For This Useful Post:
Nozu is offline Nozu
2011-01-04 , 09:23
Posts: 75 | Thanked: 27 times | Joined on Dec 2009
#422
I tried the new version of Qspot (and the new libopenspotify) the other day, but unfortunately the device still becomes sluggish very quickly (it's noticeable after 3-4 songs) and I get the system message: "Action temporarily prevented. Not enough memory." eventually. Xterm doesn't show anything abnormal in the output.
 
aenbacka is offline aenbacka
2011-01-04 , 10:02
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#423
Originally Posted by Nozu View Post
I tried the new version of Qspot (and the new libopenspotify) the other day, but unfortunately the device still becomes sluggish very quickly (it's noticeable after 3-4 songs) and I get the system message: "Action temporarily prevented. Not enough memory." eventually. Xterm doesn't show anything abnormal in the output.
That is very strange, as the fix should definitely have an impact on the problem; what bitrate have you been using when the device becomes sluggish after 3-4 songs? And do you get the error message at the same time, or at what point? What is the average duration of the tracks that you usually have played? Also output from top would be useful to see what is the situation when device is not responding.
Last edited by aenbacka; 2011-01-04 at 10:06.
 
Nozu is offline Nozu
2011-01-04 , 10:06
Posts: 75 | Thanked: 27 times | Joined on Dec 2009
#424
Originally Posted by aenbacka View Post
That is very strange, as the fix should definitely have an impact on the problem; what bitrate have you been using when the device becomes sluggish after 3-4 songs? And do you get the error message at the same time, or at what point? What is the average duration of the tracks that you usually have played? Also output from top would be useful to what is the situation when device is not responding.
I've been using a lot of 320kbit. The error message comes later, maybe after an album full of songs. The duration of songs are pretty average 4 min songs I'd say. I'll have to look into the top output next time!
 

The Following User Says Thank You to Nozu For This Useful Post:
aenbacka is offline aenbacka
2011-01-04 , 13:08
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#425
Originally Posted by Nozu View Post
I've been using a lot of 320kbit. The error message comes later, maybe after an album full of songs. The duration of songs are pretty average 4 min songs I'd say. I'll have to look into the top output next time!
I still want to verify that you are using default buffer size (30secs) and over wifi? I just tried playback of an album using high bitrate 320kbps without noticing any responsiveness issues. Could something like kernel version / settings have any impact (you wrote in an earlier post that you are using the power kernel)?
 
punto is offline punto
2011-01-05 , 01:36
Posts: 182 | Thanked: 40 times | Joined on Apr 2010
#426
Is there a tip jar by the way?
 
aenbacka is offline aenbacka
2011-01-05 , 07:33
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#427
Originally Posted by punto View Post
Is there a tip jar by the way?
Actually a tip jar is not available, I am working on this project as I enjoy it very much, and I want to contribute something to this amazing community.. And all the feedback that I get on QSpot is indeed very valuable in itself. So thank you all once again!
 
aenbacka is offline aenbacka
2011-01-05 , 07:39
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#428
I have now promoted QSpot version 0.2.1-1 to extras-testing; feel free to vote for it at the package page http://maemo.org/packages/package_in...qspot/0.2.1-1/.

Also, the library is now actively being worked on to fix the most severe issues..
 

The Following 4 Users Say Thank You to aenbacka For This Useful Post:
aenbacka is offline aenbacka
2011-01-08 , 14:04
Posts: 564 | Thanked: 693 times | Joined on Apr 2010
#429
Just wanted to inform that QSpot related announcements can now be followed on Twitter (@QSpotN900) as well.. My personal Twitter account is @aenbacka.
 

The Following 3 Users Say Thank You to aenbacka For This Useful Post:
Nozu is offline Nozu
2011-01-10 , 09:52
Posts: 75 | Thanked: 27 times | Joined on Dec 2009
#430
Originally Posted by aenbacka View Post
I still want to verify that you are using default buffer size (30secs) and over wifi? I just tried playback of an album using high bitrate 320kbps without noticing any responsiveness issues. Could something like kernel version / settings have any impact (you wrote in an earlier post that you are using the power kernel)?
I've been using 300secs buffer size as I recall you mentioned using and I've almost always used 3g. I do use the power kernel and swappolube and they may cause the problem. I decided to remove the swappolube config file and so resetting the swaps to device default and setting the buffer to default 30secs and gave Qspot a try. This time I didn't notice any device slowdown that would bother, I still received a memory error but it was after I had played over 3 standard albums of music. Here's a screenshot of top taken right after the memory error. Have to test more when I have time.
Attached Images
 
 

The Following User Says Thank You to Nozu For This Useful Post:
Reply
Page 43 of 112 « First 334142 43 444553 Last »

Tags
premium account, spotify

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 13:41.

Contact Us - Home - Archive - Top