Playcounts mangled by V3 to V4 Upgrade

Post a reply

Visual Confirmation

To prevent automated access and spam, you are required to confirm that you are human. Please place a check mark next to all images of monkeys or apes. If you cannot see any images, please contact the Board Administrator.

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: Playcounts mangled by V3 to V4 Upgrade

Playcounts mangled by V3 to V4 Upgrade

Post by MattTown » Sun Dec 04, 2011 10:03 pm

Hi,

Successful V3 to V4 upgrade about a week ago. I use playcount to ensure I hear an even spread of music througoh the 20000 tracks in the library. Just noticed that my playcounts have taken on strange values. Above a value of 8 (a plausible decimal value in my library), values go up irregularly with large numbers of the following values: 12, 16, 24, 32, 40 and 52. These high playcount values did not exist in my library before the upgrade - highest count was 8, and that was for only 1 or two tracks. Has there been some wierd decimal to binary conversion error here?

Fortunately for me it is a limited number of tracks involved (200 odd) so I can afford to manually adjust those to more plausible values (like divide by 4).

Top