Open alexmlucas opened 4 years ago
I tend to use im.filter like a volume fader, so my personal preference is to keep it down until there’s a signal (current implementation).
This could be corrected by asking the user to supply argument, which I don’t think the filter takes yet.
I’m trying to think of which object I worked through this problem on, as I think we could abstract a convention from this your question above.
The issue is how audio signals are handled, but what you describe is possible if we break out into the control domain. I’ll check the defaults on existing filter objects in Pd.
This is bringing to mind a possible takeover situation in the longer term, like for midi mapping (e.g. don’t change until argument is matched, or change relative to the supplied argument).
Or a “soft takeover” object (perhaps that’s a neat short term solution, for fun).
The cutoff frequency needs to be set to get audible output. Not sure how to correct this, is it possible to loadbang an initial value for signals, then remove that value once the parameter has been set by the user?