Bugzilla – Bug 9894
Better control over scheduled rescans
Last modified: 2012-03-05 09:28:35 UTC
It would be useful to have better control over the timing of scheduled rescans in the 'Rescan Music Library' plugin. For example, I have my system set to rescan at a fixed time of day (10:00 hrs) but, at weekends when I'm at home, I don't want that rescan to happen whilst I'm listening to music. So a more crontab-like scheduling capability where I can specify days of week as well as times of day would be a great enhancement.
Brandon: would this be yours to address in new schema? or would it fall back to the plug-in designer.
See bug 4274. There may be some other enhancement requests along these same lines. But I have to ask: Why not schedule your rescan for the middle of the night instead of at 10AM? This is what I do on my system. Not much chance that I'll be listening to music at 5:00AM. And if you schedule a non-clearing scan, it doesn't really matter if _are_ listening to music during the scheduled rescan - the system should function just fine while scanning.
i take it he's at work at 10am. but i think the intent here is worthy. personally, i would like to automate a full clear and rescan once a week.
> Why not schedule your rescan for the middle of the night instead of at 10AM? Because I don't want to waste resources by leaving my PC on every night.
An option to "skip rescan if playing" might also help.
i set my computer to hibernate, but in the bios i can wake it up once a week (or daily, etc) as per a schedule. so i could bios wake up a few minutes prior to the SC rescan, and it saves elec.
(In reply to comment #4) > > Why not schedule your rescan for the middle of the night instead of at 10AM? > > Because I don't want to waste resources by leaving my PC on every night. But you have it running on weekdays while you're at work? How is that different?
>>Why not schedule your rescan for the middle of the night instead of at 10AM? << If you run SC on a server it can be difficult to find a time that doesn't conflict with other things the server might be doing at night. I don't want it scheduled for the same time my server is doing automated backups, for instance. If you live in a house where there are both night owls and early risers, fitting it in to the time when all are sleeping can be a challenge, so more variety in scheduling options is desirable.
wouldn't task scheduler (or cron) be capable of calling a scanner.exe (or scanner.pl) on any desired schedule?
(In reply to comment #7) > (In reply to comment #4) > > > Why not schedule your rescan for the middle of the night instead of at 10AM? > > > > Because I don't want to waste resources by leaving my PC on every night. > > But you have it running on weekdays while you're at work? How is that > different? > I'm using the PC for other purposes during the day. I don't need it on at night.
Created attachment 4355 [details] Proposed patched Plugin.pm This is a proposed new plugin.pm which adds basic day selection to the rescan plugin.
Created attachment 4356 [details] Proposed patched Settings.pm This is a proposed new settings.pm which adds basic day selection to the rescan plugin.
Created attachment 4357 [details] Proposed patched strings.txt This is a proposed patched strings.txt to add basic day selection to the rescan plugin
Created attachment 4358 [details] Proposed patched basic.html Proposed patched basic,html to add basic day selection to rescan plugin
Created attachment 4359 [details] Proposed patched install.xml Proposed patched install.xml to add basic day selection to rescan plugin
I've attached 5 files to update this plugin which add a basic day selection to the rescan plugin. I don't have CVS so I can't upload them as patch files. I'm no perl expert but hopefully they will be acceptable for consideration in a future release.
Created attachment 4362 [details] Updated plugin.pm There was a schoolboy error in my earlier submission - this version fixes it.
Can you comment on how this bug is affected by the upcoming auto-rescan feature in 7.6?
It is considered that the additional complexity in the UI is not warranted for these cases.