Jeff Greenlee

I don't know if It's just my Mac or if this is expected behavior:

When I use the scope~ object, I notice it is static, and only updates the waveform if you click on the object. Is this normal? I have googled around for a discussion on this but haven't found anything. It seems surprising behavior to me because most Electronic music software scopes are .... ahem.. (pardon the pun) "live". and reflect the change in a waveform in real time. I should be able to change the frequency of a sin or trangle wave and see the wave form change without having to click on it, right?

So either that's the way it's supposed to work, or I'm missing something. The reference for the object mentions parameters "calccount" and buffersize .. but playing with eithe doesn't change the behavior.

Also, I notice that the scope~ object doesn't a change in amplitude... is that expected?

I don't know if It's just my Mac or if this is expected behavior:   

When I use the scope~  object, I notice it is static, and only updates the waveform if you click on the object.  Is this normal?  I have googled around for a discussion on this but haven't found anything. It seems surprising behavior to me because most Electronic music software scopes are .... ahem.. (pardon the pun)  "live".  and reflect  the change in a waveform in real time.    I should be able to change the frequency of a sin or trangle wave and see the wave form change without having to click on it,  right?  

So either that's the way  it's supposed to work,  or I'm missing something.   The reference for the object mentions parameters "calccount" and  buffersize  .. but playing with eithe doesn't change the behavior.    

Also,  I notice that the scope~ object doesn't a change in amplitude... is that expected?

max-for-live-scope-object-is-it-static-until-clicked-on

hey, no, the behaviour you observe is not normal. Unless you have some specific waveform coming in, which should be solved by fiddling with calccount and buffersize. The bug you observe is maybe due to an uncommon sampling rate, or I/O latency vector size, or buffer vector size, or because the graphic scheduler is too busy, or because something is not right in your patch, or because there is a bug...

I'm sorry I can't help with this - I'm here to say I'm seeing the same problem. This is with Max for Live.

I/O vector size is 4096 and Signal vector size is 64, neither seems to be modifiable. Have been fiddling with buffer and Calccount too but to no avail. Any ideas?

I'm sorry I can't help with this - I'm here to say I'm seeing the same problem. This is with Max for Live.
I/O vector size is 4096 and Signal vector size is 64, neither seems to be modifiable. Have been fiddling with buffer and Calccount too but to no avail. Any ideas?
Many thanks in advance


Max for Live scope~ object. Is it static until clicked on?