Is the range warning indicator an issue for unscaled parameters?

[ustk]

When connected to an unscaled node the warning still shows up despite the range being the same.
Does it means troubles down the road?

[Dan Korneff]

@ustk I've ignored them... wondering the same

[ustk]

@Dan-Korneff lol

[HISEnberg]

@ustk I ignore them too and don't have any issues.

[Christoph Hart]

@HISEnberg yeah if they are connected to a unscaled parameter the warning is pointless, but if not it might have performance implications or subtle range mismatches.

I can look into removing the warning for unscaled parameters, but it's not super straightforward to do so.

[HISEnberg]

@Christoph-Hart yes you are right.

I don't think there is a justification for removing them on the unscaled parameters, you can figure out pretty quick if the parameter linking is broken using your ears in most cases, plus it's a good reminder to just try to make the ranges match (even if it doesn't always work).

[ustk]

@HISEnberg Well my fear wasn't if it work or not in the network and in Hise in general but I reckon a compilation issue with those warnings...
So if no issue with that, perhaps it would be easier for you @Christoph-Hart to just put a message in the range popup or anything telling the user not to worry about.
A warning is here to make you shaking and to remind you that the abyss is closer than you think...