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: version 3.0.1 (Read 200977 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Playback Statistics component: version 3.0.1

Reply #400
I have two questions:

1) Why does Playback Statistics convert a normal human timestamp into computerspeak when writing statistics to file tags? E.g.: 2017-06-02 21:36:22 becomes 131409273821466963.

2) Is there a simple way for a layman to convert a human timestamp into this computerspeak format?

Re: Playback Statistics component: version 3.0.1

Reply #401
@randal1013 , I'm not sure what you really need but working with these dates isn't complicated.

If for example you want to dispaly the 3 dates of Playback Statistics (added date,first played & last played) on the "Playlist View" of the Default UI :
$left(%added%,10)  $right(%added%,8)
$if(%first_played%,$left(%first_played%,10)  $right(%first_played%,8))
$if(%last_played%,$left(%last_played%,10)  $right(%last_played%,8))

Here's also an example of an auto-playlist for tracks added in the last 8 weeks :
%added% DURING LAST 8  WEEKS  SORT DESCENDING BY %added%

An example of an auto-playlist for tracks added in 2016 :
"$year(%added%)" EQUAL "2016" SORT DESCENDING BY %added%

Re: Playback Statistics component: version 3.0.1

Reply #402
I appreciate the fast response, but that's not what I'm asking. What I would like to know is how to convert a readable timestamp, like 2017-06-02 21:36:22, into the long string of numbers, like 131409273821466963, that foo_playcount apparently uses.

Re: Playback Statistics component: version 3.0.1

Reply #403
Actually nevermind, I found another way to do what I wanted.

Re: Playback Statistics component: version 3.0.1

Reply #404
Where are the stats info stored? In the .cfg file? Inside the index-data folder? I see there is another file now.

Thanks.

Re: Playback Statistics component: version 3.0.1

Reply #405
Well the component hasn't been updated in years so it will still be inside the index-data folder.

Re: Playback Statistics component: version 3.0.1

Reply #406
Perfect thanks, never knew about the component, I always used the player in extremely basic mode without even adding the library, I wanted to use it like adding CDs (folders) one by one like I used to do with the stereo but every now and then I was adding the library to test if I would change my mind on how to use it and I always kept a personalized full screen multi panel theme.

Re: Playback Statistics component: version 3.0.1

Reply #407
I'm using foo_playcount to write playstats directly to the audio-files , because my library keeps growing and a lot of it is becoming FLAC the "Automatically sync filetags with stats" is becoming unusable .. it can create huge lagtimes around the 1 minute mark from time to time. Even minor lag is really off-putting, obviously.

Is there any way I can fix this lag , without having to either rely on the database-file foo_playcount creates and adding playcount info to the files myself ?
I'm not really using it as a playcount stats per se, I'm using it more as a visual check to know whether I have played an audiotrack before or haven't. . .

As such:


I saw this config screenshot on some wiki, but I don't seem to have this? :

http://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components/Play_Count_(unofficial)_(foo_playcount)

