tri~ issues

Feb 8, 2006 at 3:06am

tri~ issues

Hello,

I have built a synth that includes the tri~ object. I
have noticed some strange behavior which illustrated
by the patch below. In my synth I am using a line~
object before an mtof~ object. I use the line~ object
to slide between pitches sent to the various
oscillators including tri~. When the slide time is 0
the signal from tri~ seems to phase in and out. It is
most noticeable when the signal passes through an
overdrive~ object which is also part of my synth.
Anyone know why this is happening and how I can avoid
it?

Thanks

sg

max v2;
#N vpatcher 182 44 1076 766;
#P user scope~ 441 394 801 517 13 3 95 -1. 1. 0 0. 0
0. 102 255 51 135 135 135 0;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P newex 358 108 60 196617 loadmess 1;
#P newex 254 337 27 196617 + 1;
#P toggle 254 311 15 0;
#P newex 254 366 115 196617 selector~ 2 1;
#P newex 358 337 40 196617 tri~;
#P message 484 228 20 196617 53;
#P message 442 228 20 196617 97;
#P message 421 228 20 196617 96;
#P toggle 358 132 15 0;
#P newex 358 204 178 196617 sel 0 1 2 3 4 5 6 7;
#P message 400 228 20 196617 94;
#P message 358 229 20 196617 58;
#N counter 0 7;
#X flags 0 0;
#P newobj 358 180 66 196617 counter 0 7;
#P newex 358 155 58 196617 metro 200;
#P newex 254 496 73 196617 overdrive~ 1.;
#P newex 306 311 31 196617 mtof;
#P user scope~ 440 524 800 647 13 3 95 -1. 1. 0 0. 0
0. 102 255 51 135 135 135 0;
#P message 358 259 31 196617 $1 0;
#P newex 358 287 32 196617 line~;
#P user ezdac~ 254 662 298 695 0;
#P newex 358 311 37 196617 mtof~;
#P user gain~ 254 525 24 100 158 0 1.071519 7.94321
10.;
#P newex 306 337 40 196617 tri~;
#P comment 205 312 48 196617 compare;
#P connect 21 0 22 0;
#P connect 22 0 20 0;
#P connect 20 0 9 0;
#P connect 9 0 2 0;
#P connect 2 0 4 0;
#P fasten 2 0 4 1 259 654 293 654;
#P fasten 6 0 8 0 363 279 311 279;
#P connect 8 0 1 0;
#P connect 1 0 20 1;
#P connect 23 0 15 0;
#P connect 15 0 10 0;
#P connect 10 0 11 0;
#P connect 11 0 14 0;
#P connect 14 0 12 0;
#P connect 12 0 6 0;
#P fasten 13 0 6 0 405 251 363 251;
#P fasten 16 0 6 0 426 251 363 251;
#P fasten 17 0 6 0 447 251 363 251;
#P fasten 18 0 6 0 489 251 363 251;
#P connect 6 0 5 0;
#P connect 5 0 3 0;
#P connect 3 0 19 0;
#P connect 19 0 20 2;
#P connect 14 2 13 0;
#P connect 14 3 16 0;
#P fasten 9 0 7 0 259 519 445 519;
#P fasten 20 0 24 0 259 389 446 389;
#P connect 14 4 17 0;
#P connect 14 6 18 0;
#P pop;

#24319
Feb 8, 2006 at 8:08am

Hi Simone,

I want to thank you very very much. I have had several reports of
problems with tri~, and I was able to reproduce them, but I was never
able to figure out just what the heck was wrong with the object. I
wasted many hours exploring all sorts of complicated solutions for
what I thought was the problem, but I was never able to fix it. But
for some reason tonight, after looking at your VERY CLEAR EXAMPLE
PATCH, I opened up the code and the bug was fixed in less than a
minute. Wow that feels good!

A fixed version of tri~ will be in the next Max/MSP update. I am
currently away from my office and don’t have an OS X computer handy,
but I’ll be home tomorrow and will make the fixed externals available
tomorrow night.

Ben

#70167
Feb 10, 2006 at 1:40am

Hello,

just wondering when the fixed version of tri~ might be
available…

thanks….

glad it was a simple fix…

sg

#70168
Feb 10, 2006 at 8:28am

Another problem with tri~ is that when you play a bit with the duty
cycle parameter (expecially if you go a few times from 0 to 1) the
signal become eventually a stream of “inf”s.

