by Mizery_Made » Sun Nov 29, 2015 7:56 pm
It's because MM stores "play data" two different ways. It has a play counter that is updated, which is just a numerical representation of how many times a song has been played. However, there is also a table in the database that stores the date/time of every play. When you play a file in MM, it updates both of these sources. However, when syncing a device (be it an Android, or iDevice), it only updates the play counter (without a corresponding date/time entry in the History table). That's because these devices don't store that data (although it's been requested that MMA store and sync this data).
This script pulls its data from the History table (where Date/Time of plays are stored), not from the Play Count field. Thus, it doesn't see the device plays, as it would be unable to determine when they were played for areas of this node like time of day, season, day/month/year, etc.
It's because MM stores "play data" two different ways. It has a play counter that is updated, which is just a numerical representation of how many times a song has been played. However, there is also a table in the database that stores the date/time of every play. When you play a file in MM, it updates both of these sources. However, when syncing a device (be it an Android, or iDevice), it only updates the play counter (without a corresponding date/time entry in the History table). That's because these devices don't store that data (although it's been requested that MMA store and sync this data).
This script pulls its data from the History table (where Date/Time of plays are stored), not from the Play Count field. Thus, it doesn't see the device plays, as it would be unable to determine when they were played for areas of this node like time of day, season, day/month/year, etc.