Roland Cahen

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

comment

textbutton

flonum

loadmess

message

mc.dac~

umenu

mc.mixdown~

mc.gate~

multislider

mc.train~

mc.*~

number

slider

mc.live.gain~

mc.phasor~

mcs.vst~

toggle

ezdac~

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.

mc.vst~

Either I have not quite understood the help patcher or something goes wrong.

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 !

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~ w

mcs-vst~-mc-vst~-strange-behaviour-or-bug

but what is the difference between mc and mcs ??? I never heard about mcs. objects...

I tried to use [mc.vst~] but it does not work properly (as to polyphonic processing of each parameter of VST).

Here is a simple example (requiring VSTi "Dexed"), in which I send one exclusive messege to [mc.vst~] , yet it's effecting all the channels.

mc_vst_bug.maxpat

hi, I am a novice of Max.
I tried to use [mc.vst~] but it does not work properly (as to polyphonic processing of each parameter of VST).

mcs.vst~ is a single instance of vst~ with multichannel inputs and outputs

mcs.vst~ is a single instance of vst~ with multichannel inputs and outputs
(see in vst~ help patch)


Seems to be really limited to 2 tracks... is it a bug ?

Hi,
Any news about mcs.vst~ ?
Seems to be really limited to 2 tracks... is it a bug ?

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.

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. 

mcs.vst~ & mc.vst~ strange behaviour or bug ?