Ok, makes sense and I have used a script to change play counts from time to time. But I've also been using the fake plays script in conjunction with the adjustments, so I can only assume these discrepancies are derived from adjustments which I've made prior to using the fake plays script. Now on to detection and correction. :-?

Nyn

Hard to say. The playhistory table named "Played" only contains plays played [b]within MM[/b]. If you have increased your playcount through sync with portable device or through scripts then the playcount will be higher than what's stored in the played table. To fix it you either have to populate the Played table with the extra plays (with time stamp) or decrease your playcount. What is right is up to you to decide! :)

Hi:

While working on something in my database, I noticed that the playcount which MM is displaying is not the playcount which is being extracted when I run a SQL query in SQLite or using Bex's SQL Viewer. The playcount is higher in MM than both SQLite and SQL Viewer. Can someone tell me why the discrepancy and which is the right playcount? And more importantly, how do I identify all the tracks which are displaying a different playcount than what is actually in the SQL database? Here are a few examples:


Track1 - MM(37) SQL (32)
Track2 - MM(147) SQL(134)
Track3 - MM(62) SQL(52)
Track4 - MM(80) SQL(77)

Help, my play counts are [b]CRITICAL[/b] to my use of MM.

Nyn