Hi @iurienistor,
I welcome you to the forum and thank you for your interest in supporting the Zynthian project easier integration GeonKIcku into it’s environment. I’m just a user trying to give feedback to those developing the whole system. Fortunately, there are more of us such users. @jofemodo is the boss here. @riban is the driving force behind programming and coming up with new Zynthian features. Now he and others are busy preparing the new Bookworm Oram 64bits image, which moves Zynthian from 32bits to 64bits. I also have to thank him for entrusting me with moderation in this area, even though I’m a complete layman in this, who can only twirl the knobs.
Focusing on the integration of GeonKick into the Zynthian environment, I realized that it is important to know:
Jalvhost is used for hosting LV2 plugins- Zynthian supports
LV2 Control Ports
I found it in the thread Hosting LV2s which will tell you more than me.
I will describe my idea of integrating GeonKick into the Zynthian environment from the user’s point of view, and hopefully the right people will respond to technical questions.
Based on what exists in Zynthian, there is a LV2 DrumSynth plugin, which is close to your GeonKick in terms of control philosophy. It even has graphs for setting the course of parameters over time, but I would say that it is statically limited to 4 setting points. DrumSynth for 24 sounds displays a total of 654 pages of settings. I have described it here from the user’s point of view.
An example of the last page is in the picture.
Zynthian has a wonderful feature that each of the parameters that appear in its UI can be mapped by a simple mechanism (for the user) to a specific CC. This is detailed in the wiki Zynthian UI User Guide - V1/V4 - ZynthianWiki
If I convert the image to pseudo code, I would describe this page as:
Name_page: Ctrl#654
Ctrl_1: Dist on
Ctrl_2: Clipping
Ctrl_1: Bits
Ctrl_2: Rate
In the case of GeonKick, for example, for Level 1 L1 Oscillator 1, I would have accessible settings on 3 pages of the Zynthian UI:
Name_page: L1 Osc 1 #1
Ctrl_1: Oscillator 1 (values: ON/OFF)
Ctrl_2: Wave Function (values: Sine/Triangle/Sample/Square/Sawtooth)
Ctrl_1: Phase
Ctrl_2: Amplitude
Name_page: L1 Osc 1 #2
Ctrl_1: Frequency
Ctrl_2: Filter (values: ON/OFF)
Ctrl_1: Filter Frequency
Ctrl_2: Q
Name_page: L1 Osc 1 #3
Ctrl_1: Filter type (values: LP/BP/HP)
Ctrl_2:
Ctrl_1:
Ctrl_2:
I would resign from the possibility to set Amplitude and other parameters depending on time, which are done by clicking on the graph. Here, the number of points is generated dynamically, apparently.
From the user’s point of view, usually, working with the filter frequency is more important when playing live.
But here I also see a weaker element of my proposal. The standard range of 0-127 for CC messages is very rough, especially when setting the oscillator frequency, when I imagine it should work across the range. Here, it would probably be good to be able to set some lower and upper limits. But I’m going into too much detail.