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.
Topic: Playback Statistics component: v3.x foo_playcount (Read 252165 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Playback Statistics component: v3.x foo_playcount

Reply #475 –
Hello Peter Pawlowski, I have long wanted to thank You for such a grand/amazing program as/how Foobar2000. Thank(s) You. By this plugin to me questions. How can lift the rating in this plugin to 9? And read please reply #472.

Re: Playback Statistics component: v3.x foo_playcount

Reply #476 –
I don't know if Peter understands reply #472. It certainly doesn't make sense to me. But if it's related to your attempts to abuse shell links (*.lnk file) the issue will be solved by using proper method to duplicate tracks.

I don't see the rating scale changing. It would break compability and 0-5 scale is pretty universal. Though modern online world seems to have moved to just "thumbs up" or "thumbs down" rating.

Re: Playback Statistics component: v3.x foo_playcount

Reply #477 –
But me need 0-9 or 0-10 scale. And me more convenient to watch rating by stars. I also want files to be duplicated according by rating (or scale).

Re: Playback Statistics component: v3.x foo_playcount

Reply #478 –
%added% show nothing(N/A). I have this components from Feb 2024 and added many tracks. Tried with new portable v2.1.5, tried v1.6.18... same result. Maybe I miss something but cant find what. Tried with MP4, MP3, FLAC files.

Here is picture from new foobar2000(v2.1.5) portable installation and Column UI. Maybe Why "Show recently played" and "Show recently added" are in gray?  ::) (example to show you only %added% show nothing, while %play_count% works fine)

Re: Playback Statistics component: v3.x foo_playcount

Reply #479 –
For %added% to work, you must configure the Media Library (Preferences>Media Library) to watch your music folder(s). I can tell you've not set it up because of those grayed out items on your Library menu.

Re: Playback Statistics component: v3.x foo_playcount

Reply #480 –
The clickable star Rating column returns the %rating_stars_fixed% format once a rating has been assigned. Is it possible to return the %rating_stars% format rather than %rating_stars_fixed%?

Re: Playback Statistics component: v3.x foo_playcount

Reply #481 –
Quote from: orchid on
Are there any plans to add options for update timing (eg. update after x seconds/percentage has been played)?
Am I right in understanding that the Playback Statistics 3.1.5 component (foo_playcount) still does not support the ability to specify a percentage, above which the track's play count will be increased by one? At the moment, it seems to be not a fixed percentage of the track's duration, but the playback duration. Because in my case the counter increased at values ​​of ~60% and ~80% (in the case when I swept to the middle of the track to forcefully increase the counter).

I would really like to have this function, because the Playback Statistics Custom (foo playback custom) method, which modifies the original file, does not suit me.

Re: Playback Statistics component: v3.x foo_playcount

Reply #482 –
Could you add the ability to change when a song's play count is updated?

Re: Playback Statistics component: v3.x foo_playcount

Reply #483 –
Quote
the Playback Statistics 3.1.5 component (foo_playcount) still does not support the ability to specify a percentage, above which the track's play count will be increased by one? At the moment, it seems to be not a fixed percentage of the track's duration, but the playback duration. Because in my case the counter increased at values ​​of ~60% and ~80% (in the case when I swept to the middle of the track to forcefully increase the counter).
For me too it would be very useful to set the percentage.
I need to check audio tracks that have no defects, and it is important for me to know if I have listened to them until the end.
For this I used the old foo_navigator: I had it set to 98% copy the track to another playlist.
Now I have to keep an old edition of foobar2000 for this purpose only.

Re: Playback Statistics component: v3.x foo_playcount

Reply #484 –
Is there a field that gets updated as soon as song starts playing? %last_played% gets updated only one minute into the song. I need to maintain stats of tracks that I encounter or play as soon as it gets played.

Re: Playback Statistics component: v3.x foo_playcount

Reply #485 –
Hello folks,

