2021-07-05, 14:07
Great, now we are getting somewhere!!!
I can see why having the music files in both music and video databases would cause processing for JSON calls to produce duplicated items on the queue, and why it happens on the Pi that is also the MariaDB server but not on the other Pi (which shares the same served video db) because of path differences of the music file locations. Fixing is not trivial so less likely to get into v19 because of the risk of breaking other things, but understanding is a huge step forwards.
What I can't see is how those music files ended up as entries in the files table pf the video databse in the first place. I have tried to reproduce it for testing and so far not managed to get music files in the video database. Any ideas what you could have done? No worries if not, but it would help to know.
I can see why having the music files in both music and video databases would cause processing for JSON calls to produce duplicated items on the queue, and why it happens on the Pi that is also the MariaDB server but not on the other Pi (which shares the same served video db) because of path differences of the music file locations. Fixing is not trivial so less likely to get into v19 because of the risk of breaking other things, but understanding is a huge step forwards.
What I can't see is how those music files ended up as entries in the files table pf the video databse in the first place. I have tried to reproduce it for testing and so far not managed to get music files in the video database. Any ideas what you could have done? No worries if not, but it would help to know.