On 02/18/2014 07:00 PM, Tres Finocchiaro wrote: > After further investigation into this, it seems like it's a bug with > Glame Lowpass Filter. > > All lowpass filters default to 441Hz, which I find to be an > appropriate starting value, except Glame Lowpass Filter. > > Glame Lowpass defaults to 4.41Hz. > > I can't find reference to this value in the source code, but I'm also > not fluent in c/cpp. > > Here is the source code: > https://github.com/LMMS/lmms/blob/031b93d830aa61f5b6e7116b907c46deb2afa49c/plugins/ladspa_effect/swh/lowpass_iir_1891.c > > I tried to change it to default to 441 but had no luck due to my > inexperience with C. The value is stored in plugin_data->*cutoff, but > I can't make heads or tails as to where this value comes from or how > to set a default. >
LADSPA code strucure is a bit tricky for someone not used to C. Having the LADSPA SDK helps, as it contains the documentation of each struct and function in the LADSPA codebase. The default value is set with macro flags in the LADSPA_PortRangeHint structure, which each port has. There's no way to set a discrete value as default (unless you set it to lower/upper limit), but instead you have to choose from the default values already defined in the LADSPA API. 440 is one of the set values provided by the API (explaining why it's used in so many filters), it can be set by using the macro LADSPA_HINT_DEFAULT_440 in the HintDescriptor field. ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ LMMS-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmms-devel
