As far as I know, there is no way for 3-rd party developers to control VST plug-ins no matter which wrapper you choose (of course I can only be sure about my implmentation - it doesn't expose any interface for this - but others don't seem to use Foobar presets infrastructure anyway).If I was to make some sort of track-dependent processing then it'd be a separate DSP service. So you would basically have a secondary track-dependent chain in the Foobar's main DSP chain. It'd be universal, not just for VST plug-ins. I don't think it's difficult to make but I just don't see the point. Why on earth would anybody tag separate tracks to process them in a different way? Am I missing something and that's what people actually do? Don't get me wrong, I do realize there are many poorly mixed or mastered recordings. But is tagging every such track an acceptable solution?
I noticed that all plugins using VST have a "preset" checkbox and window that opens up and allows you to save your own presets outside of the actual plugin code. So there must be a way of sending a message to the plugin remotely to load a specific preset.
Well, there are some helpers in the SDK. It wasn't a big deal to import/export whole DSP chain, for example. The way I see it is like this:You put track-dependent DSP in the list of Active DSPs.Then you select tracks you need to process in the playlist and open the context menu to call a command for opening per-track DSP dialog.In that dialog you can build DSP chains the same way you do it in the Foobar's main DSP manager (except for per-track DSPs — you could end up in recursion).Finally you assign either particular state or a preset to tracks you selected earlier. If that's a state then you have your chain immediately assigned to tracks and that's it — you won't be able to edit this chain in a centralized manner. If that's a preset, then you have an opportunity to edit the chain later for all tracks you have assigned it to.Of course, this is not an exact rendition of the final UI. Feel free to make suggestions and ask questions.
Do you see that list with "More Bass" item inside it? That's where you could add your volume boosting presets and apply them on a per-track basis. So there answer is yes, it would be able to handle that.I think I made my previous posting a little bit messy by describing an additional level of flexibility. The idea is that there two ways doing the job: you can either create a preset and assign it to as many tracks as you want (so you will be able to edit that preset later and it will affect all tracks), or you can apply a preset to a track without naming it.