Scope~ doesn't seem to be working anymore
hooked up a cycle~ to a scope~, and can't get anything to show on the scope. Audio is on, I fooled with display range and catcount, Nothing changes. It's also not working in the help menu. Anyone else having issues?
Taking your description literally, yes, if you connect a cycle~ to a scope~ you will see nothing. That's because the frequency of cycle~ is 0 by default, so it's outputting a constant signal value of 1, which doesn't look like much of anything in scope~.
If, on the other hand, your cycle~ object has a nonzero frequency and you still see nothing, try restarting Max and rebuilding a simple test patch like the one above from scratch, and then if you still see nothing, post your patch and a full description of your system (Max version, OS version, etc.).
Thanks for the feedback!
I had actually set the cycle~ to a number of different frequencies, with the same non result. That said, I did try the test patcher with a restart and scope~ still is showing anything. It also shows nothing in the help file or tutorial.
Running Max 7.3.3 64 bit
Intel Core i7-4810MQ 2.8Ghz, 16G Ram, Windows 8.1
Got it. Yeah, your patch works fine on my Mac, so I'm guessing it's related to your install of Max or its interaction with your OS/computer. If it were I, tedious though it may be, I'd probably try reinstalling Max. Since I'm on Mac, I probably can't be of much help to you beyond that suggestion.
I have the same problem. Scope used to work, and now it doesn't. Also running windows 10 and latest version of max 7. Other displays work fine (e.g. spectroscope). This is quite irritating. I submitted a support request. Note that scope does work in Max 8 (which i can test using ableton 10). How long until Max 8 comes out?
UPDATE: I found the problem, my Signal vector size got set to 1 somehow. (I/O vector size was 256). I changed it to match io vector size and it is working fine. Not sure what it should be, but that is working.!
Now i wish i knew how to unreport a problem!
There seems to be a separate issue with scope~. Folks were discussing it here.
https://cycling74.com/forums/scope~-with-triggernone-doesn't-initialize-properly