Howdy, we’ve taken note of these and have added feature requests to our backlog, though there definitely isn’t a timeline for us getting to this workload.
If you could give us a few specific examples of your needs for these modules, it might give us more insight into building specific modules to solve your problems that can’t be solved with what’s already in vsig (your examples for 1 and 4 already help us out a bit). Off the top of my head, a few follow ups though these are without the context of the specific problem you’re trying to solve, so I admit they may be naive suggestions…
2) Take a look at c_master_taper. I frequently use it to map input knobs. Frequency selection tapering can be done with the c_master_taper, and for dB/amplitude conversion either take 10.0 * log10 of the squared value for going amplitude -> dB, or 10^(in/20) to go from dB -> amplitude. dB conversions inherently throw out phase, since the logarithm is undefined (well, imaginary) for negative values and the dB value itself contains no phase information for amplitude conversion.
3) A c_quantize hooked up to a c_table_n might be able to help you in the short term.
4) You could put a bridge on the output of c_table_n by connecting a c_fltr_a to it. I like 20 ms as a baseline time constant for parameter smoothing.
