Maybe this can help to adopt CLAP-only software to run on Zynthian?
(Havn’t tested yet…)
Maybe this can help to adopt CLAP-only software to run on Zynthian?
(Havn’t tested yet…)
Interesting but it does not support native GUI (over VNC). I am working on this feature, investigating using carla but will also compare omx-clap-host (and mod-host) as possible options. If we have full zynthian UI integration, the need for native GUI reduces (see mod-ui for an example of this) but users still like being able to see the native GUI and there are often features that are challenging to integrate into zynthian UI, e.g. Surge-XT has a novel mechanism for assigning modulation paths to parameters.
I am working on this and many changes have happened. One of my goals is to use it in zynthian, so any requests will be kindly considered.
This is the real game changer that hosts CLAP and LV2 unchanged in the same supervisor with plenty of features and security boundaries that are needed for zynthian and my openmixer project.
Have a look at it ![]()
I have sent several patches to mod-host fixing bugs and splitting its protocol into a separate lib but they reamin silent, They only wotk on libreaudio -they are active- and only merge what they need, so I have implemented all what I needed to completely dimiss it.
Audinux carries my mod-host patches, they are in PRs upstream. I might even keep the protocol as a sparate lib to remove this dependency.
I have considered using native GUIs but I got inspiration form zynthina and how you deal with the LV2 params in pages, So I have gone further and have abstracted the GUI in declarative params and the implementaion is a separate thing: I generate the GUI baed on the contract or mod-gui.
I think this way we can re-use the widgets, the dsp functions and avoid dupliucations and implementations that diverge in time. Have a look at the FreeMixer repos, omx-contracts, omx-plugins, all is there.
The gap you name is real: omx-clap-host has no native GUI today, by design in the console, where every panel is drawn from the plugin’s parameters. For the standalone host it is a different matter, and I am looking at opening the plugin’s own X11 window on request, as jalv -s does, so it shows over the VNC display. The rest of what jalv gives you is there now:
Plugin-hostd puts a crashed plugin back with its settings.
On Surge XT specifically, we found a crash in the plugin itself (unclamped unison after a type change) that any host will hit; happy to share the trace.
This is an interesting package that we use to qualify plugin before using them, we do it in batch and at load-time, before using them, to have a profile. We keep the CPU and RAM usage, analyze if they are candidates to run safely in a Reat Time thread (RT) and if they behave as expected. We have detected a bunch of errors always reported upstream.
I hope it can br useful to rank plugins. Again my inspiration had its origiin zynthian when you classified all the plugins. As I am very lazy I prefer to have an automatic process ![]()
PS on plugin GUIs. The host already shows a plugin’s own window over X11, I have not run any of this on a Zynthian yet, so I am not claiming it works there until I can test it. It would help to have a bootable image to automatically test it.
I have a branch devoted to zynthian, I am building a native engine to use plugind-host as the plugin manager,