Any help appreciated ! :) (I'm using foobar2000 default UI btw)

Re: Playback Statistics component: version 3.0.1

Reply #408
@Viniman, why are you still using the old v0.9.1 foobar2000 ?  :o
If you upgrade your foobar you'll be able to use Playback Statistic version 3 (was released on 2011-07-13). There's no lag time on version 3. Version 3 introduced new data pinning scheme :  "Playback statistics are now pinned to a combination of artist + album + disc number + track number + track title information, contrary to pre-3.0 versions which would pin data to file paths".
http://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components/Playback_Statistics_v3.x_(foo_playcount)

Re: Playback Statistics component: version 3.0.1

Reply #409
I am sure this question has been asked before, but I can't find the answer.  My PC crashed while Foobar was open and it seems the Payback statistics from that session were not saved.  Is there a way to recover the stats of what was played during that session?

Re: Playback Statistics component: version 3.0.1

Reply #410
foo_jesus is the only guaranteed way to keep stats for a session without user intervention. Otherwise, you'd need to manually trigger a configuration save periodically.

Re: Playback Statistics component: version 3.0.1

Reply #411
Is it possible to display an unrated track as blank instead of as a question mark?

Re: Playback Statistics component: version 3.0.1

Reply #412
Nevermind, I figured it out from an earlier post--just need to format as [%rating%].
Thanks for the plugin!

Re: Playback Statistics component: version 3.0.1

Reply #413
is it possible to offer a enhanced %played_per_day% to show  3 or 4 digits after the decimal point?
now  %played_per_day% shows only 2 digits is meaningless for most songs, as I have 10k songs with more than 10 years in library,
end up showing a lot meaningless 0.01 and 0.02

Download - version 3.0.1:
http://www.foobar2000.org/components/view/foo_playcount

Documentation:
http://wiki.hydrogenaudio.org/index.php?ti...oo_playcount%29

This component requires foobar2000 v1.1 or newer.

Changes since 3.0:
- No longer attempts to update tags on remote files or streams when playing.

Re: Playback Statistics component: version 3.0.1

Reply #414
Fun fact: for all its complexity, LDAP timestamp usage and whatnot... foo_playcount doesn't take account of daylight-saving/summer time changes!

It's mindboggling how this could get neglected considering ~70 countries observe DST, so I would really like to be wrong, but it looks like I'm not. I only discovered it by accident when my winter windows time didn't agree with foobar's timestamp.

I was CET (UTC+1) until March 30th, now I'm CEST (UTC+2). Foo_playcount thinks I'm constantly in summer time. Compare:

CET
  • Windows folder creation time: ‎30 ‎March ‎2019, ‏‎17:11:43
  • Foo_playcount %added%: 2019-03-30 18:11:43

CEST
  • Windows folder creation time: ‎‎31 ‎March ‎2019, ‏‎18:25:24
  • Foo_playcount %added%: 2019-03-31 18:25:25

And just the same with Last.fm (scrobbles at 50% but site displays playback start)

CET
  • Last.fm timestamp: 30 Mar 5:19pm
  • Foo_playcount %first_played%: 2019-03-30 18:20:33

CEST
  • Last.fm timestamp: 31 Mar 11:25am
  • Foo_playcount %first_played%: 2019-03-31 11:26:09

Re: Playback Statistics component: version 3.0.1

Reply #415
Is there a way to merge last.fm statistics with the database of this component?



Re: Playback Statistics component: version 3.0.1

Reply #418
@Peter  , it seems that you are using "album artist" tag and not the "artist" tag in somehow contrary to what is stated at the plugin documentation :
"Playback statistics are now pinned to a combination of artist + album + disc number + track number + track title information, contrary to pre-3.0 versions which would pin data to file paths."

BTW - [for those who forgot] When %album artist% is missing it returns the %artist% so the wording in the documentation is not so "wrong".

So here's my issue. Generally it's not so important (because usually when using "album artist" the different "title" & "track number" tags "help" to create a unique combination) but there's a case when the current combination can cause a problem.

Lately I decided to create some "cover" albums for some "classic" soul tracks and the "problem" occurred while creating them.
The last occasion the problem happened was today. I "collected" all my 13 covers of Michael Jackson's "I Wanna Be Where You Are".

I Updated all the tracks with:
"Title" - "I Wanna Be Where You Are (cover)"
"Album" - "I Wanna Be Where You Are (covers)"
"Album Artist" - Michael Jackson

Then suddenly while preparing the "track number" for the tracks of this album all of the tracks' statistics were overwritten by the statistics of one of them (the one I was listening to) !!
At that particular moment all the elements of the "combination" were exactly the same for these 13 tracks.
If the plugin was using "artist" instead of "album artist" it would not have happened.

So here's my request @Peter : Can you replace "album artist" with "artist" or maybe add "artist" to the combination ?
If you decide not to change the combination at least update the documentation.



If it is intended at least you should update the documentation which as of now states :
"Playback statistics are now pinned to a combination of artist + album + disc number + track number + track title information, contrary to pre-3.0 versions which would pin data to file paths."

http://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components/Playback_Statistics_v3.x_(foo_playcount)

Playback Statistics 3.0.3
foobar2000 1.5 beta 16
Win 7 x64

Thanks in advance.

Re: Playback Statistics component: version 3.0.1

Reply #419
since this update I've been getting "playback error file is in use" during writing sometimes. I assume this is because I have "automatically synchronize file tags with statistics (causes file tag rewrites during playback, disrecommended)" enabled. However, I've had that enabled for as long as it's existed and NEVER had a single problem until this update. (1.5). More importantly? Is this setting even needed? Like I said, I've had this enabled for however old this plug-in has had such a feature which I assume is nearly a decade now...

Re: Playback Statistics component: version 3.0.1

Reply #420
I just remembered there have been quite a few times where my playback data on files was randomly erased and importing from file tags was the only way I was able to get them back, so I guess I'm answering myself in saying that yes, rewriting during playback was very useful to me and I hope this new bug gets fixed. Literally a decade with zero playback interruption until Foobar 1.5. Clearly the issue lies there

Re: Playback Statistics component: version 3.0.1

Reply #421
Re "playback error: file is in use"
What's the complete error message you're getting?
What is written in foobar2000 console while the error occurs?
Where are your files located - local disk, removable disk, network share or other?
What file format are you listening to?
Full list of installed components?

A Process Monitor log of the failure would also be helpful, revealing exact order of file operations performed.
Microsoft Windows: We can't script here, this is bat country.

Re: Playback Statistics component: version 3.0.1

Reply #422
That was the entire error message that popped up. I didn't think to check console.
Files are (stupidly due to my storage issues but won't be an issue soon when I expand to 1 TB) located on the same SSD that Foobar is installed on. Fle formats are m4a, flac, and mp3. Same file types since the mid 00s.

I would love to grab a log of the issue. I read your post the day you posted it, but it's proven hard to reproduce the issue since it only seems to happen once every few hundred plays. I'll update with the rest of the proper information, I apologize for not being better prepared in my original posts - I originally only came to ask if the feature was needed before I remembered when it saved my playback stats due to the component randomly forgetting a few songs' playback stats. I'm playing the waiting game now it seems

But anyway, Happy holidays!

Re: Playback Statistics component: version 3.0.1

Reply #423
Finally happened again after a few hundred more plays. Unfortunately logs didn't seem to clear anything up. I didn't see any issues with ProcMon. Here's Foobar's own ( seemingly worthless) logs

Here's the one that got interrupted:

Quote
Opening track for playback: "C:\Users\[LOCATION] 02. Fluctuation.mp3"
Autosaving... (T)
Configuration saved in: 0:00.768731
Autobackup: Backed up 13579 items to autobackup.20191228-195731.zip
Decoding interrupted
Last.fm Playcount Sync: Automatically loving this track....
Last.fm Playcount Sync: Attempting to love "Fluctuation" by "岩崎琢"
Last.fm Playcount Sync: Contacting Last.fm....
Recovering from interrupt @ 0:42.593719
Decoding interrupted
Decoding failure at 1:02.368 (File is already in use):
"C:\Users\[LOCATION] 02. Fluctuation.mp3"

And here's a normal one of the same track:
Quote
Opening track for playback: "C:\Users\[LOCATION] 02. Fluctuation.mp3"
Autosaving... (T)
Configuration saved in: 0:00.283869
Autobackup: Backed up 13579 items to autobackup.20191228-201109.zip
Decoding interrupted
Last.fm Playcount Sync: Automatically loving this track....
Last.fm Playcount Sync: Attempting to love "Fluctuation" by "岩崎琢"
Last.fm Playcount Sync: Contacting Last.fm....
Recovering from interrupt @ 1:02.394535
Last.fm Playcount Sync: Contacting Last.fm....
Last.fm Playcount Sync: Last.fm responded ok. Attempting to update playcount...
Last.fm Playcount Sync: Playcount updated successfully.

The only difference I see is literally the message about it failing.

components are:

Code: [Select]
Core (2019-11-28 12:47:26 UTC)
    foobar2000 core 1.5
foo_abx.dll (2019-02-18 18:03:34 UTC)
    ABX Comparator 2.0.6c
foo_albumlist.dll (2019-11-28 12:46:52 UTC)
    Album List 4.7
foo_audioscrobbler.dll (2012-08-20 20:49:44 UTC)
    Audioscrobbler 2.3.1
foo_cad.dll (2013-06-04 02:54:44 UTC)
    CD Art Display 1.0.2
foo_cdda.dll (2019-11-28 12:46:48 UTC)
    CD Audio Decoder 3.0
foo_converter.dll (2019-11-28 12:46:44 UTC)
    Converter 1.5.4
foo_customdb.dll (2013-04-19 02:58:12 UTC)
    Custom Database 0.1.0_beta1
foo_discord_rich.dll (2019-05-23 20:19:30 UTC)
    Discord Rich Presense 1.1.0
foo_dop.dll (2008-09-29 01:01:00 UTC)
    iPod manager 0.6.3.0
foo_dsp_effect.dll (2019-02-18 18:03:34 UTC)
    Effect DSP 0.35
foo_dsp_eq.dll (2019-11-28 12:46:46 UTC)
    Equalizer 1.2.1
foo_dsp_std.dll (2019-11-28 12:46:34 UTC)
    Standard DSP Array 1.3.2
foo_facets.dll (2011-08-19 06:06:16 UTC)
    Facets 1.0
foo_httpcontrol.dll (2013-04-26 21:12:30 UTC)
    HTTP Control 0.97.14-fb2kc
foo_input_std.dll (2019-11-28 12:47:14 UTC)
    FFmpeg Decoders 3.4.6-0ac9001
    Standard Input Array 1.5
foo_input_tta.dll (2009-10-08 08:58:36 UTC)
    TTA Audio Decoder (unofficial) 2.4.2
foo_jesus.dll (2010-10-12 23:58:16 UTC)
    Autosave & Autobackup 10
foo_jscript_panel.dll (2016-03-14 21:44:19 UTC)
    JScript Panel 1.1.3
foo_keep_queue.dll (2014-02-09 09:12:20 UTC)
    Keep Queue 0.3.5
foo_lyricsgrabber2.dll (2011-04-27 20:09:26 UTC)
    Lyrics Grabber 2 0.5.5.2 beta
foo_osd.dll (2018-04-08 03:40:30 UTC)
    On-Screen Display 1.74
foo_playcount.dll (2019-12-07 08:25:08 UTC)
    Playback Statistics 3.0.3
foo_playlisthistory.dll (2011-06-06 19:50:22 UTC)
    Playlist History 0.1.6
foo_queuecontents.dll (2012-04-04 00:40:40 UTC)
    Queue Contents Editor 0.5.1
foo_rgscan.dll (2019-11-28 12:46:46 UTC)
    ReplayGain Scanner 2.3
foo_skype.dll (2011-05-22 04:33:24 UTC)
    Skype playing notifications 0.2
foo_softplaylists.dll (2014-02-10 08:51:40 UTC)
    Soft Playlists 2012-10-10
foo_stop_after_queue.dll (2019-02-18 18:03:34 UTC)
    Stop After Queue 1.1.1
foo_textdisplay.dll (2012-08-06 10:12:04 UTC)
    Text Display UI Element 1.1 beta 1
foo_texttools.dll (2011-05-05 22:21:06 UTC)
    Text Tools 1.0.5
foo_ui_columns.dll (2019-02-18 18:03:52 UTC)
    Columns UI 1.0.0
foo_ui_std.dll (2019-11-28 12:47:06 UTC)
    Default User Interface 1.5
foo_uie_biography.dll (2016-05-30 09:52:50 UTC)
    Biography View 0.4.2.5
foo_uie_lyrics3.dll (2016-05-05 18:13:36 UTC)
    Lyric Show Panel 3 0.5
foo_uie_wsh_panel_mod.dll (2013-04-19 01:58:00 UTC)
    WSH Panel Mod 1.5.6
foo_unpack.dll (2019-11-28 12:46:44 UTC)
    ZIP/GZIP/RAR Reader 1.8
foo_wave_seekbar.dll (2016-05-20 23:10:30 UTC)
    Waveform seekbar 0.2.45.4

Again, I've NEVER had this happen before update 1.5 for Foobar itself. But I don't know what could've happened "behind the scenes" that would've caused this to suddenly happen. I'll have to figure out how to revert to 1.4 without losing anything if this keeps happening

Edit: I didn't keep the log cuz it was like 20 GB for just a few minutes and for that same reason, I can't run ProcMon all the time. This issue is almost impossible for me to reproduce on purpose. I even tried turning my CPU to 100% usage (by simply opening Red Dead Redemption 2's Online mode which kills my i7 4770k) and still could not cause the issue even after several hours. I thought it was a CPU issue because I first noticed while playing RDO which as I said, uses 100% CPU but again I couldn't get it to happen on purpose, it just happens randomly even when using very little CPU like when I'm playing World of Tanks.

Re: Playback Statistics component: version 3.0.1

Reply #424
Thanks for the details.

Is it to be expected that the file is retagged twice during playback?
Microsoft Windows: We can't script here, this is bat country.