SynthMaker

VST Automation broken between SM versions

Archive · 2009 5 old posts

From the original SynthMaker forum (2004–2014), with its members’ names and dates.

skitchy ·

Using Cubase Studio 4.

I have a plugin that is still working fine, that was exported from an older version of SM (about 2-3 updates ago). Demo here : http://www.dyvision.co.uk/dyscratch/dyscratch.html However, if I now export the EXACT same schematic (unaltered) from the current version of SM 1.1.2 the automation parameters are not present inside Cubase. This also means that the knobs will not read/write automation.

So the problem must lie within the VST export routine of the newer SM versions, or an internal code change in a low level module.

skitchy ·

Okay, I've tracked it down to a specific module - VST Arrays. I have read another thread about this, and it blamed Cubase. That's just not the case. The plugin exported with old SM works fine. The same plugin exported with new SM is broken. And trial and error (about 4 hours worth) tracked the problem to a VST array.

skitchy ·

WORKAROUND : The VST Array MUST have a connection to the 'Name' pin (string). It is labelled as 'optional' but you can avoid the headache I just had by giving it a name 😉 To SM developers : I assume that Cubase expects a name for the arrays, and if it doesn't find one the entire VST parameter list gets ignored. SM needs to supply a name to any un-named array when exporting a VST dll.

TomC ·

skitchy wrote: WORKAROUND : The VST Array MUST have a connection to the 'Name' pin (string). It is labelled as 'optional' but you can avoid the headache I just had by giving it a name 😉 To SM developers : I assume that Cubase expects a name for the arrays, and if it doesn't find one the entire VST parameter list gets ignored. SM needs to supply a name to any un-named array when exporting a VST dll.

At least with Cubase 4 giving the Array a name does NOT solve the problem. At least not the problem I reported about a year ago concerning automation parameters not showing up in Cubase 4.

If you have enough parameters with automation, from a random parameter on nothing more shows up. I had examples which showed that behavior which didn't use a single VSTArray. It's just much more easier to get the number of parameters up to the buggy point with the array.

Tom

skitchy ·

Sorry to hear that Tom. For my purposes right now the workaround seems stable enough, but we can at least deduce that there is an issue here (at least a year old) that needs a solution.

Wrote something here? To have a post removed or your name hidden, write to [email protected].

Before your first post

A few rules keep this a friendly place. You agree to them once.

Shown next to what you post, here and in the app. It doesn’t have to be your real name: 3–24 lower-case letters, digits or _ (capitals become lower case, spaces become _).

    Then your post goes up straight away.

    Delete this reply?

    Open it in SynthMaker?

    It goes on the track you’re editing there, in place of that track’s sound, and into My sounds. Your other tracks stay as they are.

    Want to keep that track’s sound? Start a new song in SynthMaker first (Song › New song), then open this.

    Report this reply?

    Only the developer reads reports. The person isn’t told who reported them.

    What’s wrong with it?

    Block this person?

    You won’t see their posts and replies here any more. They aren’t told, and you can unblock them at any time.

    People you’ve blocked

    Their posts and replies are hidden from you. Unblock someone to see them again.

    The community rules

    A few rules keep this a friendly place. Everyone agrees to them once, before their first post.