View Issue Details

IDProjectCategoryView StatusLast Update
0012222Last.fm pluginScrobblingpublic2014-10-14 02:19
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version1.1.0 
Target Version1.1.0Fixed in Version1.1.0 
Summary0012222: Caching doesn't work correctly
DescriptionStatus doesn't indicate when tracks are being cached, and when a connection is re-enabled (so that cached tracks are released), the track status doesn't update correctly (apparently the cached tracks aren't submitted).

1 Play 4 tracks with last.fm enabled
--> Status shows Tracks played 4/70 (as expected)
2 Disconnect ethernet while track 5 continues playing, and continue playing track 6, 7
--> Tracks cached indicates 3 as expected.
--> Last.fm status indicator continues to show 'OK' even after refreshing!! Shouldn't it show e.g. "Disconnected. Caching tracks."
3 Reconnect ethernet while track 8 is playing. Wait for track 8 to complete
--> Tracks played: 5/71. Tracks cached: 0. i.e. the tracks that had been cached didn't bump up the Tracks Played indicator when they were removed from the cache!!
TagsNo tags attached.
Fixed in build36

Relationships

related to 0012092 closedpeke Service: Plugin Options should show service status and statistics 

Activities

peke

2014-10-08 21:01

developer   ~0040740

Fixed in 35

1. It should correctly add to total scrobbled tracks.

2. As it can't determine exactly why it can't scrobble (last.fm do not return enough info) it shows "Caching tracks" whenever plugin cache track

rusty

2014-10-12 06:04

administrator   ~0040751

Tested build 35 and:

1. The total scrobbled tracks is updated correctly. However, the tracks scrobbled for the current session isn't updated correctly. i.e.
Tracks scrobbled: x/y
y is now correct, but x still isn't (after caching stops, y updates with the cached tracks, but x only increases by 1).

2. Caching tracks is spelled incorrectly (in the ui, it shows 'Cashing' with an _s_ )

peke

2014-10-13 00:45

developer   ~0040754

Fixed 2 in 36

Re 1. It is by design as Caching can't be calculated as actual scrobbling for session due the fact that tracks can be cached over number of MMW starts and thus it add only to total scrobbles.

rusty

2014-10-14 02:19

administrator   ~0040760

Verified 36.