Cycling 74 » Topic: "invalid inlet number" for matrix~ ? http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/feed Wed, 19 Jun 2013 20:12:42 +0000 http://bbpress.org/?v=2.2.4 http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/#post-29453 <![CDATA["invalid inlet number" for matrix~ ?]]> http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/#post-29453 Mon, 01 Jan 2007 07:38:46 +0000 Cheng Chien-Wen The max window in my patch keeps showing “invalid inlet number” when I send a message to connect input (from inlet 11, 12…and more) and output of matrix~. The error message does not happen when I use other inlets before 11. However,the signal does connect well even though the Max window keeps showing the error message. I checked the dump data, and everything is OK.

I tried to save the matrix~ subpatch as an independent patch, then the error message disappears. I was wondering what situation will make matrix~ show “invalid inlet number” message. Is it related to the CPU consumption of my whole patch ?

I am sure I did not send error message command to matrix~ since all the signals are connected as my message commands requested.

Any ideas about why the error message keeps showing ?
I am using Intel-Mac, Max/MSP 4.6

Thanks.

]]> http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/#post-92151 <![CDATA[Re: “invalid inlet number” for matrix~ ?]]> http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/#post-92151 Mon, 19 Jan 2009 07:33:00 +0000 Brian H. Sorry to dredge this up, but it states a problem I’m having exactly and can’t quite figure what the problem is. Do you have to manipulate [matrixctrl] output in any way, or can it be fed directly into [matrix~]?

Thanks,
brian

]]> http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/#post-92152 <![CDATA[Re: “invalid inlet number” for matrix~ ?]]> http://cycling74.com/forums/topic/invalid-inlet-number-for-matrix/#post-92152 Mon, 19 Jan 2009 08:45:28 +0000 Brian H. BTW, I am using [pattrforward] to take the output from [matrixcntrl] and get it to [matrix~] in a sub-patcher. From trial-and-error, it seems like this error is somehow related to one of the pattr’s (?)

]]>