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

[jsummers]

No rush, no worries what we have here is very much appreciated

[Big_Berny]

AutoRateAccurate 2.3 RC1

Since it seems to work stable I changed Beta to Release Candidate. Since there were only a few downloads (much less than 2.2.1 downloads) I'd be happy to get some more reports about that new version and specially the filter-feature.

[Macarena]

Hi Big_Berny,

I'd like to contribute to make the script even better:


Macarena

[twinbee]

Love the way you can define the math formula for different possibilities. I'm rather uncertain of using an autorating script personally, but I might have to try this out if only because the ratings can be restored if need be. Is there a field in MM which shows me that autorated tracks have been autotagged?

Also, how did you get the skip parameter - does Mediamonkey have something like this as a field in the database? (I wish Mediamonkey had something like this, since obviously, MM only looks for when a track has been fully played).

[Big_Berny]

@Macarena: Thanks for the report, I'll have a look!

@twinbee: Yes, the script stores different informations in a customfield (or some other fields I needed) like the status. It looks like this:

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/IG=Ignored)
|
SkipCounter

As you can see the second information is MR, AR, BR or IG. So if you want to get all songs which are autorated just make a playlist with songs that contain 'AR' in the customfield. Or use the MagicNodes-script to create a node just with autorated songs.

About your second question: AutoRateAccurate tracks Skips by itself, MM can't do that. These Skips then also get stored in the customfield. By the way there is also a feature called 'Incremental Playcounter' implemented in the script which makes the playcnter more accurate as PlayCounter increases as soon as 100% of a song gets played - that means it also increases if you play two times 50% of the song.

[Big_Berny]

Ok Macarena, here's a first try tro solve your problem. Could you test it please and report? Do you use filters?

AutoRateAccurate 2.3 RC2

Changes since RC1:
-Fixed: Try to fix 'out of range' problem. (Thanks Macarena)

[Macarena]

Ok Macarena, here's a first try tro solve your problem. Could you test it please and report? Do you use filters?

AutoRateAccurate 2.3 RC2

Changes since RC1:
-Fixed: Try to fix 'out of range' problem. (Thanks Macarena)

- with RC1: the previous error report was appearing cca three times and then never for another five runs
- with RC2: there is (IMO) smoother run of ARA with monitoring (MM native) at the start-up, no error message, and seems to do the job

FYI: number of tracks is 30thousands+ Should I clear sth and rerun ARA?

Thanks, M

[Big_Berny]

That's good news. To be honest I don't know exactly why RC1 gave that error but maybe it was something with the database. Theoretically RC1 and RC2 should have the same result.

AutoRateAccurate should work with every library size. So there's no need to delete anything. Thanks for your reports!

[Big_Berny]

And thanks to the guy or girl who donated some other months on last.fm!!!

[Big_Berny]

Here is it: AutoRateAccurate 2.3

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.
-Added: Check for updates in MediaMonkey over "Tools/Extensions". (No notifications for new beta versions!)
-Changed: AutoCalibration and AutoRating have been merged which improved the speed a lot! The speed increases are up to 45%.
-Changed: Due to speed optimizations "AutoCalibrate at startup" has been replaced with "AutoRate at startup".
-Changed: Removed "Rate non-played but skipped songs". Enabled by default because it doesn't decrease speed anymore.
-Changed: Removed formula "Fast". Useless with the new optimizations.
-Fixed: Minor fixes.

The only change since RC2 is the implementation of the update-checker. Just click on "Tools/Extensions", choose AutoRateAccurate and select "Find update". Now you'll see if there's an update. Beta-versions won't show up there so if you wnat to participate please still check this thread!
The biggest changes since 2.2.x are the filter-possibility to exclude songs form autoratings (like audiobooks for example) and the huge speed optimizations which make the script rate my library (13'000 songs) in 4.3 seconds - that's 45% faster than before!

Hope you like it!
Big_Berny

[spacefish]

The only change since RC2 is the implementation of the update-checker. Just click on "Tools/Extensions", choose AutoRateAccurate and select "Find update". Now you'll see if there's an update.

Awesome, Berny! Thanks.

[nynaevelan]

Berny:

I am receiving the following error when MM is moving to the next track, this occurred while an autosync was "preparing tracks":



Do you think this is another one of those timing issues??

Nyn

[Big_Berny]

Hi nyn,
you really try to find difficult bugs, aren't you?

At the moment I have no ideas how I could fix that one as MM itself opens a query and the script can't open another one. I have no idea if there's a way to find out if there's a query already opened. I'll ask other script-devs maybe they have a solution. Btw I also listen to music while synching but this error never appeared here. Can you reproduce it?

Thanks!
Big_Berny

[nynaevelan]

Berny:

Unfortunately it happened to me twice more before I reverted back to 2.2. Maybe because ARA is trying to rate more tracks than 2.2 did? I'll reinstall this weekend to try to re-rate all my tracks before running a sync.

Nyn

[MoDementia]

Berny, I have some code in DEISync that checks for transactions in progress (and maybe some others) it's a real pain in the $%#@$

Work backwards from this sub

Code: Select all

Sub CommitFinished(CopyFileName)