Export and Invalid outputStrings()

[TinTaka]

Hi, I recently purchased PnS and am enjoying learning how to build plugins. I'm running PnS 3.6 on MacOS Sequoia and have built a simple MIDI note mapper that uses 20 outputStrings() that are being updated in the DSP code.

I had to create a config.ini file to use more that 16 outputStrings() and it all works just fine in the dev environment.

However, when I export to a VST3 plugin and load it in my also recently purchased PatchWork it complains that the 4 last outputStrings() are not defined. Same thing happens when running the standalone App.

Here are the error messages:

There were errors while loading custom_controls.kuiml.inc:
- error: $script_output_string16$: Unknown identifier (object does not exist).
- error: $script_output_string17$: Unknown identifier (object does not exist).
- error: $script_output_string18$: Unknown identifier (object does not exist).
- error: $script_output_string19$: Unknown identifier (object does not exist).
- error: Fatal error: skin loading failed

Any ideas of what I'm doing wrong?

Cheers
Paul

[Blue Cat Audio]

Are you using the latest preview or the official release? I remember that a few things may have been fixed in the preview.

[TinTaka]

Hi, thanks for the reply. I have no idea why but it seems to be fine now. I just re-exported and opened the VST3 in Patchwork and to my surprise no errors. As a novice in PnS, I must have done something stupid and then unknowingly corrected it. There was a lot to get my head around as I wanted a custom skin right off the bat and so had to dive straight into KUIML. Anyway, thanks for your support.

Paul

[TinTaka]

UPDATE!

If I export with 'Use generic params" selected it fails as described before. All is good if this option is not selected during export.

The version I'm using is 3.6 downloaded about 5-days ago using the "download next release preview" link on the download page.

Paul