Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
2
General - (fb2k) / Re: Foobar2000 Wrapped
Last post by paregistrase -
Played times comes from enhanced playcount. I have zero idea what reset statistics does for specific tags or where it comes from.

Ok, is from the last.fm component.

It reset the statistic that record Playback Statistics v3.x (foo playcount). The one that Peter introduced in v2.

Is correct, the only tag from that one that i have are from the album I listen today, after the reset.
3
General - (fb2k) / Re: Foobar2000 Wrapped
Last post by regor -
Played times comes from enhanced playcount. I have zero idea what reset statistics does for specific tags or where it comes from.

EDIT: updated the repository with latest changes.
5
3rd Party Plugins - (fb2k) / Re: foo_skipcount (discussion)
Last post by regor -
By the way, is there some way to log automatic skips by foo_skip? Since they don't involve user intervention.

EDIT: about the previous post, the details panel does in fact show a %skip_times% but the tag is not available at other places or has another name.
6
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by Major_Tom -
Here you are:

Spoiler (click to show/hide)

Whatever you changed, I can't reproduce the strange behaviour with this debug version - switching back to the regular version, the wrong menus are back again
7
General - (fb2k) / Re: Foobar2000 Wrapped
Last post by paregistrase -
Since historical last.fm times are most likely to predate listens generated by foo_enhanced_playcount, I simply count all last.fm data up until the very first play recorded by the component. After that, I'd count component listens only.
That could do too, but then there are also situations where people is playing things on the mobile and therefore there would be also valid last.fm times posterior to first play on component.

It's fine for me to allow a bigger time window, but anyway this is just starting to be a last.fm quirk and how listens are scrobbled which is not something on my side. Will put a 30 secs window and it's done for me.

Below that, last.fm doesn't record the song, so seems safe....
8
General - (fb2k) / Re: Foobar2000 Wrapped
Last post by regor -
Since historical last.fm times are most likely to predate listens generated by foo_enhanced_playcount, I simply count all last.fm data up until the very first play recorded by the component. After that, I'd count component listens only.
That could do too, but then there could be situations where people play things on the phone and there would also be valid last.fm times posterior to first play by the component (if they are imported)

It's fine for me to allow a bigger time window, but anyway this is just starting to be a last.fm quirk and how listens are scrobbled which is not something on my side. Will put a 30 secs window and it's done for me.

EDIT: finally added support for foo_skipcount https://hydrogenaud.io/index.php/topic,124741
Right now is only used to calculate the score for a single character, the "hunter".:"You\'re always searching for new favorites. You skip tracks more than other listeners. Maybe it\'s the thrill of the chase?' "

But maybe there is also interest in adding skip stats to the report?
9
General - (fb2k) / Re: Foobar2000 Wrapped
Last post by marc2k3 -
Since historical last.fm times are most likely to predate listens generated by foo_enhanced_playcount, I simply count all last.fm data up until the very first play recorded by the component. After that, I'd count component listens only.
10
General - (fb2k) / Re: Foobar2000 Wrapped
Last post by paregistrase -
Ok, current algorithm will consider a duplicate any listen equal to another one within a 3 secs window.

It should only try to deduplicate when there are last.fm listens, otherwise it just considers all of them (and does not affect performance for other users).

Check the repository. Seems to work fine with an array of dates, check it with your library. (probably all your listening times will be halved)

Jesu - Falling From Grace
["2015-06-03 20:36:42", "2023-03-06 19:08:35", "2023-03-06 19:32:46", "2023-03-06 19:40:09"]  |||  ["2015-06-03 20:44:01", "2023-03-06 19:15:55", "2023-03-06 19:27:51", "2023-03-06 19:40:10"]

Ageless Oblivion - All Was Froze
["2023-05-20 09:01:43", "2023-05-20 09:09:44"]  |||  ["2023-05-20 09:01:53", "2023-05-20 09:09:47"]

Aviador Dro 4000 - Vivir Para Morir

["2023-02-10 14:42:28", "2023-04-25 13:50:59"]  |||  ["2023-02-10 14:42:40", "2023-04-25 13:51:00"]

There is some of them with 12 seconds
The totals have been cut a lot