search

jrmuizel / banshee-unofficial-plugins

Automatically exported from code.google.com/p/banshee-unofficial-plugins
0 stars 1 forks source link

Automatic scan after install #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
After enabling the plugin for the first time, it should either inform the
user how to activate the scan of his/her music collection or, even better,
just do it.

At the very least, it should be more informative about why playlist
generation fails if it has not scanned the music collection yet.

Original issue reported on code.google.com by alex.hun...@gmail.com on 13 Aug 2008 at 8:03

GoogleCodeExporter commented 9 years ago

Original comment by bertrand.lorentz@gmail.com on 14 Aug 2008 at 4:51

GoogleCodeExporter commented 9 years ago

Original comment by dominik....@gmail.com on 5 Mar 2009 at 2:01

GoogleCodeExporter commented 9 years ago 
After thinking about this - the automatic scanning behavior should be 
configurable.

* The default action would be to scan the whole library, and recheck the library
status every time banshee starts (and scan new tracks if necessary)

* Only do the auto-check/rescan of the library if banshee was quit 
successfully, and
did not segfault. This should prevent situations where mp3s segfaulting mirage 
(see
issue #31) prevent banshee to start.

* If a mirage-analysis-process was stopped, automatic analysis is disabled - 
until
reenabled by the user.

This requires a preferences GUI. As proposed in Issue #9 we should use the new
Banshee Preferences Source Action to handle the configuration. I am postponing 
this
to 0.5.1 which will require Banshee 1.5+.

Unfortunately 0.5.0 will not include a fix for this yet.

Original comment by dominik....@gmail.com on 9 Mar 2009 at 10:54