On 20.04.19 12:14, Alexander E. Patrakov wrote:
[forgot to CC the list - sorry for any duplicates]
сб, 20 апр. 2019 г. в 14:39, Georg Chini <georg@xxxxxxxx>:
I think using malloc() when a parameter changes is not interfering
with real-time operation because the filter must be reset after
a parameter change anyway.
The parameter changes allowed during the runtime are not expected to
need a filter reset. In-place rebuild - yes, reset - no. The filtered
audio should smoothly follow gradual changes of the filter parameters.
Many LADSPA plugins actually implement internal smoothing of parameter
value changes, or even internally keep two filter versions and
interpolate between them, in order to avoid clicks, because such
gradual changes are an expected thing in pro audio workflows.
Out of curiosity: How does that work? I do not see any function
in the LADSPA standard which notifies the plugin of parameter
changes. So how does the plugin know that a parameter has
changed? Does it have to copy the parameter values to its own
internal structures and compare them each time during run()?
Or does it rely on a new connect() call?
_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
