Forums > MaxMSP

scope object

Aug 01 2010 | 12:12 pm

unfortunately i have the problem that the scope object doesn`t show anything if it is feeded with an audio oscillator signal…i have tried out all the given examples…no success!
I use msp/jitter as a student version on windows 7 (64bit).
Please help!

By the way…is there a way to see that jitter was really activated?


Aug 01 2010 | 2:03 pm

I have this problem even if the firewall etc. is switched off…is it really recommended to use msp/jitter on windows 7 64 bit? …or is it just something i do incorrect…?

Aug 01 2010 | 3:04 pm

if jitter is in demo mode the console will show "jitter is in demo mode"

Aug 01 2010 | 5:07 pm

make a new object, type into it and the Max window will report whether or not you have a full Jitter install

Aug 01 2010 | 6:44 pm

Any suggestions concerning the scope object?

Aug 01 2010 | 7:13 pm

try this patch; if the [scope] object isn’t working, then post your patch

— Pasted Max Patch, click to expand. —


Aug 01 2010 | 7:26 pm

hey brendan, thx for your help! unfortunately i don`t know how to use the posted code…could you give me hint where to look in the manual?

Aug 01 2010 | 10:25 pm

here we go…

— Pasted Max Patch, click to expand. —
Aug 02 2010 | 10:40 am

your patch is ok (though I don’t like at all your dsp to be turned on automatically!)

two typical reasons for your scope~ not working might be:
– you don’t have a valid audio driver selected (you can try to set "none", and then set back your chosen driver)
– your signal vector size is 1 (if you are not sure, try with 512 for both signal and i/o vector size)

you can check both these settings in Options/DSP Status


Aug 02 2010 | 12:50 pm

YESS…thx a lot!!

i set the signal vector size to 256 (512 is not offered in the menu bar) and it works! finally i can switch off the tv set and watch funny signals with the scope~ object! Thx

Great forum! hopefully i can help someone some day

Apr 16 2015 | 7:24 am

Thank you, Andrea Agostini, for pointing out that a difference between the I/O Vector Size and the Signal Vector Size could cause more troubles. Many people have been complaining of High CPU usage for no particular reason and the answer is the same… mismatched values between the I/O Vector Size and the Signal Vector Size. It seems that different installs/updates will possibly play around with these numbers.

Thanks again.

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

Forums > MaxMSP