Cabbage Logo
Back to Cabbage Site

Creating custom UIs with Cabbage 3

#81

Just tried with the most recent version, seems like nothing changed. I assume it’s nothing to do with me trying to run the react project like normal on my browser considering it can’t the function as a whole

#82

That’s probably the issue. If the UI is not launched by Cabbage using its own webview component, then that function won’t exist. It’s injected into the window at runtime by Cabbage. The best is to export a plugin, launch the plugin in reaper, save the plugin. Now start modifying the contents of its resources folder with your own custom scripts. When you want to refresh the plugin, just use Reaper’s open command, it’s the quickest way to reopen and instantiate the plugin after you make changes.

#83

would rescanning in ableton do the same thing?

#84

once the plugin is seen you don’t have to rescan again. Just reopen the project, or delete and add the plugin again

#85

oh alright! great, will get to work then

#86

Got it to work! Wondering how to feed audio back into the js now for some fun visuals…

#87

You can just pass an array of samples to the JS front-end. I’ve shown an example here with the genTable widget, but you can develop, or intercept that information any way you like. Be careful that you don’t flood the webview with too much data.

#88

Hi Rory, it’s been a long time!

How stable is Cabbage3 now? Do you recommend to stick with Cabbage 2 if I need to release plugins and distribute them?

Thanks!

Julien

#89

I think if you wish to develop your own interfaces and stay away from the drag and drop stuff in Cabbage 3 then I think it should work fine. The basic system is extremely simple and lightweight. As for distributing web-based plugins, you’d be the first to try this with Cabbage. Do you have a particular idea in mind?

#90

I’d like to leverage some fancy audio visualization libraries for my plugins, but regarding the controls it should be quite straightforward (sliders, knobs, buttons, presets selectors)

#91

If you want to give it a go, try installing the latest beta build. Then use the command palette to create a new vanilla plugin project. This will place a .vst3 in your vst3 folder, and all the projects resources into your library folder. It creates a simple Csound based plugin with vanilla UI using html/js. From there it’s very simple to build your own interfaces from scratch using whatever frameworks you like. However, if you need to distribute stuff you’ll need to statically link Csoud to avoid users having to install Csound.

1 Like