Why do some objects need a number box at the input?


    Apr 10 2008 | 9:06 am
    One example: A [route] with 4 outlets has 4 message boxes attached to set 4 different frequencies on a [phasor]. But it does not work when I connect the message boxes directly to the [route] input. I need a number box in between. Why is that necessary and, mmore generally, when do I need such a thing before an input and when not?

    • Apr 10 2008 | 10:20 am
      Is it just integers you're putting in the message boxes? It could be to do with integer/floating point number handling. a number box converts inputs to integers, which is probably why route is happier with the number box in between. Try using simple integers such as 1, 2, 3 and 4 in the message boxes, and put a number box on the outlets from route to see if it's coming out.
      On 10/04/2008, Peter Ostry wrote: > > > One example: A [route] with 4 outlets has 4 message boxes attached to set > 4 different frequencies on a [phasor]. But it does not work when I connect > the message boxes directly to the [route] input. I need a number box in > between. Why is that necessary and, mmore generally, when do I need such a > thing before an input and when not? > > > -- > Peter > >
    • Apr 10 2008 | 10:51 am
      Quote: notyouraveragejoe wrote on Thu, 10 April 2008 12:20 ---------------------------------------------------- > Try using simple integers such as 1, 2, 3 and 4 in the message boxes, and put a number box on the outlets from route to see if it's coming out. ----------
      There are no numbers coming out, just bang: 4 radio buttons send 0,1,2,3 to the [route]. 4 message boxes with float and int numbers at the [route] outlets. A banged message sets the frequency of the following [phasor]. But not if I connect the box directly to the [phasor], only when I put a float number box between (In need the float).
      Here is the example. If I remove the number box, the [phasor] gets nothing: -------------------- #P window setfont "Sans Serif" 9.; #P flonum 930 241 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0; #P window linecount 1; #P message 990 205 14 196617 4; #P message 973 205 14 196617 2; #P message 957 205 14 196617 1; #P message 930 205 23 196617 0.5; #P newex 930 171 70 196617 route 0 1 2 3; #P newex 930 269 55 196617 phasor~ 4; #P comment 928 82 61 196617 LFO FREQ; #P comment 949 99 40 196617 0.5 Hz; #P comment 949 114 40 196617 1 Hz; #P comment 949 128 40 196617 2 Hz; #P user radiogroup 930 98 18 58; #X size 4; #X offset 14; #X inactive 0; #X itemtype 0; #X flagmode 0; #X set 3; #X done; #P comment 949 142 40 196617 4 Hz; #P user scope~ 930 300 1030 350 256 3 128 -1. 1. 0 0. 0 0. 102 255 51 135 135 135 0; #P user ezdac~ 843 84 887 117 0; #P connect 8 0 1 0; #P connect 9 0 10 0; #P connect 3 0 9 0; #P connect 10 0 14 0; #P connect 11 0 14 0; #P connect 13 0 14 0; #P connect 9 1 11 0; #P connect 9 3 13 0; #P connect 9 2 12 0; #P connect 12 0 14 0; #P connect 14 0 8 0; #P window clipboard copycount 15; --------------------
      Not a big problem of course, but as a newbie I am uncertain about the behaviour of these many objects in various combinations.
    • Apr 10 2008 | 12:54 pm
      I have no problem running the above patch. I took out the number box and connected the message boxes directly to the phasor and it worked fine. Maybe I'm misunderstanding your problem.
    • Apr 10 2008 | 1:53 pm
      aaargh, found the thing ... This patch is ok, it was another one beside it, where I set the phase of a triangle pulse in the same manner. Did not work without a number box. But now I looked at the Max window and saw the problem: "error: triangle doesn't understand "int".
      I am sorry about the false alarm. Should look more at this Max window.
      Thanks, your suspicion that it might be related to int/float handling was correct. It was exactly that.