mattias petersson

i want to use poke~ and count~ in a patch but since my solution keeps writing zeros at sample index 0 when stopped it makes waveform~ flicker. (at least this is what i think happens..)

so, is there a way to turn off waveform~'s auto-updating when writing to the buffer?

please have a look at my simple test patch below.

i remember using similar techniques in MaxMSP 4 without flickering btw.

i want to use poke~ and count~ in a patch but since my solution keeps writing zeros at sample index 0 when stopped it makes waveform~ flicker. (at least this is what i think happens..)
so, is there a way to turn off waveform~'s auto-updating when writing to the buffer?
please have a look at my simple test patch below.

waveform-constantly-redrawing

i made a work around that used gate~ to close the sample index input

but did that really work? because even a closed gate~ will also put out zeros when the signal network is running, right?

but did that really work? because even a closed gate~ will also put out zeros when the signal network is running, right?
it doesn't do it for me anyway..


also, i don't think gate works like that, it shouldn't output anything when closed

thanks, but it's still the same thing you know..

i'm not so sure, i think snapshot will send an output every time it updates anyway

in any case, it doesn't re-draw with the patch i posted on my machine 

you could use the buftime message to control update rate of waveform~ in ms.

volker b�hm wrote on Sun, 07 June 2009 16:06

ah.. 'buftime 0' is the solution. thanks!

volker b�hm wrote on Sun, 07 June 2009 16:06you could use the buftime message to control update rate of waveform~ in ms.

ah.. 'buftime 0' is the solution. thanks!


hm, the smaller the update interval the higher the cpu load.

this is not indicated in dsp status, by the way. use e.g. activity monitor or top (mac) to check the cpu load of max.

a value of 350 works well here for permanent update.

or you might like to set it really high if you don't want it to update...

Quote:ah.. 'buftime 0' is the solution. thanks!

hm, the smaller the update interval the higher the cpu load.
this is not indicated in dsp status, by the way. use e.g. activity monitor or top (mac) to check the cpu load of max.

a value of 350 works well here for permanent update.
or you might like to set it really high if you don't want it to update...


yes, i just realized that. my first thought was that 'buftime 0' meant "off".. stupid me. 

waveform~ constantly redrawing