mcs.vst~ & mc.vst~ strange behaviour or bug ?
Hi Max,
mc. is a superb opening and improvement for max/MSP but it introduces new questions and some issues.
I have tried to use mcs.vst~ with 8 tracks but only track 1-2 seem to work : check example
Strangely the same patch with mc.vst~ instead seem to work in an odd way : the first instance of 8 control the 7 others which windows are piled one on to of another.
Bizarre !
Either I have not quite understood the help patcher or something goes wrong.
Best regards
Roland
hi
but what is the difference between mc and mcs ??? I never heard about mcs. objects...
mcs.vst~ is a single instance of vst~ with multichannel inputs and outputs
(see in vst~ help patch)
Hey Roland, this is a very old topic but.. Did you manage to solve this problem? I am having the exact problem. I am using a FabFilter EQ and the instance 2 controles the 1st, the 3 the 2nd and the 1st, and so on...
mcs is meant to group all of the vst's outputs into a single multichannel output. it does not create multiple instances of the vst. if your vst only has 2 outputs then the maximum you could get would be 2.
mc is different in that it creates multiple copies of the same vst and all of the ch1 outputs are grouped into one output and all of the ch2 outputs are grouped into the next.