#P window setfont “Sans Serif” 9.;
#P flonum 279 111 35 9 0. 1. 3 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P user number~ 287 167 326 182 9 3 3 2 0. 0. 0 0. 250 0. 0 0 0 221
221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 260 139 49 196617 tri~ 130;
#P message 187 312 27 196617 stop;
#P message 187 295 67 196617 startwindow;
#P newex 260 312 29 196617 dac~;
#P user gain~ 260 192 21 89 158 0 1.071519 7.94321 10.;
#P window linecount 2;
#P comment 248 85 100 196617 play with this a few times…;
#P comment 332 167 100 196617 sooner or later you’ll get an “inf” here;
#P connect 8 0 6 1;
#P connect 6 0 2 0;
#P connect 6 0 7 0;
#P connect 2 0 3 0;
#P connect 2 0 3 1;
#P connect 4 0 3 0;
#P connect 5 0 3 0;
#P window clipboard copycount 9;


HomePage: http://www.giri.it
Computer Music Italian Forum http://www.virtual-sound.com

#70169
Feb 14, 2006 at 1:24am

> just wondering when the fixed version of tri~ might be
> available…

It’s available now from the incremental downloads page:

http://cycling74.com/twiki/bin/view/IncrementalDownloads

Ben

#70170
Feb 14, 2006 at 1:25am

Hi Maurizio,

Sorry, but I’m not able to reproduce your bug with the latest version of tri~.

Ben

#70171
Feb 17, 2006 at 2:52pm

#70172
Feb 17, 2006 at 3:46pm

Dear Ben,

unfortunately I still can reproduce it, expecially when I change the
duty cycle very fast a few times…

Ibook g4 1.2 Mhz
OSX 10.3.9
MaxMSP 4.5.6

NB I only have one version of tri~ in my computer. The creation date
is Feb 14 2006

m


HomePage: http://www.giri.it
Computer Music Italian Forum http://www.virtual-sound.com

#70173
Feb 17, 2006 at 5:52pm

I can reproduce this bug on my machine:

OSX 10.3.9
MaxMSP 4.5.6
Newst version of tri~
powerbook g4 1.5 Ghz

I did some digging, however, and I’m finding that the infs don’t seem
to be related to just changing the duty cycle, but rather, subjecting
the duty cycle parameter to “unnecessary” roughness. I can use a
dc-offset [cycle~ 10.] to modulate the duty cycle all day long, and
there’s no issue, but if I run it through [~* 100] -> [clip 0. 1.]…
the min/max values of the resulting waveform from tri~ are… strange.
FWIW.

-David

max v2;
#N vpatcher 10 59 631 618;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P comment 252 288 136 196617 …and magic happens here.;
#P message 253 88 17 196617 1.;
#P message 227 88 23 196617 0.5;
#P message 238 163 34 196617 reset;
#P flonum 156 46 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P newex 156 107 40 196617 +~ 0.5;
#P newex 156 86 41 196617 *~ 0.5;
#P user number~ 193 298 232 313 9 3 3 2 0. 0. 0 0. 250 0. 0 0 0 221 221
221 222 222 222 0 0 0;
#P user number~ 207 279 246 294 9 3 3 2 0. 0. 0 0. 250 0. 0 0 0 221 221
221 222 222 222 0 0 0;
#P newex 193 211 53 196617 minmax~;
#P message 261 106 31 196617 100.;
#P message 238 106 23 196617 50.;
#P message 215 106 23 196617 10.;
#P newex 156 155 56 196617 clip~ 0. 1.;
#P newex 156 131 35 196617 *~ 1.;
#P newex 156 65 58 196617 cycle~ 10.;
#P newex 137 179 49 196617 tri~ 130;
#P message 64 364 27 196617 stop;
#P message 64 347 67 196617 startwindow;
#P newex 137 364 29 196617 dac~;
#P user gain~ 137 235 21 89 158 0 1.071519 7.94321 10.;
#P comment 297 97 79 196617 click on these…;
#P connect 5 0 1 0;
#P connect 1 0 2 0;
#P connect 4 0 2 0;
#P connect 3 0 2 0;
#P connect 17 0 6 0;
#P connect 6 0 15 0;
#P connect 15 0 16 0;
#P connect 16 0 7 0;
#P connect 7 0 8 0;
#P connect 8 0 5 1;
#P connect 1 0 2 1;
#P connect 20 0 7 1;
#P connect 19 0 7 1;
#P connect 9 0 7 1;
#P fasten 10 0 7 1 243 119;
#P connect 11 0 7 1;
#P connect 5 0 12 0;
#P connect 18 0 12 0;
#P connect 12 0 14 0;
#P connect 12 1 13 0;
#P pop;

#70174
Feb 28, 2006 at 6:22pm

Dear tri~ lovers,

I believe we are moving closer to a well-behaved object. Please
download and install the new version at the incremental updates page
at

http://cycling74.com/twiki/bin/view/IncrementalDownloads

Do not hesitate to let me know about any bugginess that persists!

Dutifully yours,
Ben “tri~ceratops rex” Nevile

#70175

You must be logged in to reply to this topic.