scope~ problem.

Feb 8, 2006 at 4:16pm

scope~ problem.

scope~ does not seem to be producing any graphical output anymore. I literally booted up as normal and it’s stopped working. My friend who owns the computer mentioned that he had performed a cleanup which involved the removal of some Java installation, possibly the SDK or the Runtime. I don’t know if this affected it, but it was working fine before.

Has anyone had a problem similar to this, or know of any reason why this might happen?

#24328
Feb 8, 2006 at 4:55pm

I have noticed this problem as well. If I start max,
then bring up the scope~ help file. It does not work.
And yes I selected wave input.

Anthony

#70224
Feb 9, 2006 at 3:29pm

Anybody else experiencing this isssue?

#70225
Feb 9, 2006 at 4:05pm

What’s your signal vector size? Scope~ doesn’t do anything (it seems) if
it’s set to 1.

#70226
Feb 9, 2006 at 4:55pm

AH HA! My vector size IS 1! Wich leads to the question,
what should my vector size be?

Anthony

#70227
Feb 9, 2006 at 6:04pm

On around Feb 9, 2006, at 17:55, apalomba@austin.rr.com said something
like:
> what should my vector size be?

Depends on what you want. Discussed at length in Getting Started.

Short answer: for many purposes 256 or 512 are good compromises.

>
————– http://www.bek.no/~pcastine/Litter/ ————–
Peter Castine | ^
| Litter Power & Litter Bundle for Jitter
pcastine@gmx.net |
pcastine@bek.no | iCE: Sequencing, Recording, and Interface Building
4-15@kagi.com | for Max/MSP
| Extremely cool
| http://www.dspaudio.com
| http://www.dspaudio.com/software/software.html

#70228

You must be logged in to reply to this topic.