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

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

----------begin_max5_patcher----------
582.3ocyV1saaCBEG+ZWo9Nf7kScQFrINdOH6lopIBljxjMXYvJosZ4Ye.Nt
0oMo9i3jra.oCb37+7CN.ud+cd9KkaYJevO.+B348pwhmyl0hWiAO+bxVZFQ
4lnufsQt7O9OreLMaq1YufWv.3f2FPTkKqzYLsyMXi4URgVPxYNe9IqLkHHu
4SsC5mKX0Zx2G7XaGU7Wbi.QyBZryScKkQSeGdPz4hlfiZrVPzzm3h0+tjQ0
0gHL1rT.HbtsCissH3r.viNW9682Y6McOb1.JSRRyYJEPoIk5MbQpbysjVIG
GVvNg0hDGxhlBXQk44Lg9yzhjWjw0UorSfnfdgnhRlxr7DMWJZkGQgQtDwso
GruYPvawHfWTnMRgt3EGeIgmIqkYU1j9rnWO3P7H3v75RNDdx.gI1KYkmHWQ
iqXhaAKveIQrtUckIr77pb6bRvcwICPZlbD9Hva9HfGLrE7vAS.7VkIMgeZg
mYMIcfufYIIC.fAyPGgf3gSPzhEtxvvICfrWRIzccUo0R0Qi9Yp56beu8LTs
hJKXcp5kUqZ1Xd+7NkjQoxJg9Pysxvvgmgn.nKEquP.VeMoq6B7V721YNPEi
m1meU70BR1vdDFMZPk3ZwIWverPellw1YB3smSvQyo5m5iOcgdsN7y3hO8UX
2pZG3CzSIqJoMoSyOOAs9AQJSo4B22NZMqnCmzS7zTl3fxsbdZgz7xydg7U6
o8VaI8QZeLAtRZadezV3+2RCd0kFtORCcSjFruR65ughtNm0rFLc+CfvYZlw
-----------end_max5_patcher-----------

Brendan

http://cycling74.com/forums/topic.php?id=26095

Hi.
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

hth
aa

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.