Welcome Guest! To enable all features please Register.

Notification

Icon
Error
Last.fm scrobbling not working
Options
Previous Topic Next Topic
rmstock Offline
#1 Posted : Wednesday, December 21, 2011 8:37:31 AM(UTC)
Rank: Newbie

Joined: 12/19/2011(UTC)
Posts: 2
Hi,

Any suggestions as to why Last.fm scrobbling is not working?

I'm playing tracks via Android. Last.fm shows that it is playing the track via Jamcast so the account details are correct. However once the track has completed does register on Last.fm as having been played.

This is a feature I would really like to see working!

Thanks & regards
Rob
Back to top
Scott Offline
#2 Posted : Sunday, December 25, 2011 10:28:26 AM(UTC)
Rank: Administration
Scott

Joined: 1/25/2009(UTC)
Posts: 1,615
Location: Orlando, FL, USA
rmstock;3640 wrote:
Hi,

Any suggestions as to why Last.fm scrobbling is not working?

I'm playing tracks via Android. Last.fm shows that it is playing the track via Jamcast so the account details are correct. However once the track has completed does register on Last.fm as having been played.

This is a feature I would really like to see working!

Thanks & regards
Rob

Hi Rob,

Thanks for checking out Jamcast! Sounds like communications are OK with the last.fm submission services... are you allowing tracks to play over 30 seconds (or more)?

The rule with scrobbling is that tracks that don't play for over 30 seconds should not be submitted. However, Jamcast can't determine how much you've listened to, best we can do is see that a minimal amount of data has been streamed to the device before submitting.

Try letting the tracks complete if you haven't already tried that. If you feel like you're already doing so, check medialog.txt (or paste it here if you like), that's where we log last.fm related issues. The logfiles are located in the Jamcast installation directory.

And if it's a bug, we'll fix it in a jiffy. Smile

Thanks!
Scott
Jamcast Technical Support
Docs: http://www.sdstechnologies.com/Wiki/
Back to top
WWW BLOG
rmstock Offline
#3 Posted : Friday, January 13, 2012 8:48:09 AM(UTC)
Rank: Newbie

Joined: 12/19/2011(UTC)
Posts: 2

Hi Scott,

I've been allowing tracks to play all the way through.

I've just done a test by restarting Jamcast server and then playing one track all the way through via my Android phone. As per my original post, it initially shows in Last.fm as currently listening to but once the track has completed and I refresh Last.fm then it no longer shows.

Below are the entries from medialog.txt. There does not appear to be any references to Last.fm although I'm not sure what I'm looking for (other than the obvious).

Is the scrobbling done at the server end or the phone? I've successfully scrobbled via Spotify & Windows Media player from the PC running Jamcast. I've also successfully scrobbled from my phone via Spotify & Last.fm app in the past.

Regards
Rob

