Dynamcally resizable VST Parameter Array

[exonerate]

Ok, I'm not sure if this is a limitation of the VST spec (I've not been able to find any info on it), but does the VST parameter array have to be a set size? can it not work like the normal arrays in SM?

I've seen that the old arrays in SM used to have set sizes and these were superseeded with the more flexible ones we now have, so I was just wondering if the VST parameter array is an old component that didn't get updated like the other arrays or if it's a limitation of the vst spec and they have to be a set size.

Anyway a dynamically resizable array would really be great, because then the multi stage env could have unlimited points and only use the memory for the number of points.

Also I'm making some "draw morph oscillators" similar to those in zebra 2, but I want the number of waveforms to be user definable up to any size they want. This would be a killer feature, I have a way of doing it for saving and loading presets basically when the user saves the preset I save the bank of waveforms to a seperate text file and just save the location to the presets. I thought that would be fine but how could I save it when they just save the project from the host?

Well actually the simplest and maybe only way (if it's a limitation of the VST spec) would be to send a before and after trigger from the preset manager primitive when the user saves the project in the host, is that possible? can a VST know when the project has been saved?

I'm trying to break new ground here and do something no other synth does, please have a look at my suggestions and see if they are possible, thanks.

Cheers

Exo

[Acrobat]

can a VST know when the project has been saved?

interesting q. , maybe the VST can go search for "last modified" date of the song file...

[DigitalWhiteByte]

Old post, Old question.

Can a "VST Array", having a size variable?

The primitive "VST Array" does not update the number of entries dynamically,
and thus a problem of VST spec, or just need to update the primitive so that it does?

[oddson]

This just came up for me on another thread today... is that why you're asking or is it just coincidence.

What I decided was that you could store a (normalized) length variable along-side the array and then as long as you've allocated enough data points you could extract an array of any lesser size and just store zero in the points above that index.

[oddson]

Like this:

[DigitalWhiteByte]

Hehe, thanks

But this solution was already taking the order to make the pseudo-dynamic arrays, but this always involves a great waste of resources for the memory.
Then came a limit imposed by the VST spec?
Anyway thanks, as always.

[oddson]

...involves a great waste of resources...

Small waste of resources. I don't think it can be helped.

Has anyone checked what happens if you try to load an old preset after you increase an array size?

If it just fills with zeros this would be OK by for some uses (like the Multi-Stage Envelope) but not others (like wave files where the number of data points matters).

My solution would work for both and the amount of wasted memory is likely pretty small compared with the audio requirements.