Is it possible that people who had previous database errors might have a few incorrect reference counts, and this is the root of the problem?

Reference counts aren't persistent - they only exist for the time between downloading and synchronising so there's no scope for them to really go stale apart from within emplode itself.

What I'm wondering is if there's a particular way of deleting that isn't dropping the reference count and is therefore not causing the item to be deleted, just unreferenced since they _are_ removed from the parent playlist.


--
Mike Crowe
I may not be speaking on behalf of empeg above :-)