Bug 226752 - amarok calculate score unwise (may be out of range).
Summary: amarok calculate score unwise (may be out of range).
Status: RESOLVED DUPLICATE of bug 207155
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.2.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 01:41 UTC by Valerian
Modified: 2010-02-14 10:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Valerian 2010-02-14 01:41:17 UTC 
Version:           2.2.2 (using KDE 4.3.4)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Length:0:00
Bit rate:Unknown
Sample rate:0
Size:8,2 MiB
Format:mp3

Score:-1073740000
Rating:2
Play Count:1
First Played:14.02.10
Last Played:14.02.10
Collection:Local Collection

yet, this is a good mp3 file (it even can be played by amarok! also amarok ignore all tags...{sadly}).

i have some files with scores like this.
think this is associated with wrong file info recognition (i fully rescan collection and restart A-k just in case).
i interrupt this file.
another similar file played till the end got 50 (first time played).
still have some similar files to rate (never played).

think negatve score values is bad, yet more sophisticated calculation mechanism will pleasure me more (i have many files with inadequate score (for ex. =0) and big playcount (were another amarok errors ...{sadly}). i thought scores will be back in no time, but they are still inaccurate (rigid for good files...{sadly}) )...
Comment 1 Myriam Schweingruber 2010-02-14 10:06:50 UTC 
This only happens for tracks that show a length of 0

*** This bug has been marked as a duplicate of bug 207155 ***