Quote:
Originally Posted by Subsonic808   stike  tutt
Nooooooo, that will not suffice at all. That would be like saying "Only do a mono version. If you need stereo, just use another instance". The last thing I want to do in a 150+ channel surround mix is waste 3 or more insert slots for EQing on every multichannel track. That would be a total waste of time. Plus, I have never heard anyone complain about the routing capabilities in Voxengo or Flux plugins - if you don't need it, don't touch it. |
I think you picture it more complicated as it should be.
Yes the way I propose you'd need to run 4 instances after each other to process all the channels in a 5.1 config, but you also have the added flexibillity of having the plugin window on the centre channel to be open along with the EQ which is on the L-R ch. and the surrounds.
What you don't get when you make the plugin like this is, that you have to setup extra sub-busses to process just to process the centre channel. The plugin should be a 5.1 plugin which processes 1 or more channels, the channels you don't want to process are passed through to the next instance, on which you'll pass-through the channel processed in the first instance. (I assume that the channels that passed-through don't require much processing power, just a time alignment with the processed sound)
Anyway, that's just how I see this, but maybe it is more elegant to do this all within one plugin, but it would either mean the plugin interface will get very large or you'll have different pages on which you can see the different settings of each channel which I find more annoying. (this is basically the same as what you can do with a multi-mono plugin in Pro Tools on a 5.1 buss)
Usually the source tracks in a 5.1 mix are mono anyway, on the busses it's different but that's post-panning.