Is it necessary to trigger a rescan just because someone edits and saves a playlist through the web interface ? Isn't the information already in the database when the playlist has been edited through the SBS web interface ?
It causes a bit of problem for me in the "TrackStat Playlist" plugin which creates a playlist of last played tracks, the result is that a rescan will be triggered immediately after a track has been played or rated. It will cause a lot of rescans as you might imagine. I'm not sure if the rescan itself is a problem as long as it's pretty fast, but it could be a problem for third party plugins that subscribes to "rescan done" notifications and initiates a larger operation. The real solution for third party plugins is of course enhancement request #6023, but I thought I mention the problem since it feels incorrect that it issues a rescan in this case. Let me know if you want a bug report for it and I'll register one. -- erland Erland Isaksson 'My homepage' (http://erland.isaksson.info) (Install my plugins through Extension Downloader) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library, Title Switcher and Database Query plugins' (http://wiki.erland.isaksson.info/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=77585 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
