Hi all,

I know that in the v2 final release software the problem of play counts not updating was supossed to be resolved, but I'm sure that sometimes (not laways) a song's play count isn't being incremented. Maybe it's just for songs on my second hard disc - I'm not sure. Also I often notice this effect when I've added a whole new album to my empeg (which should end up on my second hard disc). I'd play through the entire album X times, but the play counts for all of the songs would all be X-N, so sometimes the play counts weren't being incremented, and when this happened it is true for every song on the playlist (not just the new album if I play something else afterwards). This has nothing to do with the problem of the empeg losing its current play list position that occurs when the power is lost too quickly as I haven't seen that effect occur in very long time.

I'm running the v2 final release software, hijack v340, and I use jEmplode (various versions depending upon which bug I'm trying to avoid) to manage my collection.

Sorry I can't be more specific right now, or mess around with uninstalling, or upgrading hijack, as I'm too busy. I just thought I let the group know of this problem, and see if others have also noticed similar issues.

Thanks,
Ross

Does anybody else have this problem? I've still got it and it's even more interesting now...

OK, so the problem is, quite simply, that for some songs the play counts aren't being updated. The songs affected are apparently completely random.

Now I've just installed emphatic v2 to my empeg and initialised all of the song ratings to 5... but looking through the db with jEmplode a random sample of songs scattered around the db haven't been initialised to 5 - they're still stuck on zero. These same songs suspiciously also have zero play counts, despite other songs in the same playlist having play counts greater than zero! This is true for all songs with skip_count = 0, and the total number of songs affected is about 600 out of 3000 in total. Again, they just seem to be randomly affected tracks within albums where every other track is functioning perfectly. I've checked the FIDs of the mp3s, but that doesn't seem to be a factor as the affected FIDs cover a large range from 336 to 69776.

So it seems that for some songs the dynamic data isn't being updated. Any ideas?

Some background information, I'm running v2 final software, exclusively using jEmplode to deal with the database (various versions - mostly 69 now), and am running the latest versions of Hijack (413), and emphatic (2.04). I used to have my music split over a 10Gb and a 30Gb hard disc, but 6 months ago I migrated all of the music across to a new 40 Gb hard disc. This problem essentially existed both then and now. Also I used a fresh dynamic data partition to store the play counts on the new hard disc, so they were all reset to zero.

Ross

...affected FIDs cover a large range from 336 to 69776...

That's a lot of FIDs. Do you have a lot of small files?

I know that your error distribution seems random, but I am wondering if the player software somehow reacts badly when trying to update dynamic data of a FID that is too high or references an invalid block in the dynamic partition.

An interesting test might be to reset your counts to zero (perhaps you can copy the data temporarily using dd to a file on a different partition) and try playing a series of low numbered FIDs. Check to see if it is updating. Then play one very high numbered FID and then a sequence of low ones again. This would check to see if a high FID is blocking future dynamic data updates.

Yeah, what Paul said. I think you may find a correlation between high FIDs and dynamic data that doesn't update.