I could have sworn I made a post about this before already, but search doesn’t turn it up, so apologies if this is redundant.
fluid.bufscale~ should have a
clip attribute (and/or a separate
fluid.bufclip~, which would be a pain…) since you have to guess a useful
@inputlow value before starting otherwise you risk wasting resolution or getting loads of garbage data further down the line from loads of errors like these:
fluid.bufstats~: Negative weights clipped to 0
So granted, it’s being clipped at the
fluid.bufstats~ level, but this not only spams the window with yellow comments, but it can also heavily skew your data if you’re expecting one thing and get another (again, having to “guess” what a useful
@inputlow value would be).
With this coming down the pipeline (hopefully):
Being able to
dBtoa would help here as I could more easily plug the output of
fluid.bufscale~ and know what I’ll get, but for now I’m having to eyeball values or get spam.