Bug 151330 - Amarok scrobbler support broken
Summary: Amarok scrobbler support broken
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: amarok
Version: 3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-16 23:39 UTC by Peter Lawler
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-03-17 09:14:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Lawler 2005-03-16 23:39:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
Scrobbler requirements are (iirc):
Track must be at least 30 seconds long
Track must play at least 50%

This build seems to submit immediately upon start of playback.

Version-Release number of selected component (if applicable):
amarok.i386 0:1.2.2-1

How reproducible:
Always

Steps to Reproduce:
1. Start amarok
2. Configure for scrobbler submission
3. Play track

  

Actual Results:  Indicator says track is submitted immediately

Expected Results:  Amarok should wait for at least 30 seconds, then for at least 50% of playback before submission.

Additional info:

Could this be related to bug 151329?

Comment 1 Aurelien Bompard 2005-03-17 09:14:47 UTC
The amarok devlopers are aware of the scrobbler specs :
http://bugs.kde.org/show_bug.cgi?id=94417
The limit seems to be 240 seconds, not 30.

Comment 2 Peter Lawler 2005-03-17 21:40:08 UTC
http://www.audioscrobbler.com/development/protocol.php is the full protocol
spec. I was getting 30 seconds confused with minimum track length for submission.

Either way, amarok should not immediately submit data.

Comment 3 Peter Lawler 2005-03-17 22:22:25 UTC
Work around for 151329 fixes this issue.


Note You need to log in before you can comment on or make changes to this bug.