01/13/2012 13:35:26 Startup v1.7.0.175 (Microsoft Windows NT 6.0.6002 Service Pack 2)...
01/13/2012 13:35:28 Starting network services on [unknown hostname] @ 192.168.0.4:58642...
01/13/2012 13:35:28 The media server started successfully on [unknown hostname] @ 192.168.0.4:58642
01/13/2012 13:36:35 HTTP/1.1 GET request: /Media/image/jpeg/AlbumArt/106/150 USER-AGENT: Android/2.3.3, UPnP/1.0, JamcastPlayer/0.9.4, USN: uuid:ad85391b-d111-48e1-abfc-16704e211f77, Host: 192.168.0.4:58642, Connection: Keep-Alive
01/13/2012 13:36:35 Media stream pipeline: .mp3 File -> Image Resizer -> Android Device @ 192.168.0.5
01/13/2012 13:36:35 Response: Server: Windows NT/6.0, UPnP/1.0, Jamcast/1.7, Date: Fri, 13 Jan 2012 13:36:35 GMT, Content-Type: image/jpeg, Accept-Ranges: none
01/13/2012 13:36:35 Begin streaming to Android Device @ 192.168.0.5...
01/13/2012 13:36:35 I/O stats for .mp3 File: queue=0 reads=310,760 totalreadbytes=9,156 readsnodata=310,758 writes=2 totalwritebytes=9,156 writesempty=2 writesfull=0 maxbytes=8,192
01/13/2012 13:36:35 I/O stats for Image Resizer: queue=0 reads=5 totalreadbytes=5,833 readsnodata=4 writes=1 totalwritebytes=5,833 writesempty=1 writesfull=0 maxbytes=5,833
01/13/2012 13:36:35 Network send stats: bytes=5,833 sleeps=3
01/13/2012 13:36:35 Streaming to Android Device (192.168.0.5) completed.
01/13/2012 13:36:48 HTTP/1.1 GET request: /Media/audio/mpeg/Track/1328 Range: bytes=0-, Host: 192.168.0.4:58642, Accept: */*, User-Agent: Android/2.3.3, UPnP/1.0, JamcastPlayer/0.9.4, USN: uuid:ad85391b-d111-48e1-abfc-16704e211f77, Cache-Control: no-cache, Connection: Close
01/13/2012 13:36:48 Request received from Android Device (192.168.0.5):
Source format: audio/mpeg 128kbps 16-bit 44100 Hz 2 channels
Output format: audio/mpeg 128kbps 16-bit 44100 Hz 2 channels
01/13/2012 13:36:48 Media stream pipeline: .mp3 File -> Android Device @ 192.168.0.5
01/13/2012 13:36:48 Response: Server: Windows NT/6.0, UPnP/1.0, Jamcast/1.7, Date: Fri, 13 Jan 2012 13:36:48 GMT, Content-Type: audio/mpeg, Content-Length: 2548299, Accept-Ranges: bytes, Content-Range: bytes 0-2548298/2548299
01/13/2012 13:36:48 Begin streaming to Android Device @ 192.168.0.5...
01/13/2012 13:36:48 HTTP/1.1 GET request: /Media/image/jpeg/EmbeddedImage/1328/72 USER-AGENT: Android/2.3.3, UPnP/1.0, JamcastPlayer/0.9.4, USN: uuid:ad85391b-d111-48e1-abfc-16704e211f77, Host: 192.168.0.4:58642, Connection: Keep-Alive
01/13/2012 13:36:48 Media stream pipeline: .mp3 File -> Image Resizer -> Android Device @ 192.168.0.5
01/13/2012 13:36:48 Response: Server: Windows NT/6.0, UPnP/1.0, Jamcast/1.7, Date: Fri, 13 Jan 2012 13:36:48 GMT, Content-Type: image/jpeg, Accept-Ranges: none
01/13/2012 13:36:48 Begin streaming to Android Device @ 192.168.0.5...
01/13/2012 13:36:48 I/O stats for .mp3 File: queue=0 reads=21,619 totalreadbytes=9,156 readsnodata=21,617 writes=2 totalwritebytes=9,156 writesempty=2 writesfull=0 maxbytes=8,192
01/13/2012 13:36:48 I/O stats for Image Resizer: queue=0 reads=4 totalreadbytes=2,128 readsnodata=3 writes=1 totalwritebytes=2,128 writesempty=1 writesfull=0 maxbytes=2,128
01/13/2012 13:36:48 Network send stats: bytes=2,128 sleeps=2
01/13/2012 13:36:48 Streaming to Android Device (192.168.0.5) completed.
01/13/2012 13:36:48 HTTP/1.1 GET request: /Media/image/jpeg/EmbeddedImage/1328 USER-AGENT: Android/2.3.3, UPnP/1.0, JamcastPlayer/0.9.4, USN: uuid:ad85391b-d111-48e1-abfc-16704e211f77, Host: 192.168.0.4:58642, Connection: Keep-Alive
01/13/2012 13:36:49 Media stream pipeline: .mp3 File -> Android Device @ 192.168.0.5
01/13/2012 13:36:49 Response: Server: Windows NT/6.0, UPnP/1.0, Jamcast/1.7, Date: Fri, 13 Jan 2012 13:36:48 GMT, Content-Type: image/jpeg, Content-Length: 9156, Accept-Ranges: none
01/13/2012 13:36:49 Begin streaming to Android Device @ 192.168.0.5...
01/13/2012 13:36:49 I/O stats for .mp3 File: queue=0 reads=4 totalreadbytes=9,156 readsnodata=2 writes=2 totalwritebytes=9,156 writesempty=1 writesfull=0 maxbytes=9,156
01/13/2012 13:36:50 Network send stats: bytes=9,156 sleeps=1
01/13/2012 13:36:50 Streaming to Android Device (192.168.0.5) completed.
01/13/2012 13:36:59 HTTP/1.1 GET request: /Media/image/jpeg/AlbumArt/106/150 USER-AGENT: Android/2.3.3, UPnP/1.0, JamcastPlayer/0.9.4, USN: uuid:ad85391b-d111-48e1-abfc-16704e211f77, Host: 192.168.0.4:58642, Connection: Keep-Alive
01/13/2012 13:36:59 Media stream pipeline: .mp3 File -> Image Resizer -> Android Device @ 192.168.0.5
01/13/2012 13:36:59 Response: Server: Windows NT/6.0, UPnP/1.0, Jamcast/1.7, Date: Fri, 13 Jan 2012 13:36:59 GMT, Content-Type: image/jpeg, Accept-Ranges: none
01/13/2012 13:36:59 Begin streaming to Android Device @ 192.168.0.5...
01/13/2012 13:36:59 I/O stats for .mp3 File: queue=0 reads=49,782 totalreadbytes=9,156 readsnodata=49,780 writes=2 totalwritebytes=9,156 writesempty=2 writesfull=0 maxbytes=8,192
01/13/2012 13:36:59 I/O stats for Image Resizer: queue=0 reads=3 totalreadbytes=5,833 readsnodata=2 writes=1 totalwritebytes=5,833 writesempty=1 writesfull=0 maxbytes=5,833
01/13/2012 13:36:59 Network send stats: bytes=5,833 sleeps=1
01/13/2012 13:36:59 Streaming to Android Device (192.168.0.5) completed.
01/13/2012 13:39:09 I/O stats for .mp3 File: queue=0 reads=317 totalreadbytes=2,548,299 readsnodata=5 writes=312 totalwritebytes=2,548,299 writesempty=1 writesfull=117 maxbytes=262,144
01/13/2012 13:39:09 Network send stats: bytes=2,548,299 sleeps=4
01/13/2012 13:39:09 Streaming to Android Device (192.168.0.5) completed.
Back to top
Scott Offline
#4 Posted : Wednesday, February 08, 2012 10:11:09 AM(UTC)
Rank: Administration
Scott

Joined: 1/25/2009(UTC)
Posts: 1,615
Location: Orlando, FL, USA
Hi Rob,

Thanks for your patience on this. last.fm scrobbling has been fixed in 1.7.5 (now available), indeed it was broken in 1.7.0. I appreciate you bringing this to my attention.

Thanks!
Scott
Jamcast Technical Support
Docs: http://www.sdstechnologies.com/Wiki/
Back to top
WWW BLOG
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.162 seconds.