

trixmoto wrote:Sorry, I thought I'd fixed this. I can't replicate it myself but it occurs when the database transactions are called too quickly - if you process less tracks at once it shouldn't occur. I'll try to get it sorted in the next version though.


Users browsing this forum: No registered users and 12 guests