Knob Parameter Links in Milliseconds Instead of Percentage.
Will we be able to set knobs to milliseconds instead of percentage. I have VST parameters that use precise milliseconds instead of percentages. No precise knob control possible on Unify GUI or controller if VST parameters are in milliseconds. Is this feature coming in the future?
There are technical reasons that make this impossible. Basically, the plug-in "knows" about milliseconds, but does not share that information with the host (in this case, Unify).
Can you set values in milliseconds in an automation lane in your DAW? If not, you won't be able to do it in Unify either. If so, please let me know
- which are the plug-in(s) in question, and which format (VST, VST3, AU)?
- which DAW you use, and on which platform (Windows or Mac)?
I'm using Ableton Live 11 in Windows 10. Yes, I can use automation and set up macro knobs in Ableton Live to accomplish what I want need to do. I'm Unifying SA Recordings (Spitfire Audio) Landfill Totems by Hainbach. I always use VST versions of plugins, even though more plugins are being issued or upgraded only in VST3 and AU formats. This is the first SA Recordings plugin that uses milliseconds to control the Synth's attack. Finer knob control would be nice. Not a big deal. Thank you!
I have just ordered the Landfill Totems product for testing. Stay tuned...
Free cassette recording by Hainbach for the first 1500 customers who order! I don't own a working cassette player anymore. lol
The actual Hainbach - Landfill Totems VST GUI opened within Unify shows milliseconds under the Attack. I wanted to setup Hainbach - Landfill Totems within Unify "only" so I can create unified patches in Unify standalone, Logic, Cubase, FL Studio, and Ableton Live. That's the idea behind Unify? Using percentages doesn't accurately control the Attack knob. Even with my controller, mouse, or trackpad I can't adjust the Attack accurately. Thanks for the help. See attached.
This is a very tricky issue. The VST standard doesn't really provide a way for host programs (DAWs, Unify, etc.) to know the true value of parameters. From the host's perspective, all parameter values are "normalized" to the range 0.0 to 1.0. Most (but not all) plug-ins also provide a way for a host to pass in a value in this range (e.g. 0.25) and receive back a text representation of what that normalized value represents. This might not even be a number; for a waveform-select parameter, it might be a word like "Sine" or "Square". The key point is that this is a one-way conversion. There is no way for the host to know how to go the other way, i.e. to convert a user-input value back to the corresponding normalized value.
The Hainbach plug-in's handling of the attack parameter is particularly vexing, because
- The normalized parameter value range is 0.0 to 1.0 (as always)
- The value displayed in the plug-in's own GUI is in the range 0.0 to 15.0 seconds, with milliseconds as the unit below 1.0 sec
- The converted value that a host program can request is "0%" to "1500%". (Remember, these are text strings, not actual numbers.)
Believe me, if I could fix this to be the way you want it, I would have done it long ago.
I will just use the Hainbach - Landfill Totems VST's GUI Attack control instead of assigning it to a Unify knob. All I wanted was a Unify knob to control the Attack. Since I can't control the Hainbach - Landfill Totems Attack, with any accuracy, using a Unify knob I'll move on. I haven't yet encounter any such issues, so far, while unifying my other VSTs. Thank you.