@orange I think these warnings are mostly useful for debugging and spotting where a scriptnode graph is likely to crash, as it can happen sometimes with some nodes.
This connection should be fine altough it would be better to keep the ranges identical when possible. You could use a control.smoothed_parameter_unscaled in that case.
On Windows, if the monitor has a 4k (or more) resolution, and using a resolution factor higher than 100% for the Operating System , that happens. I think it is a Windows thing.
@DanH I got the pitch partly working but it's glitchy and another member of the forum has shared some of their work on the time stretch with me but it has some of their specific C++ stuff in it which I need to make more generic. I haven't had time yet to really dive into it.
I think I already shared my pitch shift node in another thread.
Its a bit much to take in debugging the first time.
I found an assertion failure for jlimit in MathsFunctions (lower value is bigger than the higher value).
But I still try to figure out where this jlimit belongs to.