Why is the plugin-Envirionment GUI different for JFXes vs. VSTs ?

For JFSXes the plugin-environment GUI lacks some important features: - you can't switch off PDC - the wet/dry knob does not acknowledge PDC by inserting an appropriate delay to the dry path (which it does for VSTs) - you can't select Midi Buses (which the JSFX plugin would see/send as Bus 1, alike single-Bus VSTs do) All in all it would be a lot less confusing, if the plugin-environment GUIs would be identical. -Michael

Regarding the midi buses - these are easily set within the JSFX itself - and many JSFX's I have created need to dynamically change the bus routing depending on the midi received - so if this was to be added to the main GUI - I would hope that the buses could still be changed dynamically within the JSFX code.

Of course I do know this. I also did JSFXes using Midi buses. But there are "standard" users, who don't do JSFX programming. They should be able to use Midi Buses with JSFXes that are not aware of buses (ie by far the majority) - in the same way as they are able to use buises with VSTs-. -Michael

Regarding Midi buses, of course it needs to be possible not to filter the message for a dedicated bus when the plugin is a JSFX, while it always needs to be filtered for a single bus with VSTs (which never are aware of buses). But most JSFXes also are not aware of buses and the filter should optionally be provided for them as well. I suppose it would be enough if for JSFXes the "Midi Bus 1" setting for Midi in and out, in the menu would be replaced by "All Midi Buses" with in and "provided Midi Bus" , with out. Or such options could appear additionally in the menu. I don't see much backward compatibility problems in doing so. Anyway it's horrible for the guy who does the User guide that the (rather complex) Midi bus feature is even more complicated by working differently on JSFXes and on VSTs. -Michael (recently having tryed to help with the Guide)