Hi,

of course we are in contact with Steinberg, but there´s no way we can put pressure on them regarding this issue.

VST3 is "their" standard, and it has a lot of benefits. I´m sure that applications like VE PRO will make clear what might be missing, but you cannot expect changes over night.

Please feel free to contact my colleagues at Steinberg - the more input and requests they get, the better [:)]

Best,

Paul

Paul,

does VSL consider to implement to suggested CC mapping as a work around?

Peter

Hi Peter,

there are no plans to do that, sorry to say. We support the formats that are available. There are many issues on our to-do-list that have a higher priority, to be honest.

Thanks for your understanding!

Best,

Paul

@Paul said:

there are no plans to do that, sorry to say. We support the formats that are available. There are many issues on our to-do-list that have a higher priority, to be honest.

Hello Paul,

I must say I am disappointed you don't consider this. It would be relatively easy to implement. You would solve a problem for quite a few users. (BTW, I don't understand what you mean with "format" here)

But I am happy you finally took the time to tell us VSL's position.

Best regards,

Peter

@pjak said:

[...] (BTW, I don't understand what you mean with "format" here) [...]

I think Paul meant to say "standard" (i.e. VST3).

Hi Peter,

@Another User said:

You would solve a problem for quite a few users.

We will keep on solving problems, it´s just that each day only has 24 hours.

Please read my initial response again, I have just said that right now there are no plans to add this feature [:)]

Best,

Paul

Who is the right person to contact at Steinberg? I believe, a generic support address won't do much good.

@Abel said:

[quote=Paul]Please feel free to contact my colleagues at Steinberg - the more input and requests they get, the better

Who is the right person to contact at Steinberg? I believe, a generic support address won't do much good.

There is no right person. Forget contacting Steinberg. They will have no interest in changing their spec, as they believe that it is better than the old VST2 spec. You really have two choices:

1. Find out what the "improved" method of handling what used to be Program Changes is, and update your template.
2. Use the VST2 version of VE Pro.

DG

Hello VSL users,

In a previous post I suggested to translate CC into PC as a workaround. However, I thought this would only be possible with a multi script as supported by Kontakt 4 (which I don't have yet, and which might not work properly with some old libs).

But it seems there is an undocumented way to enable multi scripts even with Kontakt 2 and 3! So it should be possible to implement this translation within Kontakt 2 and 3 as well. If this is true, then we don't need any support by VSL to get it working.

In fact, there already exists a script, that is mentioned on the native instruments support forum, that claims to do this (don't know if VSL would allow me to post a link to native instruments forum, please let me know if it is OK)

Will look into it next weekend.

VST3 we are coming... [H]

Peter

Hi Peter,

we´d prefer to keep links to "experimental" scripts and programs not linked - of course everybody interested can contact you via PM!

Thanks for understanding!

Best,

Paul