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
Variables for Automation
3 posts
• Page 1 of 1
Variables for Automation
I'm working on a VST idea that is nearly complete. A weird problem has come up.
The user needs to be able to use automation in the DAW for the VST idea to work correctly. The DAW (Samplitude) doesn't show any automatable variables for the plugin.
Does anyone know how you can make a variable in your VST be seen by the DAW, so that it can be automated by the DAW? I have a slider that I want to be able to be automated in the DAW.
I have other VSTs I've made where the variables are listed and automatable by the DAW. I didn't do anything special that I remember to get that to happen. I'm not sure why it's not happening with my newest VST.
The user needs to be able to use automation in the DAW for the VST idea to work correctly. The DAW (Samplitude) doesn't show any automatable variables for the plugin.
Does anyone know how you can make a variable in your VST be seen by the DAW, so that it can be automated by the DAW? I have a slider that I want to be able to be automated in the DAW.
I have other VSTs I've made where the variables are listed and automatable by the DAW. I didn't do anything special that I remember to get that to happen. I'm not sure why it's not happening with my newest VST.
-
SBMastering - Posts: 17
- Joined: Tue Jun 12, 2012 11:47 pm
Re: Variables for Automation
The "Auto" input on the (VST) PresetParameter primitive has to be set on true. I guess you have one included at the parameter you want to use inside the VST?
But there were some randomn bugs with some hosts. One can be found here:
http://synthmaker.co.uk/forum/viewtopic ... ion#p81561
EDIT: Ah and i forgot the most important . Of course you have to include a Preset Manager in your VST!!
Ohhh....That reminds me to ask for a bugfix...thanks...
So maybe someone who's reading it and owns Cubase can test it?
EDIT: I tested it myself just to find out that the bug still persists...
But there were some randomn bugs with some hosts. One can be found here:
http://synthmaker.co.uk/forum/viewtopic ... ion#p81561
EDIT: Ah and i forgot the most important . Of course you have to include a Preset Manager in your VST!!
Ohhh....That reminds me to ask for a bugfix...thanks...
So maybe someone who's reading it and owns Cubase can test it?
EDIT: I tested it myself just to find out that the bug still persists...
- stw
- Posts: 111
- Joined: Tue Jul 13, 2010 11:09 am
Re: Variables for Automation
Plus - for automation - all values stored in presets must be in (0-1) range if your create your own modules. Values don't need to be scaled that way if you don't use automation in DAW, just rendering.
Need to take a break? I have something right for you.
Feel free to donate. Thank you for your contribution.
Feel free to donate. Thank you for your contribution.
- tester
- Posts: 1786
- Joined: Wed Jan 18, 2012 10:52 pm
- Location: Poland, internet
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 33 guests