Forums > MaxMSP

probably a bug in the saw~ ?

September 23, 2009 | 10:53 am

hello

this little thing crashes my max when i turn on ezdac:

– Pasted Max Patch, click to expand. –

tested on 2 systems, both Mac platform:
10.5.8 with 5.08, 10.5.7 with 5.07

doesn’t crash when i supply an argument to saw~. also this works fine in the help file where "saw~" got no arguments too.

any ideas on that?

thank you


September 23, 2009 | 12:46 pm

In Max 4.6.3 does not crashes but also does not sound.

#P window setfont "Sans Serif" 9.;
#P flonum 178 231 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 163 251 27 9109513 *~;
#P flonum 350 82 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P flonum 220 81 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 349 108 47 9109513 cycle~ 1.;
#P newex 221 105 54 9109513 phasor~ 50;
#P newex 221 141 139 9109513 +~ 0.;
#P newex 222 173 63 9109513 pong~ 1 0. 1.;
#P user ezdac~ 153 301 197 334 0;
#P newex 164 203 69 9109513 saw~;
#P connect 9 0 8 1;
#P connect 8 0 1 0;
#P connect 8 0 1 1;
#P connect 0 0 8 0;
#P connect 7 0 5 0;
#P connect 6 0 4 0;
#P connect 4 0 3 0;
#P connect 5 0 3 1;
#P connect 3 0 2 0;
#P connect 2 0 0 1;
#P window clipboard copycount 10;


September 23, 2009 | 2:03 pm

Saw~ is an antialized filter, it doesn’t really make sense not to have a signal connected to it to set the frequency. In the next incremental version it won’t crash anymore though. Thanks.


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