Assuming there are no bugs to be fixed in the current version, the next major revision (1.6) will hopefully feature a redesigned GUI, and will automatically switch people over from PLAY_DATE and PLAY_TIME to LAST_PLAYED. Any other feature requests are welcome.

ability to set first played to 05/14/2005

As in custom time stamps?

This might be added to 1.6, or I might remove the ability to do custom time stamps all together. Be forwarned that using custom time stamps will make your settings incompatible with any public columns_ui FCS.

If you want your date to be displayed somewhere like that, you can use


Edit: Fixed stupid errors in my code, should work now.

no, you're right. now that i think about it, it would make everything much easier if there is only one standard.

I have to go to work now for a while. When I return (about 5 hours from time of posting), I will begin working on 1.6. Depending on the complexities faced, it may be released in the next 24 hours, or it may take a few days. As I said before, any feature requests or suggestions are seriously considered and welcome.

Is it possible to add a field to the status bar which shows the sum of the playcounts of all marked tracks?

I don't think so. At least, I don't know how to do it. I'll look into it.

Any option to disable the new tag?

I only use the play counter, which I love.

Should I stick with the old one?

I've already implemented an option to disable any/all the tags, which will be available in version 1.6 (hopefully to be released very shortly - within an hour or two).

foo_playcount 1.6 (Source & Binary Included)

Version 1.6 (May 14 2005)

1) UI update.

2) Removed ability to have custom timestamping formats. Everybody now uses LAST_PLAYED and FIRST_PLAYED standards. Eg. 2005-11-24 16:59:32. You can use TAGZ to display the information in any order you wish.

3) Removed a lot of code that was no longer neccessary due to the removal of custom timestamping.

4) Cleaned up some code here and there.

5) Made it possible to not write any/all of the tags.

Thank you very much =)

Now that 1.6 is done, I'm open to suggestions for new features as I have no new plans for the next version (other then looking into the status bar option).

1.6.1 will be released shortly changing "LAST_PLAYED" and "FIRST_PLAYED" to "LAST PLAYED" and "FIRST PLAYED" as that is the accepted standard. See here.

foo_playcount 1.6.1 (Source & Binary Included)

1) Minor UI Changes

2) Fixed stupid error. Changed "LAST_PLAYED" and "FIRST_PLAYED" to "LAST PLAYED" and "FIRST PLAYED". This is the encouraged standard. See the Encouraged tag standards here.

Four releases in one day may seem a little excessive. However, this should be the last release for a while (assuming there are no other bugs).

??
the standard is WITH underscores
http://www.hydrogenaudio.org/forums/index....showtopic=31530

Not according to the wiki. I don't care, I now preclaim it to be without underscores, but spaces instead. I argued that it shouldn't use underscores. Obviously someone changed the wiki so that it didn't use underscores, which confuses the matter. Because ALBUM ARTIST doesn't use underscores, and the wiki says so, I'm going to leave it as spaces.

I think so too, I always use _ in my tags :S
Much easier if all use that, less confusing.

Well I'm not releasing two versions, so until Lyx gets back from his weekend trip, nothing is going to change, spaces will remain.

Whatever you do, please keep it consistent.

Either Album Artist, First Played, Last Played, and Play Counter
or Album_Artist, First_Played, Last_Played, and Play_Counter.

As you're probably not going to reach a consensus on this topic,
I would still advocate the ability to define your own field names.

Let people decide if they want to break standards, don't enforce them.

I was about to change PLAY_COUNTER to PLAY COUNTER.

If people want to define there own field names, they can take the source and change it. For the sake of simplicity, my version is going enforce standards.

Welcome to consistency.

foo_playcount 1.6.2 (Source & Binary Included)

1) Changed PLAY_COUNTER to PLAY COUNTER. Will automatically transfer over all old PLAY_COUNTER statistics to the new PLAY COUNTER tag.

To enable Lyx's Navigator columns_ui FCS to use LAST PLAYED instead of LAST_PLAYED, overwrite the code in the last played column with the below:

we had a standard, now you want to enforce a new one, i don't think that's a good way
..for the sake of simplicity you could have kept things like they were before
why do you want to change things?
the wiki was change by Canar on 8th may, i don't know why he did that

I don't know why Canar changed it, but he did and I agree with him

Thank you for the new release.

Are you considering to release a version thet supports external SQLite databases?

