Kong Vst Plugin: Bank Access Problems In Renoise

[vvoois (vV)]

I bought a set of Kong plugins just a few weeks ago.

The plugins don’t allow bank access so they serve their active preset only, but this also means that current parameters either are all ignored perhaps due to this problematic access attempt or simply bank access and preset selection.

I have swapped information with the Kong audio developers how to resolve this issue, perhaps the same solution is already being applied in Renoise to other plugins that have had a similar problem which could probably be also applied to these plugins.
If you need more info, i can provide you the mail address of the developer, but the info looks quite sufficiently detailed.

A summarized except of the email i post below, quotes are mine, answers from the Kong audio developer below:

I noticed in the demo’s that presets weren’t loaded when i have
saved the plugins with the song information.
But now that i registered the plugins, the programmed
presetinformation still isn’t accepted when plugins are loaded with
song projects Sad. When i manually save
FXP information and reload it later, the plugin doesn’t seem to be
doing much with the parameter stream either besides changing the INIT preset name into
the name of the preset but the plugin doesn’t process the parameters being sent to it.
I currently now have to manually reselect (and configure) all the
presets of each instance i saved with my projects.

Our preset system is independent from the host sequencer. That said, the host sequencer can interact with QIN engine through the “Program Change” Extender, if needed.
As for loading/saving *.fxp files, please use the built-in fxp system of the QIN engine plugins. This will ensure the saved *.fxp will work in any host, and will enable the exchange of the presets as well.
About saving the plugin status with the host project files. Well…Ableton Live is another one that’s having the problem as well.
Cubase and most host sequencers out there do allow the plugins like ours to behave the way they behave. In other words, the plugin’s bank is not accessible to the host except the active preset.
We are also working on a new version of QIN which should address this issue too.
The Renoise devs probably can make it compatible as well on their side, if you could rely this info to them.

What is the exact trick to parametrize the
keyswitch or program change extenders from within the host application?
Does it work by leaving out the attempt to access the bank preset list? How does Cubase this?

The Renoise dev can address the part of saving projects with the QIN plugin info if they can have their host to only access a single preset, instead of the whole bank.
Our QIN is not designed to support the host side’s preset list, and there will be no support of that in the future either.
Our new QIN engine will address the “project saving” part with the few hosts that do allow plugins to not provide chunk info of the banks, but that has nothing to do with whether we support host side’s preset listing.