Component management. 2019-01-27 08:56:32 In the 3rd party plugins section, I've posted about a problem I'm experiencing after a component update that I'm being told could be due to having too many of them. Due to the way that happened, I'm not entirely sold on the idea, but the potential need to do away with some of the components I have installed has brought new relevance to some concerns I've been having for a long time about the whole process of component management within foobar2000.I was going to just put this in the same thread, but I think it probably should be put in a new one here:-------Apart from components from the official repository, I also have a handful of others from a number of places. Like the SoX-based resampler found in this board, one or two exotic (videogame) inputs from another place, and possibly something else... Keeping these updated requires manual work and I don't expect foobar to provide automatic checks for them, but, maybe, at some point, it could be possible to give foobar a list of local folders (and URLs?) to check when updating (maybe a separate button or a checkbox for "external sources" or whatever), and have it install whatever components it finds in those places. That would certainly make the process a lot smoother.Also, once installed, it's very easy to forget which components are on the repo and receive updates automatically and which are not and require manual checking and/or downloading. If foobar could mark or highlight them in some way, it would be really helpful as a reminder.In addition, if this problem of loading failures is indeed caused by an excess of components, couldn't something be done about it other than just having to sacrifice some?The most convenient way for the user would be, of course, if foobar could dynamically manage the loading and unloading of those components depending on whether they are being used. Yeah, I realize this is easier said than done, and I don't want to come across as a captain obvious. Maybe you are already working on something to that effect. I have no idea.The next best thing would be if the user could selectively put some components in a "low priority" or "don't load" list, so that he doesn't have to actually remove them and loose track of them (maybe keep receiving updates for them, even if currently unused?), so that, if he eventually needs them, he can just check another component/s off and enable that one.As an addition to this, it's not vital, but, it would be very convenient if that loading limit could be worked into this so that you already get a warning when you try to apply a list with too many components enabled, or not enough disabled, depending on how you look at it.