Yes, I know that this is a problem but unfortunately it can't be solved that easily. An option would be that it always writes as English(US)-date for example but I don't know if this is better for us Europeans.florin wrote:I too think it's date related, I used to have English(US) (M/d/yyyy), but after installing Windows 7 I set it to Romanian (dd.MM.yyyy). I got the error at the very start of the auto-rating process, probably because all my songs were rated with the old format. I changed back my regional settings to US and now it seems to be working again, but it would be nice to be date-format independent.
Interesting enough, one newer added song had: 0001 AR 000002548371709 05.07.2009 435 AutoRateAccurate 05, but it still worked and now it's: 0001 AR 000004610353599 5/7/2009 435 AutoRateAccurate 05
In a future version this maybe can be solved when the script uses its own database-fields which can be defined as date and not just as text like the customfield.
Well that's strange because I don't have that problem... Here the process takes a while but in the meanwhile the new songs begins. There's no skip. Do you use 2.4.2?One more thing, can you make the auto-rating process run in the background (low-priority)? The problem is that when I start MM I play a song, auto-rating starts and when the song ends it takes a while until MM goes to the next song (I have a big library so it takes a while).