Re: A bit confused on how FlowStone store/load data
Posted: Wed Jan 20, 2016 11:21 am
I think you are right!
But, you would need a Preset Prim inside the FS schematic in order to identify to the DAW what actually needs to be saved in the DAW proprietry format. Unless the DAW saves the whole memory space assigned to the plugin...? Reaper has the option to save full plugin state but this is known to cause long load and save times.
This is where I hope someone more knowledgable than me can chip in. It may be that different DAWs handle the VSTi state in different ways but I don't know about this point.
If you want all your float-based wavetable arrays to be fixed at birth then you only need to have a menu selector scheme to choose what you have previously created in the Flowstone edit environment. That would be just one VST parameter to choose the table. But if you want the plugin to be able to load various tables that would need the preset manager scheme.
Can anyone else help with this?
Cheers
Spogg
But, you would need a Preset Prim inside the FS schematic in order to identify to the DAW what actually needs to be saved in the DAW proprietry format. Unless the DAW saves the whole memory space assigned to the plugin...? Reaper has the option to save full plugin state but this is known to cause long load and save times.
This is where I hope someone more knowledgable than me can chip in. It may be that different DAWs handle the VSTi state in different ways but I don't know about this point.
If you want all your float-based wavetable arrays to be fixed at birth then you only need to have a menu selector scheme to choose what you have previously created in the Flowstone edit environment. That would be just one VST parameter to choose the table. But if you want the plugin to be able to load various tables that would need the preset manager scheme.
Can anyone else help with this?
Cheers
Spogg