Forums > MaxMSP

Issue with (matrix~) and sub patches

December 27, 2009 | 11:50 pm

Hey everyone,

If you saw my earlier post about having patch-bay type arrangement, I have now got that working with thanks to Luke Hall, Wetterberg, My old college tutor Tim and my old man! What a mission!

Now this has brought up an issue that was actually the root of the problem all along.

When signal goes out of the matrix and back into it again if it has a direct through, in the case of a delay unit where you mix the dry and wet sound, it appears to short the matrix unit out (virtually of course).

Is there a way around this?

Here is an example of where this happens

– Pasted Max Patch, click to expand. –

If you connect any of the three example effects to the matrix the uni shorts, whereas if for instance you were to put (tapin~)(tapout~) objects in the dry signal line in any of the effects and then connect it up the system works.

I am sure this is not how it is meant to be, or if it is, there must be a better object to use then (tapin~)(tapout~)

Any help or guidance is much appreciated

Cheers

Ben


December 28, 2009 | 12:43 am

This is where you need to use the [send~] and [receive~] objects instead of connecting the outlets back into the inlets. Using [send~] and [receive~] creates one signal vector of delay and means that the [matrix~] doesn’t attempt the impossible and blow itself up. Make this change and everything should be alright.

lh


December 28, 2009 | 1:25 am

AWESOME!!! Cheers Luke!

Life saver, not quite sure what a "signal vector of delay" is but I like it! I shall look up more about that so I can document it for uni.

Ben


Viewing 3 posts - 1 through 3 (of 3 total)