Sidechaining

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Now we have the glorious Modular Plugin Area, using side chaining VSTs should be easy in LUNA. Unfortunately... LUNA doesn't appear to like displaying more than a single stereo in, however many the plugin has declared.

Take Chunkware Vanilla Compressor, for example. Plugin Manager happily lists it as having 4 inputs. But insert it, and it's only got a single stereo input. Exactly the same applies with Slim Slow Slider's Side Chain Compressor.

More examples in the Effects forum.

Post

It's this typical problem:

Vanilla comp indeed has 4 inputs, but it doesn't declare these inputs as 2 x stereo.

I.e. it doesn't respond on the "effGetInputProperties" vst opcode.

And so LUNA sees this as 1 input with 4 channels.

Don't forget LUNA is fully multi-channel oriented.

Conclusion: If a vst plug has multiple input "jacks", it should properly process the "effGetInputProperties" opcode!

Post

Ah, I see! :) Okay, that explains it. In that case, as it's such a common problem, can we have some combinator plugs in the MPA to get around this? That is, a plug that can have its number of inputs and outputs configured to overcome mismatches like this. (Or maybe allow the inputs/outputs on each plugin to be reconfigured directly?)

Post

Maybe a micro version of a Tracktion rack, that serves as a wrapper around one plugin. The user can control what inputs / outputs the wrapper presents to the MDA and the routing of this interface points to the gozindas and gozoudas of the plugin.

DaveL
You can twist perceptions, reality won't budge.
-- Rush Show Don't Tell

Post

I've added a note about this on the whishlist:

A way to regroup a vst plug's I/O. Cause some vst plugs dont do "effGetInputProperties" or "effGetOutputProperties". Probably via the Plugin Manager.

Post

That would mean the configuration applied to all instances of the plugin. What about plugins, like Kontakt2, that can dynamically regroup their outputs? (Fortunately, K2 seems to work, although I've not tried anything that fancy in LUNA.)

Post

Do you think that is a big problem?

Anyway, giving a global solution (i.e. where all instances will share the regrouped io info) is definitely step 1. This will work via the plugin manager, or maybe just by editing vstplugins.xml.

And this should already be a big step forward to workaround these "problematic" vst plugs.

And i think that IF a plug is able to change its IO, it will also respond to the relevant vst opcodes, as we're then talking about the more "pro" plugins.

What do you think?

Post

I think you're probably right! :)

Post Reply

Return to “MuTools”