Jakob Riis

Does anyone else experience this bug where the *~ object are not ignoring integers and floats in the left inlet when a signal is also connected?

number

flonum

comment

loadmess

number~

ezdac~

Does anyone else experience this bug where the *~ object are not ignoring integers and floats in the left inlet when a signal is also connected?

I use Max 7.3.3  - 32 bit Mac

Does anyone else experience this bug where the *~ object are not ignoring integers and floats in the left inlet when a signal is also connec

*~-bug

Did you mean to say "are NOT ignoring"? When a MSP signal is connected to an inlet, ints and floats are supposed to be ignored; that's the correct behavior. If they're NOT being ignored, that would be unusual.

The quotation from the Reference is in fact a bit strange, but the behaviour of the object is ok: if you connect more connectors (signals / control) to the left inlet they will be added (and control connections will be "converted" to constant component signals).

@Chrisotpher - Yes - according to the reference ints ands floats should be ignored if a signal is also connected. But they are not being ignored... Did you if you get this result as well in the attached patch?

@Yaniki - I understand your point, but I think this behavior is kind of "messy"... I think it's a bug...

Workaround in my actual case are be to have a [sig~ 1] in the left inlet and the use the right inlet for both floats and signals, then it get the result I expected in the first place.

@Chrisotpher -  Yes - according to the reference ints ands floats should be ignored if a signal is also connected. But they are not being ignored... Did you if you get this result as well in the  attached patch?

@Yaniki  - I understand your point, but I think this behavior is kind of "messy"... I think it's a bug...

I do replicate what you see. The int in the left inlet is being treated as if it were coming in the right inlet. (Send a number in the right inlet, and it will override the number that came in the left inlet. Then send a number in the left inlet and it will override the number that came in the right inlet. So it appears that a number coming in EITHER inlet is getting treated as if it came in the right inlet.) I agree that this looks like a bug. I suggest that you report it.

i have never seen anthing else during the last 15 years: when you send a number in an inlet of a signal object which also gets a signal the signal is multiplied with this number and/or treated as input of the second inlet.

p.s. and i bet it has been reported 15 years ago :)


i have never seen anthing else during the last 15 years: when you send a number in an inlet of a signal object which also gets a signal the signal is multiplied with this number and/or treated as input of the second inlet.

Yes, I think I reported this to the Max mailing list (!) for the Max 4 version the first time. The actual behaviour is: if you put both a signal and a float on the same inlet (left or right) of a math operator, the signal is assigned to the current inlet and the float to the other inlet. Check the attached image. The reference is still wrong (and the objects behaviour wont change, of course).

*~ bug?