| Summary: | amarok calculate score unwise (may be out of range). | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Valerian <asperezhigin> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 2.2.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
This only happens for tracks that show a length of 0 *** This bug has been marked as a duplicate of bug 207155 *** |
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}) )...