[PD] "wrong" floating point values in pyext

day 5 day5ive at gmail.com
Mon Feb 20 16:30:20 CET 2006


hay guyes what's goin on in this thraed lol ?

#N canvas 480 195 240 203 10;
#X obj 23 119 / 100;
#X obj 24 145 prepend set;
#X obj 23 93 counter 10000;
#X msg 24 172 26.36;
#X obj 66 118 sel 100;
#X obj 123 118 s \$0-turnoff;
#X obj 23 7 r \$0-turnoff;
#X obj 68 52 nbx 5 14 -1e+37 1e+37 0 0 empty empty empty 0 -6 0 10
-262144 -1 -1 2 256;
#X obj 21 30 cnv 15 147 17 empty empty empty 20 12 0 14 -245368 -66577
0;
#X obj 23 71 metro 2;
#X obj 23 30 tgl 15 0 empty empty empty 0 -6 0 8 -262144 -1 -1 0 1
;
#X text 47 30 << click to start;
#X connect 0 0 1 0;
#X connect 0 0 4 0;
#X connect 1 0 3 0;
#X connect 2 0 0 0;
#X connect 4 0 5 0;
#X connect 6 0 10 0;
#X connect 7 0 9 1;
#X connect 9 0 2 0;
#X connect 10 0 9 0;


./d5

On Feb 20, 2006, at 6:00 AM, geiger wrote:

> floating point is not very good at representing some numbers, it can 
> only
> do it approximately, this is also troublesome if you want to build a
> counter that counts by 0.01 increments and stops if the sum == 100
> This will not work, because it never sums up to 100.
>
> Guenter





More information about the Pd-list mailing list