If you have a problem or need to report a bug please email : support@dsprobotics.com
There are 3 sections to this support area:
DOWNLOADS: access to product manuals, support files and drivers
HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects
USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here
NEW REGISTRATIONS - please contact us if you wish to register on the forum
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
A bit confused on how FlowStone store/load data
11 posts
• Page 2 of 2 • 1, 2
Re: A bit confused on how FlowStone store/load data
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
-
Spogg - Posts: 3358
- Joined: Thu Nov 20, 2014 4:24 pm
- Location: Birmingham, England
11 posts
• Page 2 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 36 guests