Thanks everyone.
This script was the only reason I stuck with MM 2.5 rather than upgrade to version 3. However, now that I see that the ratings are not actually updated to the track tags, I see no point in using it. You see, the thing is, if you move your collection, or for any reason need to rebuild the db, all the ratings are lost. Personally, I think it's better to update the metadata, so that if the track is scanned again, you'd see the updated rating.
And yes - I tried to sync the tags, but the sync does not see or apply track rating updates that are created by this script. Don't know where the script stores the updated track ratings, but it is not stored where the sync sees it, or where a scan done by MM on another computer can see it.
I was using a shared database which allowed ratings to be shared among more than one computer, but I found that this caused long delays between tracks, (and also tended to hang some apps) so I went back to separate databases for each computer, with one shared folder for music files, but in this case, autorating is not actually shared among both computers, because, as you say, "the file rating is only being saved on the computer where the rating occurred".
The script is cool, and I do hope that our smart guy diddeleedoo (thanks man!) might make it work in Version 3, and perhaps even make an option to actually apply the updated ratings permanently to the metadata of the track, rather than store it in the database where it could be lost.
Is anyone aware of any other tool that will update the ratings for a track based on if the track is played through, or skipped, and that will actually update the Tags for the track?
Many thanks!!


