When is a scrobble a scrobble?A track should only be scrobbled when the following conditions have been met: The track must be longer than 30 seconds. And the track has been played for at least half its duration, or for 4 minutes (whichever occurs earlier.)
Last.fm already have their own guidelines in place which scrobbler authors are supposed to stick to. No matter how long a track is, you shouldn't have to listen for more than 4 minutes for it to count.
... blocking tracks from being scrobbled, based on tags ...
To keep proper track of feature requests:This plugin misses certain functionality from original one (blocking tracks from being scrobbled, based on tags). I added my own tag named "LFM_BLOCKED" and when it has value "1" or "yes" tracks are not scrobbled. Use case:On my PC there are ripped both my CDs and CDs of my wife. Sometimes I play her music for her from my account and honestly I don't want them to be counted on my LFM profile. Simple tag for all wife's CDs allowed me to achieve this.
I've made some tests and... I think it is bit vague how this plugin works. It seems that I can not rewind track to make it scrobbled - looks like only track of which 100% of its length is listened is scrobbled, while 50% should be enough accordingly to L.fm rules, even if rewind was used - as long as total time was more than 50% of track.
Plugin says that it scrobbles something (would be nice to have information which exactly track was send - its title - just to make it more clear) and it scrobbles everything, no matter if tags are present or not - and that was confusing for me and that's why I asked for adding special functionality. [...]
Quote from: EpicForever on 21 November, 2017, 11:47:08 AMI've made some tests and... I think it is bit vague how this plugin works. It seems that I can not rewind track to make it scrobbled - looks like only track of which 100% of its length is listened is scrobbled, while 50% should be enough accordingly to L.fm rules, even if rewind was used - as long as total time was more than 50% of track. I cannot reproduce that. It tracks the total time the track has been played, regardless of any seeks (Same as foo_audioscrobbler).(...)
OK, but it seems that foo_scrobble plugin requires that total tracked time is at least 100% length of the track. As far as I remember from my experiments foo_audioscrobbler was simply sending scrobble after half of this time was achieved. So I could listen to 20% of the song, then skip next 30% with seekbar AND on 80% of track length, track was scrobbled. And I could advance to next track at let's say - 82%. Still 50% was achieved (in 2 parts - 20% + 32% ) and everything was in accordance with the rules. In foo_scrobble, when I omit just 5% of the track - there is no scrobble. I haven't checked if I can search back and forth and scrobble is done if total listening time sums up to at least 100%. But it does not matter if scrobble should be sent after 50% (or after 4 minutes, whichever occurs first - as mentioned by marc2003).
I've added a new release that allows skipping tracks based on a titleformat script and adds a mainmenu command to toggle scrobbling.
I've not tested this yet but given it has dialogs for artist/title title formatting, it should support not submitting based on tags like the old component. Just make sure the value is blank if a certain condition is met and then the component should either not submit or last.fm will refuse the submission because of bad parameters. For example...Code: [Select]$ifequal(%rating%,1,,%artist%)
foo_scrobble: Requesting auth tokenfoo_scrobble: Failed to get auth token. (error: -2, <unknown error>)
Trying to request authorization:foo_scrobble: Requesting auth tokenfoo_scrobble: Failed to get auth token. (error: -2, <unknown error>)Nothing is happening in my browser either.
I installed this plugin on my work machine. Turns out that for some reason, IT blocks the API request call (I can't explain why Chrome doesn't even open though). Anyway, I switched my wifi to a guest account that for some reason is unblocked, and now I was able to authorize and everything is working perfectly again.