I'm trying to use mc.maximum~ to tell me the maximum value of all incoming channels. However, this does not appear to be the correct usage for mc.maximum~. Consequently, I'm confused as to what, exactly, mc.maximum~ does.

The attached patcher explains both my expectation and my confusion... Any comments that would enlighten me would be appreciated...

mx.maximum_question.maxpat

Hi,
I'm trying to use mc.maximum~ to tell me the maximum value of all incoming channels. However, this does not appear to be the correct usage for mc.maximum~. Consequently, I'm confused as to what, exactly, mc.maximum~ does.

The attached patcher explains both my expectation and my confusion... Any comments that would enlighten me would be appreciated... 

Hi,
I'm trying to use mc.maximum~ to tell me the maximum value of all incoming channels. However, this does not appear to be the correct usa

mc-maximum~-expectations-vs-reality

It appears that *I'm* not that sophisticated..

Unfortunately, I don't understand how your patcher addition answers my original question or the one about negative values that's posed within my patcher.

Let me ask the question in another way to be more clear...

1. comparing the value of an incoming signal to a constant value (e.g. 

 - which will tell me which is larger, the signal value or 0.5.

2. comparing two signal values (by connecting two signals to the two inputs of a 

 object) and telling me which of the two values is higher.

 object would be able to behave in both of these two modes, however, it appears that only the first mode is possible. This is the easy one...

However, when I connect an "mc." signal to both inputs of an 

 object, the behaviour is a little different (as shown in the right-hand panel in my original patcher).

I'm asking how to get that second mode to work using an 

 object - or whether it's possible at all.

The maximum~ object can be used in two ways:

1. comparing the value of an incoming signal to a constant value (e.g. maximum~ 0.5 - which will tell me which is larger, the signal value or 0.5.
2. comparing two signal values (by connecting two signals to the two inputs of a maximum~ object) and telling me  which of the two values is higher.

I would expect that an mc.maximum~ object would be able to behave in both of these two modes, however, it appears that only the first mode is possible. This is the easy one...

However, when I connect an "mc." signal to both inputs of an mc.maximum~ object, the behaviour is a little different (as shown in the right-hand panel in my original patcher).

I'm asking how to get that second mode to work using an mc.maximum~ object - or whether it's possible at all.

 with no argument AND no signal in the right inlet is comparing the value of an incoming signal to a constant value of 0. it seems (i.e. 

 is actually multiple independent instances of 

 that operate on each of the audio channels independently, and cannot compare between them.

See here: https://docs.cycling74.com/max8/vignettes/mc_wrapper

Geoff,

A maximum~ or mc.maximum~ with no argument AND no signal in the right inlet is comparing the value of an incoming signal to a constant value of 0. it seems (i.e. maximum~ 0.)

An mc.maximum~ is actually multiple independent instances of maximum~ that operate on each of the audio channels independently, and cannot compare between them. 

So the only remaining (but tangential) question is why it behaves the way it does when you connect mc signals to both inputs...

mc.maximum~ : expectations vs. reality