Blue Cat Audio • KUIML Persistence

I am evaluating Blue Cat Audio Plug n Script and feel as though I am slowly understanding some of the broader concepts. However, despite some excellent documentation available both from Blue Cat and LetiMix, for some reason I'm having some difficulty getting over a couple of hurdles.

For context, I am familiar with writing plugins using JUCE and have also evaluated HISE, so I come to this with a general understanding of the separation of duties between the DSP and UI and the asynchronous nature of communication between them.

Let me start with the most immediate question I have and based on the response we will see in what order I should tackle any remaining questions. This question has been asked before (viewtopic.php?t=601452) but was not answered.

In short, I am wondering whether I am able to declare PARAMs in my KUIML skin and have those persist to a preset. Further - am I able to declare such PARAMs as an alternative to declaring inputParameters in my DSP script?

I understand that I can declare a PARAM in KUIML and specify that I want it to be persistent. However, I am not understanding in what manner it is persisted. The LetiMix documentation mentions that is should be saved as follows:

When you make a param persistent (meaning its value is kept even when you reload the script) this parameter value is also saved within the preset (and within the default preset, called "Init" internally).

I interpret this to mean that the PARAM value will be saved as part of the preset. I have tried saving a preset, but I don't see the value making its way into the resulting XML and reloading the preset does not restore the value. I think I must be misinterpreting this, and perhaps am misunderstanding the purpose of the PARAM element.

Any guidance here would be much appreciated. Thanks in advance!

Statistics: Posted by mackemlad — Sun Sep 08, 2024 1:23 am — Replies 0 — Views 9

---