param~ vs param
Given that both param and param~ are controlled by a non signal rate outside the rnbo~ object, would param and sig~ together be equivalent to param~?
I am asking because I have noticed that param~ only works in the top level patcher, whereas param seems to work anywhere.
param~ can be additionally controlled by an audio buffer but, AFAIK, only the web target supports it.
We're having discussions around param~ internally as the range and clamping details are a little odd, so we might have some updates in a future release.
If you wanted to roll your own, it would more likely be a combination of inlet~ and param.
Thank you Alex, that clears it up.
So the approach might be to use inlet~, then use *~ to multiply the signal using the output of the param?
I will also experiment with sig~ and param, as the sample accurate objects (sig~, line~ etc) seem to be getting me the precision I need.
technically, param~ is effectively a [+~] of a [param] value and in [inlet~], but if your param -> sig~ and sample accurate objects are giving you the results that you like, sounds like you should just do that
Got it, that makes sense , thank you - I'll stick with the param/sig~ approach for now . Curious to see the next implementation of param~!