|
|
Untitled.gif (116,290 bytes) |
|
|
It seems the edited values are fractional which I overlooked. Is it possible to keep the units the same as the parameter displays when editing? |
|
|
Is this a VST2 plugin? Those always have a natural range of 0..1 but do allow to query a "user visible value". |
|
|
PS. VST3 and LV2 plugins should allow proper numeric entry. |
|
|
The plugin in the GIF is VST3. I want to say 8.6 allowed the unit to be entered correctly. Only now does the entry become normalized when the expected value is used. |
|
|
I gave this a try with SSL Channel Strip 2 in Mixbus 32C V9.2.172. It responds to values 0 to 1 only. Putting a -18 or 15 just gives a 0.00 or 1.00 respectively. This true with the VST3 and the VST2 version being tested. |
|
|
When adjusting the Gate Depth maunally with automation in MixBus32C, I was able to enter 34, 40, 50, etc.... and they would work. However, other parameters on 32C EQ worked on values of 0 to 1. |
|
|
I'm confused. What plugin are you actually testing? |
|
|
We both tested the VST3 version of SSL Channel Strip 2. Any automatable parameter appears as normalized when attempting to edit the value. This is not isolated to the SSL plugin either. Prior versions of Ardour/MixBus allowed the correct unit to be entered directly (i.e., dB or percentage values). |
|
|
https://store.solidstatelogic.com/plug-ins/ssl-native-channel-strip-2 ? I do not have access to this plugin. Many VST3 that I tested do provide conversion functions from 0..1 to the plain (actual) value. In that case numeric entry can be used to change the value. e.g. the mda.vst3, BLENDEQ (by Analog Obsession), and most importantly the Steinberg reference VST3 plugins. However some plugins do not provide this, and expose the underlying 0..1 range. There is nothing we can do in that case. Note that this is different from the displayed human readable representation, which most VST3 do support. There has not been a change in Ardour's codebase for this in the last 2+ years (before v7). If it worked before, it is likely due to a different version of the plugin. |
|
|
@x42 Reading back my posts, they were a bit confusing. The SSL plugin had 0..1 values. With the Mixbux32C Gate Depth (built in plug in), however I could enter values such as 30, 35, 42, etc and they would work.... Thank you for your explanation. That is what I have seen, it depends on the plugin like you say. @prokoudine Maybe a note in the Manual can be added ? @sollapse If you need to enter exact values, you can always hit CTRL while changing the slider with the mouse to get fine control. CRTL and ALT pressed together gives even more detailed control of the slider. I will check Cubase, but I think it will be the same 0 to 1 values on Automation. Maybe SSL will listen to that feature request ? It is generally quicker to type a value, and would be nice if the plugin accepted human readable values. |
|
|
@Schmitty2005 The Harrison channelstrip (a LADSPA, LV1 plugin) is halfway there. Some parameter values do not provide a conversion function and you you also get 0..1. The built-in Mixbus Gate is odd too: when you switch its mode to "Expander" the depth is reduced by 1/4 (range 0..15), yet numeric entry is still 0..60. |
|
|
I was not sure if Gate was LV2 or LADSPA, as it is built in. I assumed LV2. When I check SSL2 Channel Strip 2 VST3 in Cubase 13, I was able to type text entry 15000 for 15kHz for the EQ freq. The Automation also reports the proper Freq, not a 0..1 value, so the automation seemed consistent with the plugin knob values all the time. When Checking in BitWig, the automation knob on the track editor was 0..1 when rotating, but double clicking to enter a value showed converted kHz value , accepted kHz values, and the proper value in kHz also showed in the generic plugin box. Would adding this functionality to Ardour be a feature request then ? A lot of work for little reward ? Not necessarily a plug-in vendor issue ? Or a small bug ? |
|
|
NONE of my VST3's that I tried exposed anything other than 0..1 values when text entering. LV2 Harrison XT Plugins allowed text entry! VST3 AVA plugins did not . I also tested a variety of Waves, Brainworks, Arturia, Native Instruments, Baby Audio, and a few other brands . All VST3. Nothing other than 0..1 values for text entry on any parameter I tried. I was beginning to think it was a Windows only VST3 problem. But then I tried BLENDEQ, and everything worked as expected. I could enter the text values as a human, and it would work. Looks like I will be trying out BLENDEQ for a while...... |
|
|
I can add that in recent versions of Ardour, I've been able to edit parameters for Kontakt 7 (VST3) directly in which the value was translated properly. It seems something has changed with the handling of automation parameters. |
- Anonymous