I noticed some odd behavior on my system.
I am using playback statistics foo_playcount v3.1.5.

Refer to the animated gif below.
  • I am adjusting rating on playlist item #85 (Melissa Janssen)
  • Very wierdly playlist item #83 (Alivia Penalva) also gets adjusted simultaneously.
  • I can confirm they are two very different FLAC files



Does anyone know why this is happening? Any idea how to fix it?
(this issue only affects that particular pair)

.

Re: Playback Statistics component: v3.x foo_playcount

Reply #486 –
Quote from: thevudia14 on
Is there a field that gets updated as soon as song starts playing? %last_played% gets updated only one minute into the song. I need to maintain stats of tracks that I encounter or play as soon as it gets played.
Might have to use Playcount 2003 for that instead (be sure to read the instructions to decide first how to bind stats, since changing it afterwards resets everything)

Quote from: boxerfan88 on
Does anyone know why this is happening? Any idea how to fix it?
(this issue only affects that particular pair)
They must have the same combination of tags. The original component binds the stats to tags like it says in the docs. It says it looks at %artist% though I'm not sure if %album artist% is prioritized.

One hacky way to get around that is to insert a hair space or zero width space to the %title% field of one track, which makes the tags different (so different stats) but looks the same. (Just be careful with zero width space to remember you added it since you'll never see it highlighted when selecting text. And note this might interfere with online internet look-ups, like lyrics or biography info - if so you can $replace the space away in search settings) -

Code: [Select]
$replace(%title%,$char(8203),)

...which is a bit of workaround just for one track. In any case, I use this method just to separate %album% fields for a few duplicate / deluxe edition albums.

Re: Playback Statistics component: v3.x foo_playcount

Reply #487 –
Quote from: anamorphic on
Quote from: boxerfan88 on
Does anyone know why this is happening? Any idea how to fix it?
(this issue only affects that particular pair)
They must have the same combination of tags. The original component binds the stats to tags like it says in the docs. It says it looks at %artist% though I'm not sure if %album artist% is prioritized.

One hacky way to get around that is to insert a hair space or zero width space to the %title% field of one track, which makes the tags different (so different stats) but looks the same. (Just be careful with zero width space to remember you added it since you'll never see it highlighted when selecting text. And note this might interfere with online internet look-ups, like lyrics or biography info - if so you can $replace the space away in search settings) -

Thank you for the tip. I added a <space> at the end of the title for one of the track, and it de-linked it. Thanks for the workaround.

What I find odd is that the docs says that artist is one of the parameter used for pinning (I guess some sort of hash or key). The two tracks that I showed definitely had artist name very very different, therefore should not yield an identical hash or key. I wonder if there is an inherent bug ... hmm ...

Re: Playback Statistics component: v3.x foo_playcount

Reply #488 –
Pretty sure it's a hash collision, which is not really a bug but just bad luck. Unless you think that using too few bits for the hash is a bug.

Re: Playback Statistics component: v3.x foo_playcount

Reply #489 –
Quote from: Case on
Pretty sure it's a hash collision, which is not really a bug but just bad luck.

Okay, thanks for confirming my hunch.

Quote
Unless you think that using too few bits for the hash is a bug.

Oh well, to me it is, because the artist name was totally different.
(If the artist name was only very slightly different, I could accept it as bad luck.)

Anyways, here goes my enhancement request to the component author to consider increasing the hash size so as to reduce the chances of hash collision (factor in more bits of the artist name).  :)

.
 

Re: Playback Statistics component: v3.x foo_playcount

Reply #490 –
Additionally, if that's really what's going on, the component could provide a tool to output any tracks from library which share the same hash and different tags. That would greatly help, since at least the user could know which ones are problematic and edit their tags in some way to avoid it.

I mean, if the current hashing method has conflicts in real libraries, then there is no easy way to notice if there is a collision in a 300k library unless you find it by chance, which is totally undesirable.