MATCH FADER VALUE TO VST PARAMETER
I'd suggest :
- check the range of values expected by your compressor's attack (for ex 0...1)
- check the dispayed range (here 0...400ms)
- build a fader going from 0...400 (integer values), link it to a scale module which will convert 0...400 to 0...1
So you have your chain : fader - scale - compressor
- check the range of values expected by your compressor's attack (for ex 0...1)
- check the dispayed range (here 0...400ms)
- build a fader going from 0...400 (integer values), link it to a scale module which will convert 0...400 to 0...1
So you have your chain : fader - scale - compressor
-
imodularsynth
- Member
- Posts: 36
- Contact:
VST parameters are (normally) always 0.0 to 1.0 (I never saw a VST with a restricted input range, and the maximum range is defined by VST standard)
So, normally, you just need to scale the knob output value (let's say 400 in your case) to 1.0, simply by adding a divider of 1/400 between the knob output and the VST parameter input.
Take care however that some parameters can have a non-null value at minimum. So you will probably need to code something in the form y=ax+b between the knob output and the VST parameter input (typical example would be a delay between 10 and 1000ms : the knob shall start at 10, leading to a value of 0 to the plugin input)
So, normally, you just need to scale the knob output value (let's say 400 in your case) to 1.0, simply by adding a divider of 1/400 between the knob output and the VST parameter input.
Take care however that some parameters can have a non-null value at minimum. So you will probably need to code something in the form y=ax+b between the knob output and the VST parameter input (typical example would be a delay between 10 and 1000ms : the knob shall start at 10, leading to a value of 0 to the plugin input)
Who is online
Users browsing this forum: No registered users and 29 guests
