Hi, today I encountered something which seems to be a bug in wrap~ (pd-0.49.0) on my architecture. The attached patch shows that wrap~ ist outputting a 1 instead of the expected 0 when inputting the division of 880 by 220. Inputting the value 4 with sig~ to wrap~ doesn't cause this, so I assume the result of the division is represented differently internally. This is on 64 bit Linux.
The pd sources contain two versions of wrap_tilde_perform with a comment that a similar bug had occured in a previous version before and been fixed but somehow it doesn't seem to be resolved completely. Does anybody have/know a fix? It is pretty important in my code as this causes all kinds of strange behaviour in my dsp calculations. Maybe people on other systems/architectures could also check if it appears on their machines as well and report back. -- Orm
#N canvas 697 134 484 401 10; #X obj 27 255 wrap~; #X obj 28 197 /~; #X msg 28 174 880 220; #X obj 363 124 metro 100; #X obj 79 232 snapshot~; #X floatatom 79 255 5 0 0 0 - - -; #X obj 28 306 snapshot~; #X floatatom 28 329 5 0 0 0 - - -; #X obj 311 40 loadbang; #X msg 286 106 \; pd dsp 1; #X msg 363 94 1; #X obj 266 260 wrap~; #X obj 318 237 snapshot~; #X floatatom 318 260 5 0 0 0 - - -; #X obj 267 308 snapshot~; #X floatatom 267 331 5 0 0 0 - - -; #X obj 267 197 sig~ 4; #X text 30 352 this shows '1' on my system; #X text 265 352 this shows '0' on my system; #X connect 0 0 6 0; #X connect 1 0 0 0; #X connect 1 0 4 0; #X connect 2 0 1 0; #X connect 3 0 4 0; #X connect 3 0 6 0; #X connect 3 0 12 0; #X connect 3 0 14 0; #X connect 4 0 5 0; #X connect 6 0 7 0; #X connect 8 0 9 0; #X connect 8 0 10 0; #X connect 8 0 2 0; #X connect 10 0 3 0; #X connect 11 0 14 0; #X connect 12 0 13 0; #X connect 14 0 15 0; #X connect 16 0 11 0; #X connect 16 0 12 0;
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list