Forums > MaxMSP

bug in selector~ in max 5.02?

May 16, 2008 | 3:30 am

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…

macbook pro 2.4, OSX 10.4.11, max 5.02


May 16, 2008 | 4:14 am

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.



Eli
May 16, 2008 | 4:18 am

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?


May 16, 2008 | 1:24 pm

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

thank you both for the help,

cheers


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