No, but I'm running on Windows where inotify doesn't work and the (planned?) course is to periodically check for updates, which is also broken. So I've disabled that as well.
I'm running a clear/rescan right now and streaming to three synced players. This is possible since the SQLite method of clear/rescan creates an entirely new database, then swaps it for the old one when it finishes, unlike with MySQL. I don't know what happens at the point when it finishes (I'll know in another 10 minutes), whether the music stops when the new database is swapped in. I don't think the coordination between manual rescanning and auto-rescanning has really been tested. Maybe it hasn't even been implemented yet, since with TinySC, where auto-rescanning will be going live soon, I don't believe there's any way to run a manual rescan. I have been seeing some dropouts when streaming to these synced players, and they always seem to happen about 12-15 seconds after the start of a track for some reason. Sometimes when pressing play there's a longish wait before a track will begin - a few seconds longer than with 7.5/MySQL. I'm also seeing occasional slow searches and long waits for browse album pages in the web ui. I think we could be starting to see the limitations of SQLite. Most of the time it's just as fast as with MySQL, but there's a lot more variability in response time. -- JJZolx Jim ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=76850 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
