Sergio Martins

In this patch, i have a selector~ receiving int numbers from a dial object, and i get a messange saying that it doesnt understand floats... can anyone check this out? I did the same patch in 4.6 and works fine...

bug-in-selector-in-max-5-02

The problem is really with dial. It seems to always put out a floating point value.

An int between dial and your subpatcher will work around this problem.

The problem is really with dial. It seems to always put out a floating point value. 

An int between dial and your subpatcher will work around this problem.


I think this is not a selector~ problem but a dial problem. Dial is outputting floating-point numbers even when outputting whole integers.

A quick fix is to have the dial connecting to a [number] object either inside or outside of the patch, changing the floating-point numbers into integers.

Did the programmers intend for [dial] to always output floats?

I think this is not a selector~ problem but a dial problem. Dial is outputting floating-point numbers even when outputting whole integers. 

Did the programmers intend for [dial] to always output floats?


Ah, thats right, the dial, i checked it with a print...

bug in selector~ in max 5.02?