kode54's version supports an external database, but obviously not the latest changes I have made. I may consider adding support for an external database if it is not to hard (I will look at kode54's code).

I've written a masstagger script to convert PLAY_COUNTER/FIRST_PLAYED/LAST_PLAYED to there equivalents without underscores. Get it here.

I wish you would not have added in the "DB Only Mask" option set to mp3 only. This wrote all of my play counter information to my FLAC files.

I didn't want to write anything to my files. Had I known I would have removed my database first.

You might want to change this....or put up a warning, because I know there are others would probably do not want to write this data to their files.

Edit: I just noticed that it is the same default as in v1.5. Is it possible to add in the option to set all files as a default, and then you can change after install?

It shouldn't be, I must've changed something accidentally. I will investigate. By default its set *.wav only, and nothing to do with mp3.

Edit: Just saw your edit. It's possible, but the idea is that most people prefer it written to the file. If there is a general consensus by a large majority that it should be set to all formats by default, I'm open to it.

You replied just as I made an edit to my post.

It appears that the DB Only Mask is a default to .mp3 in v1.5 as well. Perhaps a new feature would be to have the option to disable file writing to all file types (as a default). Once installed, you can then select whether you want to write to your files.

It does not default to *.mp3. It defaults to *.wav.

*.mp3 is a setting that is carrying over from your previous foo_playcount settings.

Like i said in my edit above, it's possible, but the idea is that most people prefer it written to the file. If there is a general consensus by a large majority that it should be set to all formats by default, I'm open to it.

I would think that a default to not write to the file would probably be best. This would accommodate those that do not want to change their files, and can easily be turned on after install. Having the write option turned off will not remove any play count information held in the file already, so it won't affect those that like to write to their files.

Just a thought.

Edit: I also had re-installed my copy of v1.5, it wasn't the one I had been using. The default for that .dll was .mp3. I know that it was the original because the day and month orders were not the same as the ones I had been using. Oh well....no big deal.

Also note that it only defers the writing of tag information to the file, it does not prevent it. I cannot stop foobar from writting any information to the file at some point. If the tags are ever updated (i.e. spelling correction), the foo_playcount information will also be written to the file.

Edit: I have the source code for 1.5 and the default is definately *.wav.

If you change pack to 1.5 after using my version, your timestamp settings will be reset to the 1.5 default settings (i.e. PLAY_DATE and PLAY_TIME.)

I didn't realize that. Guess I could always activate the "Block tag update operations" in the Database section. That way the files won't be changed.

kl33per, I just noticed that the version of foo_playcount I have is 1.6.1, but I downloaded it from your link to 1.6.2. It also still has PLAY_COUNTER instead of PLAY COUNTER.

Thanks!

Forgot to forward the version number, hold on.

Edit: Download it now.

Got it, thanks. I checked it and the version number is 1.6.2, but under the Tag Writing section, it still has PLAY_COUNTER. I haven't tried out my new script yet, so I don't know if it is just the window text, or if the parameter is still unchanged. Thought you might like to know.

That's just window text, when it writes it, it writes PLAY COUNTER. I will do another silent update. You don't have to download unless the text on the preferences page is giving you nightmares

Edit: Update done.

That's cool. Thanks for the update. It looks good!

I'm glad someone appreciates it all.

kl33per, I think you do a great job here! Can't understand, why some people are not grateful for your time you spend in the further development of this plugin!

I'm sure they're all greatuful on the inside, thanks Chaser.

why have the tags changed again? can i get my underscores back?

Short answer, nope.

Long anwser.

Basically a few of us have decided that all tags should not have underscores (eg. ALBUM ARTIST, the most common two word tag does not have an underscore). It is quite easy to update your config.

LAST_PLAYED = LAST PLAYED
FIRST_PLAYED = FIRST PLAYED
PLAY_COUNTER = PLAY COUNTER

i really like the new version, but i think im going back to the old version. too much confusion with all the tags. these are only tags ive seen with spaces in them with the exception with %album artist% it just creates gapps in the strings which makes me always look twice at the tags cause it looks akward.

That's your prerogative. However, all public columns_ui configs will use spaces eventually, so by using the old version you are locking yourself out.

bahh u win %play counter% it is.. time to bust out the masstagger again

I posted a masstagger script a few posts up.

Edit: Direct link to script

someone has got to make their mind up on underscores or not. this is getting rediculous.

Yes, very confusing, I'll stick with the underscores version.