Yep, having it too.
I was really unhappy with that at first, mostly because I was thinking Protools…
Turns out I rethought my workflow and stopped using badly dev plugs like waves.
Where do thy get that idea that some plugins should be mono an or stereo and just others surround ? Nonsense. It is that way because of the conception of soundesigner ii / protools in the first place.
Should have been updated a long time ago.
Some vst3 plugins work brilliantly for surround, like flux.
You just put the plug you need and it appears in the right format.
I do use wns though, but I put them on sources tracks and never on 5.1 busses.
But anyway, even with vst3 plugs, you simply cannot make different adjustments for front/rear or a channel basis for instance.
At least for now…
I used to think it was a big drawback (even a show stopper) for Nuendo, now I’m just used to it.
I have to say that even if I certainly wouldn’t want to see a protools multi-mono conception here, it could be really interesting to target different channel(s) with the same plug instance and different adjustments.
But maybe not by default.
If I may ask, why don’t you use wns on the source channels pre-panner ? It really is soft on CPU.
Of course you have to automate them individually, instead of one instance, it’s true…
Maybe that could de be a feature request, if not already…