Saving and Restoring Custom Sequence Data as String in Plug'n Script / KUIML Presets

[pentacom]

Hi,

I'm working with Plug'n Script and KUIML, and I have a question about storing and restoring custom sequence data.

I'm able to convert the sequence data in the plugin(DSP) into a string, send it to outputStrings, and display it in the UI.
What I'd like to do next is:

• Save that stringified sequence data into the plugin's preset, and
• Restore it later and send it back to the DSP side when the preset is loaded.

How can this be done within the Plug'n Script / KUIML system?

Thanks in advance!

[Blue Cat Audio]

Hi,

Sorry for the delay. I guess the sequence is recorded from something coming thru the DSP (audio or MIDI?). In this case there is currently one missing piece for this purpose in PnS, which is saving the state of the DSP in a string or a byte stream. That's in work, but it's not available yet.

What you could do currently is store this information back into an input string in the GUI (input strings are persistent), but this requires that the GUI is opened when the sequence is stored.

[pentacom]

Hi,

Sorry for the delay. I guess the sequence is recorded from something coming thru the DSP (audio or MIDI?). In this case there is currently one missing piece for this purpose in PnS, which is saving the state of the DSP in a string or a byte stream. That's in work, but it's not available yet.

What you could do currently is store this information back into an input string in the GUI (input strings are persistent), but this requires that the GUI is opened when the sequence is stored.

Thanks for the reply. Saving the DSP state as a string or byte stream would be a very helpful feature. I’m looking forward to it.

For now, I’ve managed to store the data in the preset and restore it to the DSP by copying the outputString into the inputString on KUIML. That seems to work as a workaround.



Additionally, when exporting with "Use generic parameters" unchecked, the OutputParams are exposed to the DAW parameters.
Is there a way to publish only the InputParams instead?

[Blue Cat Audio]

Thanks for the reply. Saving the DSP state as a string or byte stream would be a very helpful feature. I’m looking forward to it.

For now, I’ve managed to store the data in the preset and restore it to the DSP by copying the outputString into the inputString on KUIML. That seems to work as a workaround.



Additionally, when exporting with "Use generic parameters" unchecked, the OutputParams are exposed to the DAW parameters.
Is there a way to publish only the InputParams instead?

Good news: the latest preview of PnS has both private output parameters (not exposed to host) and internal DSP state save/restore included!