An obligatory scrolling waveform example 
Finally, a better way of doing realtime graphics
2 Likes
That looks insane!
How will this work in an exported plugin? very curious to see where this is going
Should work just as it does in the videos posted above. I’ve been trying to send fft data so we can make some fabfilter like spectrograms, but it seems to get a little slow. It’s till early days, perhaps I’m chocking it somehow 
[edit] I have this working faster now. When I get time I’ll try to port @oeyvind SVG spectral display instrument using something like snap.js or svg.js. The improvement in performance should be remarkable.
2 Likes
Is this the way of the future? Moving away from JUCE?
Not at all. JUCE gives us the wrappers for all the plugin formats, and much more, This is just a way to generate nicer, and far more efficient graphics.
Fantastic 
It looks insane! Can’t wait to try it
1 Like
This is so great! Any E.T.A. when it will be inside of Cabbage?
I’ve really gone down a rabbit hole with this 
I’m at the point where I think I can implement it without using websockets at all. As for ETA, I can’t really give one. I’m swamped with real work at the moment 
Hi Rory,
Is it still in the pipeline? Can’t wait to try it out 
I think @Andy.Fillebrown is almost ready with the new websocket opcodes. Once they are ready I will implement this. I’m doing something similar in another project right now, so I have most of the part already complete, so with any hope it shouldn’t take too long to get it up and running.
2 Likes
Hi Rory,
You probably saw I’m working more and more on plugins using Cabbage, thanks again for this framework it’s a pleasure to be able to release plugins using it!
I’d like to refactor the UI of my previous plugin and add a scrolling waveform (or anything that could indicate how the plugin catches transients and visualize it). Do you think this webview component will be implemented in Cabbage soon? Otherwise I’ll probably use a less performant approach and try to find workarounds.
Thanks!
Julien / nymano
I have to wait till the next release of Csound before I can implement this as the new websocket opcodes depend on an API change. @Andy.Fillebrown (who wrote this new opcodes) has made the relevant PRs and they have been merged into the Csound6 and Csound7 branches. So we’re just waiting on the next point release of Csound6. Once that’s out I can start rolling out these updates. I’ll ask the Csound devs now when they expect a new release for Csound6.
1 Like
But I’d say in the meantime, you might be as well off to use one of the less performant ways of doing it. It will be one thing to get this implemented, but I imagine it will need quite some testing once it’s in the wild.
1 Like
Thank you! I’ll try this implementation then: Continuous display of audio data
If it doesn’t work I’ll try to be creative
I have a feeling this option may need to be explored!
1 Like
Hi there
Where are these new websocket opcodes that @Andy.Fillebrown wrote? I could not find any PR or anything in the source tree. Do they work with arrays?
Hi @mesca, welcome to the forum. You can find those plugins here:
You’ll need to build yourself but the last time I tried it was pretty straightforward.
1 Like
Perfect. Thanks!