On Jun 27, 2009, at 12:27 PM, Phil Meyer <[email protected]> wrote:
>> I've changed all scanning in the current 7.4 over to the new scanner >> code I've been working on. I expect there will be bugs. >> > Are you saying this is now merged to 7.4/trunk? No, sorry I wasn't clear. This is only in SQLite and the nightlies. > >> I've started a wiki page that attempts to describe how the new >> scanner in 7.4 works, >> please read it and let me know if you need more info or have >> problems. >> > Is MusicIP interraction still supported? I think I read somewhere > that it didn't work in the noweb-sqlite branch? MIP should still work as before, although I haven't tested it in the past few weeks. > I guess that MySQL support is still missing? Any adeas of a > timeline for that? Until it is supported, or all plugins have been > converted, I can't use this as my day-to-day server, and have to run > SQLite version in parallel for beta testing. No MySQL support yet, sorry :(. Maybe I'll try to hack on this some evening. But please don't avoid SQLite if your only concern is performance. It performs very well in my experience. And yes my scans are consistently faster than in 7.3.3. I meant to post some benchmarks on the wiki page, will do that a bit later. > Does anyone know of a decent (preferably freeware) GUI SQLite query > analyser? I haven't found a decent one yet - running queries and > capturing results with the console sqlite.exe command is such a chore. If you Google for SQLite GUI you should find some. There is even one that is a Firefox plugin. > > Do you think that some existing bugs are now fixed? eg. if > compilation status is changed, a scan for new/changed files will > actually correctly apply the change to the DB? Not sure about this specific case but this is exactly the kind of bug I want to fix. Some such as changing genres or years are already handled. This is one of the areas where I really need people's help, trying common use cases for changing tags. > > Unsure from the page how auto rescan works. Is this a mode that can > be enabled, so the library is automatically kept up to date? Does > it automatically kick in the instant it sees a single file has > changed? Other apps have a delay, such that it will start scanning > a minute or so after it has detected no further file updates (to > avoid file system thrashing, and less likely to get things wrong > where songs on the same album are written back in a batch). Right now it's always enabled for Mac and Linux with local files. I plan to make it a pref though. There is a built-in delay to handle exactly the situation you describe. The rescan kicks off 15 seconds after the last event is received. > > Rescannng in process (rather than spawning another process) - what > modes do this, is it controllable? I think scanning in another > process was better than in the server process, to avoid drop-outs in > the music. Is in-process using another thread now? This needs testing to see if there is any impact. If it's a problem we can easily have the auto-rescan kick off a new process. In-process is supported for low-memory environments mostly. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
