I don’t know if these two things are connected, but somehow I think they are.
Yes, they are… if the client doesn’t accept the whole song, the server figures that it must have been skipped or something, so it doesn’t update the play count.
I’ll open a ticket for this and see if I can reproduce it.
This issue only occurs when playing m4a songs. Playing mp3 works fine. No errors in the log, and the database gets updated when the files have been played.
Are the lossless or regular m4a files?