chaug wrote: > Thanks, Erland, for taking the time to write that post. I hope it will > also others with the same problem. For me, the only way to get LMS > running again was the option "Clean cache folder, including media > library database, artwork cache etc." in the frontend configuration > interface of the ReadNAS. The only problem with that is that it also > seems to kind of uninstall most plugins. I'm saying "kind of" because > LMS still remembers that I "have" those plugins and tells me that there > are updates available for them (without listing them as installed, > though). This is not a huge problem, only that the DataBase Query plugin > is among those and if I select the "update" the whole trouble starts > from the beginning. At the same time, selecting the "update" seems to be > the only way to eventually uninstall it, since it is no longer listed as > installed. So for the time being, I am stuck with a plugin update > waiting to be installed which I never want to install again... I guess I > can live with that, but if there is another way of uninstalling it, I'd > be happy to try it. > You can try to shutdown LMS and remove the section for the plugins you don't want in the plugin-data.yaml file in the LMS cache directory. Remove the whole indented section after the Database Query line and not just one line.
You can also try to manually edit the plugin/extensions.prefs file in the LMS Preference folder when LMS is shutdown and remove the line " DatabaseQuery: 1". It feels extremely strange that Database Query plugin should cause any problems if you just install it because it doesn't do much before you enter the Database Query plugin menu and select one of the reports. So if you haven't tried it, I would just install it and uninstall it immediately afterwards. However, since I don't know exactly how your setup will behave, I can understand if you don't want to risk it, there could maybe be something strange in your setup that causes problems immediately after installation. chaug wrote: > > This is what I tried. Both refresh_rescan and refresh_startup are > currently set to 0 but after I restarted LMS, the CPU load for LMS went > up to around 100% again and the LMS webinterface remained inaccessible. > Just as before. Same thing after rebooting the whole device. When > looking at trackstat.prefs, I noticed that many of the variables have > the same strange value: 1336855428. Just thought I'd mention it. > There are two lines for each setting: refresh_rescan: 1 and _ts_refresh_rescan: 1347509211 It's the first one without the _ts_ prefix that is the actual setting, the one with the strange value is just a timestamp when the setting was last changed. It's the one without the _ts_ prefix you need to adjust. chaug wrote: > > So I'd like to say this for anyone else with similar problems: don't > give up on using musicbrainz IDs. It seems to work also on a NAS. At > least I can see the IDs in the TrackStat backup file, which, I take it, > means that TrackSTat is using them. The problem that we're discussing > here, hence, has is not caused by the musicbrainz-IDs that I've added to > (parts of) my music collection. It seems to be closely connected to the > database query plugin. > For musicbrainz id's to work with TrackStat there is at least two settings you need to ensure is set: - Enable musicbrainz tags (musicbrainz_enabled) - Rescan refresh (refresh_rescan) The "Enable musicbrainz tags" setting will ensure musicbrainz tags are taken into account when TrackStat does its refresh operation which adjusts previous paths in the database to the changed paths/filenames detected when performing a rescan. The "Rescan refresh" setting will ensure that TrackStat runs the refresh operation after each rescan in LMS. The "Startup refresh (refresh_startup)" option is optional, it will ensure the refresh operation is also run at startup of LMS. This is not needed if you perform rescans regularly in LMS. If I remember correctly, I introduced it to cover cases where people browsed with the Music Folder menu to add files to the music library instead of doing a rescan, in this case they know that they can just restart LMS to get the TrackStat data in sync again. ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=35962 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
