MM Helper 1.2.0 (Up again)

[Christoph]

Hey,
have you pressed return after changing the value?

I didn't changed this behaviour because of unwanted changes when working with this field. But I changes the tooltip of the input field.

Christoph

[Christoph]

Maybe I should add a little button besides the field to save the new play count. Then it should be clear that you first have to save the new value.

[martialartsguy]

Maybe I should add a little button besides the field to save the new play count. Then it should be clear that you first have to save the new value.

christoph-

That would probably be a bit clearer too.

I also just tried something that threw me off.

I have a song with a play that has no Last Played date, but was played once. I set the following choices for synchronize:

Start Time: Date Added (in this case the song was added 4/22/2004)
End Time: Now

When I pushed Start I checked the Single File date and it had 2/17/1954!!!

[Christoph]

Hey,
I can't reproduce your behaviour.
My steps:
1. I took a new song that hasn't never been played before.
2. I set the play count to 1 which creates no plays.
3. I synchronize the song with start time "Date Added" and end time "Now"

On my computer a correct date was created.

Christoph

[martialartsguy]

Hey,
I can't reproduce your behaviour.
My steps:
1. I took a new song that hasn't never been played before.
2. I set the play count to 1 which creates no plays.
3. I synchronize the song with start time "Date Added" and end time "Now"

On my computer a correct date was created.

Christoph

Whoops, I meant to say that the End Time was set to "Last Played," which should probably just give a popup error instead. So it's trying to read off a non-existent Last Played date, and somehow comes up with the 1950s!

[Christoph]

Ok, that's correct.
I will add a message for this. Thanks.

[martialartsguy]

Hey, no problem - I just did all of my songs that had "played" and gave them new playdates with this - it works beautifully.

Let me know when you have updates and I'll download and check for you.

[m1abrams]

Trying to use your Play Date Manager to fix the lastplayed dates of my music that I imported from jriver mediacenter. For some reason all the lastplayed dates are messed up, example 11/22/64734 . Which is a bit in the future. So I would just happy just nulling them all out if someone can point me in an easy way to do that, or use your tool. However your tool does not like that date and throws an unhandled exception for "Not a legal OleAut date"

[Christoph]

Hey,
there are several ways to fix them:
1. Use the "Refresh play count and last play date" option to recreate the play count and the last played date
2. Remove existing play dates if they also have the incorrect date by entering "0" in the "new play count" field.

Christoph

Edit:
Can you tell me your steps to cause the exception?

[RobSpook]

Been using you newer version for a few days now, and It's much better than the previous as far as user friendliness...

I REALLY like how you did the "Synchronize" option... it's perfect! Almost... I would really like Play Date Manager to remember my settings from the previous use, so that every time I open PDM it defaults to Synchronize, Start Time (Last Sync Date), End Time (Last Play Date).

Maybe it would be good to have a small button to "Select All" and "Select None" to make large lists easier to select.

two thumbs up mate!

[m1abrams]

Hey,
there are several ways to fix them:
1. Use the "Refresh play count and last play date" option to recreate the play count and the last played date
2. Remove existing play dates if they also have the incorrect date by entering "0" in the "new play count" field.

Christoph

Edit:
Can you tell me your steps to cause the exception?

Just select any track that has an invalid date for lastplayed. Click the MM helper icon and then click Play Date Manager, it opens the manager and immediately throws the error.

[m1abrams]

Hey,
there are several ways to fix them:
1. Use the "Refresh play count and last play date" option to recreate the play count and the last played date
2. Remove existing play dates if they also have the incorrect date by entering "0" in the "new play count" field.

I do not think I can do either of those tasks since the program closes out, if I select continue it is a never ending process.

[Christoph]

Hey,
@RobSpook:
Thanks. Nice to hear this. I will implement your wishes in the next version.

@m1abrams:
Ok, I will try to correct this issue.

Christoph

[martialartsguy]

Christoph-

One suggestion, unless I just don't know how to do this.

I would like to increase the playcount of an entire album by one (or more). Some tracks have six playcounts and some have two. What I'd like to do is add one playcount to the entire album, say from the last synch. Is this possible to implement or is it already possible?

[RobSpook]

Hey,
@RobSpook:
Thanks. Nice to hear this. I will implement your wishes in the next version.

@m1abrams:
Ok, I will try to correct this issue.

Christoph

Thanks, m8! Also I noticed a strange behavior when using the last sync date. For one song, the total playcounts was 54, with 52 history plays, so PDM had to add two plays. It added two, but they were the same as the last played date, so I had three identical playdates.

Now honestly, I don't care too much about the accuracy of the playdates, just that the history plays and playcounts match for the purpose of using DEISync I guess I don't understand the "last sync date", because it doesn't seem to work, or maybe it's because the song doesn't have a last sync date yet? What is the logic for a song without a last sync date?

Thanks much!