Page 1 of 2
Filter interface bugs
Posted: Fri Mar 25, 2016 5:59 pm
by ebeling
A few of the LADSPA plug-in filters have a bandwidth control. In version 2.1.2 this slider jumps between integer multiples of octaves instead of providing the choice of fractions of an octave. Entering other decimal values in the numeric field does not appear to have the intended effect. This bug applies to the single and triple band parametric filters, and also to the blend parameter of the C* Stanford style JVRev and possibly to other effects.
The high pass and low pass filters don't work (the ones called high/low pass filter....... with seven dots). All that happens is that a message comes up saying which day of the week it is (the correct day, fortunately). Similar problems occur with the Notch filter.
I'm on Fedora 23 and have installed audacity 2.1.2 from the distribution.
Re: Filter interface bugs
Posted: Fri Mar 25, 2016 6:34 pm
by steve
The effects with 7 dots may be due to incorrect listings in the pluginregistry.cfg file.
The first thing I would suggest is that you try resetting Audacity back to "clean installation".
Close Audacity then open the hidden folder
~/.audacity-data and delete the files:
audacity.cfg
pluginregistry.cfg
pluginsettings.cfg
This will reset Audacity back to a clean installation (though any "Chains" that you have created will still exist.
You will need to re-enable any non-standard plug-ins using the "Add/Remove Plug-ins" feature (
http://manual.audacityteam.org/o/man/in ... tml#manage).
Note that most LADSPA plug-ins are now very old and most are unmaintained.
If you are aware of specific LADSPA plug-ins that worked in previous versions of Audacity but do not work in the current version, then we can probably look into that, but if the problem is with the plug-in, then there may not be anything that we can do about it.
Note that a lot of filter types are available as Nyquist plug-ins, and these should work correctly in Audacity. If there are problems with Nyquist plug-ins, then there are probably people on this forum able to fix them. There is a collection of Nyquist plug-ins on the Audacity wiki:
http://wiki.audacityteam.org/wiki/Downl ... t_Plug-ins
Re: Filter interface bugs
Posted: Sat Mar 26, 2016 2:54 pm
by Gale Andrews
ebeling wrote:A few of the LADSPA plug-in filters have a bandwidth control. In version 2.1.2 this slider jumps between integer multiples of octaves instead of providing the choice of fractions of an octave. Entering other decimal values in the numeric field does not appear to have the intended effect. This bug applies to the single and triple band parametric filters, and also to the blend parameter of the C* Stanford style JVRev and possibly to other effects.
The high pass and low pass filters don't work (the ones called high/low pass filter....... with seven dots). All that happens is that a message comes up saying which day of the week it is (the correct day, fortunately). Similar problems occur with the Notch filter.
I'm on Fedora 23 and have installed audacity 2.1.2 from the distribution.
If the single and triple band parametric filters are the ladspa-swh plugins, I cannot reproduce that in 2.1.3-alpha on Ubuntu 14.04. The "Bandwidth (octaves)" slider in "Single band parametric" navigates to fractional values and Plot Spectrum shows a difference between for example 2.02 octaves and 2.936 octaves.
You may want to report the issue to Fedora, or try self-compiling the
LV2 port of the swh plugins.
Gale
Re: Filter interface bugs
Posted: Sat Mar 26, 2016 4:50 pm
by ebeling
Thanks Steve, removing those files helped.
Just another minor thing. The built in echo effect used to allow for negative values of the gain parameter or "decay amount". This is no longer possible. I found that useful and would appreciate having that option.
Re: Filter interface bugs
Posted: Sat Mar 26, 2016 5:17 pm
by steve
ebeling wrote:The built in echo effect used to allow for negative values of the gain parameter or "decay amount". This is no longer possible.
I presume that was a bug. A negative value would mean "less than no echo"
I don't have an old version handy - what did negative values do?
Re: Filter interface bugs
Posted: Sun Mar 27, 2016 1:20 pm
by ebeling
steve wrote:
I presume that was a bug. A negative value would mean "less than no echo"
I don't have an old version handy - what did negative values do?
I haven't read the code, but supposedly it implements a delay of the form y[n] = a*x[n] + g*y[n-D], where D is the delay in samples and g is the gain factor. It is not uncommon to have negative gain as long as you stay within the range -1 < g < 1.
Re: Filter interface bugs
Posted: Sun Mar 27, 2016 4:13 pm
by steve
ebeling wrote:It is not uncommon to have negative gain as long as you stay within the range -1 < g < 1
Gain is generally described either as a ratio in "dB", or as a linear "multiplication" figure.
In the latter case, a gain of "1" is called "unity gain" and is equivalent to a gain of 0 dB. If you think of gain as a box where you put something in one end and get something out of the other, for unity gain, what comes out is identical to what goes in. If the gain is "0", then that's equivalent to multiplying by 0, so you put something into the box and nothing comes out. The Echo effect "decay factor" is the linear gain for each delay loop. With a "decay factor of 1, the echo is identical to the input, just shifted to a later time. With a "decay factor" of 0.5, the echo is half the amplitude of the input. With an input of 0. there is no echo.
This is the relevant code:
Code: Select all
history[histPos] = obuf[i] = ibuf[i] + history[histPos] * decay;
where "decay" is read from the "Decay factor" text control:
Code: Select all
FloatingPointValidator<double> vldDecay(3, &decay, NUM_VAL_NO_TRAILING_ZEROES);
vldDecay.SetRange(MIN_Decay, MAX_Decay);
S.AddTextBox(_("Decay factor:"), wxT(""), 10)->SetValidator(vldDecay);
Re: Filter interface bugs
Posted: Sun Mar 27, 2016 4:35 pm
by Gale Andrews
steve wrote:ebeling wrote:The built in echo effect used to allow for negative values of the gain parameter or "decay amount". This is no longer possible.
I presume that was a bug. A negative value would mean "less than no echo"
I don't have an old version handy - what did negative values do?
On Windows in 2.0.0 and 2.0.5, negative values were a "no effect".
In 2.1.0, the negative sign seems to be ignored, and the effect ran assuming the value was positive.
Gale
Re: Filter interface bugs
Posted: Fri Jan 17, 2020 12:53 am
by ebeling
Still, after all these years, I consider the possibility to set a negative gain factor in the echo useful in some cases. Please consider it a feature request.
And also, the text box is too small. It shows only two decimals (a third if you scroll), whereas three or four decimals are often necessary for fine-tuning the echo rate. This effect is potentially very useful for comb filter effects, but then the user needs to be able to set all those parameters.
Re: Filter interface bugs
Posted: Fri Jan 17, 2020 1:48 am
by steve
ebeling wrote: ↑Fri Jan 17, 2020 12:53 am
I consider the possibility to set a negative gain factor in the echo useful in some cases.
How can you have less than "no echo" ? Isn't that like having less than no oranges?