AutoRateAccurate 2.4.3 (22/10/2009) - for MM3

[PhilDG]

Berny,
The problem has been resolved now - can't think what the problem was but I had another Windows Update to install last night and today it's fine. Thanks for looking into it though.

[Guest]

I would just like to add my request to the requests of others for a way to prevent ARA from rating audiobooks and the like - I would be happy with a simple genre ignore list or filters... any way to prevent my 10,000 lectures from skewing the music ratings...

[Big_Berny]

Hi Guest,
thanks for the request. I'll have a look. Is one genre enough for you or do you need more?

Big_Berny

[Guest]

Thanks for the quick response (sorry, I haven't made a forum account yet). A single genre would be slightly more useful but the more genres I can use to filter the better. In addition to thousands of lectures I have hundreds of audiobooks from Audible and other sources - all of which I would like to be able to ignore when it comes to ARA. I use multiple genres to generate my Music filter and would be looking for something similar with ARA - or just a way to use my filter - whichever is easier.

[xma]

Can someone explain what means each of the filed below:

0000 NR XXXXXXXXXX 0 AutoRateAccurate 06

How do you, then, reflect what are the best rated songs using AutoRate ?

Can I safely delete my 'manual' ratings ? How a song played on a portable device is updated ?

Thank you.

[Big_Berny]

Here are the different informations which are stored in the customfield and used to calculate the ratings:

Code: Select all

0000 MR 0000000000000000 01.01.2004 12 AutoRateAccurate 06
|    |  |                |          |  |                |
|    |  |                |          |  |                Number which shows the format of customfield (internal)
|    |  |                |          |  |
|    |  |                |          |  String to indentify if the content is from AutoRateAccurate
|    |  |                |          |
|    |  |                |          PlayedTimePart (How many seconds of the song has been played 
|    |  |                |                          without the playcounter has been increased)
|    |  |                FirstPlayedDate (When the song has been played the first time)
|    |  |
|    |  Points (Value calculated by the formula; only there if WritePoints enabled)
|    |
|    Status (MR=ManualRating/AR=AutoRating/BR=BaseRating)
|
SkipCounter

The second question I don't understand completely. The information in the customfield is just for the script and normally shouldn't bother ther users. To find out what the best rated songs are just check the normal ratings. The script uses the same rating-field like you do if you rate a song.

Surely you can safely delete you manual ratings if you want. But depending what you want manual ratings may be more accurate as they are really rated by yourself. On the other hand if haven't played a song for years autoratings have the advantage that the ratings gets lower. So manual ratings are probably more acurate in the moment but not so 'updated'.

About portable device: Since AutoRateAccurate uses the normal rating-field the songs get synched with the ratings. So you also see the ratings on the portable device if it is able to show them. If the rating increases after listening a song on a portable device depends on the device itself. iPods for example are able to synch back the playcounter so that MM sees that it has been played. If you have such a device the autoratings will be updated as soon as you synch the player. If you have a MP3 player which isn't able to synch back playcounter informations then the autoratings will only be based on how much (and when) you played the song on the PC.

Btw: If you want to keep manual ratings and you have an iPod you can also rate songs on the iPod and AutoRateAccurate will recognize that it's an autorating.

[xma]

Kudos for the crystal clear explanations !

[Big_Berny]

No problem!

By the way here's my todo-list for the next version:
-Add possibility to filter songs - DONE (For GOLD-users only)
-Faster (and stabler) AutoCalibration and AutoRating - DONE (Over 40% faster than before. Takes 4.3s instead of 7.4s (5.8s if 'Also rate non-played songs' disabled) on my system now)
--Maybe adding another feature if it really gets a lot faster.

And thanks again for the donations and specially also for over 250 downloads of 2.2.1 after 20 days.

[Big_Berny]

AutoRateAccurate 2.3 Beta1

Changes:
-Added: Possibility to exclude songs (like audiobooks for example) from autoratings. Just edit in MM the filter "AutoRateAccurate". (Only for MM-GOLD-Users)
-Added: Excluded songs get the status "IG" (Ignored) in the customfield.
-Changed: AutoCalibration and AutoRating have been merged which improved the speed a lot! The speed increases are between 25% and 45%. So rating my library takes 4.3s on my PC with 13000 songs now. That's why "AutoCalibrate at startup" has been replaced with "AutoRate at startup" which improves the accuracy again.
-Removed: "Rate non-played but skipped songs". Enabled by default because it doesn't decrease speed anymore.
-Removed: Formula "Fast". Useless with the new optimizations.
-Fixed: Minor fixes.

ToDo:
-Finishing code clean up.

Some Notes:
-Because of the big changes due to the optimization I suggest to backup the database first!
-If you used 2.2.1 before please autorate your library with this version first. Then install 2.3 Beta1, restart MM and autorate the library with the new version. Tell me if there are a lot of songs which get updated! There could be little differences in the two scripts but they should be quite minor.

[jsummers]

Well first things first this is much faster
Second not one song got updated different with the update using default rating system

Third, now I get a error when my mp3 player sync's with mediamonkey.



During the sync a error dialog continues to fire "Errir executing script event."

I am using the
Beta script of yours
MM3.0.4.1185
Creative Zen Vision:M if that helps
Vista ( UCA disabled )


Looks the the updates are very good just wondering if you have any idea what is up with this error?

[Big_Berny]

Thanks jsummers, that's really good news!
And the bug you mentioned is already fixed!

AutoRateAccurate 2.3 Beta2a

Changes:
-Fixed: Problem when trackinformation change, for example when synching. (Thanks jsummers!)

EDIT: Fixed the bugfix in Beta 2a.

[jsummers]

then


many times.

Bummer. Well I am more the willing to buy a few months of last.fm for yah With as many songs as me I just would not rate songs without this script.


I also have a question for you. Sorry if this is posted someplace in the form and I missed it, but is the current rating used to determine the new rating? Just wondering if there is a manual way to push a songs rating up or down but allow it to still be autoRated. not a big deal

[Big_Berny]

Argh, I just was some minutes too late with uploading Beta 2a. Exactly your bug should be fixed in it! So download again from the last post.

About your last request:
At the moment there's no way to have a manual influence to autoratings. Maybe I'll think about such a feature but it needs some time as I have to look how this could be implemented easily and usefully. I didn't implemented that one because if you already rate songs there's no need for the script to autorate it as manual ratings should be more accurate anyway. For example: why push an autorating to 4-stars if you also just could rate it with 4-stars?

[jsummers]

YAY! No errors! Thanks!


It may be I am just way to picky or live in a dream world or who knows .... any how the reasons I ask is I personally make autoPlaylist's often highly based on ratings. Every now and then a song pops up high in rating or lots of play counts and gets in my playlist. Then I sync it then play the list and if my Vision:M would detect skips then songs that I would like pushed down would do so in the autoRating in time. But creative dropped the ball on that one so I sometimes have songs getting more plays and higher ratings then I would like. I would like to be able to let the song be autoRated but not with its current values. I suppose I could just as easy make a "black playlist" and put the songs I hope to affect on this list and make my auto playlists not put songs on the black list on, or find something to change playcounts on these songs. Or just stop being so picky. Or just rate these songs by low for a bit then let it get auto rated another time.

anyhow thanks for the awesome script and the fix and speed updates. This script rocks! I think it should be part of MM

[Big_Berny]

Ok, I'll have a look. I'm working on a next version with other speed improvements and features anyway. But it may take a while as I also have other things to do beside scripting.