yeah, I just don't think it's as smooth for regular scopey things - it's great for visualising audio, especially the spectral and buffer-showing stuff. It also appears the "defineline curve" doesn't work properly, so I can't get that interpolation looking properly :(
And lastly, I think it's great to be able to do a small gl window OR integrate the reading into a greater gl context in the group.
You might be a step ahead of this already, but there's no reason you couldn't use jit.catch~ to create that running buffer and send its output matrix to any appropriate gl object. Making ctlmatrixes for jit.gl.nurbs like this can be nice, for example.
This should get you into the ballpark; the example uses plain vanilla jit.gl.graph, but like I said, that matrix could go anywhere…
yeah, I've been doing a/b testing tonight to see, why catch isn't really up to the task for me. It's acting weirdly, BUT it's phase-locky-scope-emulating "mode 3" is *really* good, better than the scope~, from what I can tell.
Some cool stuff in there Graham, I really like waaa.qt.wave~ too.
I'm hoping that some more aesthetically pleasing scopes are on the way... Plot~ can be a bit nicer, but I often finish something and think that scope~ and waveform~ let it down aesthetically. They look pretty dated when compared to current software/plugins.