Foobar2000:Components 0.9/Playback Statistics Custom (foo playback custom)
This component stores playback statistics (play count, first played date, last played date) in a tag like foo_playcount_mod, but has a faster response time. If the component is unable to write a tag, you can have it write the information into the custom_info database (this requires you to have foo_custominfo installed).
- Writes playback statistics (play_counter, first_played, last_played) in tags
- Allows you to select which information to be written
- Allows you to select the tags where the information is to be stored: only in the tag, only in the custominfo database or in custominfo database only if tag cannot be written.
- Allows you to select when the information is updated (when the song starts playing, when it has finished etc).
Note: All of the following can be changed
- Default tag name for play count: %play_counter%
- Default tag name for first played: %first_played%
- Default tag name for last played: %last_played%
- format of first played and last played is: YYYY-MM-DD HH:MM:SS
- Update playback statistics: when song has been played for 60 seconds
Copy the foo_playback_custom to foobar2000's components directory. Restart foobar.
- . Run foobar2000
- . Check to see that foo_playback_custom is installed by going to Preferences -> Components. Also, check to see if you are using the latest version
- . Go to Preferences -> Tools -> Playback Statistics Custom
Playback Statistics Update Timing
This option allow you to change when the plugin updates information:
- Disable (Do not update)
- Update when a track is started
- Update when a track is ended
- Update when playback percentage is
You can select a value between 1% and 99%
- Update counter when playback second(s) is:
You can set any value greater than 1 second
Playback statistics settings
- Use the dropdown menu to select where you would like to store the information:
- 'only tag': this option will write the information into the song's tag.
- 'only foo_custominfo database': this option will write the information into the foo_custominfo database. You need the foo_custominfo component to be installed.
- 'tag and foo_custominfo...': this option will write the information to the song's tag whenever possible, if it is unable to do so (e.g. format does not support tagging -> wav), then the information will be stored in foo_custominfo.
Which option should i choose? Writing tags in information means that the information will always be present regardless of whether you rename or move the file. However, when you back up your collection even a single change in tag will register as a file change and will result in the backup program copying the entire file again. if you play lots of music, you could easily be forced to copy a lot of (otherwise unchanged) music needlessly. Also, writing the tag will change the file's MD5 signature, which will wreak havoc if you're using MD5 to verify your files. Foo_custominfo database option avoids the need to write the tags in the file, so you don't have the backup or the MD5 problem. However, foo_custominfo information is lost when you rename/move the file, and the options aren't acccessible through masstagger/properties window. The third option is a compromise between the two, however requires the foo_custominfo component to be installed. So it's not justified for people who don't use wav/wma files very often..
- Use the checkboxes to select which tags you want to write
- If you want to use a different tag to store the information (e.g. Play_Count instead of Play_counter), type Play_count in the box next to the tag and press the apply button.
- Only Tracks in media library update playback statistics
If selected, no information will be written to songs that are not in the media library
- Store playback statistics with foo_custominfo database...
If selected, the component will write information to custominfo database if it fails to write a tag. NOTE: foo_custominfo has to be installed.
Q. I get a popup window when playback statistics is being updated. Is this normal?
A. Normally, the window shouldn't appear while using the component. it only appears when I/O processing time while writing the tag is long. The track might also stop playing.
- While playing losssless files (e.g. Flac, APE, Wavpack, TAK) which are highly compressed, IO processing time can be long
- Another component is trying to update the file information at the same time
- Your Hard drive is slow/ fragmented
- Use a lower compressed lossless file
- Try changing the update time setting. (Usually components like foosic and audioscrobbler update at around 1 min.)
- Defrag your hard drive
If none of the above works, use foo_custom_pc instead.